UML Weekend Crash Course™ - To Parent Directory

Session 6—Building the Use Case Diagram 65
An association between ShipOrder and OrderProcessingSystem. “They also notify
the Order Processing department that the order has shipped. The clients want the
new system to handle the notification to Order Processing.”
An association between StockClerk and Stock Product. “The stock clerk looks up
the correct location for the new products, places the products in that location, and
updates the location inventory with the product quantity.”
An association between FillOrder and OrderProcessingSystem. “They also notify
the Order Processing department that the order has been filled. The clients want the
new system to handle the notification to Order Processing.”
An association between OrderFulfillment and LocateProduct. “Other staff members
fill orders by locating the products required for the order.”
Receiving
ReceiveProduct
AccountsPayableSystem
Shipping
ShipOrder
FillOrder
OrderProcessingSystem
Stock Clerk
OrderFulfillment
StockProduct
LocateProduct
Figure 6-3
Associations from the problem statement
Step 5: Evaluate the actors and Use Cases to find opportunities for refinement
Rename, merge, and split actors and Use Cases as needed. When you build your diagrams
based on interviews with users, it is easy to fall into the trap of replicating the current
system (see Session 4). From your first draft of the descriptions of the actors and Use
Cases, start asking critical questions, especially the simple but powerful question, “Why”
For example, ask, “Why is this actor responsible for these particular duties” or “Why do
these tasks have to be done together, separately, in this order, or done at all” A system
rewrite or major revision provides a great opportunity to clean house and address a lot of
the legacy problems that have accumulated over time.