STRUCTURING

SYSTEM
PROCESS
REQUIREMENTS
COMSCI 2201
Learning Objectives
 Understand the logical modeling of processes by studying
examples of data flow diagrams;
 Draw data flow diagrams following specific rules and
guidelines that lead to accurate and well-structured process
models;
 Decompose data flow diagrams into lower-level diagrams;
 Balance higher-level and lower-level data flow diagrams;
 Use data flow diagrams as a tool to support the analysis of
information systems; and
 Discuss use case modeling.
Process Modeling
Process Modeling (cont…)
 Graphically represent the processes that:
– capture,
– manipulate,
– store,
– distribute data between a system and its environment and
among system components.
 Utilize
information gathered during requirements
determination.
 Processes and data structures are modeled.
Definitions and Symbols

entity
Definitions and Symbols (cont…)
Process:
– work or actions performed on data (inside the
system)
Data store:
– data at rest (inside the system)
Entity:
– external entity that is origin or destination of data
(outside the system)
Data flow:
– arrows depicting movement of data
Context-Level Data Flow Diagrams

Focus is on the data flowing into and out

of the system and the processing of the
data.
Shows the scope of the system:
– What is to be included in the system.
– The external entities are outside the scope
of the system.
The Basic Symbols of a Context Level
Data Flow Diagram
Example:
Context Diagram
 A DFD that summarizes all processing activity
within the system in single process symbol.
 The process is given the number 0
▪ Describes highest level view of a system.
▪ All external agents and all data flows into and out
of a system are shown in the diagram.
▪ The whole system is represented as one process.
▪ The data flows that pass between the external
entities and the system.
 Context Diagram: BASIC RULES
1. List potential external entities (people, places). Look
for entities that:
▪ Give data to the system without explaining the process that
creates the data.
▪ Take data from the system without explaining what it does
with that data.
2. Establish what flows are sent to and from the system
from the external entities.
3. External entities should not be connected to one
another.
4. Draw the context diagram.
Context Diagram: Example

A context-level data
flow diagram
for an airline
reservation system
Context Diagram: Example
Data Flow Diagram
 Data Flow Diagram (DFD) is a picture of the
movement of data between external entities and the
processes and data stores within a system.
 A graphical system model that shows all of the main
requirements for an information system: inputs, outputs,
processes, and data storage
 They are primarily used in the systems development
process.
Data Flow Diagram (cont…)

Level-0 diagram
– a data flow diagram that represents a system’s
major processes, data flows, and data stores at a
high level of detail.
– Processes are labeled 1.0, 2.0, etc. These will be
decomposed into more primitive (lower-level)
DFDs.
Level-0 Diagram

FIGURE 7-5
Level-0 DFD of Hoosier Burger’s
food-ordering system
Data Flow Diagram: Basic Symbols
Data Flow Diagram: External Entities
 Represent another department, a business, a person, or a
machine.
 A source or destination of data, outside the boundaries of the
system.
 Labels should be noun phrases.
Data Flow Diagram: Data Flow
 Shows movement of data from one point to another.
 Described with a noun.
 Arrowhead indicates the flow direction.
 Represents data about a person, place, or thing.
 Can represent flow between process and data store by two
separate arrows.
Data Flow Diagram: Process
 Denotes a change in or transformation of data.
 Represents work being performed in the system.
 Can connect to any other symbol (including another process
symbol).
 Naming convention:
– Assign the name of the whole system when naming a high-level process.
– To name a major subsystem attach the word subsystem to the name.
– Use the form verb-adjective-noun for detailed processes.
Data Flow Diagram: Data Store
 A depository for data that allows examination, addition, and
retrieval of data.
 Named with a noun, describing the data.
 Data stores are usually given a unique reference number, such
as D1, D2, D3
 Represents a:
 Database
 Computerized file
 Filing cabinet
Data Flow Diagram: Naming Guidelines

 External Entity  Noun

 Data Flow  Names of Data
 Process  Verb phrase
– A system name
– A subsystem name
 Data Store  Noun
