Presentation is loading. Please wait.

Presentation is loading. Please wait.

A U Use Case Exercise Solution Professor J. Alberto Espinosa Business Analysis & Data Design ITEC-630 Spring 2008.

Similar presentations


Presentation on theme: "A U Use Case Exercise Solution Professor J. Alberto Espinosa Business Analysis & Data Design ITEC-630 Spring 2008."— Presentation transcript:

1 A U Use Case Exercise Solution Professor J. Alberto Espinosa Business Analysis & Data Design ITEC-630 Spring 2008

2 22 Practice Example We need to develop an order-processing system for a mail-order company that sells musical instruments of all sorts. Currently, the company has a paper catalog from which customers phone in or fax their orders and orders are only taken by hand. The proposed system should automate this process. It needs to allow customers to place orders by mail, phone, fax or directly through the web. Customers can pay with a money order or credit card. Customers can buy multiple items in various quantities with a single order. The system needs allow sales clerks to monitor the status of order fulfillment and notify customers when delays are anticipated. The system also needs to handle returns and cancellations. The system needs to interface with three existing external systems: (1) a Warehouse System – to send re-stocking orders to the central warehouse when necessary and to inquire about stock availability; (2) an Accounting System – to record customer receivables and pre-payments and inquire about customer payments; and (3) a Payment Processing system to process all charge card transactions..

3 33 Context Diagram Example Order Processing System Customer Sales Clerk Payment Processing System Warehouse System Place or cancel orders, return merchandise & inquire catalog Send notification of delays Submit client check and credit card payments Place or cancel order on behalf of client & re-order merchandise Re-stocking orders & inquire inventory availability Accounting System Upload customer receivables & pre-payments & inquire about customer payments Receive approvals

4 44 Actor Specification Cards

5 55 Actor Specification Actor Name: Customer Type: PrimaryPersonality: InitiatorAbstract: No Role Description: It’s a person that wishes to place orders or cancel them Actor Goals:  Purchase items  Cancel orders  Inquire catalog  Return items Use Cases Involved with :  Purchase items  Cancel orders  Inquire catalog  Return items

6 66 Actor Specification Actor Name: Sales Clerk Type: PrimaryPersonality: ProxyAbstract: No Role Description: It’s a person that communicates with the customer when they are placing orders over the phone or via mail. This actor enters customers’ transactions on the system on their behalf, so this actor’s goals are the same as the customer’s goals Actor Goals:  Purchase items  Cancel orders  Inquire catalog  Return items Use Cases Involved with :  Purchase items  Cancel orders  Inquire catalog  Return items

7 77 Actor Specification Actor Name: Payment Processing System Type: SecondaryPersonality: External serverAbstract: No Role Description: This system is part of an existing payment system being updated to handle credit card and money order payments Actor Goals:  None  Use Cases Involved with :  Purchase items  Cancel orders  Return merchandise 

8 88 Actor Specification Actor Name: Accounting System Type: SecondaryPersonality: External serverAbstract: No Role Description: This system is part of the existing accounting system which will receive information about receivables, payments and pre-payments to update the company’s books Actor Goals:  None  Use Cases Involved with :  Purchase items  Cancel orders  Return merchandise 

9 99 Actor Specification Actor Name: Warehouse System Type: SecondaryPersonality: External serverAbstract: No Role Description: This system is part of the existing supply chain management system that manages the procurement of products and the company’s inventory. Actor Goals:  None  Use Cases Involved with :  Re-Stock Inventory 

10 10 Use Case Model

11 11 Initial Use Cases

12 12 Use Case Specification (shortened) Use Case IDUC-001 Use CasePlace an order directly via web ActorsCustomer, Payment Processing System DescriptionLog on to the web site, enter password, select merchandise, place in shopping cart, pick more items, proceed to checkout, select payment method, process payment, exit. Priority1 Non-Functional Requirements Assumptions Source

13 13 Use Case Specification (shortened) Use Case IDUC-002 Use CaseCancel order directly via web ActorsCustomer, Payment Processing System DescriptionLog on to the web site, enter password, select merchandise purchased, and cancel order, if items have not been shipped yet, reverse charges as needed. Priority2 Non-Functional Requirements Assumptions Source

14 14 Use Case Specification (shortened) Use Case IDUC-003 Use CaseReturn merchandise ActorsCustomer DescriptionLog on to the web site, enter password, select merchandise purchased that will be returned, retrieve a return label with a return code Priority2 Non-Functional Requirements Assumptions Source

15 15 Use Case Specification (shortened) Use Case IDUC-004 Use CaseInquire catalog ActorsCustomer, Sales Clerk, Warehouse System DescriptionLog on to the web site (no password required to inquire catalog), select product category, present product display and price list Priority1 Non-Functional Requirements Assumptions Source

16 16 Use Case Specification (shortened) Use Case IDUC-005 Use CasePlace an order via mail, fax or phone ActorsSales Clerk DescriptionCustomer communicates with sales clerk via phone or sales clerk receives customer order via fax or mail, select merchandise ordered by the client, enter payment method and payment information. Priority1 Non-Functional Requirements Assumptions Source

