Use Case Table:

Use Case: View Menu

Field Description
Use Case Name View Menu
Actor(s) Customer
Preconditions The system has an updated menu with available items.
Post conditions The customer successfully views the menu.
Main Flow 1. The customer selects "View Menu" from the system.
2. The system retrieves and displays the available menu items, including
descriptions and prices.
3. The customer browses the menu categories (e.g., appetizers, main courses,
desserts, beverages).
4. The customer can view details of a specific item (e.g., ingredients,
calories).
Alternative If the customer wants, they can filter menu items by category, price, or
Flow dietary preferences.
Exception Flow If the system fails to retrieve the menu, it displays an error message and
suggests retrying later.

Use Case: Place Order

Field Description
Use Case Name Place Order
Actor(s) Customer, Waiter
Preconditions The customer has viewed the menu and selected items.
Post conditions The order is successfully recorded in the system and sent to the kitchen.
Main Flow 1. Customer selects items from the menu.
2. Customer confirms the order.
3. Waiter (optional) enters the order into the system.
4. System records the order and forwards it to the kitchen.
5. Order status is updated to "In Progress."
Alternative If the customer modifies the order before confirmation, the system updates
Flow the selection.
Exception Flow If the system encounters an error, it prompts the user to retry.

Use Case: Pay Bill

Field Description
Use Case Name Pay Bill
Actor(s) Customer, Waiter
Preconditions The order must be completed and ready for billing.
Post conditions Payment is successfully processed, and the bill is marked as paid.
Main Flow 1. Customer requests the bill.
2. System generates the bill.
3. Customer selects a payment method.
4. System processes the payment.
5. System confirms the payment and updates order status.
Alternative If the customer splits the bill, the system divides the amount accordingly.
Flow
Exception Flow If payment fails, the system prompts for another payment method.

Use Case: Manage Inventory

Field Description
Use Case Name Manage Inventory
Actor(s) Manager
Preconditions The inventory module must be active in the system.
Post conditions Inventory levels are updated and recorded.
Main Flow 1. Manager logs into the system.
2. Manager selects the inventory management option.
3. System displays current inventory levels.
4. Manager updates stock levels or adds new items.
5. System records changes and updates reports.
Alternative If the manager wants to generate an inventory report, the system provides it.
Flow
Exception Flow If an item is out of stock, the system alerts the manager.

Use Case: Serve Food

Field Description
Use Case Name Serve Food
Actor(s) Waiter
Preconditions The food is prepared and ready to be served.
Post conditions The customer receives the ordered food.
Main Flow 1. The system notifies the waiter that the food is ready.
2. The waiter picks up the order.
3. The waiter serves the food to the customer.
4. The system updates the order status to "Served."
Alternative If the customer requests additional condiments, the waiter provides them
Flow before marking the order as "Served."
Exception Flow If the wrong order is served, the system allows order corrections.
Use Case: Manage Staff

Field Description
Use Case Name Manage Staff
Actor(s) Manager
Preconditions The manager must be logged into the system.
Postconditions Staff records are updated.
Main Flow 1. Manager selects the "Manage Staff" option.
2. System displays staff details.
3. Manager can add, edit, or remove staff.
4. System updates the staff database.
Alternative Flow If a staff member is promoted, the system updates their role accordingly.
Exception Flow If an incorrect staff record is deleted, the system prompts for confirmation.

Use Case: Handle Reservations

Field Description
Use Case Name Handle Reservations
Actor(s) Customer, Manager
Preconditions The system must have available tables.
Post conditions The reservation is confirmed and stored in the system.
Main Flow 1. Customer requests a table reservation.
2. The system checks table availability.
3. Customer selects a date, time, and number of guests.
4. The system confirms and stores the reservation.
Alternative Flow If a customer cancels a reservation, the system frees up the table.
Exception Flow If no tables are available, the system suggests alternative time slots.

Use Case: Generate Bill

Field Description
Use Case Name Generate Bill
Actor(s) Waiter, Customer
Preconditions The customer has completed their meal, and all orders are recorded.
Post conditions The bill is generated and presented to the customer.
Main Flow 1. The customer requests the bill.
2. The waiter selects "Generate Bill" in the system.
3. The system retrieves the order details and calculates the total.
4. The system generates the bill and displays it.
5. The waiter presents the bill to the customer.
Alternative If a customer wants to split the bill, the system calculates individual amounts
Flow accordingly.
Exception Flow If there is an incorrect charge, the system allows adjustments before
finalizing the bill.
Use Case: Process Payment

Field Description
Use Case Name Process Payment
Actor(s) Customer, Waiter
Preconditions The bill is generated and provided to the customer.
Post conditions Payment is completed, and the system records the transaction.
Main Flow 1. The customer selects a payment method (cash, card, digital wallet).
2. The waiter inputs the payment details.
3. The system verifies the payment.
4. The system updates the transaction record.
5. The system generates a payment confirmation receipt.
Alternative If a discount or coupon is applied, the system recalculates the total before
Flow payment.
Exception Flow If the payment fails, the system prompts for an alternative payment method.

Use Case: Customer Feedback Submission

Field Description
Use Case Name Customer Feedback Submission
Actor(s) Customer
Preconditions The customer has completed their dining experience.
Post conditions The feedback is recorded in the system for analysis.
Main Flow 1. The customer accesses the feedback form via the app or waiter-provided
link.
2. The system presents a form with rating and comment fields.
3. The customer enters ratings and comments.
4. The system saves the feedback for future analysis.
Alternative If the customer chooses not to submit feedback, the system simply logs the
Flow visit.
Exception Flow If an issue occurs during feedback submission, the system notifies the
customer to try again later.

