UML Weekend Crash Course™ - To Parent Directory

200
Saturday Evening
Scenario 5, in Figure 19-11, is the same as steps 1 through 6 of Scenario 1, but the final
condition is different. When no unfilled items remain, the Use Case terminates.
See scenario #1, steps 1 through 6
[no unfilled items remain]
Figure 19-11
Scenario 5: No more items
Mapping the Sequence and Collaboration Diagram
Elements to the Class Diagram
Because the Class diagram is the source for code generation in object-oriented development,
you need to map what you find in the interaction diagrams back to the Class diagram.
Each event becomes an operation on the class of the receiving object. In the classes in
Figure 19-12, you can see each of the events declared as an operation on the receiving
objects.
OrderFulfillmentClerk
+getItemNbr():int
+getOrderNbr():int
+displayOrder(Order):void
+displayMsg(String):void
Order
-Order(order:Order)
+getProdSerialNbr(itemnbr:int):int
+fillItem(itemnbr:int):Product
+backorder():Order
Inventory
OrdersDB
+reduceInv(prod:Product):boolean
+getProduct(prodserialnbr:int):boolean
+getOrder(ordernbr:int):Order
Figure 19-12 Updated class operations
The first event modeled in Figure 19-4 was sent from the System to
OrderFulfillmentClerk. The event name was getOrderNbr(). The operation is assigned to the
OrderFulfillment class, the class of the receiving object.
The return, sequence #2 in Figure 19-4, shows up as the return on the operation signature.
It is important to remember that there is no reference to the return on the sending
class. Any object may invoke the operation getOrderNbr(). Whichever object invokes the
operation at runtime will receive the return. In this scenario, the invoking object in this
case happens to be System.