17 17 Use Case Specification (shortened) Use Case IDUC-006 Use CaseCancel order via fax, phone or mail ActorsSales Clerk DescriptionCustomer communicates with sales clerk via phone or sales clerk receives customer cancellation order via fax or mail, select merchandise purchased, and cancel order if items have not been shipped yet. Priority1 Non-Functional Requirements Assumptions Source

18 18 Use Case Specification (shortened) Use Case IDUC-007 Use CaseReturn merchandise via sales clerk ActorsSales Clerk DescriptionCustomer communicates with sales clerk via phone or sales clerk receives customer merchandise return request via fax or mail, select merchandise purchased to be returned, print a return label with a return code, mail to customer Priority1 Non-Functional Requirements Assumptions Source

19 19 Use Case Specification (shortened) Use Case IDUC-008 Use CaseRe-order merchandise from inventory system ActorsSales clerk, Warehouse System DescriptionEnter list of items and quantities to re-order from warehouse with shipping priorities Priority3 Non-Functional Requirements Assumptions Source

20 20 Use Case Specification (shortened) Use Case IDUC-009 Use CaseUpdate Accounting Data ActorsAccounting System DescriptionDownload data from the system into the external Accounting System (i.e., receivables and pre-payments) and upload data from the external accounting system on customer payments Priority3 Non-Functional Requirements Assumptions Source

21 21 Base Use Cases

22 22 Use Case ID UC-001 Use Case Place an order via web site Actors Customer, Payment Processing System Description Purchase Pre-conditions Customer has registered, customer logged in, main menu is displayed Flow of Events 1. Browse catalog 2. Pick items to shopping cart 3. Indicate quantities for each item 4. Proceed to checkout 5. Select shipping method 6. Perform tax calculation 7. Display order details, with shipping and taxes 8. Customer OK’s transaction 9. Process payment 10. Thank you 11. Return to home page Post-conditions Main menu is displayed, log out customer after 20 min or inactivity Alternative Flows Allow for different shipping destinations Etc.

23 23 Use Case ID UC-002 Use Case Cancel order directly via web Actors Customer, Payment Processing System Description Customer selects an order not shipped yet and cancels it Pre-conditions Customer has registered, customer logged in, main menu is displayed Flow of Events 1.Select cancel order option 2.Display list of orders placed by client, not shipped yet 3.Client selects order to cancel 4.Client confirms order cancellation 5.Reverse credit card charge or process refund 6.Thank you screen 7.Return to home page Post- conditions Main menu is displayed, log out customer after 20 min or inactivity Alternative Flows Priority Non-Functional Requirements Assumptions Source

24 24 Use Case ID UC-003 Use Case Return Merchandise Actors Customer Description Customer selects an order already shipped, requests a merchandise return, and gets a return reference number and label Pre-conditions Customer has registered, customer logged in, main menu is displayed Flow of Events 1.Select return merchandise option 2.Display list of shipped orders for client, not more than 30 days old 3.Client selects order from which to return merchandise 4.Client selects specific items to return 5.Client confirms items to be returned 6.System gives client a return confirmation number 7.System gives client a printed label to affix in the return box 8.Thank you screen 9.Return to home page Post-conditions Main menu is displayed, log out customer after 20 min or inactivity Alternative Flows Priority Non-Functional Requirements Assumptions Source

25 25 Use Case ID UC-004 Use Case Inquire Catalog Actors Customer, Sales Clerk, Warehouse System Description Customer or sales clerk browse product catalog on-line Pre-conditions Customer has registered, customer logged in, main menu is displayed Flow of Events 1.Display catalog browsing options (by brand, type, price, etc.) 2.Product catalog is displayed 3.Prompt customer for other display options or exit catalog 4.Return to home page when exit option is chosen Post-conditions Main menu page is displayed, log out customer after 20 min or inactivity Alternative Flows Priority Non-Functional Requirements Assumptions Source

26 26 Etc. Other use cases?

27 27 Use Case ID UC-010 Use Case Log in Actors Customer, Sales Clerk Description Customer or sales clerk log into the system and get authenticated Pre-conditions Login page is displayed when the customer accesses the system Flow of Events 1.Customer enters ID and password 2.System verifies that customer is valid 3.System matches password entered against password on file 4.Authenticate the customer 5.Retrieve basic customer data from files 6.Display personalized greeting for the customer 7.Display home page Post-conditions Main menu is displayed, log out customer after 20 min or inactivity Alternative Flows Priority Non-Functional Requirements Assumptions Source

28 28 Use Case ID UC-011 Use Case Register Actors Customer, Sales Clerk Description New customer registers in the system, or sales clerk does the same on his/her behalf Pre-conditions Login page is displayed (it contains option to register for new customers) Flow of Events 1.Customer selects option to register 2.Customer enters required information (name, shipping address, etc.) 3.Customer enters password 4.Customer submits information 5.Display thank you note and successful registration message 6.Display option to proceed to log in 7.Return to login page Post-conditions Login page is displayed Alternative Flows Priority Non-Functional Requirements Assumptions Source


Download ppt "A U Use Case Exercise Solution Professor J. Alberto Espinosa Business Analysis & Data Design ITEC-630 Spring 2008."

Similar presentations


Ads by Google