Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 14

Data Flow Diagrams (DFD)

Data Flow Diagram


• A data flow diagram (DFD) maps out the flow of information for any
process or system. It uses defined symbols like rectangles, circles and
arrows, plus short text labels, to show data inputs, outputs, storage
points and the routes between each destination. Data flowcharts can
range from simple, even hand-drawn process overviews, to in-depth,
multi-level DFDs that dig progressively deeper into how the data is
handled. They can be used to analyze an existing system or model a
new one.
Symbols and Notations Used in DFDs

• Two common systems of symbols are named after their creators:


• Yourdon and Coad
• Gane and Sarson

Using any convention’s DFD rules or guidelines, the symbols depict the
four components of data flow diagrams.
• 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.
• 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.”
• 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.”
• 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.”
Symbols
DFD rules and tips
• Each process should have at least one input and an output.

• Each data store should have at least one data flow in and one data
flow out.

• Data stored in a system must go through a process.

• All processes in a DFD go to another process or a data store.


Levels in Data Flow Diagrams (DFD)
• In Software engineering DFD(data flow diagram) can be drawn to
represent the system of different levels of abstraction. Higher level
DFDs are partitioned into low levels-hacking more information and
functional elements. Levels in DFD are numbered 0, 1, 2 or beyond.
Here, we will see mainly 3 levels in data flow diagram, which are: 0-
level DFD, 1-level DFD, and 2-level DFD.
0-level DFD
• It is also known as context diagram. It's designed to be an abstraction
view, showing the system as a single process with its relationship to
external entities. It represent the entire system as single bubble with
input and output data indicated by incoming/outgoing arrows.
1-level DFD
In 1-level DFD, context diagram is decomposed into multiple
bubbles/processes.in this level we highlight the main functions of the
system and breakdown the high level process of 0-level DFD into sub
processes.
2-level DFD
• 2-level DFD goes one step deeper into parts of 1-level DFD. It can be
used to plan or record the specific/necessary detail about the
system’s functioning.
Examples of how DFDs can be used
• DFD in software engineering
• DFD in business analysis
• DFD in business process re-engineering
• DFD in system structures
• DFD in agile development

You might also like