DFD Process Examples Learning Objective Learn process of

DFD Process & Examples

Learning Objective: Learn process of a DFD Know the components of a DFD Understand Create the rules and conventions of creating DFD’s 3 DFD’s Success Criteria: Notes 3 about DFD’s in books DFD’s created in books

Purpose of a DFD A diagram is a much easier way to view the processes that take place in an information system than by reading a written description. A data flow diagram (DFD) is a process-modelling tool that depicts the flow of data through a system. It depicts all the input, the processing and the output and storage of data.

Components of a DFD Data Source or External entity – a source or destination of data flow that is outside the area of study. Data Store – repository of data; ‘D’ indicates a permanent computer file; ‘M’ indicates a manual file, ‘T’ indicates a transient store, deleted after processing. Process – transforms incoming data flow into outgoing data flow. Data flow – a connector shows relationships between the representative shapes. Entity M Datastore Level Process

The Steps in Drawing a DFDs are drawn in a number of steps (at least two), each step is referred to as a level. The steps involve top-down design and functional decomposition. That is we start at the top with an overall picture and then add detail as we work down. Example: A teacher gives his IT class a test on databases. The result for each student is out of a possible 40, which is first calculated as a percentage, but is then converted to an A to E grade. This grade is recorded in the teacher’s mark book and the graded paper finally returned to the student.

The Steps in Drawing a DFD The first level is the context level. The context level only contains a single process (a consolidation of all processes) along with all the external entities. This assist the database designer ‘discover’ the data that will be passing through the system with no detail given to all the processes. Context Level: Unmarked test paper 0. Graded test Process test paper Student

The Steps in Drawing a DFD Level 0 shows all general processes, external entities and data storage. For all of our databases, this is a sufficient level of detail. 1. 0 Unmarked test paper Student Graded test paper Process test paper Marked test paper 2. 0 Calculate grade Calculated grade D Teacher’s markbook

DFD Rules A data flow line must have a source A data flow line must have a destination Data flow lines must not cross. It may be necessary to draw some entities or data stores more than once. The name of the context level process identifies the main purpose of the information system. A data store must have at least one incoming data flow. Data cannot flow directly from an entity to another entity or a data store without a process in between. Data cannot flow directly from a data store to another data store or entity without a process in between. A process cannot have outputs that are greater than the sum of its inputs. That is, its inputs must be able to produce the outputs shown. A process must have an output

Limitations of a DFD Paraphrase the below notes into your exercise books. The data flow diagram is one of the best techniques available for developing a comprehensive collection of data items in a problem. Eventually the diagram will become substantial system documentation. A DFD however does not provide specification for process sequence or process control. The diagram gives no indication in what order the processes are to take place, nor does it give information as to how or why decisions might be made. Both have no place or meaning in a DFD. There are other modelling tools that cater for these requirements. A DFD shows what an information system does, but not the how, who, when or why. Processes are not described in detail on a DFD. A database designer would need to provide the details in a separate document called a process specification.

Lemonade Stand Example DFD (I do) Creating a context and level 0 DFD for a lemonade stand

Bus Garage Repairs DFD (We do) Buses come to a garage for repairs. A mechanic and helper perform the repair, record the reason for the repair and record the total cost of all parts used on a Shop Repair Order. Information on labor, parts and repair outcome is used for billing by the Accounting Department, parts monitoring by the inventory management computer system and a performance review by the supervisor.

Restaurant Order Processing System DFD (You do) At a restaurant, a customer orders what they want from the menu. The order is given to the kitchen where it is prepared. At the end of the evening, the bill is calculated and given to the customer. All bills are kept in duplicate in the order book. Draw a simple DFD (Level 0) for this flow of information.

Check what you have learnt 1. Most often, an information system is designed to take the place of an existing system. Why would it be useful to make a DFD of the old system first? 2. Two errors that are sometimes made with data flow lines are called ‘miracles’ and ‘black holes’. What do you suppose these errors are?

Check what you have learnt 3. The following is a DFD (level 0) for making a loan from a school library Student data Student Resource ID Card 1. 0 Make a loan Barcode Resource data D Student records D Resource records New loan data Current loan data D Loan records a) Add to the diagram the process ‘Make a return’, including appropriate data flows. b) Take the ‘Make a loan’ process to the next level of decomposition using the processes that occur in your library system.

Learning Objective: Learn process of a DFD Know the components of a DFD Understand Create the rules and conventions of creating DFD’s 3 DFD’s Success Criteria: Notes 3 about DFD’s in books DFD’s created in books

Lemonade Stand – DFD (Context Level) 0. 0 Order and money Customer Product and change (if required) Lemonade prepared

Lemonade Stand – DFD (Level 0) 1. 0 Order + Money Take order Order + Money Customer Change Purchase 2. 0 Calculate change Order 3. 0 Prepare order Money Change D Till

Bus Garage Repairs – DFD (Context Level) Bus given to Mechanic Bus returned/repaired 0. 0 Bus prepared

Bus Garage Repairs – DFD (Level 0) Bus delivered Bus goes to garage Mechanic identifies issue Parts and Time used Accounting Dept Bus Parts Time used Bus/Invoice provided 1. 0 Bus processed 2. 0 Bus repaired 3. 0 Invoice processed Invoice details D MYOB