DATA FLOW DIAGRAM

PREPARED BY:
AHMED HUSSAIN BCS18-032
AHMED RAZA BCS18-001
REHAN HASHMI BCS18-042
SHAEEL AHMED BCS18-040
DAUD MAJID BCS18-035
OUTLINE

Introduction To Data-flow Diagram

Types of Data Flow Diagram
Rules For Creating DFD
Elements Of Data-flow Diagram
Different Kinds (And Levels) Of Data-flow Diagram
DFD Hierarchy
Real World Applications of Data-flow Diagram
INTRODUCTION TO DATA-FLOW DIAGRAM

What Are Data-flow Diagrams?

A Data Flow Diagram (DFD) is a traditional way to visualize the information flow within a system or
a process. The purpose of a DFD is to show the scope and boundaries of a system as a whole.

Components of DFD
DFD provides information about the outputs and inputs of each entity and the process itself. A
data-flow diagram has no control flow, no decision rules and no loops.
For each data flow, at least one of the endpoints (source and / or destination) must exist in a process.

 Notation’s of DFD
There are several notations for displaying data-flow diagrams. The notation presented was described
in

1979 by Tom DeMarco.

INTRODUCTION TO DATA-FLOW DIAGRAM

What Are The Benefits Of Data-flow Diagram?

 It aids in describing the boundaries of the system.

 It is beneficial for communicating existing system knowledge to the users.
 A straightforward graphical technique which is easy to recognize.
 DFDs can provide a detailed representation of system components.
TYPES OF DATA FLOW DIAGRAM

Types of Data Flow Diagram

Data Flow Diagrams are either Logical or Physical.
1. Logical DFD:
This type of DFD concentrates on the system process, and flow of data in the
system. For example in a Banking software system, how data is moved between different
entities.
2. Physical DFD:
This type of DFD shows how the data flow is actually implemented in the system. It is
more specific and close to the implementation.
RULES FOR CREATING DATA FLOW DIAGRAM

All data flows must flow to or from a process.

A Process must have at least one input flow and one output flow.
The inputs to a process must be sufficient to produce output flows.
Processes must transform data.
Data Flows can not cross each other.
Entities must be labelled in lower case.
 The maximum number of processes in one DFD is recommended to be from 6 to 9,
minimum is 1 processes in one DFD.
ELEMENTS OF DATA-FLOW DIAGRAM

Four Basic Elements Are Used To Construct Data-flow Diagrams:

Processes
 Data-flows
 Data Stores
 External Entities
ELEMENTS OF DATA-FLOW DIAGRAM
PROCESS
A process is a function where the manipulation and transformation of data take place.
Notation
Process is represented with a box, divided into three main parts.
1. The top left-hand box contains the process number. This is simply
for identification and reference purposes.
2. The main part of the box is used to describe the process itself, giving the processing performed on the
data it receives.
3. The smaller rectangular box at the bottom of the process is used in the Current Physical Data-Flow
Diagram to indicate the location where the processing takes place.
This may be the physical location — the Customer Services Department or the Stock Room, for example.
However, it is more often used to denote the staff role responsible for performing the process. For
example, Customer Services, Purchasing, Sales Support, and so on.
ELEMENTS OF DATA-FLOW DIAGRAM

Rules To Draw Process In DFD:

Process names should be an imperative verb specific to the activity.

Processes may not act as data sources or sinks.
Data flowing into a process must have some corresponding output.
 Data-flowing out of a process must have some corresponding input to

which it is directly related.

ELEMENTS OF DATA-FLOW DIAGRAM

DATA-FLOWS
A data flow represents the flow of information, with its direction represented by
an arrowhead that shows at the end(s) of flow connector.
Notation

The directed line is labelled with the data-flow name, which briefly describes the
information contained in the flow.
ELEMENTS OF DATA-FLOW DIAGRAM

Rules for Data-Flows

Data stores may not be directly linked by data-flows; information is

transformed from one stored state to another via a process.

Information may not flow directly from a data store to an external entity, nor
may it flow from an external entity directly to a data store. This communication
always takes place via a process.
ELEMENTS OF DATA-FLOW DIAGRAM
DATA STORE
A data store is a place where data is stored and retrieved within the system.
Notation

A data store is represented in the data-flow diagram by a long rectangle, containing

two locations.
The small left-hand box is used for the identifier, which comprises a numerical
reference prefixed by a letter.
The main area of the rectangle is labelled with the name of the data store. Brief
names are chosen to reflect the content of the data store.
ELEMENTS OF DATA-FLOW DIAGRAM
RULES FOR DATA STORE
One convention that could be used is to determine the letter identifying a data store by
the store's nature.
 “M” is used where a manual data store is being depicted.
“D” is used where it is a computer based data store.
 “T” is used where a temporary data store is being represented.
Data stores may not act as data sources or sinks. Data flowing into a data store must
have some corresponding output, and vice versa.
ELEMENTS OF DATA-FLOW DIAGRAM

