SADM 6/ed - CASE STUDY 2 ECS - Milestone 6: Process Modeling
Page: 6-1
MILESTONE 6 – PROCESS MODELING
 Synopsis
rocess modeling is a technique for organizing and documenting the structure and flow of
data through a system’s processes and/or the logic, policies, and procedures to be
implemented by a system’s processes. In this milestone we focus on using and constructing
data flow diagrams (DFDs) and decomposition diagrams to perform process modeling.
P
Data flow diagrams are tools that depict the flow of data through a system and the work or
processing performed by that system. A decomposition diagram is a DFD planning tool that shows
the top-down functional decomposition and structure of a system.
During this milestone you will first construct a context diagram to establish project scope and
boundaries. Secondly, you will draw an event decomposition diagram to partition the system into
logical subsystems and/or functions. Thirdly, you will draw event diagrams to model individual
processes. Finally you will construct a system data flow diagram that shows the big picture of the
system, and a primitive data flow diagram for a single event process.
 Objectives
After completing this milestone, you should be able to






Construct a context diagram to illustrate a system’s interfaces with its environment.
Identify external and temporal business events for a system.
Logically group events to create an event decomposition diagram.
Create event diagrams.
Merge event diagrams into a system data flow diagram.
Draw appropriate primitive data flow diagrams.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2004
SADM 6/ed - CASE STUDY 2 ECS - Milestone 6: Process Modeling
Page: 6-2
 Prerequisites
1. Process modeling - Chapter 9
2. Optional: Solutions for Milestone 3-5
 Assignment
As a systems analyst or knowledgeable end-user, you must learn how to draw decomposition and
data flow diagrams to model business process requirements. The preliminary investigation and
problem analysis phases of the methodology have been completed and you understand the current
system’s strengths, weaknesses, limitations, problems, opportunities, and constraints. You have
already built the data model (Milestones 4 and 5) to document business data requirements for the
new system. You now need to build the corresponding process models.
 Activities
