1. Tutorial SSD

2. 1 Domain: mail order video company Use Case: processing an order Actors: order processing administrator, customer Description: Customer make an order. Then customer request video. The new requested video becomes one line on the order (product number, description, unit price, quantity, price, VAT). The system supply many requested videos. Once the customer finish his order, the system display his/ her receipt.

3. Processing an order SSD : Customer : System MakeOrder() Order Line := *[more items] AddOrderLine(Item ID) Receipt:= FinishOrder()

4. 2 Domain Online EStore. Use Case: Remove item from cart. Actor : customer Description: A customer submits a request for removal to the system. The system displays the cart contents and asks the user to select the item to remove. The user tells the system which item to remove, the system displays the updated cart and the customer receives confirmation from the system that the item has been removed.

5. Remove item from cart SSD : Customer : System RequestRemoveItem( ) Content SelectItem(ItemId) Confirm Deleted Updated Content

6. 3 Actor ActionSystem Response 1.The Sales Person enters customer Details (name, address, phoneNo, customerId) 2. System saves customer information. 3. The Sales Person ends customer registration. Draw the SSD for use case (register a customer)?

7. SSD :System : Sales Person enterCustomer (name, address, phoneNo, cId) Saved customer information endCustomerRegisteration()

8. 4 Draw SSD for the following use case: Use Case: Purchase Tickets with Check. Actors: Customer (initiator), clerk. Purpose: Reserve seats on an airplane and capture their check payment. Overview: A customer arrives at the counter requesting to purchase tickets. The clerk finds a suitable flight and reserves seats on it for him\her. The customer pays for the tickets with check. When done, the customer leaves with purchased tickets.

9. Actor ActionsSystem Response 1. This use case begins when a customer comes to the ticket counter requesting tickets. 2. The clerk asks the customer about the departure city, destination city, and the date and enters them into the system. 3. The system displays the available flights on that date. 4. The clerk then lists the flights to the customer and the customer chooses one. The clerk enters the choice into the system. 5. The system displays the information of only the chosen flight. 6. The clerk asks the customer about the number of passengers and the flight class. The clerk enters this information to the system. 7. The system adds the requested flight information to the running sales transaction. And updates the available seats on the flight. 8. The clerk then asks the customer of any special requests like handicapped access or special meals and enters this information into the system. 9. The system notification the airline of the special requirements for this passenger. 10. The clerk then indicates to the system that data entry is complete. 11. The system calculates the total and presents it to the clerk. 12. The clerk tells the customer the total. 13. The customer writes a check of the total to the travel agency, signs it, and gives it to the clerk. 14. The clerk requests identification and upon receiving it, the clerk enters the ID number into the system and indicates to the system that the customer has paid. 15. The system then prints the tickets and logs the sale. 16. The clerk gives the tickets and a receipt to the customer. 17. The customer leaves with the tickets.

10. :Syste m : Clerk enterCityDate (departure city, destination city,date) available flights chooseFlight (flight) information of chosen flight. enterNoPassengerClass(NoPassengers, class) requested flight information,updated No seats enterSpecialrequest(request) notification of the special requirements isCompleteInfo() total isPaidCustomer ( ID number) tickets and receipt

11. 5

13. Tools for creating UML diags. Violet (free) http://horstmann.com/violet/ UMLet http://www.umlet.com/