DEVELOPING

DATA FLOW
DIAGRAMS (DFD)
OUTLINE
▪ DFD Recap
▪ Entity, Process, Data Store, Data Flow

▪ Context Diagram Recap

▪ Developing DFD and Exploding Levels
▪ DFD Level 0
▪ Creating Child diagrams (level n)
▪ DFD Examples
DFD RECAP
▪ What happened last meeting?
▪ We came to know DFD (definition, symbols & advantages)
▪ We saw Context Diagrams

▪ DFDs are made to DIAGRAM THE FLOW OF DATA

▪ Model the data, not the process flow

▪ First step in creating a DFD is to make a Context Diagram

DFD RECAP
▪ What is a Context Diagram?
▪ The top – most and primary level for a DFD
▪ A guide and starting point in making DFD
▪ DOES NOT CONTAIN A DATA STORE SYMBOL
▪ DOES CONTAIN ALL ENTITIES
▪ Always try to get the best Context Diagram so you have a guide for
DFD Level 0, Level 1, Level 2, etc.
DFD RECAP
▪ There are four symbols in a DFD:
▪ Square, Circle or Rounded Rectangle, Rectangle (open-ended or
not) and Arrows.
▪ Square is for Entity
▪ Circle or Rounded Rectangle is for Process
▪ Rectangle (open-ended or not) is for Data Store
▪ Arrow is for Data Flow
 ENTITY
▪ Represented by a SQUARE
▪ A NOUN
▪ These are usually the users of your system like a person, company or
another sub-system.
▪ Shows the source and recipient of a data

Full Name, Student

Description Records Information
STUDENT TEACHER
SOURCE Student
Info

I ENT
CI P
RE
PROCESS
▪ Represented by Circle or Rounded Rectangle
▪ For CONTEXT DIAGRAMS, this contains the SYSTEM NAME.
▪ You cannot use a combination of circle and rounded rectangle in a DFD diagram.
▪ Represent either a system, work being done or an activity
▪ As much as possible, names should be in the form Verb or Verb-Adjective-Noun
▪ The exception is a process that represents an entire system or subsystem.

Clinic Calculate
Clinic Identify
Recording Student
System Recording Item
Grade
System
DATA STORE
▪ Represented by a rectangle (open-ended or not)
▪ This is NOT included in a Context Diagram
▪ Label it with a noun, describing the data ex. Student Masterfile, Customer Info,
Grades
▪ This is a storage of data or information, whether physical or digital.
▪ Include any data stored, such as:
▪ A computer file or database.
▪ A transaction file .
▪ A set of tables in the database.
▪ A manual file of records such as folders, index cards, etc.

Student Masterfile Customers

DATA FLOW
▪ Represented by arrows
▪ Arrows represent data moving in the system and software.
▪ Arrow names should be the data moving in your system.
▪ Always label your arrows.
▪ A data is a form of information. It is collected, processed and interpreted.
▪ Arrowheads indicate flow direction.

New Student Info Cat details Patient Information

CONTEXT DIAGRAM RECAP
▪ The top – most and primary level for a DFD
▪ A guide for the system analyst and the starting point in making DFD
▪ Include ALL entities and ALL major data flow from and to your system
▪ It contains only one process, representing the entire system. This
process is given the number zero.
▪ It contains ALL entities interacting with the system.
▪ It does not contain any data stores.
CONTEXT DIAGRAM RECAP
▪ Example of a simple Context Diagram

Queue Number
0 SECRETARY
Patient Information
Clinic
PATIENT Management
Chief Complaint
System Patient’s complaint
DOCTOR
Prescription
Patient findings

Patient Prescription
 DEVELOPING DFD AND
EXPLODING LEVELS
▪ Steps in developing data flow diagrams

Make a list of business

activities to know the ff: Explode
Create a Draw Check
1. Entities & create
Context Diagram for
2. Processes a child
Diagram Level 0 errors
3. Data Stores diagram
4. Data Flows
DEVELOPING DFD AND
EXPLODING LEVELS
▪ After creating a Context Diagram, it’s time to create Level 0, Level 1,
Level 2, so on and so forth
▪ Develop Diagram 0 by analyzing the major activities within the
context process.
▪ Include all Entities and major Data Stores.

▪ After developing Diagram 0, create a child diagram for each of its

process, as long as possible.
▪ This means you need to split or explode the processes based on the previous
diagram. The result will show your Child Diagram(s).
DEVELOPING DFD AND
EXPLODING LEVELS
To be able to create child diagrams you have to:
▪ You have to review the list of business activities from your data
gathering. You will be able to get your Processes from there.

1 2

Consult
Queue
Queued
Patient
Patient
DEVELOPING DFD AND
EXPLODING LEVELS
▪ You have to review your list and analyze what Data does an Entity
give to the Process.

n
??????
PATIENT ???
DEVELOPING DFD AND
EXPLODING LEVELS
▪ You have to review your list and analyze what happens to an input
Data Flow from an Entity.
Wh
at h
This inp app
is an ut d ens
inpu ata on
t da flo the
ta f l w?
ow
n
?????? ??????
DOCTOR
PATIENT ???
DEVELOPING DFD AND
EXPLODING LEVELS
▪ You have to review your list and analyze what Data is stored to the
Data Store.

n
??????
???
???
DEVELOPING DFD AND
EXPLODING LEVELS
▪ You have to analyze and investigate unclear areas.

Are
th
unc ere
are lear
as?
??

Okay let’s start with Level 0!

DFD LEVEL 0
▪ DFD Level 0 is more detailed than the context diagram; Explosion of the Context
Diagram
▪ Show Processes but keep them general
▪ It should include up to 9 processes only.
▪ Show Data Stores at this level
▪ Inputs and Outputs at the context diagram remains constant
▪ Processes are numbered with integers starting with 1

1 2
??????
??? ??? ???

DFD Level 0
DFD LEVEL 0
▪ Example of DFD Level 0
in a simple
Food Ordering System
DFD LEVEL 0
▪ Remember that your DFD Levels depends on the
complexity of your system and requirements of your case,
business or clients.
▪ Always analyze the DATA.
DFD EXAMPLES – CONTEXT
DIAGRAM
DFD EXAMPLES – DFD LEVEL 0
DFD EXAMPLES – DFD LEVEL 1
DFD EXAMPLES – DFD LEVEL 2