What is DFD draw 0 and 1st DFD?

A Data Flow Diagram (DFD) is a traditional visual representation of the information flows within a system. A neat and clear DFD can depict the right amount of the system requirement graphically. It can be manual, automated, or a combination of both.

It shows how data enters and leaves the system, what changes the information, and where data is stored.

The objective of a DFD is to show the scope and boundaries of a system as a whole. It may be used as a communication tool between a system analyst and any person who plays a part in the order that acts as a starting point for redesigning a system. The DFD is also called as a data flow graph or bubble chart.

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements in the DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that represents the order of events; arrows in DFD represents flowing data. A DFD does not involve any order of events.
3. Suppress logical decisions. If we ever have the urge to draw a diamond-shaped box in a DFD, suppress that urge! A diamond-shaped box is used in flow charts to represents decision points with multiple exists paths of which the only one is taken. This implies an ordering of events, which makes no sense in a DFD.
4. Do not become bogged down with details. Defer error conditions and error handling until the end of the analysis.

Standard symbols for DFDs are derived from the electric circuit diagram analysis and are shown in fig:

Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data store.

Data Store: A set of parallel lines shows a place for the collection of data items. A data store indicates that the data is stored which can be used at a later stage or by the other processes in a different order. The data store can have an element or group of elements.

Source or Sink: Source or Sink is an external entity and acts as a source of system inputs or sink of system outputs.

Levels in Data Flow Diagrams (DFD)

The DFD may be used to perform a system or software at any level of abstraction. Infact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Levels in DFD are numbered 0, 1, 2 or beyond. Here, we will see primarily three levels in the data flow diagram, which are: 0-level DFD, 1-level DFD, and 2-level DFD.

0-level DFDM

It is also known as fundamental system model, or context diagram represents the entire software requirement as a single bubble with input and output data denoted by incoming and outgoing arrows. Then the system is decomposed and described as a DFD with multiple bubbles. Parts of the system represented by each of these bubbles are then decomposed and documented as more and more detailed DFDs. This process may be repeated at as many levels as necessary until the program at hand is well understood. It is essential to preserve the number of inputs and outputs between levels, this concept is called leveling by DeMacro. Thus, if bubble "A" has two inputs x1 and x2 and one output y, then the expanded DFD, that represents "A" should have exactly two external inputs and one external output as shown in fig:

The Level-0 DFD, also called context diagram of the result management system is shown in fig. As the bubbles are decomposed into less and less abstract bubbles, the corresponding data flow may also be needed to be decomposed.

1-level DFD

In 1-level DFD, a context diagram is decomposed into multiple bubbles/processes. In this level, we highlight the main objectives of the system and breakdown the high-level process of 0-level DFD into subprocesses.

2-Level DFD

2-level DFD goes one process deeper into parts of 1-level DFD. It can be used to project or record the specific/necessary detail about the system's functioning.

A picture is worth a thousand words. A Data Flow Diagram (DFD) is a traditional way to visualize the information flows within a system. A neat and clear DFD can depict a good amount of the system requirements graphically. It can be manual, automated, or a combination of both.

It shows how information enters and leaves the system, what changes the information and where information is stored. The purpose of a DFD is to show the scope and boundaries of a system as a whole. It may be used as a communications tool between a systems analyst and any person who plays a part in the system that acts as the starting point for redesigning a system.

It is usually beginning with a context diagram as level 0 of the DFD diagram, a simple representation of the whole system. To elaborate further from that, we drill down to a level 1 diagram with lower-level functions decomposed from the major functions of the system. This could continue to evolve to become a level 2 diagram when further analysis is required. Progression to levels 3, 4 and so on is possible but anything beyond level 3 is not very common. Please bear in mind that the level of detail for decomposing a particular function depending on the complexity that function.

DFD Diagram Notations

Now we'd like to briefly introduce to you a few diagram notations which you'll see in the tutorial below.

External Entity

An external entity can represent a human, system or subsystem. It is where certain data comes from or goes to. It is external to the system we study, in terms of the business process. For this reason, people used to draw external entities on the edge of a diagram.

Process

A process is a business activity or function where the manipulation and transformation of data take place. A process can be decomposed to a finer level of details, for representing how data is being processed within the process.

Data Store

A data store represents the storage of persistent data required and/or produced by the process. Here are some examples of data stores: membership forms, database tables, etc.

Data Flow

A data flow represents the flow of information, with its direction represented by an arrowhead that shows at the end(s) of flow connector.

What will we do in this tutorial?

In this tutorial, we will show you how to draw a context diagram, along with a level 1 diagram.