1. Draw a Context Diagram using the accompanying narrative.
2. Given the accompanying use-case (event/response) matrix, draw the Event Decomposition
Diagram.
3. Given your decomposition diagram from above and the use-case matrix, draw Event Diagrams.
Your instructor will tell you which ones to draw. Use your data model from milestones 3 and 4
as an attribute reference. Also, state any assumptions you make.
4. Merge your event diagrams from #3 above into a System Diagram.
5. For all transaction processes described in the accompanying narratives, draw the Primitive Data
Flow Diagram.
Your instructor will specify deliverable format and software to be used. Deliverables should be
neatly packaged in a binder, separated with a tab divider labeled “Milestone 6.”
References:
Completed Solutions from Prior Milestones
Provided by instructor.
Context Diagram Narrative
Exhibit 6.1
Completed Use-Case (or Event-Response) List
Exhibit 6.2
Primitive Diagram Narrative(s)
Exhibit 6.3
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2004
SADM 6/ed - CASE STUDY 2 ECS - Milestone 6: Process Modeling
Page: 6-3
Deliverables:
Context Diagram:
Due: __/__/__
Time:_______
Functional Decomposition Diagram:
Due: __/__/__
Time:_______
Event Decomposition Diagrams:
Due: __/__/__
Time:_______
System Diagram:
Due: __/__/__
Time:_______
Primitive Diagram(s):
Due: __/__/__
Time:_______
ADVANCED OPTION
Exhibit 6.2 is a partial Use-Case list. Add all maintenance Use-Cases necessary to match
the system narrative in Exhibit 6.1 and to maintain the data structure established in previous
milestones. Then draw the Event Decomposition Diagrams and the System Diagram based on the
complete list.
Use-cases:
Due: __/__/__
Time:_______
Activity diagrams and state models:
Due: __/__/__
Time:_______
Milestone’s Point Value:
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
_______
Copyright Irwin/McGraw-Hill 2004
SADM 6/ed - CASE STUDY 2 ECS - Milestone 6: Process Modeling
Page: 6-4
Exhibit 6.1
Use the following narrative to construct the Context Diagram for the Equipment Check-out System
(ECS).
The purpose of the Equipment Check-out System (ECS) is to provide
maintenance employees with the equipment needed to complete their maintenance
jobs. Employees will occasionally request equipment check-outs. The Equipment
Depot staff will maintain records of those check-outs and provide the employees
with the appropriate equipment and an equipment check-out receipt. When
employees have finished with the equipment, the employee must conduct an
equipment check-in at the Equipment Depot. In response to the equipment checkin, the Equipment Depot staff will maintain records of the equipment check-in and
provide the employee with an equipment check-in receipt. Occasionally,
supervisors will make request an equipment purchase that results in the
Equipment Depot staff needing purchase equipment through equipmentdeals.com.
The supplier daily sends an electronic file showing the status of all orders, which
will be imported into the system so that the Equipment Depot staff can field status
requests from supervisors. When the Equipment Depot staff receives ordered
equipment, they will use the packing slip to verify the shipment and notify the
requesting supervisor of their availability. The Safety Committee will periodically
submit a list of employee skill classifications that can safely check-out any piece
of equipment. Supervisors will submit the skill classifications for each employee.
Upon request the system will generate a report for supervisors showing listing
employees having a history of excessive equipment losses or damage. Upon
request the system will generate for employees a statement detailing what
equipment they have checked out and are expected to have in their possession
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2004
SADM 6/ed - CASE STUDY 2 ECS - Milestone 6: Process Modeling
Page: 6-5
Exhibit 6.2
Below is a partial Use-Case list for the ECS system. Though this is a more complete list
than what was provided for the Exhibit 6.1, it still represents just a portion of all the
events that would be present in the ECS system. (Note: instructors may choose to add or
reduce items from this list to reflect any changes they want to impose on the scope of the
system for this case study.) To develop a functional decomposition diagram, the list of
business events should be examined for possible logical groupings (e.g., which events are
closely related?).
Actor
Employee
Employee
Use-Case Name
Check Out Equip
Check In Equip
Trigger
Responses
Equipment Check-Out
Generate check-out
receipt
Create new Check-Out
Transaction record
Generate check-in
receipt
Equipment Check-In
Employee
Turn in Lost Equip
Employee turns in
equipment
Time
Report Check-Outs Over
30 Days
Generate Equip CheckedOut Rpt
Import Order Status
Daily
Supervisor
Request New Equip
Purchase
Equipmentdeals.com
Update Order Status
Purchase request from
supervisor or decision by
Equip Depot Staff
Packing slip is received
Supervisor
Send Hiring Notice
Hiring Notice
Supervisor
Send Termination Notice
Safety Committee
Submit Equip Restriction
Notice
Send Skill Classification
Update
Generate Employee
Losses & Damage Rpt
Employee Termination
Notice
Equip Restriction Notice
Employee
Time
Supervisor
Supervisor
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Upon request
Nightly
Skill Classification Update
Upon request
Update Check-Out
Transaction record
Update Check-Out
Transaction record if
possible
Generate report for
Supervisors
Generate report for
Employee
Purchase Order status
information is updated
Purchase Request is
recorded.
Purchase Order marked
as being received
Employee is entered to
the system and eligible
to check-out equipment
Employee is removed
from the system
Skill Classifications are
recorded
Employee’s skill
classification is changed
Generate report for
Supervisor
Copyright Irwin/McGraw-Hill 2004
SADM 6/ed - CASE STUDY 2 ECS - Milestone 6: Process Modeling
Page: 6-6
Exhibit 6.3
Use the following narrative to construct the Primitive Diagram for the CHECK OUT EQUIP event.
Given an Employee ID, confirm that the employee is authorized to check out
equipment. If the employee is authorized, then for each requested piece of
equipment, check the equipment restrictions to confirm that the employee has
been assigned an acceptable skill classification. If the request is for tracked
equipment, the system can also check availability by making sure the equipment
does not have an outstanding check-out. If the employee is authorized and the
equipment available and not restricted from use by that employee, record the
check-out. Provide the employee with a receipt that details the check-out and the
location of the equipment so the Equipment Depot staff can pull it.
In addition to referring to the above narrative, be sure to examine the normalized data model for
ECS. The normalized data model depicts data entities that would appear as data stores for the above
processing.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2004