UML Weekend Crash Course™ - To Parent Directory

Session 15—Applying the Activity Diagram to the Case Study 161
The narrative also told you that the system must:
Update inventory
Notify Accounts Payable
Print a confirmation to go with the receiving documents
Return to its initial state (prior to this Use Case) upon receiving the Cancel option
Figure 15-3 shows the activities to notify accounts payable, update inventory, and print
the confirmation. I added an activity to display a message for each action so that the user
knows that his requirement was met. Right now it looks like you just have fragments, but
you’ll tie all these pieces together further into the session.
Notify Accounts
Payable of the
updated Purchase
Order
Update inventory
for the Products
received
Print the receiving
confirmation
Display the
"Accounts notified"
message
Display "inventory
updated
successfully"
message
done
Figure 15-3 Modeling the post-conditions and terminations
Next, you need to model the processing for each piece in the shipment. Figure 15-4 sets
up the loop “for each product” with a decision diamond that asks whether there are “more
pieces to receive.”
For each product in the Shipment:
1. Find the Purchase Order using the PO_nbr
2. If not found, display “invalid P.O.” error message and set the item aside
3. Else (P.O. found)