DFD

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system.

DFDs can also be used for the visualization of data processing (structured design).

It views a system as a function that transform the input into desired output .

DFD Vs Flowchart

Flowcharts are used to break down a complex process into simple steps (denoted by different boxes)
that are connected by arrows

It starts at the beginning of the process and follows each step through the process until the end

Flowcharts can also show how to deal with problems that may occur during the process.
A DFD shows how data flows through a system which is processed as well

The flow of the data from an external or internal source as well as where the data will end up is shown
in a DFD

DFD Diagrammatic Notations

There are essentially two different types of notations for data flow diagrams defining different visual
representations for processes, data stores, data flow and external entities named after their creators:

Yourdon and Coad

Yourdon and DeMarco

Gane and Sarson

Yourdon and Coad type data flow diagrams are usually used for system analysis and design, while Gane
and Sarson type DFDs are more common for visualizing information systems

One main difference in their symbols is that Yourdon-Coad and Yourdon-DeMarco use circles for
processes, while Gane and Sarson use rectangles with rounded corners, sometimes called lozenges
External entity: an outside system that sends or receives data, communicating with the system being
diagrammed. They are the sources and destinations of information entering or leaving the system. They
might be an outside organization or person, a computer system or a business system. They are also
known as terminators, sources and sinks or actors. They are typically drawn on the edges of the
diagram. External entities are objects outside the system, with which the system communicates.
External entities are sources and destinations of the system's inputs and outputs. 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: any process that changes the data, producing an output It might perform computations, or sort
data based on logic, or direct the data flow based on business rules A short label is used to describe the
process, such as Submit payment. A process transforms incoming data flow into outgoing data flow
A process is a business activity or function where the manipulation and transformation of data takes
place A process can be decomposed to finer level of details, for representing how data is being
processed within the process.

Data store: files or repositories that hold information for later use, such as a database table or a
membership form. Each data store receives a simple label, such as Orders. 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 table, etc Data stores are repositories of data in the system. They
are sometimes also referred to as files.
Data flow: the route that data takes between the external entities, processes and data stores It portrays
the interface between the other components and is shown with arrows, typically labeled with a short
data name, like Billing details. Dataflows are pipelines through which packets of information flow
Label the arrows with the name of the data that moves through it.

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

Creating Data Flow Diagrams

1. Create a list of activities

2. Construct Context Level DFD

(identifies external entities and processes)

3. Construct Level 0 DFD

(identifies manageable sub process )

4. Construct Level 1- n DFD

(identifies actual data flows and data stores )

5. Check against rules of DFD

Data Flow Diagram Levels

Context Diagram. A context diagram is a top level (also known as "Level 0") data flow diagram. It only
contains one process node ("Process 0") that generalizes the function of the entire system in
relationship to external entities.
DFD Layers. Draw data flow diagrams can be made in several nested layers. A single process node on a
high level diagram can be expanded to show a more detailed data flow diagram. Draw the context
diagram first, followed by various layers of data flow diagrams.

DFD Levels. The first level DFD shows the main processes within the system. Each of these processes can
be broken into further processes until you reach pseudo code.

Perfect Pizza wants to install a system to record orders for pizza and chicken wings. When regular
customers call Perfect Pizza on the phone, their phone number goes automatically into the Pizza
system. The phone number invokes the name, address, and last order date comes automatically up
on the screen. Once the order is taken, the total, including tax and delivery, is calculated. Then the
order is given to the cook. A receipt is printed. Occasionally, special offer (coupons) is printed so the
customer can get a discount. Drivers who make deliveries give customers a copy of the receipt and
coupon (if any). Weekly totals are kept for comparison with last years performance.

Draw a context diagram for Perfect Pizza

Explode the context-level diagram showing all the major processes.