WHAT IS THE DIFFERENCE BETWEEN DATA FLOW DIAGRAM
AND FLOW CHART
DEFINITIONS
DATA FLOW DIAGRAM
 A data flow diagram (DFD) is graphic
representation of the "flow" of data
through business functions or processes.
More generally, a data flow diagram is
used for the visualization of data
processes.
 Graphical representation of a system’s
data and how the processes transform
the data is known as Data Flow Diagram.
MAIN DIFFERENCES
 Data flow diagrams are used to describe
data flow within a system. They can
depict transformations on data as well as
storage locations. They trace the route
that data travels in a system, from start to
finish.
 Data flow diagrams are not program
flowcharts and do not include control
elements.
 A DFD details the flow of data through a
system. Data flow diagrams represent
the flow of data.
 In a data flow diagram, identifying the
procedural information is not necessary.
 In a DFD, the arrows are actually data
transfer between the elements, which are
themselves parts of a system.
FLOW CHART
 A flowchart is a type of diagram that
represents an algorithm or process,
showing the steps as boxes of various
kinds, and their order by connecting
these with arrows.
 The flowchart is a means of visually
presenting the flow of data through
an information processing systems, the
operations performed within the system
and the sequence in which they are
performed. 
 Flowcharts are used to describe the
detailed logic of a business process or
business rule.
 The program flowchart describes boxes
that describe computations, decisions,
interactions & loops.
 A flow chart details the processes to
follow.
 A flow chart shows the flow of control.
 In a flow chart, a reader can determine
what operations will be performed, in
what order, and under what
circumstances. 
 In a flow chart, the arrows represent
transfer of control (not data) between
elements and the elements are
instructions or decision
 Data flow diagram shows the flow of data
between the different entities and
datastores in a system.
 Data flow diagram provides a very high
level view of the system.
 At high level, DFDs are analysis.
 A DFD shows how the data moves
through a system.
 A data flow diagram is concerned with
the logical aspects of an activity
 Data flow diagram is functional
relationship which includes input values
and output values and internal data
stored.
 Data flow diagrams are welcomed tools
used in structured analysis and design
methods, showing the flow of information
through a system.
 The data flow diagram results are a
series of diagrams representing the
system activity in a clear and concise
manner.
 Data Flow Diagram commonly used by
business, industries or by cellular
companies to show the relationships
among the business processes within an
organization to external systems,
external organizations, customers and
other business processes.
SYMBOL DIFFERENCES
When using a data flow diagram to illustrate
the processes of a system, it is necessary to
use five symbols. They are:
PROCESS:
Represents an activity that processes /
transforms data
ENTITY:
Represents a source or destination of a
data flow outside the area of study.
 A flow chart shows the steps involved to
carried out a task
 A flow chart is a lower level view
(basically showing the algorithm).
 At the higher level, a flowchart is a
design level tool.
 A flowchart is closer to the operations
that system does.
 A flow chart is concerned with the
physical aspects of a task and as such is
used to represent something as it
is currently. This is useful in developing
understanding about a
situation/communication/training etc.
 Flow chart is process relationship which
includes input and output values.
 Flow charts are easy-to-understand
diagrams, which visually illustrate how
each process works by being broken
down into steps.
 A flowchart is a schematic representation
of a process. They are commonly used in
business/economic presentations to help
the audience visualize the content better,
or to find flaws in the process.
Using a flow chart typically requires the use of
three types of symbols: They
YES are:
NO
DECISION:
Use to represent a decision point in the
process.
PROCESS:
Use to represent an event which is controlled
within the process.
FILE/DATA STORAGE: START/END:

A data store is a storage bin for information Represent the start and the end of a process.
within the system.

DATA FLOW:

It shows the data flow direction, typically from its

source to its destination.

PHYSICAL FLOW:

It shows the flow of any physical material from

its source to its destination.
LEVEL DIFFERENCE
DATA FLOW DIAGRAM
Level 0: On Level 0, a DFD shows all the data
flows from the system to the external entities,
with the whole system being represented as
one large process
Level 1: A Level 1 DFD normally shows very
few (8 - 10) processes, and is intended to
explain the basic functioning of the system.
Higher Levels: Higher levels break down
single processes to show internal data flows.
Higher levels of the diagram break up any
single process into subprocesses, and show
that process's interaction with the system as
well as the internal composition of the process.
Breaking down is done until no further break-
down is possible. DIFFERENCE IN DIAGRAM
DATA FLOW DIAGRAM
 Each process should have both input and
output
 Each data store probably has both input
and output
 Data flows cannot flow between data
stores
 Data flows cannot flow between entities
and data stores
FLOW CHART
Macro Level: Generally, a macro-level
flowchart has fewer than six steps.
Mini Level: The term (mini or midi) is used for
a flowchart that falls between the big picture of
the macro level and the fine detail of the micro
level. Typically, it focuses on only one part of
the macro-level flowchart.
Micro level: The micro-level, or ground level,
view provides a very detailed picture of a
specific portion of the process by documenting
every action and decision. It is commonly used
to chart how a particular task is performed.
FLOW CHART DIAGRAM
 In drawing a proper flowchart, all
necessary requirements should be listed
out in logical order.
 The flowchart should be clear, neat and
easy to follow. There should not be any
room for ambiguity in understanding the
flowchart.
 The usual direction of flow of Procedure
or is from left to right or top to bottom.
  Diagrams must be balanced across
levels
 A data flow cannot be output and input of
the same process.
 Flows connected with a process with
opposite directions should not have the
same name
 Data flows should not cross one another.
 Each diagram has a name (title)
 Each object has name unique names for:
processes, terminators, data stores.
 Name of each object should precisely
reflect its features.
BUILDING DIFFERENCES
DFD
When building a data flow diagram, the
following items should be considered:
Allocating the entities:
What are the process entities, it could be
person place, department, organization or thing.
Entities are the means of data entering in the
main process. They are the sender or recipient
of data.
 
Main process:
Represents an activity that processes/transform
data. The process plays a significant role in the
business process. Labeling processes is used
to develop levels of DFDs that describe
increasingly detailed levels of a process. Each
process must have a unique ID
 Only one flow line should come out from
a process symbol.
 If the flowchart becomes complex, it is
better to use connector symbols to
reduce the number of flow lines.
 Avoid the intersection of flow lines if you
want to make it more effective and better
way of communication.
 Ensure that the flowchart has a logical
start and finish.
FLOW CHART
When building a flow chart, the following items
should be considered:
A start and end point are set:
The purpose of a flow chart is to accomplish a
goal or document a process of any kind from
start point to end point. To get started, you need
to decide what the problem is, or where you are
now, and label that as your starting point and
ending point.
Actions are added:
Once you know where you are and where you
need to go, you need to fill in the appropriate
actions in order to make your flow chart. Each
action should be a single, simple sentence, and
detail one action.
Dependant actions are added.
If you have actions that are complex and require
decisions create diamonds with arrows that
point towards action dependent on the outcome
of the statement in question. Note: diamond
boxes usually contain yes/no answers.
Otherwise, the flow charts can become too
complex to follow in a directly linear way.