Describing the system from the viewpoint of the data it processes

Presented to: Dr.Sherine Youssef Presented by: Noha Seddik Passant Wahdan

History & Definition • Data flow diagrams were proposed by Larry Constantine. based on Martin and Estrin's "data flow graph" model of computation. showed how the data moved from one process to another “what happened to it?”. the original developer of structured design. . • • A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system • • DFDs show the flow of data from external entities “where did it come from?”into the system.

Data stores . which take data as input. which can either be electronic data or physical items. and output it Arrows representing the data flows . do something to it. Processes .1 2 3 4 DFD COMPNENTS External entities . . which are sources or destinations of data.


2. 3.Each external entity must be involved with at least one data flow. 4.Each data store must be involved with at least one data flow.RULES 1. 5.Data cannot legally flow directly from a source to a destination or between a source/destination and a data store unless they pass through an .All processes should modify the incoming data. producing new forms of outgoing data.All processes must have at least one data flow in and one data flow out.

and on the level-0 flows inside and repeat the Level-n+1 expansion in n Take a level another DFD process and refine it . process Level-1 Take a processes. surrounding Context external Make the entitiesprocess Level-0 central BIG and draw stores.• • LEVEL DFD TYPES The table shows the three types of DFD CONTENT Context Shows one process with its inputs and System One process + Context outputs only.

 . data flows suggesting composites. with processes suggesting programs and procedures.   Implementation of a more efficient system through comparison with old system’s DFDs. and how the system will be implemented. and data stores suggesting data entities.ADVANATGES & DISADVANATGES No information about the timing of      processes. or information about whether processes will operate in sequence or in parallel (unlike flowchart).   Users are able to visualize how the system will operate. what the system will accomplish. and databases. files.   The elements of a data flow diagram lead directly into physical design.