Beruflich Dokumente
Kultur Dokumente
for
<Project>
Version 1.0 approved
<CSC207>
<27/8/2009>
Revision History
Name
Date
Version
Copyright 2004 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Page 1
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.
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.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.
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.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.
Page 5
Use Cases
Customer
Waiter
Kitchen Staff
Reservation Database
Order Database
Manage Reservation
Manage Customer Reservation
Manage Order
Update Reservation
Update Orders
Page 6