Data Flow Diagram: Basic Rules
1. The explosion of the context diagram.
2. May include up to nine processes.
3. Each process is numbered.
4. Major data stores and all external entities are included.
5. Start with the data flow from an entity on the input side.
6. Work backwards from an output data flow.
7. Examine the data flow to or from a data store.
8. Analyze a well-defined process.
9. Take note of any fuzzy areas.
Data Flow Diagram: Basic Rules
 Data Flow that Connects:
Data Flow Diagram: Example
Data Flow Diagram: Example

A context-level data flow diagram

for an Ordering System
Data Flow Diagram Levels
 Data flow diagrams are built in layers.
 The top level is the context level.
 Each process may explode to a lower level.
 The lower level diagram number is the same as
the parent process number.
 Processes that do not create a child diagram are
called primitive.
DATA FLOW DIAGRAM LEVELS:
Creating Child Diagrams

 Each process on diagram 0 may be

exploded to create a child diagram.
 A child diagram cannot produce output or
receive input that the parent process does
not also produce or receive.
 The child process is given the same number
as the parent process.
– Process 3 would explode to Diagram 3
DATA FLOW DIAGRAM LEVELS:
Creating Child Diagrams (cont…)

 Entities are usually not shown on the child

diagrams below Diagram 0.
 If the parent process has data flow
connecting to a data store, the child
diagram may include the data store as well.
 When a process is not exploded, it is called a
primitive process.
Checking the Diagrams for Errors
 Forgetting to include a data flow or pointing an arrow in the
wrong direction:
Checking the Diagrams for Errors (cont…)
 Connecting data stores and external entities directly to
each other:
Checking the Diagrams for Errors (cont…)

 Incorrectly labeling processes or data flow.

 Including more than nine processes on a data flow
diagram.
 Omitting data flow.
 Creating unbalanced decomposition (or explosion)
in child diagrams.
Typical Errors
that can Occur
in a Data Flow
Diagram
(Payroll
Example)
Decomposition of DFDs
Functional decomposition
– an iterative process of breaking a system
description down into finer and finer detail.
– Creates a set of charts in which one process on a
given chart is explained in greater detail on
another chart.
– Continues until no sub-process can logically be
broken down any further.
Decomposition of DFDs (cont…)

PrimitiveDFD is the lowest level of a DFD.

Level-1 diagram
– results from decomposition of Level-0 diagram.
Level-n diagram
– a DFD diagram that is the result of n nested
decompositions from a process on a level-0
diagram.
 Level-1 DFD FIGURE 7-8
Level-1 diagram showing the decomposition
of Process 4.0 from the level-0 diagram for
Hoosier Burger’s food-ordering system

Level-1 DFD shows

the sub-processes
of one of the
processes in the
Level-0 DFD.
Processes are labeled 4.1, 4.2, etc.
These can be further decomposed This is a Level-1
in more primitive (lower-level) DFD for Process
DFDs if necessary. 4.0.
Level-n DFD
FIGURE 7-9
Level-2 diagram showing the decomposition of
Level-n DFD shows
Process 4.3 from the level-1 diagram for Process
the sub-processes
4.0 for Hoosier Burger’s food-ordering system
of one of the
processes in the
Level n-1 DFD.

This is a Level-2
DFD for Process
4.3.

Processes are labeled 4.3.1, 4.3.2, etc. If this is the

lowest level of the hierarchy, it is called a primitive DFD.
More Examples
Time Depot Inc. is a nationwide leading sellers of high quality
watches. The company wanted to have a website to easily track
their sales for each store branches. The following are the list of
requirements they wanted to have on their web application:
1. The CEO requested to view sales report of the company.
2. The Store Manager wants to synchronize sales report on the
web application and also requests to modify employee
information.
3. The Supplier is the one that delivers product on the store and
modifies information about the product and supplier.
Construct a Context Level DFD, Level 0 DFD and Level 1 DFD for
this scenario.
(1) List Of Activities Per External Entities

(a) CEO:
– company sales report
(b) STORE MANAGER:
– store sales report
– modify employee information
(c) SUPPLIER:
– modify product information
– modify supplier information
(2) Construct Context Level DFD
(3) Construct
Level 0 DFD
(4) Construct
Level 1 DFD

Data
(4) Construct
Level 1 DFD

Data
2.3 2.4
2.1 2.2

2.5
 Data
Data
(4) Construct
Level 1 DFD Data

Data