Revision History Name Date Reason For Changes Version
Copyright 2004 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. Use Cases for <project> Page 1
1. Guidance for Use Case Template
Document each use case using the template shown in the Appendix. This section provides a description of each section in the use case template.
2. Use Case Identification
2.1. Use Case ID
Give each use case a unique integer sequence number identifier. Alternatively, use a hierarchical form: X.Y. Related use cases can be grouped in the hierarchy.
2.2. Use Case Name
State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples: View part number information. Manually mark hypertext source and establish link to target. Place an order for a CD with the updated software version. 2.3. Use Case History
2.3.1 Created By Page Neo Tao You and Jeffrey Pang Jian Hao
2.3.2 Date Created
27/08/2009
2.3.3 Last Updated By
Supply the name of the person who performed the most recent update to the use case description.
2.3.4 Date Last Updated
Enter the date on which the use case was most recently updated.
3. Use Case Definition
3.1. Actors The customer An actual person that makes an online reservation via the system.
Reservation Database A database that stores the reservation after the customer makes it. Use Cases for <project> Page 2
Waiter An actual person that views the reservations made and can mark the customer as arrived via the system. Order Database A database that stores current orders pending for the kitchen to prepare.
Kitchen Staff An actual person that can view orders and mark order as done via the system.
3.2. Trigger The Customer accesses the system online to make a reservation.
3.3. Description The customer accesses the system online to make a reservation. The reservation will be stored in the reservation database and could be viewed by the waiter. When the customer arrives at the restaurant, the waiter will mark the customer as arrived on the system, and the system will send the order to the order database. The Kitchen staff will be able to view the order, and prepare the order and mark the order as done when completed.
3.4. Preconditions List any activities that must take place, or any conditions that must be true, before the use case can be started. Number each precondition. Examples: 1. Users computer has sufficient free memory available to launch task. 3.5. Postconditions Describe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples: 1. Reservation Database will be updated with the reservation as arrived. 2. Order database will be updated with the order as completed. 3.6. Normal Flow Manage Reservation Make Reservation Select Table.1 Customer selects vacant table from floor plan of restaurant. Select Table.2 Customer enters name and contact details.
Select Order.1 Customer selects dishes to order from online menu.
Select Order.2 Customer confirms order and checks out.
Make Payment.1 Customer selects to pay online or at restaurant.
Make Payment.2 If paying online, direct customer to online payment site. Use Cases for <project> Page 3
Update Reservations.1 Update the reservation database after Manage Reservation is completed.
Manage Customer Reservation
View Customer Reservation.1 Retrieve reservations from reservation database and display.
Mark Customer as arrived.1 indicates customer has arrived, includes Add Customers Order Into Order Database and Update Reservations.
Manage Order View Orders.1 View existing orders to prepare.
Mark Order as done.1 indicate order is completed, includes Update Orders.
Update Orders.1 Update order database when orders are completed.
3.7. Alternative Flows
Manage Reservation Modify Reservation Change Seat.1 Customer selects vacant table from floor plan of restaurant.
Change Order.1 Customer selects dishes to order from online menu.
Change Order.2 Customer confirms order and checks out.
Delete Reservation.1 Reservation deleted from database.
3.8. Exceptions When user tries to modify reservation less than 24hrs to reservation time, error will be displayed.
3.9. Includes Manage Reservation includes Update Reservations.
Mark Customer as Arrived includes Update Reservations and Add Customers Order into Database.
Manage Orders includes Update Orders.
Use Cases for <project> Page 4
3.10. Priority Indicate the relative priority of implementing the functionality required to allow this use case to be executed. The priority scheme used must be the same as that used in the softwarerequirements specification.
3.11. Frequency of Use
Manage Reservation used by Customer 5 times per hour. Manage Customer Reservation used by Waiter 1 time per minute. Manage Order used by Kitchen Staff 1 time per minute.
3.12. Business Rules
List any business rules that influence this use case.
3.13. Special Requirements
Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.
3.14. Assumptions List any assumptions that were made in the analysis that led to accepting this use case into the product description and writing the use case description.
3.15. Notes and Issues
List any additional comments about this use case or any remaining open issues or TBDs (To Be Determineds) that must be resolved. Identify who will resolve each issue, the due date, and what the resolution ultimately is. Use Cases for <project> Page 5
Use Case List
Primary Actor Use Cases
Customer Manage Reservation Waiter Manage Customer Reservation Kitchen Staff Manage Order Reservation Database Update Reservation Order Database Update Orders Use Cases for <project> Page 6
Use Case Template
Use Case ID: Use Case Name: Created By: Last Updated By: Date Created: Date Last Updated:
Actors: Description: Trigger: Preconditions: 1. Postconditions: 1. Normal Flow: 1. Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
