Scribd
Upload
63 views17 pages

System Design - DFD: Debarshi Mukherjee Assistant Professor - IT

Data flow diagrams (DFDs) are used to model systems and focus on the logical flow of data in a system. [1] DFDs show the movement of data between external entities, processes, and data stores with a graphical representation. [2] Processes transform incoming data flows and are represented by bubbles, while data stores hold data and are represented by rectangles. [3] DFDs help analyze existing systems, identify inefficiencies, and communicate requirements to stakeholders.

Uploaded by

friendlynidhi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
63 views17 pages

System Design - DFD: Debarshi Mukherjee Assistant Professor - IT

Data flow diagrams (DFDs) are used to model systems and focus on the logical flow of data in a system. [1] DFDs show the movement of data between external entities, processes, and data stores with a graphical representation. [2] Processes transform incoming data flows and are represented by bubbles, while data stores hold data and are represented by rectangles. [3] DFDs help analyze existing systems, identify inefficiencies, and communicate requirements to stakeholders.

Uploaded by

friendlynidhi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

System Design - DFD

Debarshi Mukherjee
Assistant Professor - IT
A simple process for making lunch

DATA FLOW DIAGRAMS


Systems Analysis
• Focus is the logical view of the
system, not the physical
• “What” the system is to accomplish,
not how

• Tools:
– data flow diagrams
– data dictionary
– process specification
– entity-relationship diagrams
Data Flow Diagram:
"a network representation of a system.
The system may be automated, manual,
or mixed. The DFD portrays the system
in terms of its component pieces, with all
interfaces among the components
indicated."
- Tom DeMarco
hence DFDs:
focus on the movement of data between
external entities and processes, and
between processes and data stores
Example Data Flow
Diagram
data store

data flow process

external
entity
Data Flow Diagrams are:

• Used to perform structured analysis


to determine logical requirements
• A graphical tool, useful for
communicating with users,
managers, and other IS personnel
• Useful for analyzing existing as well
as proposed systems
• A relatively simple technique to learn
and use
Why Conduct Process
Modeling?
• Understand components of
current logical or physical
system for purpose of rebuilding
in a different physical
form/technology, possibly with
some changed functionality
• Find inefficiencies in current
system
• Re-engineer current system
Sources/Sinks
(external entities)
• Any class of people, an
organization, or another
system which exists
outside the system you
are studying.
• Form the boundaries of source
the system. /
• The system and external sink
entities exchange data in
the form of data flows.
• Must be named, titles
preferred to names of
individuals - use a noun
Data Flows
• data in motion
• marks movement of data through the
system - a pipeline to carry data
• connects the processes, external
entities and data stores
• Unidirectional
• originate OR end at a process (or both)
• name as specifically as possible -
reflect the composition of the data - a
noun
• do not show control flow! Control flow
is easy to identify- a signal with only
one byte - (on/off).
• HINT: if you can't name it: either it's
control flow, doesn't exist or you need
to get more information!
Processes
• transform incoming data
flows into outgoing data
flows
• represent with a bubble or
rounded square
• name with a strong
VERB/OBJECT process
combination; examples:
create_exception_report
validate_input_characters
calculate_discount
Data Stores
• data at rest
• represents holding areas for
collection of data, processes
add or retrieve data from
these stores
• name using a noun (do not
use ‘file’) data store
• only processes are connected
to data stores
• show net flow of data
between data store and
process. For instance, when
access a DBMS, show only
the result flow, not the
request
Data Flow Diagram Don’ts
1. BLACK HOLES
2. MIRACLES
3. Let it get too COMPLEX: 7 ± 2 processes
4. Leave things UNLABELED
(corollary: labels should have meaning)
5. Data stores that are “SOURCES” or
“SINKS”
6. Data flows that are UNASSOCIATED with
a PROCESS
7. Expect your diagram to be “perfect” the
first time!
Data Flow Diagram Don’ts

process 1. ‘Black Hole’


stuff

process 2. ‘It’s a Miracle’


stuff
Data Flow Diagram Don’ts

ds-1

A.1

A.2 data

4. Leave Things Unlabeled

Corollary: Labels Should


Data Flow Diagram Don’ts

data store 5. Miracle data


source

5. Black hole data


data store source
Data Flow Diagram Don’ts
6. Data Flows Unassociated With a Process

entity to
data store entity
to entity -
or reverse

data store
to data
store
Thank You!

End of Part 1

You might also like