1. Screens for Order Garments

2. What happens in the Use Case? The user picks / adds a retailer –The user types in an account number. If the account number is valid, the account details are retrieved from the retailer entity and displayed. Otherwise, the account number field is cleared and the user can add a retailer, or retrieve by name. The ‘system’ responds by adding / retrieving a retailer and setting up a new order.

3. An ‘Add order line’ loop ensues: The user clicks ‘add a line’ The system responds by displaying the designUI. The user enters a design number The system displays the design details.

4. The user may ask to order, if so The system responds by enabling the required fields and button. The user enters the quantity and size The system displays the line total The user confirms the orderline The system creates the new orderline, the new garments and updates the order. The system redisplays the orderline scrollbox.

6. Retailer UI

7. This is the design screen before the Add to Order button has been clicked

8. This is the design screen after the Add to Order button has been clicked

9. Sales ClerkSystem 1. Fill in retailer’s details2. Set up a new order. Record / retrieve retailer’s details 3. Inputs design number4. Retrieve and display garment price, size range and description 5. Input design no, quantity and size6. Write order line with orderno, designno, quantity and size. Write ‘quantity’ new instances of garment with status ‘not started’. Display accumulated price. Display new set of orderliness. 7. Indicate finished8. Enable ‘confirm order’ button. 9. Order confirmed10. Order saved. Happy path

10. Alternate paths 1a Cancel order2a end 3a Cancel order4a If new retailer, delete retailer. Delete order. End 5a Cancel order6a If new retailer, delete retailer. Delete order. Delete order lines. Delete garments. End. 7a onwards Cancel order8a If new retailer, delete retailer. Delete order. Delete order lines. Delete garments. End.

11. Alternate paths 5b Change orderline6b. Display orderline and ask for change. 7b Enter amend or delete8b. If delete, delete orderline, delete garment instances, redisplay order with updated prices. Resume at 3. If amend, prompt for new data. 9b Enter new data10b. Rewrite orderline with new data. Add/delete garment instances. Redisplay order with updated prices. Resume at 3. 3c Enter invalid design no4c. Design no doesn’t exist. Resume at 3.

12. Some of the Classes used

13. Sales ClerkSystem 1. Fill in retailer’s details2. Set up a new order. Record / retrieve retailer’s details 3. Inputs design number4. Retrieve and display garment price, size range and description 5. Input design no, quantity and size6. Write order line with orderno, designno, quantity and size. Write ‘quantity’ new instances of garment with status ‘not started’. Display accumulated price. Display new set of orderliness. 7. Indicate finished8. Enable ‘confirm order’ button. 9. Order confirmed10. Order saved.