Top-Down Approach to Drawing Data Flow Diagrams

The top-down approach for plotting data flow diagrams mainly includes "from general to specific" according to the level of detail shown (Kendall & Kendall, 2008, p. 220). System analysts begin to compile a list of business activities using information gathered from interviews, surveys, personal observations. Next, we use the list to define the four elements of the data flow graph as follows: § External entity - Sending and receiving data to / from the system § Data flow - Data movement § Process - Data change or conversion § Data storage - Virtual repository (Kendall & Kendall, 2008) that can add, confirm and retrieve data

3-6. Data flow diagrams are created in a hierarchy called top-down system development approach. In this approach, developers start with the broadest, least detailed level and deploy at each level of the previous level until the system is completely specified (to refine sophistication). The rationale behind this approach is to first consider the goals of the main system, then worry about the details after specifying the main system component. However, this process is iterative, revision is common and rarely seen as "final" until the minimum chart level is specified and approved.

My previous duties as business analysts, process engineers, and integrated analysts have created flow charts showing the flow of business processes from triggers on one system and the flow of data to other systems . Detection is performed on each system and what kind of data is needed. Today, we use various usability tools and custom software, so we ignore this process and realize the end-to-end panorama of the system. Without this critical work, and without our time and resources, assuming that someone or something is covered we will get things into trouble.

A data flow graph (DFD) is a graphical representation of a data "stream" through an information system. Unlike the system flow chart, it shows the flow of data through the process, not the computer's hardware. The data flow diagram was invented by the structural design developer Larry Constantine based on Martin and Estrin's "data flow graph" calculation model. The usual way is to first draw a system context diagram that shows the interaction between the system and external entities. DFD shows how to divide the system into smaller parts and is designed to emphasize the flow of data between those parts. Next, "disassemble" the context level data flow graph to display the details of the system being modeled.