business analysis & data design itec-630 spring 2008
DESCRIPTION
Business Analysis & Data Design ITEC-630 Spring 2008. Use Case Exercise Solution Professor J. Alberto Espinosa. Practice Example. - PowerPoint PPT PresentationTRANSCRIPT
AUUse Case ExerciseSolution
Professor J. Alberto Espinosa
Business Analysis &Data Design
ITEC-630 Spring 2008
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.
.
33
Context Diagram Example
OrderProcessing
System
Customer
Sales Clerk
PaymentProcessing
System
WarehouseSystem
Place or cancelorders, return merchandise & inquire catalog
Send notificationof delays
Submit clientcheck and credit card payments
Place orcancel order
on behalf of client &
re-ordermerchandise
Re-stocking orders &inquire inventory availability
AccountingSystem
Uploadcustomer
receivables &pre-payments &
inquire aboutcustomer payments
Receiveapprovals
44
Actor Specification Cards
55
Actor Specification
Actor Name: Customer
Type: Primary Personality: Initiator Abstract: 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
66
Actor Specification
Actor Name: Sales Clerk
Type: Primary Personality: Proxy Abstract: 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
77
Actor Specification
Actor Name: Payment Processing System
Type: Secondary Personality: External server Abstract: 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
88
Actor Specification
Actor Name: Accounting System
Type: Secondary Personality: External server Abstract: 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
99
Actor Specification
Actor Name: Warehouse System
Type: Secondary Personality: External server Abstract: 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
1010
Use Case Model
Customer
Sales Clerk
Accounting System
Warehouse System
Payment Processing System
Order Processing System
UC-001 Place WebOrders
UC-002 CancelOrders (Web)
UC-003 ReturnMerchandise (Web)
UC-004 InquireCatalog
UC-005 Place Mail,Fax or Phone Orders
UC-006 Cancel Orders(Mail, Fax, or Phone)
UC-007 ReturnMerchandise (Mail, Fax or Phone)
UC-008 PlaceRe-Stocking Order
UC-009 UpdateAccounting Data
1111
Initial Use Cases
1212
Use Case Specification (shortened)
Use Case ID UC-001
Use Case Place an order directly via web
Actors Customer, Payment Processing System
Description Log 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.
Priority 1
Non-Functional Requirements
Assumptions
Source
1313
Use Case Specification (shortened)
Use Case ID UC-002
Use Case Cancel order directly via web
Actors Customer, Payment Processing System
Description Log on to the web site, enter password, select merchandise purchased, and cancel order, if items have not been shipped yet, reverse charges as needed.
Priority 2
Non-Functional Requirements
Assumptions
Source
1414
Use Case Specification (shortened)
Use Case ID UC-003
Use Case Return merchandise
Actors Customer
Description Log on to the web site, enter password, select merchandise purchased that will be returned, retrieve a return label with a return code
Priority 2
Non-Functional Requirements
Assumptions
Source
1515
Use Case Specification (shortened)
Use Case ID UC-004
Use Case Inquire catalog
Actors Customer, Sales Clerk, Warehouse System
Description Log on to the web site (no password required to inquire catalog), select product category, present product display and price list
Priority 1
Non-Functional Requirements
Assumptions
Source
1616
Use Case Specification (shortened)
Use Case ID UC-005
Use Case Place an order via mail, fax or phone
Actors Sales Clerk
Description Customer 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.
Priority 1
Non-Functional Requirements
Assumptions
Source
1717
Use Case Specification (shortened)
Use Case ID UC-006
Use Case Cancel order via fax, phone or mail
Actors Sales Clerk
Description Customer 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.
Priority 1
Non-Functional Requirements
Assumptions
Source
1818
Use Case Specification (shortened)
Use Case ID UC-007
Use Case Return merchandise via sales clerk
Actors Sales Clerk
Description Customer 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
Priority 1
Non-Functional Requirements
Assumptions
Source
1919
Use Case Specification (shortened)
Use Case ID UC-008
Use Case Re-order merchandise from inventory system
Actors Sales clerk, Warehouse System
Description Enter list of items and quantities to re-order from warehouse with shipping priorities
Priority 3
Non-Functional Requirements
Assumptions
Source
2020
Use Case Specification (shortened)
Use Case ID UC-009
Use Case Update Accounting Data
Actors Accounting System
Description Download 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
Priority 3
Non-Functional Requirements
Assumptions
Source
2121
Base Use Cases
2222
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 catalog2. Pick items to shopping cart3. Indicate quantities for each item4. Proceed to checkout5. Select shipping method6. Perform tax calculation7. Display order details, with shipping and taxes8. Customer OK’s transaction9. Process payment10. Thank you11. 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.
2323
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 option2. Display list of orders placed by client, not shipped yet3. Client selects order to cancel4. Client confirms order cancellation5. Reverse credit card charge or process refund6. Thank you screen7. 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
2424
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 option2. Display list of shipped orders for client, not more than 30 days old3. Client selects order from which to return merchandise4. Client selects specific items to return5. Client confirms items to be returned6. System gives client a return confirmation number7. System gives client a printed label to affix in the return box8. Thank you screen9. 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
2525
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 displayed3. Prompt customer for other display options or exit catalog4. 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
2626
Etc.Other use cases?
2727
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 password2. System verifies that customer is valid3. System matches password entered against password on file4. Authenticate the customer 5. Retrieve basic customer data from files6. Display personalized greeting for the customer7. 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
2828
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 register2. Customer enters required information (name, shipping address, etc.)3. Customer enters password4. Customer submits information5. Display thank you note and successful registration message6. Display option to proceed to log in7. Return to login page
Post-conditions Login page is displayed
Alternative Flows
Priority
Non-Functional Requirements
Assumptions
Source