Note: The software we are using here is Visual Paradigm. You are welcome to download a free 30-day evaluation copy of Visual Paradigm to walk through the example below. No registration, email address or obligation is required.

How to Draw Context Level DFD?

1. To create new DFD, select Diagram > New from the toolbar.
2. In the New Diagram window, select Data Flow Diagram and click Next.
3. Enter Context as diagram name and click OK to confirm.
4. We'll now draw the first process. From the Diagram Toolbar, drag Process onto the diagram. Name the new process System.
   
   
5. Next, let's create an external entity. Place your mouse pointer over System. Press and drag out the Resource Catalog button at the top right.
   
   
6. Release the mouse button and select Bidirectional Data Flow -> External Entity from Resource Catalog.
   
   
7. Name the new external entity Customer.
   
   
8. Now we'll model the database accessed by the system. Use the Resource Catalog to create a Data Store from System, with bidirectional data flow in between.
   
   
9. Name the new data store Inventory.
   
   
10. Create two more data stores, Customer and Transaction, as shown below. We have just completed the Context diagram.
    
    

How to Draw Level 1 DFD?

1. Instead of creating another diagram from scratch, we will decompose the System process to form a new DFD. Right-click on System and select Decompose from the popup menu.
   
   
2. The data stores and/or external entities connected to the selected process (System) would be referred to in the level 1 DFD. So when you are prompted to add them to the new diagram, click Yes to confirm.
   Note: The new DFD should look very similar to the Context diagram initially. Every element should remain unchanged, except that the System process (from which this new DFD decomposes) is now gone and replaced by a blank space (to be elaborated).
3. Rename the new DFD. Right-click on its background and select Rename.... In the diagram's name box, enter Level 1 DFD and press ENTER.
4. Create three processes (Process Order, Ship Good, Issue Receipt) in the center as shown below. That is the old spot for the System process and we place them there to elaborate System.
   
   

Wiring with connection lines for data flows

The remaining steps in this section are about connecting the model elements in the diagram. For example, Customer provides order information when placing an order for processing.

1. Place your mouse pointer over Customer. Drag out the Resource Catalog icon and release your mouse button on Process Order.
   
   
2. Select Data Flow from Resource Catalog.
   
   
3. Enter order information has the caption of flow.
   
   
4. Meanwhile, the Process Order process also receives customer information from the database to process the order.
   Use the Resource Catalog to create a data flow from Customer to Process Order.
   
   
   
   Optional: You can label the data flow "customer information" if you like. But since this data flow is quite self-explanatory visually, we are going to omit it here.
5. By combining the order information from Customer (external entity) and the customer information from Customer (data store), Process Order (process) then creates a transaction record in the database. Create a data flow from Process Order to Transaction.
   
   
   
   Drawing Tips:
   To rearrange a connection line, place your mouse pointer over where you want to add a pivot point to it. You'll then see a bubble at your mouse pointer. Press and drag it to the position desired.
   
   
   
   Up to this point, your diagram should look something like this.
   
   
6. Once a transaction is stored, the shipping process follows. Therefore, create a data flow from Process Order (process) to Ship Good (process).
   
   
7. Ship Good needs to read the transaction information (i.e. The order number to pack the right product for delivery. Create a data flow from Transaction (data store) to Ship Good (process).
   
   
   
   Note: If there is a lack of space, feel free to move the shapes around to make room.
8. Ship Good also needs to read the customer information for his/her shipping address. Create a data flow from Customer (data store) to Ship Good (process).
   
   
9. Ship Good then updates the Inventory database to reflect the goods shipped. Create a data flow from Ship Good (process) to Inventory (data store). Name it updated product record.
   
   
10. Once the order arrives in the customer's hands, the Issue Receipt process begins. In it, a receipt is prepared based on the transaction record stored in the database. So let's create a data flow from Transaction (data store) to Issue Receipt (process).
    
    
11. Then a receipt is issued to the customer. Let's create a data flow from Issue Receipt (process) to Customer (external entity). Name the data flow receipt.
    
    
    
    You have just finished drawing the level 1 diagram which should look something like this.
    
    

How to Improve a DFD's Readability?

The completed diagram above looks a bit rigid and busy. In this section, we are going to make some changes to the connectors to increase readability.

1. Right-click on the diagram (Level 1 DFD) and select Connectors > Curve. Connectors in the diagram are now in curve lines.
   
   
2. Move the shapes around so that the diagram looks less crowded.
   
   

More DFD Examples

The list below directs you to various Data Flow Diagram examples that cover different businesses and problem domains. Some of them consist of the use of multiple context levels.

What is a 0 DFD diagram?

What is first level DFD?

What are the two types of DFD?

What is a DFD answer?