EXTERNAL ENTITIES
An external entity can represent a human, system or subsystem. It is where certain
data comes from or goes to.
Notation

External entities are represented on the diagram as ovals drawn outside of the
system boundary, containing the entity name and an identifier.
Notation for external entities names consist of a singular noun describing the role
of the entity.
Above the label, a lower case letter is used as the identifier for reference purposes.
ELEMENTS OF DATA-FLOW DIAGRAM

Rules for External Entity

Each external entity must communicate with the system in some way, thus there
is always a dataflow between an external entity and a process within the system.
External entities may provide and receive data from a number of processes.
A line is drawn across the left corner of the ellipse, for each occurrence of the
external entity on the diagram.
DIFFERENT KINDS (AND LEVELS) OF DATA-
FLOW DIAGRAM

Context Diagram (Level-0-dfd Or Fundamental System Model)

A context diagram, is drawn in order to define and clarify the boundaries of the
software system.
It identifies the flows of information between the system and external entities
through data flow.
The entire software system is shown as a single process (bubble).
DIFFERENT KINDS (AND LEVELS) OF DATA-
FLOW DIAGRAM
Example of Context diagram
A context diagram for Online Shopping System
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

Constructing Context Diagram

Draw and label a process box representing the entire system.

Draw and label the external entities around the outside of the process box.
Add the data-flows between the external entities and the system box.
Documents and other packets of information flow entirely within the system, these should
be ignored from the point of view of the context diagram – at this stage they are hidden
within the process box.
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

General Instruction in Constructing Context Diagram

Identify data-flows by listing the major documents and information flows associated with
the system, including forms, documents, reference material, and other structured and
unstructured information (emails, telephone conversations, information from external
systems, etc.).
Identify external entities by identifying sources and recipients of the data-flows, which lie
outside of the system under investigation. The actors an any use case models you have
created may often be external entities.
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

What is LEVEL 1 DFD?

 A level 1 data flow diagram (DFD) is more detailed than a level 0 DFD but

not as detailed as a level 2 DFD.

It breaks down the main processes into sub processes that can then be
analyzed and improved on a more intimate level.
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

Example of Level-1 DFD

A Level-1-DFD for Online Shopping System
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

Constructing Level-1-DFD

Draw the data-flows between the external entities and processes.

Identify data stores by establishing where documents / data needs to be held within the system.

Add the data stores to the diagram, labelling them with their local name or description.

Add data-flows flowing between processes and data stores within the system.
Each data store must have at least one input data-flow and one output data-flow (otherwise data
may be stored, and never used, or a store of data must have come from nowhere).
Ensure every data store has input and output data-flows to system processes. Most processes are
normally associated with at least one data store.

Check diagram. Each process should have an input and an output. Each data store should have an
input and an output
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

General Instructions in Constructing Level-1-DFD

Identify processes. Each data-flow into the system must be received by a process.
For each data-flow into the system examine the documentation about the system
and talk to the users to establish a plausible process of the system that receives the
data-flow. Each process must have at least one output data-flow.
Each output data-flow of the system must have been sent by a process; identify
the processes that sends each system output.
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

Level 2 DFD
A level 2 data flow diagram (DFD) offers a more detailed look at the processes that
make up an information system than a level 1 DFD does. It can be used to plan or
record the specific makeup of a system. ... You can then input the particulars of your
own system.
DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM

Example of Level-2 DFD

DIFFERENT KINDS (AND LEVELS) OF DATA-FLOW
DIAGRAM
Constructing Level-2-DFD
Make the process box on the level 1 diagram the system boundary on the level 2 diagram that
decomposes it.
Identify the processes inside the level 2 system boundary and draw these processes and their
data-flows.
Identify any data stores.
Identify data-flows between the processes and data stores that are entirely within the level 2
system boundary.
Check the diagram.
DATA FLOW DIAGRAM HIERARCHY
To make the DFD more transparent (i.e. not too many processes), multi-level DFDs can be
created. DFDs that are at a higher level are less detailed (aggregate more detailed DFD at
lower levels).
1. The contextual DFD is the highest in the hierarchy (see DFD Creation Rules). The so-
called zero level is followed by DFD 0, starting with process numbering (e.g., process 1,
process 2).
The lowest level should include processes that make it possible to create a process
specification (Process Specification) for roughly one A4 page.
2. Next, the so-called first level - DFD 1 - the numbering continues. e.g. process 1 is
divided into the first three levels of the DFD, which are numbered 1.1, 1.2 and 1.3.
3. Processes in the second level (DFD 2) are numbered e.g. 1.1.1, 1.1.2, 1.1.3 and 1.1.4.
The number of levels depends on the size of the model system. The external entity is
displayed at the highest level where it is first used and at every lower level as well.
REAL WORLD APPLICATIONS OF DATA-FLOW
DIAGRAM

General Applications of Data Flow Diagrams

Library Management System DFD

Hotel Management System DFD
LIBRARY MANAGEMENT SYSTEM
HOTEL MANAGEMENT SYSTEM
THANK YOU!
Any Question?