RUseCase

Advance booking
Use Case Name: Restaurant Booking System Scenario: Advanced Booking Trigger: Someone decides they want to make a booking, calls restaurant Actors: Customer, receptionist Brief Description: Requirements (date, time, number in party) given to the receptionist who checks if they are available, and books the table if they are. Flow Of Activities: 1. Customer calls the restaurant. 2. Receptionist logs in. 3. Requirements given. 4. Receptionist checks if an appropriate table is available. 5. Yes or no. Successful: Table booked. Alternative: Transaction cancelled. Pre-Condition: Customer wants to book a table. Post-Condition: Customer has booked a table. Assumptions: Receptionist is available to take the request. Jake Briggs - 10/02/14



Delete user
Use Case Name: Restaurant Booking System Scenario: Delete User Trigger: A user in the system no longer works for the restaurant Actors: Administrator Brief Description: User is removed from the system. Flow Of Activities: 1. Administrator logs in. 2. Finds specific user. 3.Deletes user. Successful: User removed. Alternative: User could not be found. Pre-Condition: Someone needs to be removed from the system. Post-Condition: Someone has been removed from the system. Assumptions: Administrator knows who to remove. Jake - 10/02/15