[201

0]

SUBMITTED TO:
MISS MADIHA

SUBMITTED BY:

DEPARTMENT:
[DIFFERENCE BETWEEN
BCS_5
DFD AND FLOW
DATE:
CHART.]
DIFFERENCES IN DIFFERENT MEANS

ASSIGMENT NO:
2
 WHAT IS THE DIFFERENCE BETWEEN DATA FLOW
DIAGRAM AND FLOWCHART
DEFINITION:
DATA FLOW DIAGRAM
• A graphical tool that depicts the
flow of data in an information
systems, the relationship among
the data flows and how data come
to be stored at specific location.
• Represents the functions or
processes which capture,
manipulate, store and distribute
data between a system and its
environment and between
components within a system.
MAJOR DIFFERENCES:
DFD
• 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 higher level DFDs are more
analysis.
• A DFD shows how the data moves
through a system.
• Data flow diagram determines the
flow of data, for example, between
subroutines, or between different
programs.
• 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
FLOWCHART
• 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.
FLOW CHART
• Flow chart shows the steps involved
to carry 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.
• Flow chart describes the program.
• 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
 internal data stored.
• In a DFD, the arrows are actually
data transfer between the elements,
which are themselves parts of a
system.
SYMBOLS DIFFERENCES:
DFD SYMBOLS
PROCESS
ENTITY
FILE STORAGE
DATA FLOW
When using a data flow diagram to
illustrate the processes of a system, it is
necessary to use five symbols. The
external entity, an oval, represents a
source or destination of a data flow outside
the area of study. The process, a
rectangular box, represents the
manipulation of data flows within the
system. A line represents the data flow
with arrows showing the direction flow,
typically from its source to its destination.
A data store is a storage bin for
information within the system, represented
by an open-ended narrow rectangle. A
resource flow shows the flow of any
physical material from its source to its
destination.
LEVEL DIFFERENCES:
DFD LEVELS
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
values.
• In a flow chart, the arrows represent
transfer of control between
elements and the elements are
instructions or decision.
FLOW CHART SYMBOLS
Start / End
Process Step
Decision yes
no
Connector
Using a flow chart typically requires the
use of three types of symbols: an
elongated circle representing the start and
the end of a process; a rectangle signifying
instructions or actions; and a diamond
indicating that a decision is necessary. As
you work through the whole procedure that
you are charting, indicate each process
with a symbol and show the connection to
the next process and the flow of each
process with an arrow.
FLOWCHART LEVEL
Macro Level: Generally, a macro-level
flowchart has fewer than six steps.
Mini Level: The term (mini or midi) is
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.
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.

DIFFERENT COMPONENTS:
DFD MAJOR COMPONENTS FLOWCHART MAJOR
COMPONENTS
The components described or illustrated in The flow chart must include components:
a DFD should include: 1. Start and end symbols
2. Arrows
1. External entities 1. information flow
2. Processes 2. control pass
3. Processing steps
1. Level-1 processes
4. Input/Output
2. Sub processes 5. Conditional or decision
3. Data stores 3. Commonly a Yes/No question
1. Transient data stores or True/False test.
4. Complex decision
2. Manual data stores
3. Computerized data
stores
4. Data flows
1. Unidirectional data
flows
2. Bidirectional data
 flows
DIFFERENT USES:
DFD USES
A DFD is used to:
• To provide an indication of how
data is transformed as we move
through the system.
• To depict the functions that
transforms the data flow.
• To create stable systems.
• Better communication with the
users
• Flexibility and maintenance.
Rules differences for Drawing:
DFD
• 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
• 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
FLOW CHART USES
A flow chart is used to:
• Define and analyze processes;
• Build a step-by-step picture of the
process for analysis, discussion, or
communication; and
• Define, standardize or find areas for
improvement in a process
• When better communication is
needed between people involved
with the same process.
• To document a process.
FLOW CHART
• 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 the flow of a
procedure or system is from left to
right or top to bottom.
• 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.
• 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.
• Names of object usually do not
point to specific occurrences of
objects.
• 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.
• It is useful to test the validity of the
flowchart by passing through it with
a simple test data.