System Development for TCS - Milestone 5: Process Modeling
Page: 5-1
MILESTONE 5 – PROCESS MODELING
 Synopsis
Process 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.
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 a functional decomposition diagram to partition the system
into logical subsystems and/or functions. Thirdly, you will complete a partially completed event list
that identifies and confirms the business events to which the system must respond. Once that task is
completed, you will refine the decomposition diagram drawn earlier to include event-handling
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 a functional decomposition diagram.
Create event diagrams.
Merge event diagrams into a system data flow diagram.
Draw appropriate primitive data flow diagrams.
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Page: 5-2
 Prerequisites
1. Process modeling — Chapter 8.
2. Milestone 3 or 4 solution.
 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. As part of a
requirements analysis phase, you have already built the data model (Milestones 3 and 4) 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 Functional Decomposition
Diagram.
3. Given your decomposition diagram from above and the use-case matrix, draw an Event
Decomposition Diagrams.
Use your data model from Milestones 3 and 4 as an attribute reference. Also, state any
assumptions you make.
4. Develop event data flow diagrams for the Tool Check-In/Out Subsystem’s transaction
processing and then merge your event diagrams into a System Diagram. In other words, your
goal is to develop a System Diagram to show the processing of all the transactions processed by
the Tool Check In/Out Subsystem. The Tool Check-In/Out Subsystem is described later on in
the narrative introduction of Exhibit 5.2.
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 5.”
References:
Completed Data Model Solution from Milestone 4
Provided by instructor.
Context Diagram Narrative
Exhibit 5.1
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Page: 5-3
Completed Use-Case (or Event-Response) List
Exhibit 5.2
Primitive Diagram Narrative(s)
Exhibit 5.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:_______
ALTERNATIVE OPTION
Draw use-case diagrams using the object-oriented analysis notation described in Module
A. For ___ use-cases (specified by your instructor), draw appropriate activity diagrams or state
models.
Use-cases:
Due: __/__/__
Time:_______
Activity diagrams and state models:
Due: __/__/__
Time:_______
Milestone’s Point Value:
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
_______
System Development for TCS - Milestone 5: Process Modeling
Page: 5-4
Exhibit 5.1
Use the following narrative to construct the Context Diagram for the Tool Crib System (TCS).
The purpose of the Tool Crib System (TCS) is to provide Physical Plant
employees with the work tools needed to complete their zone maintenance jobs.
Employees will occasionally conduct tool check-outs. The TCS staff will maintain
records of those check-outs and provide the employees with the appropriate tools
and a tool check-in receipt. When employees have finished with the tool(s), the
employee must conduct a tool check-in at the Tool Crib. In response to the tool
check-in, the TCS staff will maintain records of the tool check-in and provide the
employee with a tool check-in receipt. Occasionally, zone foremen will make a
tool purchase decision that results in the TCS staff needing to generate a purchase
order that is sent to the supplier. When shipments of new tools are received, the
TCS staff will notify the foreman of their availability and also send a shipment
receipt notice to Accounts Payable notifying them that the purchase order has
been filled and can now be paid.
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Page: 5-5
Exhibit 5.2
The table below contains representative business events that are to support by the new Tool Crib
System. Be sure to include any additional events that your instructor may choose to add to this list.
(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.)
In order 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?). Logical groupings
or associations of events can suggest subsystems that make up our Tool Crib System. Let’s assume
that you made the following observations and decisions:
1. Some of the events are logically related because they pertain to tool check-in/out. Thus, you
will create a TOOL CHECK-IN/OUT SUBSYSTEM to handle these events.
2. Some of the events are logically be related because they pertain to an employee. Thus, you
will create a subsystem called EMPLOYEE SUBSYSTEM to handle these events.
3. Some events are logically related because they pertain to inventory control. Thus, you will
create an INVENTORY SUBSYSTEM to handle these events.
The three Tool Crib subsystems should be used as a starting point for you to complete the
functional decomposition diagram and event decomposition diagram. For your convenience, we
indicated (under the heading “subsystem”) those events that can be logically grouped and handled
by the TOOL CHECK-IN/OUT SUBSYSTEM. You should decide which of the remaining events
would be handled by the other two subsystems.
Finally, notice that in our event-response list that follows we named the responses for those events
that resulted in output information (see footnote below table)
Subsystem Actor
Event (or Use Case)
Trigger
Responses
Foreman
Registers new employees
and authorizes them to
check out tools.
EMPLOYEE HIRING
NOTICE
Foreman
Terminates existing
employees and their
authorization to check out
tools.
EMPLOYEE
TERMINATION
NOTICE
Employee
Reports that a tool has been
lost.
REPORT OF LOST
TOOL
Generate TOOL
CHECK-OUT
AUTHORIZATION
(given to employee).
Create a new
EMPLOYEE in
database.
Generate TOOL
POSSESSIONS
CHECKLIST (given to
foreman).
Create EMPLOYEE or
modify EMPLOYEE
(EMPLOYEE STATUS)
in database.
Modify EMPLOYEE
(YTD Dollar Amount of
Lost Tools and Tools
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Subsystem Actor
Event (or Use Case)
Trigger
Page: 5-6
Responses
Lost YTD).
Generate LOST TOOL
POSTING (1 per
foreman).
Generate TOOL
CHECK-IN RECEIPT
(given to the employee).
Create TOOL
TRANSACTION and
MODIFY LARGE
TOOL’s
AVAILABILITY
STATUS and/or
SMALL TOOL’s
QUANTITY ON
HAND.
Generate TOOL
CHECK-OUT RECEIPT
(given to employee).
Create TOOL
TRANSACTION and
modify LARGE TOOL’s
AVAILABILITY
STATUS.
Generate a TOOL
DAMAGE
DESCRIPTION (given
to Al Borland).
Modify a LARGE
TOOL’s
AVAILABILITY
STATUS in the
database.
Generate a TOOL
LOCATION NOTICE
(given to employee)
TOOL
CHECKIN/OUT
Employee
Checks in a tool.
TOOL CHECK-IN
TOOL
CHECKIN/OUT
Employee
Checks out a tool
TOOL CHECK-OUT
TOOL
CHECKIN/OUT
Employee
Returns a tool and reports
it as being damaged.
DAMAGED TOOL
RETURN
TOOL
CHECKIN/OUT
Employee
Returns a tool that was
found.
LOST TOOL RETURN
Tool Crib Staff
An evaluation of an
employee’s tool checkin/out performance has
been completed.
EMPLOYEE
PERFORMANCE
EVALUATION
Modify EMPLOYEE’s
EMPLOYEE STATUS
in the database.
Physical Plant
Director
Conveys a reorganization
of the Physical Plant (i.e., a
new zone is established, a
zone is collapsed into
another zone, etc.)
PHYSICAL PLANT
REORGANIZATION
PLAN
Foreman
Establishes a new skill
classification for an
employee (thus, impacting
any restrictions on tools
that employee may check
SKILL
CLASSIFICATION
UPDATE
Create or delete a
ZONE.
Modify an
EMPLOYEE’s ZONE
assignment in the
database.
Modify an
EMPLOYEE’s skill
classification in the
database.
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Subsystem Actor
Event (or Use Case)
Page: 5-7
Trigger
Responses
Generate a P.O.
CANCELLATION
NOTICE (sent to
Supplier).
Delete a PURCHASE
ORDER in the database.
Generate a P.O.
MODIFICATION
REQUEST (sent to
Supplier).
Modify a PURCHASE
ORDER in the database.
Generate SHIPMENT
RECEIPT NOTICE
(sent to Accounts
Payable).
Create a SHIPMENT in
the database.
Modify a TOOL’s
AVAILABILITY
STATUS or its
QUANTITY ON
ORDER, QUANTITY
OWNED, and
QUANTITY ON HAND
in the database.
Create a VENDOR and
VENDOR TOOL in the
database.
Delete a VENDOR in
the database.
out).
Tool Crib Staff
A decision is made to
cancel an outstanding
purchase order.
PURCHASE ORDER
CANCELLATION
Tool Crib Staff
A decision is made to
change an outstanding
purchase order.
PURCHASE ORDER
MODIFICATION
Supplier
A shipment is received.
SHIPMENT RECEIPT
Supplier
A supplier sends a product
catalog.
VENDOR TOOL
CATALOG
Tool Crib Staff
Due to unfavorable factors,
a decision is made to
discontinue ordering tools
from a particular supplier.
VENDOR
DISCONTINUATION
DECISION
Foreman
A decision is made that a
new tool is needed for
employees to complete a
zone job.
NEW TOOL REQUEST
Tool Crib Staff
An accounting of the tool
inventory is completed
(and tool quantities and
availability needs to be
adjusted accordingly).
INVENTORY COUNT
Manufacturer
A tool that was previously
sent for repair has been
returned.
REPAIRED TOOL
RETURN
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
Generate a PURCHASE
ORDER (sent to
SUPPLIER).
Create a PURCHASE
ORDER in the database.
Modify the TOOL’s
QUANTITY ON
ORDER in the database.
Update (add, modify, or
delete) TOOL in
database to reflect actual
quantities and
availability.
Modify LARGE
TOOL’s
AVAILABILITY
STATUS in the
System Development for TCS - Milestone 5: Process Modeling
Subsystem Actor
Page: 5-8
Event (or Use Case)
Trigger
Responses
Tool Crib Staff
An assessment is made of
the dollar value required to
replace a tool.
TOOL REPLACEMENT
ESTIMATE
database.
Modify a TOOL’s
REPLACEMENT COST
in the database.
Safety
Committee
A determination is made
regarding the skill
classification requirement
needed to safely utilize a
particular tool.
TOOL RESTRICTION
NOTICE
Modify a TOOL’S
restriction to a SKILL in
the database.
Accounts
Payable
Notification is received that
an invoice for a previous
shipment of ordered tools
has been paid.
PAID INVOICE
NOTICE
Delete a PURCHASE
ORDER in the database.
TOOL
CHECKIN/OUT
Tool Crib Staff
It is time to analyze the tool
check-outs.
(time)
TOOL
CHECKIN/OUT
Tool Crib Staff
It is time to analyze tool
requests.
(time)
TOOL
CHECKIN/OUT
Employee
It is time to inform
employees of their tool
possessions.
(time)
Tool Crib Staff,
Foremen, and
Safety
Committee
It is time to reassess
restricted tools.
(time)
Foremen
It is time to confirm
employee zone assignments
and tool check-out
authorizations.
(time)
Tool Crib Staff
It is time to follow up on
overdue Purchase Orders.
(time)
Tool Crib Staff
It is time to count
inventory.
(time)
Tool Crib Staff
It is time to assess vendor
performance.
(time)
Tool Crib Staff
There is a need to check
the availability of a tool.
(a decision-making need
arises)
Generate a TOOL
CHECK-OUT
ACTIVITY REPORT
(used by Tool Crib
staff).
Generate a TOOL
REQUEST ANALYSIS
REPORT (used by Tool
Crib staff).
Generate a MONTHLY
EMPLOYEE CHECKOUT STATEMENT
(generated for each
employee).
Generate a
RESTRICTED TOOLS
LIST (one copy per
foreman and safety
committee member).
Generate a ZONE
ASSIGNMENT &
AUTHORIZATIONS
LIST (one copy per
foreman).
Generate OVERDUE
PURCHASE ORDERS
REPORT (used by Tool
Crib staff)
Generate INVENTORY
LIST (used by Tool Crib
staff).
Generate VENDOR
ANALYSIS REPORT
(used by Tool Crib
staff).
Provide
AVAILABILITY OF
TOOL query results (to
TOOL
CHECKIN/OUT
TOOL
CHECK-
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Subsystem Actor
Event (or Use Case)
Trigger
IN/OUT
Page: 5-9
Responses
Tool Crib staff).*
TOOL
CHECKIN/OUT
Tool Crib Staff
There is a need to query an
employee’s check-in/out.
(a decision-making need
arises)
Provide queried TOOL
TRANSACTION details
(to Tool Crib staff).*
TOOL
CHECKIN/OUT
Tool Crib Staff
There is a need to check on
an employee’s
authorization to check out a
restricted tool.
(a decision-making need
arises)
Tool Crib Staff
There is a need to locate a
supplier from which a tool
can be purchased.
(a decision-making need
arises)
Tool Crib Staff
There is a need to locate a
specific “large tool.”
(a decision-making need
arises)
Tool Crib Staff
There is a need to check on
a purchase order.
(a decision-making need
arises)
Provide queried
EMPLOYEE, SKILL,
and tool restriction
details (to Tool Crib
staff).*
Provide queried TOOL,
VENDOR, and
VENDOR TOOL details
(to Tool Crib staff).*
Provide queried TOOL,
EMPLOYEE, ZONE,
and historical TOOL
TRANSACTION details
(to Tool Crib staff).*
Provide queried
PURCHASE ORDER
and related VENDOR
details (to Tool Crib
staff).*
TOOL
CHECKIN/OUT
* These represent responses to some decision support inquiries. You will need to establish your
own names for the output(s). For example the last item in the above list might be named
PURCHASE ORDER QUERY RESPONSE.
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed
System Development for TCS - Milestone 5: Process Modeling
Page: 5-10
Exhibit 5.3
Use the following narrative to construct the Primitive Diagram for the TOOL CHECK-OUT event.
Given an Employee ID, confirm that the employee is authorized to check out
tools.
If the employee is authorized, then do the following for each requested tool: Given
the description of the needed tool and the requested quantity, locate the tool by
checking on its quantity on hand or availability status. If the tool is available for
check out, check the tool restrictions to confirm that the employee has been
assigned an acceptable skill classification for using that tool. If the employee is
authorized, the tool is available, and the tool is not restricted from use by that
employee, record the tool check-out.
Provide the employee with a receipt that details the check-out.
In addition to referring to the above narrative, be sure to examine the normalized data model for the
Tool Crib. The normalized data model depicts data entities that would appear as data stores for the
above processing (e.g., the MEMBER entity would appear as a data store that is accessed in order to
confirm that the employee is authorized to conduct a tool check-out.)
Prepared by {Dr.M.A.Kashem} for
Systems Analysis & Design Methods 5ed