Executable UML Book Bugs

Sometimes here may be situations where different actors are somehow involved in initiating the same activity. For example, a delivery person delivers the order to the customer, but a dispatcher notifies the system that the delivery occurred. Who is the actor? The delivery person? The dispatcher? The customer? In this case, an effective strategy is to abstract away the mechanism and to focus on the eventual source of the request in terms of the role.

CreditCardCharge IS AN ATTEMPT TO PAY FOR Order
CreditCardCharge PAYS FOR Order

relate newBook to myPublisher �

reclassify object instance multiBook from StockedProduct to SpecialOrderProduct;

// Make this the shipment for the order
(Self, order) | link R6.'delivers contents of';

// Copy the delivery information for this shipment from the Order.
// (The write attribute operator is '>')
order.recipient > Self.recipient;

// Now copy the remaining information
order.(deliveryAddress, deliveryContactPhone) >
    Self.(deliveryAddress, deliveryContactPhone);

// Make this the shipment for the order
self->("delivers contents of")Order := order;

// Copy the delivery information for this shipment from the Order.
self {
    .recipient := order.recipient;
    .deliveryAddress := order.deliveryAddress;
    .deliveryContactPhone := order.deliveryContactPhone;
}

// Notify the shipping clerk� (as is)

District is resident of Child

District "is place of residence of" Child

select any book from instances of Product
    where selected.productID == rcvd_evt.productID;
relate book to self across R4 creating newSelection;
. . .

Create instance of ProductSelection (relating creates the link object)

Delete instances of ProductSelection (unrelating deletes the link object).

generate requestShipment (order:self) to Shipment creator;

generate <signal> to <object reference> delay <duration>;
cancel <signal> from <object reference> to <object reference>;
generate <signal> from <object reference> at <exact time>;