UML Weekend Crash Course™ - To Parent Directory

Session 19—Applying the Collaboration Diagram to the Case Study 195
you can place the objects anywhere you like. As you add the other information, you will
very likely want to rearrange the objects anyway to make the diagram easier to read.
:OrderFullfillment Clerk
:OrdersDB
23456789:Order
:System
:Inventory
12345678:Order
Figure 19-2 The objects participating in Scenario 1
Next, add the links between the objects (see Figure 19-3). Be sure to follow the rules
established by the Class diagram associations. The links provide the paths over which the
interactions take place.
:OrderFullfillment Clerk
:OrdersDB
:System
12345678:Order
:Inventory
Figure 19-3 The links between the objects participating in Scenario 1
Next, each step of the flowchart becomes an event and/or a return on the Collaboration
diagram. Start with “Get Order #.” The system asks the OrderFulfillmentClerk for the Order
#. Imagine this as a screen that is waiting for an entry. The message is from the System
object to the OrderFulfillmentClerk object. It is a synchronous type because the System
will wait for a reply. Lay the event arrow parallel to the link between the two objects and