Use Case: Reserve Table

Field Description
Use Case Name Reserve Table
Actor(s) Customer, Manager
Preconditions The restaurant has available tables.
Post conditions The table is successfully reserved for the customer.
Main Flow 1. The customer selects "Reserve Table" from the app or calls the restaurant.
 2. The system displays available tables and time slots.
3. The customer selects a preferred date, time, and table size.
4. The system confirms the reservation and provides a booking reference.
5. The manager receives the booking details.
Alternative If no table is available, the system suggests alternate times.
Flow
Exception Flow If the reservation system is down, the customer is asked to call the restaurant
directly.

Use Case: Manage Inventory

Field Description
Use Case Name Manage Inventory
Actor(s) Manager, Chef
Preconditions The system is connected to the restaurant’s inventory database.
Post conditions The inventory levels are updated.
Main Flow 1. The manager or chef logs into the inventory system.
2. The system displays current stock levels.
3. The manager adds, removes, or updates ingredient quantities.
4. The system automatically updates stock records.
5. If stock is low, the system generates a reorder request.
Alternative The system suggests alternative ingredients if a stock item is unavailable.
Flow
Exception Flow If the system cannot connect to the inventory database, it displays an error.

Use Case: Notify Customers About Offers

Field Description
Use Case Name Notify Customers About Offers
Actor(s) Manager, System
Preconditions Customers have opted in for notifications.
Post conditions Notifications about special offers are sent.
Main Flow 1. The manager creates a special offer or discount in the system.
2. The system fetches a list of subscribed customers.
3. The system sends promotional notifications via SMS, email, or app alerts.

4. Customers receive and view the offers.

Alternative Flow The system can schedule notifications to be sent at a later time.
Exception Flow If a customer un subscribes, they no longer receive notifications.

Use Case: Handle Customer Feedback

 Field Description
Use Case Name Handle Customer Feedback
Actor(s) Customer, Manager
Preconditions The customer has used the restaurant service.
Post conditions The feedback is recorded and stored in the system.
Main Flow 1. The customer selects "Give Feedback" in the app or website.
2. The system prompts for rating and comments.
3. The customer submits feedback.
4. The system stores the feedback.
5. The manager reviews feedback and responds if necessary.
Alternative Flow The manager can filter feedback based on ratings or keywords.
Exception Flow If the system is down, feedback cannot be submitted.

Use Case: Generate Sales Report

Field Description
Use Case Name Generate Sales Report
Actor(s) Manager, System
Preconditions The system has recorded sales transactions.
Post conditions A detailed sales report is generated.
Main Flow 1. The manager selects "Generate Sales Report."
2. The system retrieves data from the database.
3. The system calculates total sales, revenue, and expenses.
4. The system generates a report.
5. The manager reviews and downloads the report.
Alternative Flow The manager can filter reports by date, category, or staff performance.
Exception Flow If the system cannot access sales data, an error is displayed.

Use Case: Process Online Payment

Field Description
Use Case Name Process Online Payment
Actor(s) Customer, System, Payment Gateway
Preconditions The customer has placed an order.
Post conditions The payment is successfully processed.
Main Flow 1. The customer selects "Pay Online."
2. The system redirects to a payment gateway.
3. The customer enters payment details.
4. The payment gateway verifies and approves the transaction.
5. The system confirms payment and updates the order status.
Alternative If the customer has saved payment details, they can use them for faster
Flow checkout.
Exception Flow If the payment fails, the system prompts the user to retry or use another
payment method.

Use Case: Manage Table Reservations

Field Description
Use Case Name Manage Table Reservations
Actor(s) Customer, Manager, System
Preconditions The system has available tables.
Post conditions A reservation is confirmed and stored in the system.
Main Flow 1. The customer selects "Reserve Table" from the system.
2. The system displays available tables and time slots.
3. The customer selects a date, time, and number of guests.
4. The system confirms the reservation and generates a booking ID.

5. The manager can view and modify reservations if needed.

Alternative Flow The customer can modify or cancel the reservation.
Exception Flow If no tables are available, the system suggests alternative time slots.

Use Case: Manage Employee Shifts

Field Description
Use Case Name Manage Employee Shifts
Actor(s) Manager, System, Staff
Preconditions The system has staff records.
Post conditions The shift schedule is updated and visible to staff.
Main Flow 1. The manager selects "Manage Shifts."
2. The system displays the current shift schedule.
3. The manager assigns staff to shifts.
4. The system notifies staff of their assigned shifts.
5. Employees can view their schedule.
Alternative The manager can swap or edit shifts if needed.
Flow
Exception Flow If an employee calls in sick, the manager is notified to find a replacement.

Use Case: Track Inventory and Restock Items

Field Description
Use Case Name Track Inventory and Restock Items
Actor(s) Manager, System
Preconditions The restaurant has inventory items stored in the system.
Post conditions The inventory is updated, and restocking orders are placed if needed.
Main Flow 1. The manager selects "View Inventory."
2. The system displays current stock levels.
3. The system alerts the manager if stock is low.
4. The manager places a restocking order.
5. The system updates the inventory after restocking.
Alternative The system can auto-generate restocking orders when stock is below a
Flow threshold.
Exception Flow If the supplier is unavailable, the manager must manually find an alternative
source.