Download
1 / 27
270 likes | 383 Vues
Object Collaboration. Happy path. Sales Clerk. System. 1. Fill in retailer’s number. 2. Show retailer’s details. ** Set up a new order. 3. Inputs design number. 4. Retrieve and display garment price, size range and description. 5. Input design no, quantity and size.
E N D
Happy path Sales Clerk System 1. Fill in retailer’s number 2. Show retailer’s details. ** Set up a new order. 3. Inputs design number 4. Retrieve and display garment price, size range and description 5. Input design no, quantity and size 6. Write order line with order no, design no, quantity and size. Write ‘quantity’ new instances of garment with status ‘not started’. Display accumulated price. Display new set of orderliness. 7. Indicate finished 8. Enable ‘confirm order’ button. 9. Order confirmed 10. Order saved. ** New retailer is now an alternate path!
Elaborate Steps 1 & 2 • Control class RegisterNewOrder displays OrderUI. • Sales clerk responds • Uses OrderUI to enter the retailer’s number • System responds: • RecordOrder requests retailer info from Retailer. • If successful, • requests constructor on order, giving retailer number and waiting for order number in response.
Signals to OrderUI to display order number and value. • Sales clerk responds • Clicks AddLine on OrderUI • RecordOrder displays DesignUI • Sales Clerk responds • Enters Design number • RecordOrder requests design info from Design. • If successful, • Sends info to DesignUI • DesignUI • displays info • Waits for size and quantity • enables buttons. • Awaits confirmation…
Continue building… • Invent your classes as you go.
Collaboration Diagram • Is another illustration of the interaction between objects during a Use Case. • Classes are shown as icons on the diagram. • Classes that collaborate are linked. • The links are populated with messages, showing the operation that the sender invokes on the recipient.
Making a Collaboration diagram • Identify the objects involved • Sales Clerk, OrderUI, RegisterNewOrder, Retailer, Retailer Order, Retailer Order Line, DesignUI, Design. • Arrange them in layers. • Link all objects that communicate with each other. • Add the messages.
…Messages * This version omits the creation of garment instances – see later
Refining the OCD • 2. Separate out reusable functionality into another control class. • There are a group of messages that only use the DesignUI boundary class and the Design entity. • Introduce a new control class called OrderDesign. • The main control class invokes OrderDesign. • OrderDesign acts as ‘go-between’ between the DesignUI and the Design entity. • When all functionality relating to picking a quantity of a particular design has been completed, OrderDesign hands control back to RegisterNewOrder.
Make all the messages in a happy path step be increments of the step. • To do this, you need to • Check the model properties to ensure that hierarchical numbering is enabled on diagrams. • Create the Sequence diagram from the OCD. • Move the messages so that they originate in the lifeline that has been created by the previous message in the group.
…Messages * This version omits the creation of garment instances – see later
