31.07.

2024
DFD
What is Data Flow Diagram (DFD) ?
Data Flow Diagram (DFD) is a graphical representation of data flow in any
system. It is capable of illustrating incoming data flow, outgoing data flow and
store data. Data flow diagram describes anything about how data flows through
the system.
Types of Data Flow Diagram (DFD)

Logical Data Flow Diagram

Logical diagrams display the theoretical process of moving information through
a system, like where the data comes from, where it goes, how it changes, and
where it ends up.
Logical DFD is used in various organizations for the smooth running of system.
Like in a Banking software system, it is used to describe how data is moved from
one entity to another.
When to use Logical Data Flow Diagram
Logical Data Flow Diagram are mostly used during the requirement analysis
phase, user communication, and high-level system design
Why Logical DFDs
 1. Abstraction from Technical Details: Logical Data Flow Diagram (DFD)
provides a abstraction to complex model i.e. DFD hides unnecessary
implementation details and show only the flow of data and processes
within information system.
2. Clarity and Simplicity: Logical Data Flow Diagram provides clarity and
simplicity as it uses symbols and notation for data flow, data store,
processes and external entity that can be easy understand by
stakeholders.
3. User Communication: Logical Data Flow Diagram is very useful
communication tools between system analyst and end users.

EXAMPLE

Physical Data Flow Diagram (DFD)

Physical diagrams show you the practical process of moving information through
a system. It can show how your system’s specific software, hardware, files,
employees, and customers influence the flow of information.
When to use Physical Data Flow Diagram
 1. Detailed Design Phase: Physical DFDs are helpful during the detailed
design phase of a system. Logical DFD provide system processes and data
flow at higher level of abstraction while physical DFD provides a more
detailed view of data flow and processes within the information system.
2. Implementation Planning: Physical DFD helps developer during
Implementation planning as it provides a detailed view of how data flow
within the system’s physical components, such as hardware devices,
databases, and software modules. Physical DFD helps the developers in
identifying the correct technologies and resources required to implement
the system.
3. Integration with Existing Systems: Physical DFD are important for
understanding data flow when integrating a new system with existing
systems or external entities,
4. Documentation and Maintenance: Physical DFDs can be referred as
documentation for system architecture and data flow patterns, that helps
in system maintenance and troubleshooting.
Why Physical DFDs
Physical Data Flow Diagram provides Implementation Guidance
and also helps in performance optimization.
EXAMPLE:
Data flow diagram notations
The two main types of notations used for data flow diagrams are Yourdon-Coad
and Gane-Sarson, both named after their creators, all experts who helped
develop DFD methodology: Ed Yourdon, Peter Coad, Chris Gane and Trish
Sarson. There are some differences in style between the notation types. For
example, Yourdon and Coad notation uses circles to represent processes,

whereas Gane and Sarson notation use rectangles with rounded corners.
Another variation is the symbol used for data stores—Yourdon and Coad use
parallel lines while Gane and Sarson notation uses an open-ended rectangle.

Data flow diagram symbols

 1. External entities are represented by squares as the source or destination
of data.
2. Processes are represented by rectangles with rounded corners.
3. Data Flows are referred to by arrows to denote the physical or electronic
flow of data.
4. Data Stores are physical or electronic-like XML files denoted by open-
ended rectangles.

Levels in Data Flow Diagram (DFD)

DFDs can be divided into different levels, which provide varying degrees of detail
about the system. The following are the four levels of DFDs:
1. Level 0 DFD
2. Level 1 DFD
3. Level 2 DFD
4. Level 3 DFD
The choice of DFD level depends on the complexity of the system and the level
of detail required to understand the system. Higher levels of DFD provide a broad
overview of the system, while lower levels provide more detail about the
system’s processes, data flows, and data stores. A combination of different levels
of DFD can provide a complete understanding of the system.
Level 0 Data Flow Diagram (DFD)
Level 0 is the highest-level Data Flow Diagram (DFD), which provides an overview
of the entire system. It shows the major processes, data flows, and data stores
in the system, without providing any details about the internal workings of these
processes.
It is also known as a context diagram. It’s designed to be an abstraction view,
showing the system as a single process with its relationship to external entities.
It represents the entire system as a single bubble with input and output data
indicated by incoming/outgoing arrows.
1-Level Data Flow Diagram (DFD)
1-Level provides a more detailed view of the system by breaking down the major
processes identified in the level 0 Data Flow Diagram (DFD) into sub-processes.
Each sub-process is depicted as a separate process on the level 1 Data Flow
Diagram (DFD). The data flows and data stores associated with each sub-process
are also shown.
In 1-level Data Flow Diagram (DFD), the 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 Data Flow Diagram (DFD)
into subprocesses.

2-Level Data Flow Diagram (DFD)

2-Level provides an even more detailed view of the system by breaking down the
sub-processes identified in the level 1 Data Flow Diagram (DFD) into further sub-
processes. Each sub-process is depicted as a separate process on the level 2 DFD.
The data flows and data stores associated with each sub-process are also shown.
2-Level Data Flow Diagram (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.

3-Level Data Flow Diagram (DFD)

3-Level is the most detailed level of Data Flow Diagram (DFDs), which provides a
detailed view of the processes, data flows, and data stores in the system. This
level is typically used for complex systems, where a high level of detail is required
to understand the system. Each process on the level 3 DFD is depicted with a
detailed description of its input, processing, and output. The data flows and data
stores associated with each process are also shown.

How to create a data flow diagram

1. Identify inputs and outputs
2. Create a high-level overview (Level 0)
3. Break down the main functions (Level 1)
4. Add detail as needed (Level 2 and beyond)

Advantages of using Data Flow Diagrams (DFD)

Following are the Advantage of Data Flow Diagram (DFD) :
1. Easy to understand: DFDs are graphical representations that are easy to
understand and communicate, making them useful for non-technical
stakeholders and team members.
2. Improves system analysis: DFDs are useful for analysing a system’s
processes and data flow, which can help identify inefficiencies,
redundancies, and other problems that may exist in the system.
3. Supports system design: DFDs can be used to design a system’s
architecture and structure, which can help ensure that the system is
designed to meet the requirements of the stakeholders.
4. Enables testing and verification: DFDs can be used to identify the inputs
and outputs of a system, which can help in the testing and verification of
the system’s functionality.
5. Facilitates documentation: DFDs provide a visual representation of a
system, making it easier to document and maintain the system over time.

Disadvantages of using Data Flow Diagram (DFD)

Following are the Disadvantage of Data Flow Diagram (DFD) :
1. Can be time-consuming: Creating DFDs can be a time-consuming process,
especially for complex systems.
2. Limited focus: DFDs focus primarily on the flow of data in a system, and
may not capture other important aspects of the system, such as user
interface design, system security, or system performance.
3. Can be difficult to keep up-to-date: DFDs may become out-of-date over
time as the system evolves and changes.
 4. Requires technical expertise: While DFDs are easy to understand, creating
them requires a certain level of technical expertise and familiarity with the
system being analyzed.

DATA FLOW DIAGRAM DRAW WEBSITES:

https://www.edrawmax.com/
https://www.lucidchart.com/

Example:
Student Management System
BANK ACCOUNT MANAGEMENT SYSTEM