Lab Manual 05 Software Requirements Engineering Drawing Data Flow Diagrams
Lab Manual 05 Software Requirements Engineering Drawing Data Flow Diagrams
Lab Manual 05 Software Requirements Engineering Drawing Data Flow Diagrams
There are essentially two different types of notations for data flow diagrams that defines different
visual representations for processes, data stores, data flow and external entities.
1. processes,
2. data stores
3. external entities
4. data flows
The picture below shows the standard shapes for both methodologies.
3- How to create a data flow diagram
Nearly every process or system begins with input from an external entity and ends with the output of data
to another entity or database. Identifying such inputs and outputs gives a macro view of your system—it
shows the broadest tasks the system should achieve. The rest of your DFD will be built on these elements,
so it is crucial to know them early on.
Once you’ve identified the major inputs and outputs, building a context diagram is simple. Draw a single
process node and connect it to related external entities. This node represents the most general process
information undergoes to go from input to output.
c. Expand the context diagram into a level 1 DFD
The single process node of your context diagram doesn’t provide much information—you need to break it
down into subprocesses. In your level 1 data flow diagram, you should include several process nodes,
major databases, and all external entities. Walk through the flow of information: where does the
information start and what needs to happen to it before each data store?
To enhance the detail of your data flow diagram, follow the same process as in step 3. The processes in
your level 1 DFD can be broken down into more specific subprocesses. Once again, ensure you add any
necessary data stores and flows.to progress beyond a level 2 data flow diagram, simply repeat this
process. Stop once you’ve reached a satisfactory level of detail.
When your diagram is completely drawn, walk through it. Pay close attention to the flow of information:
does it make sense? Are all necessary data stores included? By looking at your final diagram, other
parties should be able to understand the way your system functions. Before presenting your final diagram,
check with co-workers to ensure your diagram is comprehensible.
Example 1: Draw levels of data flow diagram for Hotel Reservation System.
Data flow diagrams are also categorized by level. Starting with the most basic, level 0, DFDs get
increasingly complex as the level increases. As you build your own data flow diagram, you will need to
decide which level your diagram will be.
Level 0 DFDs, also known as context diagrams, are the most basic data flow diagrams. They provide a
broad view that is easily digestible but offers little detail. Level 0 data flow diagrams show a single
process node and its connections to external entities.
Data Flow Diagram Level 0
Level 1 DFDs are still a general overview, but they go into more detail than a context diagram. In a level
1 data flow diagram, the single process node from the context diagram is broken down into subprocesses.
As these processes are added, the diagram will need additional data flows and data stores to link them
together.
Data Flow Diagram Level 1
Level 2+ DFDs simply break processes down into more detailed sub processes. In theory, DFDs could go
beyond level 3, but they rarely do. Level 3 data flow diagrams are detailed enough that it doesn’t usually
make sense to break them down further.
Data Flow Diagram Level 2
Lab Task: Draw levels of Data flow diagram for hospital management System.