Scribd
Upload
15 views

Creating DFD

Uploaded by

cossykin19
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
15 views

Creating DFD

Uploaded by

cossykin19
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

C R E ATIN G D F D S

Define Entities
• External entities represent
persons, processes or machines
which produce data to be used
by the system or receive data Student
that is output by the system
• Examples: Student, Customer,
Client
2.1
Define Processes
• Processes are discrete actions
Create
that transform input data to Student
output data Record
• Examples: Create Student
Record, Calculate Purchase
Cost, Register Client
pjorn Lecture Notes
C R E ATIN G D F D S (C O N T’D )

Define Data Stores


• Data stores are temporary or permanent
repositories of information that are
inputs to or outputs of processes Student
D3
• Examples: Student Master, Client List Master

Define Data Flows


• Data flows represent the transfer of data
over time from one “place” (entity, New Student
process, data store) to another Information
• Examples: New Student Information
(from Student, to Student Master)

(Templates are posted in l:\academic\90728\DFDSymbols.ppt)


pjorn Lecture Notes
CREATING DFDS (CONT’D)

Define the System


• A system is the collection of all
business processes which perform
tasks or produce outputs we care
about. It is “what happens.”
• The system is a single process,
(Figure 4.13,
connected to external entities
Shelly,
Cashman and
• Represented in a “Context Diagram”
Rosenblatt)
Define Subsystems
• A subsystem gives a more detailed
view individual processes contained
in the context diagram
• Includes data stores, more
elementary processes
pjorn Lecture Notes
DFDs Created by Top-Down Analysis
• Create a narrative: description of system
Narrative
• Create a Context Diagram that contains a
single process (“the system”) and all
Context Diagram
entities which share data with the system
• Explode the “parent” context diagram to
produce a Diagram 0 (“child”) DFD Diagram 0 DFD
• Create Diagram 1, 2, …, n DFDs that
represent “explosions” of Diagram 0, 1,
…, n-1 DFDs until a diagram has only Diagram 1 DFDs
“primitive” processes
• Create process descriptions to be
implemented by application programs:
queries, macros, reports, programming
languages
Diagram n DFDs

E-R Diagram Process Descriptions


pjorn Lecture Notes
W H E R E TO B E G I N C R E AT I N G D F D S

• Start with the data flow from an external entity and work
forwards
• Start with the data flow to an external entity and work
backwards
• Examine the data flows into or out of a data store
• Examine data flows, entity connections and data stores
associated with a particular process
• Note fuzzy, ill-defined areas of the system for further
clarification

pjorn Lecture Notes


WHAT TO AVOID IN DFDS

Processes with no outputs or 4


no inputs Perform
Processes whose inputs are Repair
obviously inadequate to yield
outputs
Connecting data stores directly Class List
Courses Students
to each other

Having data flows terminate at


data stores
Connecting entities to anything Payroll Employees
other than processes Department
Making the data flow diagram too
cluttered (e.g.  9 processes)
1 2 3
Many processes with a single Process Process Process
input and output (linear flow) A B C

pjorn Lecture Notes


D F D E X A M P L E : B U S G A R A G E R E PA I R S

Buses come to a garage for repairs.


A mechanic and helper perform the repair, record the reason for the repair and record
the total cost of all parts used on a Shop Repair Order.
Information on labor, parts and repair outcome is used for billing by the Accounting
Department, parts monitoring by the inventory management computer system and a
performance review by the supervisor.
• Key process (“the system”): performing repairs and storing information related to
repairs
• External Entities: Bus, Mechanic, Helper, Supervisor, Inventory Management
System, Accounting Department, etc.
• Processes:
• Record Bus ID and reason for repair
• Determine parts needed
• Perform repair
• Calculate parts extended and total cost
• Record labor hours, cost
pjorn Lecture Notes
DFD EXAMPLE: BUS GARAGE REPAIRS
(CONT’D)
• Data stores:
• Personnel file
• Repairs file
• Bus master list
• Parts list
• Data flows:
• Repair order
• Bus record
• Parts record
• Employee timecard
• Invoices

pjorn Lecture Notes


Bus Garage Context Diagram
Bus

Mechanical Fixed
problem mechanical
to be repaired problems

0 Repair Supervisor
Helper Labor
Bus summary
Repair
Process List of
parts used Inventory
Labor Management
Labor, System
parts cost
Mechanic details

Accounting

pjorn Lecture Notes


BUS GARAGE DIAGRAM 0 DFD

pjorn Lecture Notes


Bus Garage Diagram 0 DFD (cont’d)

pjorn Lecture Notes

You might also like