Scribd
Upload
43 views

Handout 3c Data Flow Diagram

A data flow diagram (DFD) visually represents a system's processes, external entities, data inputs and outputs, and data stores. There are two main types: logical DFDs focus on business processes while physical DFDs specify technical implementation details. DFDs also have levels - level 0 context diagrams provide an overview, while level 1 and 2 diagrams show more subprocess details. Key elements are processes, data stores, external entities, and data flows. Creating a DFD involves identifying inputs/outputs, building a context diagram, and expanding it with additional levels for greater detail.

Uploaded by

Paolo Lozada
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
43 views

Handout 3c Data Flow Diagram

A data flow diagram (DFD) visually represents a system's processes, external entities, data inputs and outputs, and data stores. There are two main types: logical DFDs focus on business processes while physical DFDs specify technical implementation details. DFDs also have levels - level 0 context diagrams provide an overview, while level 1 and 2 diagrams show more subprocess details. Key elements are processes, data stores, external entities, and data flows. Creating a DFD involves identifying inputs/outputs, building a context diagram, and expanding it with additional levels for greater detail.

Uploaded by

Paolo Lozada
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

MODULE 3C: DATA FLOW

DIAGRAM

LEARNING OBJECTIVES

• What is a data flow diagram?


• Physical and logical data flow diagrams
• Data flow diagram levels
• Data flow diagram symbols and notation
• How to create a data flow diagram

WHAT IS A DATA FLOW DIAGRAM?

• A data flow diagram shows the way information flows through a


process or system.
• It includes data inputs and outputs, data stores, and the
various subprocesses the data moves through.
• DFDs are built using standardized symbols and notation to
describe various entities and their relationships.

1
• Data flow diagrams visually represent systems and processes
that would be hard to describe in a chunk of text.
• You can use these diagrams to map out an existing system and
make it better or to plan out a new system for implementation.
• Visualizing each element makes it easy to identify inefficiencies
and produce the best possible system.

PHYSICAL AND LOGICAL DATA FLOW


DIAGRAMS
• Before actually creating your data flow diagram, you’ll need to
determine whether a physical or logical DFD best suits your
needs.

LOGICAL DATA FLOW DIAGRAMS

• Logical data flow diagrams focus on what happens in a


particular information flow: what information is being
transmitted, what entities are receiving that info, what general
processes occur, etc.
• The processes described in a logical DFD are business
activities—a logical DFD doesn’t delve into the technical
aspects of a process or system. Non-technical employees
should be able to understand these diagrams.

2
Logical Data Flow Diagram

PHYSICAL DATA FLOW DIAGRAMS

• Physical data flow diagrams focus on how things happen in an


information flow.
• These diagrams specify the software, hardware, files, and
people involved in an information flow.
• A detailed physical data flow diagram can facilitate the
development of the code needed to implement a data system.

Physical Data Flow Diagram

3
• Both physical and logical data flow diagrams can describe the
same information flow. In coordination they provide more detail
than either diagram would independently. As you decide which
to use, keep in mind that you may need both.

DATA FLOW DIAGRAM LEVELS

• Data flow diagrams are also categorized by level.


• Starting with the most basic, level 0, DFDs get increasingly
complex as the level increases.
• As you build your own data flow diagram, you will need to
decide which level your diagram will be.

DATA FLOW DIAGRAM LEVEL 0

• Level 0 DFDs, also known as context diagrams, are the most


basic data flow diagrams.
• They provide a broad view that is easily digestible but offers
little detail.
• Level 0 data flow diagrams show a single process node and its
connections to external entities.

4
DATA FLOW DIAGRAM LEVEL 0

DATA FLOW DIAGRAM LEVEL 1

• Level 1 DFDs are still a general overview, but they go into more
detail than a context diagram.
• In a level 1 data flow diagram, the single process node from the
context diagram is broken down into subprocesses.
• As these processes are added, the diagram will need additional
data flows and data stores to link them together.

Data Flow Diagram Level 1

5
DATA FLOW DIAGRAM LEVEL 2

• Level 2+ DFDs simply break processes down into more detailed


subprocesses.
• In theory, DFDs could go beyond level 3, but they rarely do.
Level 3 data flow diagrams are detailed enough that it doesn’t
usually make sense to break them down further.

Data Flow Diagram Level 2

DATA FLOW DIAGRAM SYMBOLS AND


NOTATION
• Depending on the methodology (Gane and Sarson vs. Yourdon
and Coad), DFD symbols vary slightly. However, the basic ideas
remain the same.
• There are four basic elements of a data flow diagram:
processes, data stores, external entities, and data flows.

6
HOW TO CREATE A DATA FLOW DIAGRAM

1. Identify major inputs and outputs in your system


Nearly every process or system begins with input from an external entity
and ends with the output of data to another entity or database.
Identifying such inputs and outputs gives a macro view of your system—
it shows the broadest tasks the system should achieve. The rest of your
DFD will be built on these elements, so it is crucial to know them early
on.

2. Build a context diagram


Once you’ve identified the major inputs and outputs, building a context
diagram is simple.
Draw a single process node and connect it to related external entities.
This node represents the most general process information undergoes to go
from input to output.

3. Expand the context diagram into a level 1 DFD


The single process node of your context diagram doesn’t provide much
information—you need to break it down into subprocesses.
In your level 1 data flow diagram, you should include several process nodes,
major databases, and all external entities. Walk through the flow of
information: where does the information start and what needs to happen to
it before each data store?

7
4. Expand to a level 2+ DFD
To enhance the detail of your data flow diagram, follow the same process as
in step 3.
The processes in your level 1 DFD can be broken down into more specific
subprocesses.
Once again, ensure you add any necessary data stores and flows—at this
point you should have a fairly detailed breakdown of your system. To
progress beyond a level 2 data flow diagram, simply repeat this process.
Stop once you’ve reached a satisfactory level of detail.
5. Confirm the accuracy of your final diagram
When your diagram is completely drawn, walk through it.
Pay close attention to the flow of information: does it make sense? Are all
necessary data stores included? By looking at your final diagram, other
parties should be able to understand the way your system functions.
Before presenting your final diagram, check with co-workers to ensure your
diagram is comprehensible.

You might also like