REPORT ON DFD (DATA FLOW DIAGRAM)

SUBMITTED BY:
PRIYANKA MANNA
ROLL NO : 12000121056
SEM : 5TH SEM
PAPER NAME : SOFTWARE ENGINEERING
PAPER CODE : ESC 501

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

(AFFLITIATED TO MAULANA ABUL KALAM AZAD UNIVERSITY OF TECHNOLOGY)

DR.B.C ROY ENGINEERING COLLEGE,

DURGAPUR - 713206
 AGENDA

INTRODUCTION
COMPONENTS OF DFD
RULES OF DFD
LEVELS OF DFD
ADVANTAGES
DISADVANTAGES
CONCLUSION
INTRODUCTION:
A Data Flow Diagram (DFD) is a tradi onal visual representa on of the
informa on 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 combina on of both.
It shows how data enters and leaves the system, what changes the
informa on, and where data is stored.
The objec ve of a DFD is to show the scope and boundaries of a system
as a whole. It may be used as a communica on tool between a system
analyst and any person who plays a part in the order that acts as a
star ng point for redesigning a system. The DFD is also called as a data
flow graph or bubble chart.
Data Flow Diagram can be represented in several ways. The DFD
belongs to structured-analysis modeling tools. Data Flow diagrams are
very popular because they help us to visualize the major steps and
data involved in software-system processes.
COMPONENTS OF DFD:
The data flow diagram has 4 components
PROCESS:
Input to output transformation in a system takes place
because of process function. The symbols of a process are
rectangular with rounded corners, oval, rectangle or a circle.
DATA FLOW:
Data flow describes the information transferring between
different parts of the systems. The arrow symbol is the symbol
of data flow. A relatable name should be given to the flow to
determine the information which is being moved. Data flow
also represents material along with information that is being
moved. The direction of flow is represented by the arrow
which can also be bi-directional.
WAREHOUSE:
The data is stored in the warehouse for later use. When the
data flow from the warehouse it is considered as data reading
and when data flows to the warehouse it is called data entry
or data updating.
TERMINATOR:
The Terminator is an external entity that stands outside of the
system and communicates with the system. For example,
organizations like banks, which is not a part of the model
system and is an external entity.
RULES OF DFD:
 The name of the entity should be easy and understandable
without any extra assistance(like comments).
 The processes should be numbered or put in ordered list to be
referred easily.
 The DFD should maintain consistency across all the DFD levels.
 A single DFD can have a maximum of nine processes and a
minimum of three processes.

SYMBOLS OF DFD:
LEVELS OF DFD:
The DFD may be used to perform a system or so ware at any level of
abstrac on. In fact, DFDs may be par oned into levels that represent
increasing informa on flow and func onal 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 DFD:
 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.
 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
mul ple bubbles/processes.
 In this level, we highlight the main objec ves 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 func oning.
 User account maintainance 

 Student information management 

  Marks information management 

 Subject information management 

ADVANTAGES OF DFD:
It helps us to understand the func oning and the limits of a
system.
It is a graphical representa on which is very easy to understand
as it helps visualize contents.
Data Flow Diagram represent detailed and well explained diagram
of system components.
It is used as the part of system documenta on file.
Data Flow Diagrams can be understood by both technical or
nontechnical person because they are very easy to understand.
DISADVANTAGES OF DFD:
At mes DFD can confuse the programmers regarding the system.
Data Flow Diagram takes long me to be generated, and many
mes due to this reasons analysts are denied permission to work
on it.
CONCLUSION:
Data flow diagrams are useful in showing various business processes of
the system being developed, external en es sending and receiving
data, data flow depic ng the flow of data and data stores. DFD is a
crucial part of the requirements gathering and analysis stage of the
so ware development lifecycle that is helpful to numerous people such
as analysts, customers, and the development team.