A data-flow diagram is a way of representing a flow of data through a process or a system (usually an information system). The DFD also provides information about the outputs and inputs of each entity and the process itself. A data-flow diagram has no control flow — there are no decision rules and no loops. Specific operations based on the data can be represented by a flowchart.[1]
There are several notations for displaying data-flow diagrams. The notation presented above was described in 1979 by Tom DeMarco as part of structured analysis.
For each data flow, at least one of the endpoints (source and / or destination) must exist in a process. The refined representation of a process can be done in another data-flow diagram, which subdivides this process into sub-processes.
The data-flow diagram is a tool that is part of structured analysis and data modeling. When using UML, the activity diagram typically takes over the role of the data-flow diagram. A special form of data-flow plan is a site-oriented data-flow plan.
Data-flow diagrams can be regarded as inverted Petri nets, because places in such networks correspond to the semantics of data memories. Analogously, the semantics of transitions from Petri nets and data flows and functions from data-flow diagrams should be considered equivalent.
History
editThe DFD notation draws on graph theory, originally used in operational research to model workflow in organizations, and in computer science to model the flow of inputs and outputs across computations.[2][3] DFD originated from the structured analysis and design technique methodology in the middle of the 1970s.[3] It was first proposed by Larry Constantine,[4] and popularized by Edward Yourdon, Tom DeMarco,[5] Chris Gane and Trish Sarson,[6][7] who enriched the diagramming technique with different notations, data dictionary practices[5] and guidance for the hierarchical decomposition of processes.[6]
The primary aim of data-flow diagrams in the context of structured design was to build complex modular systems, rationalizing the interdependencies across different modules.[3] Data-flow diagrams (DFD) quickly became a popular way to visualize the major steps and data involved in software-system processes. DFDs were usually used to show data flow in a computer system, although they could in theory as well be applied to business process modeling.[8] DFDs were useful to document the major data flows or to explore a new high-level design in terms of data flow.[9]
DFD components
edit
DFD consists of processes, flows, warehouses, and terminators. There are several ways to view these DFD components.[10]
Process
The process (function, transformation) is part of a system that transforms inputs to outputs. The symbol of a process is a circle, an oval, a rectangle or a rectangle with rounded corners (according to the type of notation). The process is named in one word, a short sentence, or a phrase that is clearly to express its essence.[7]
Data flow
Data flow (flow, dataflow) shows the transfer of information (sometimes also material) from one part of the system to another. The symbol of the flow is the arrow. The flow should have a name that determines what information (or what material) is being moved. Exceptions are flows where it is clear what information is transferred through the entities that are linked to these flows. Material shifts are modeled in systems that are not merely informative. Flow should only transmit one type of information (material). The arrow shows the flow direction (it can also be bi-directional if the information to/from the entity is logically dependent—e.g. question and answer). Flows link processes, warehouses and terminators.[7]
Warehouse
The warehouse (datastore, data store, file, database) is used to store data for later use. The symbol of the store is two horizontal lines, the other way of view is shown in the DFD Notation. The name of the warehouse is a plural noun (e.g. orders)—it derives from the input and output streams of the warehouse. The warehouse does not have to be just a data file but can also be, for example, a folder with documents, a filing cabinet, or a set of optical discs. Therefore, viewing the warehouse in a DFD is independent of implementation. The flow from the warehouse usually represents reading of the data stored in the warehouse, and the flow to the warehouse usually expresses data entry or updating (sometimes also deleting data). The warehouse is represented by two parallel lines between which the memory name is located (it can be modeled as a UML buffer node).[7]
Terminator
The terminator is an external entity that communicates with the system and stands outside of the system. It can be, for example, various organizations (e.g. a bank), groups of people (e.g. customers), authorities (e.g. a tax office) or a department (e.g. a human-resources department) of the same organization, which does not belong to the model system. The terminator may be another system with which the modeled system communicates.[7]
Rules for creating DFD
editEntity names should be comprehensible without further comments. DFD is a system created by analysts based on interviews with system users. It is determined for system developers, on one hand, project contractor on the other, so the entity names should be adapted for model domain or amateur users or professionals. Entity names should be general (independent, e.g. specific individuals carrying out the activity), but should clearly specify the entity. Processes should be numbered for easier mapping and referral to specific processes. The numbering is random, however, it is necessary to maintain consistency across all DFD levels (see DFD Hierarchy). DFD should be clear, as the maximum number of processes in one DFD is recommended to be from 6 to 9, minimum is 3 processes in one DFD.[1][7] The exception is the so-called contextual diagram where the only process symbolizes the model system and all terminators with which the system communicates.
DFD consistency
editDFD must be consistent with other models of the system—entity relationship diagram, state-transition diagram, data dictionary, and process specification models. Each process must have its name, inputs and outputs. Each flow should have its name (exception see Flow). Each Data store must have input and output flow. Input and output flows do not have to be displayed in one DFD—but they must exist in another DFD describing the same system. An exception is warehouse standing outside the system (external storage) with which the system communicates.[7]
DFD hierarchy
editTo make the DFD more transparent (i.e. not too many processes), multi-level DFDs can be created. DFDs that are at a higher level are less detailed (aggregate more detailed DFD at lower levels). The contextual DFD is the highest in the hierarchy (see DFD Creation Rules). The so-called zero level is followed by DFD 0, starting with process numbering (e.g. process 1, process 2). In the next, the so-called first level—DFD 1—the numbering continues For example, process 1 is divided into the first three levels of the DFD, which are numbered 1.1, 1.2, and 1.3. Similarly, processes in the second level (DFD 2) are numbered 2.1.1, 2.1.2, 2.1.3, and 2.1.4. The number of levels depends on the size of the model system. DFD 0 processes may not have the same number of decomposition levels. DFD 0 contains the most important (aggregated) system functions. The lowest level should include processes that make it possible to create a process specification for roughly one A4 page. If the mini-specification should be longer, it is appropriate to create an additional level for the process where it will be decomposed into multiple processes. For a clear overview of the entire DFD hierarchy, a vertical (cross-sectional) diagram can be created. The warehouse is displayed at the highest level where it is first used and at every lower level as well.[7]
See also
edit- Activity diagram
- Business Process Model and Notation
- Control-flow diagram
- Data island
- Dataflow
- Data and information visualization
- Directed acyclic graph
- Drakon-chart
- Functional flow block diagram
- Function model
- IDEF0
- Pipeline
- Structured analysis and design technique
- Structure chart
- System context diagram
- Value-stream mapping
- Workflow
- List of graphical methods
References
edit- ^ a b Bruza, P. D.; van der Weide, Th. P. (1990-11-01). "Assessing the quality of hypertext views". ACM SIGIR Forum. 24 (3): 6–25. doi:10.1145/101306.101307. ISSN 0163-5840. S2CID 8507530.
- ^ Martin, David; Estrin, Gerald (1967-04-01). "Models of Computations and Systems—Evaluation of Vertex Probabilities in Graph Models of Computations". Journal of the ACM. 14 (2): 281–299. doi:10.1145/321386.321391. ISSN 0004-5411.
- ^ a b c Yourdon, Edward; Constantine, Larry L. (1975). Structured Design. New York: Yourdon Inc. pp. 54–55. OCLC 1036882595.
- ^ Bergland, G. D. (1978-06-19). "Structured Design Methodologies". 15th Design Automation Conference. Las Vegas, Nevada, USA: IEEE Press. pp. 475–493. doi:10.1109/DAC.1978.1585214.
- ^ a b DeMarco, Tom (1979). Structured analysis and system specification. Prentice-Hall software series. Englewood Cliffs, N.J: Prentice-Hall. ISBN 978-0-13-854380-8.
- ^ a b Gane, Chris; Sarson, Trish (1979). Structured systems analysis: tools and techniques. Prentice-Hall software series. Englewood Cliffs, N.J: Prentice-Hall. ISBN 978-0-13-854547-5.
- ^ a b c d e f g h Yourdon, Edward (1975). "Structured programming and structured design as art forms". Proceedings of the May 19-22, 1975, national computer conference and exposition on - AFIPS '75. p. 277. doi:10.1145/1499949.1499997. S2CID 36802486.
- ^ Tangkawarow, I R H T; Waworuntu, J (April 2016). "A Comparative of business process modelling techniques". IOP Conference Series: Materials Science and Engineering. 128 (1): 012010. Bibcode:2016MS&E..128a2010T. doi:10.1088/1757-899X/128/1/012010. ISSN 1757-8981.
- ^ Larman, Craig (2012). Applying UML and patterns : an introduction to object-oriented analysis and design and iterative development (3rd ed.). New Delhi: Pearson. ISBN 978-8177589795. OCLC 816555477.
- ^ Řepa, Václav (1999). Analýza a návrh informačních systémů (Vyd. 1 ed.). Praha: Ekopress. ISBN 978-8086119137. OCLC 43612982.
Bibliography
edit- Scott W. Ambler. The Object Primer 3rd Edition Agile Model Driven Development with UML 2
- Schmidt, G., Methode und Techniken der Organisation. 13. Aufl., Gießen 2003
- Stahlknecht, P., Hasenkamp, U.: Einführung in die Wirtschaftsinformatik. 12. Aufl., Berlin 2012
- Gane, Chris; Sarson, Trish. Structured Systems Analysis: Tools and Techniques. New York: Improved Systems Technologies, 1977. ISBN 978-0930196004. P. 373
- Demarco, Tom. Structured Analysis and System Specification. New York: Yourdon Press, 1979. ISBN 978-0138543808. P. 352.
- Yourdon, Edward. Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design. New York: Yourdon Press, 1979. ISBN 978-0138544713. P. 473.
- Page-Jones, Meilir. Practical Guide to Structured Systems Design. New York: Yourdon Press, 1988. ISBN 978-8120314825. P. 384.
- Yourdon, Edward. Modern Structured Analysis. New York: Yourdon Press, 1988. ISBN 978-0135986240. P. 688.
External links
edit
Media related to Data flow diagram at Wikimedia Commons
