Scribd
Upload
34 views31 pages

6 - Process Modelling

Process modeling uses data flow diagrams (DFDs) to formally represent business systems and how data moves between activities. DFDs decompose a system into levels of increasing detail, with level 0 showing major processes and lower levels showing their sub-processes. Analysts create DFD fragments from use cases then assemble them into a level 0 diagram, decomposing processes into lower level diagrams as needed. DFDs are validated to ensure their structure and semantics accurately reflect the business processes.

Uploaded by

akdauatem
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
34 views31 pages

6 - Process Modelling

Process modeling uses data flow diagrams (DFDs) to formally represent business systems and how data moves between activities. DFDs decompose a system into levels of increasing detail, with level 0 showing major processes and lower levels showing their sub-processes. Analysts create DFD fragments from use cases then assemble them into a level 0 diagram, decomposing processes into lower level diagrams as needed. DFDs are validated to ensure their structure and semantics accurately reflect the business processes.

Uploaded by

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

PROCESS MODELLING

Key Definitions
•Process model -A formal way of representing
how a business system operates. Illustrates the
activities that are performed and how data moves
among them
•Data flow diagramming - A common technique
for creating process models
•Logical - process models describe processes
without suggesting how they are conducted
•Physical - process models provide information
that is needed to build the system
DATA FLOW DIAGRAMS
Using a DFD to Define Business Processes

Business processes are too complex to be


shown on a single DFD
Decomposition is the process of representing the
system in a hierarchy of DFD diagrams
•Child diagrams show a portion of the parent diagram
in greater detail
Decomposition
System Decomposition
Decomposition is the
act of breaking a
system into its
component
subsystems,
processes, and
subprocesses. Each
level of abstraction
reveals more or less
detail.
Decomposition Diagrams
A
decomposition
diagram or
hierarchy chart
shows the top-
down,
functional
decomposition
of a system.
Elements of a DFD
•Process - An activity or function performed for a
specific business reason, Manual or computerized
•Data flow - A single piece of data or a logical
collection of data. Always starts or ends at a process
•External entity - A person, organization, or system
that is external to the system but interacts with it.
•Data Store - A collection of data that is stored in some
way. Data flowing out is retrieved from the data store.
Data flowing in updates or is added to the data store
Naming and Drawing DFD Elements

Process

Data flow

Data store

External
entity
Reading a DFD
Relationship among Levels of DFDs

Context diagram

Level 0 diagram

Level 1 diagram

Level 2 diagram
Context Diagram
• First DFD in every business process
• Shows the context into which the business
process fits
• Shows the overall business process as just one
process (process 0)
• Shows all the external entities that receive
information from or contribute information to
the system
Level 0 Diagram
• Shows all the major processes that comprise the
overall system – the internal components of
process 0
• Shows how the major processes are interrelated
by data flows
• Shows external entities and the major processes
with which they interact
• Adds data stores
Level 1 Diagrams
• Generally, one level 1 diagram is created for
every major process on the level 0 diagram
• Shows all the internal processes that comprise a
single process on the level 0 diagram
• Shows how information moves from and to
each of these processes
• If a parent process is decomposed into, for
example, three child processes, these three child
processes wholly and completely make up the
parent process
Level 2 Diagrams
• Shows all processes that comprise a single
process on the level 1 diagram
• Shows how information moves from and to
each of these processes
• Level 2 diagrams may not be needed for all
level 1 processes
• Correctly numbering each process helps the
user understand where the process fits into
the overall system
Common Process Errors on DFDs
Illegal Data Flows
Process Descriptions
• Text-based process descriptions provide
more information about the process than the
DFD alone
• If the logic underlying the process is quite
complex, more detail may be needed in the
form of
– Structured English
– Decision trees
– Decision tables
CREATING DATA
FLOW DIAGRAMS
Steps in Building DFDs
• Build the context diagram
• Create DFD fragments for each use case
• Organize DFD fragments into level 0 diagram
• Decompose level 0 processes into level 1
diagrams as needed; decompose level 1
processes into level 2 diagrams as needed;
etc.
• Validate DFDs with user to ensure
completeness and correctness
USE CASES
• Use cases are a text-based method of
describing and documenting complex
processes. A use case is a set of activities that
produce some output result
• Describes how the system reacts to an event
that triggers the system
• Use cases add detail to the requirements
outlined in the requirement definition
• Systems analysts work with users to develop
use cases
• Systems analysts develop process and data
models later based on the use cases
Creating the Context Diagram
• Draw one process representing the entire
system (process 0)
• Find all inputs and outputs at the top of the
use cases that come from or go to external
entities; draw as data flows
• Draw in external entities as the source or
destination of the data flows
A Context Diagram Example
Creating DFD Fragments
• Each use case is converted into one DFD
fragment
• Number the process the same as the use
case number
• Change process name into verb phrase
• Design the processes from the viewpoint of
the organization running the system
Creating DFD Fragments
• Add data flows to show use of data stores as
sources and destinations of data
• Layouts typically place
– processes in the center
– inputs from the left
– outputs to the right
– stores beneath the processes
A DFD Fragment Example
Creating the Level 0 Diagram
• Combine the set of DFD fragments into one
diagram
• Generally move from top to bottom, left to
right
• Minimize crossed lines
• Iterate as needed
– DFDs are often drawn many times before
being finished, even with very experienced
systems analysts
A Level 0 DFD Example
Creating Level 1 Diagrams (and Below)

• Each use case is turned into its own DFD


• Take the steps listed on the use case and
depict each as a process on the level 1 DFD
• Inputs and outputs listed on use case become
data flows on DFD
• Include sources and destinations of data flows
to processes and stores within the DFD
• May also include external entities for clarity
Creating Level 1 Diagrams (and Below)

• When to stop decomposing DFDs?


– Ideally, a DFD has at least three
processes and no more than seven to
nine.
Validating the DFD
• Syntax errors – diagram follows the rules
– Validating the DFD structure

For each DFD:


Check each process for:
A unique name: action verb phrase; number;
description
At least one input data flow
At least one output data flow
Output data flow names usually different than
input data flow names
Between 3 and 7 processes per DFD
Validating the DFD
• Semantics errors – diagram conveys correct
meaning
– Assure accuracy of DFD relative to
actual/desired business processes
• Examine lowest level DFDs to ensure
consistent decomposition
• Examine names carefully to ensure
consistent use of terms
Summary
• The Data Flow Diagram (DFD) is an essential
tool for creating formal descriptions of
business processes.
• Use cases record the input, transformation,
and output of business processes and are the
basis for process models.
• Eliciting use cases and modeling business
processes are critically important skills for the
systems analyst to master.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy