Data Flow Diagram 3
Data Flow Diagram 3
The Data Flow Diagram (DFD) is a graphical representation of the flow of data through an
information system. It enables you to represent the processes in your information system from
the viewpoint of data. The DFD lets you visualize how the system operates, what the system
accomplishes and how it will be implemented, when it is refined with further specification.
Data flow diagrams are used by systems analysts to design information-processing systems but
also as a way to model whole organizations. You build a DFD at the very beginning of your
business process modeling in order to model the functions your system has to carry out and the
interaction between those functions together with focusing on data exchanges between processes.
You can associate data with conceptual, logical, and physical data models and object-oriented
models.
There are two types of DFDs, both of which support a top-down approach to systems analysis,
whereby analysts begin by developing a general understanding of the system and gradually break
components out into greater detail:
Logical data flow diagrams - are implementation-independent and describe the system,
rather than how activities are accomplished.
Physical data flow diagrams - are implementation-dependent and describe the actual
entities (devices, department, people, etc.) involved in the current system.
DFDs can also be grouped together to represent a sub-system of the system being analyzed.
1
PowerDesigner support for DFD includes:
Support for the Gane & Sarson and Yourdon notations, which you choose between by
selecting Tools > Model Options.
Automatic processes and data stores numbering (see Process and Data Store Numbering).
Data Flow Diagram specific validation rules (F4) - PowerDesigner may perform
automatic corrections to your model or output errors and warnings that you will have to
correct manually.
2
Concept Tool Gane & Sarson Yourdon Description
This chapter outlines the specifics of PowerDesigner's support for data flow diagrams, and
should be read in conjunction with Business Process Diagrams.