Use Case Diagram for the Restaurant Management System

Let’s build the use case diagram for the restaurant management system and understand the relationship between its different components. First, we’ll define the different elements of our restaurant, followed by the complete use case diagram of the system.

System

Our system is a restaurant management system.

Actors

Let’s define the main actors of our restaurant management system.

Primary actors

• Customer: This is the restaurant’s primary actor who can view the menu, place orders, make a reservation, and make payments.

• Receptionist: This actor is responsible for reserving tables and updating the table reservation status.

• Server: This actor takes the order from the customer and processes the payment.

• Manager: This actor manages each branch’s menu and table configuration.

Secondary actor

• System: This can automatically notify customers when their reservation time approaches and update table statuses whenever a bill is paid or a reservation is made.

Use cases

This section will define the restaurant management system’s use cases. We’ve listed them according to their respective interactions with a particular actor.

Customer

• View menu: To browse food items and prices.

• Make reservation: To book a table.

• Cancel reservation: To cancel an existing reservation.

• Place order: To order food.

• View order: To check order status or details.

• Receive notification: To receive a notification when the reservation time approaches.

• Pay bill: To complete payment using cash or a card.

• Search available tables: To check real-time table availability.

• Request Bill Details: To get the details to pay the bill.

Manager

• Add/modify menu section: To manage food categories.

• Add/modify menu item: To manage individual food items.

• Add/update table configuration: To define branch-specific table layouts.

• View menu: To access the menu for decision-making or management.

Receptionist

• Search available tables: To check real-time table availability.

• Make reservation: To book a table for a customer.

• Cancel reservation: To cancel an existing reservation.

• Receive notification: To receive notification when a reservation time approaches.

• Modify reservation: To modify an existing reservation.

Server

• View menu: To assist with customer ordering.

• Take order: To take and enter customer orders.

• Fetch order list: To view assigned or active orders.

• Replace meal item: To substitute an item in an existing order.

• Generate bill: To calculate the total bill against the food order.

System

• Send notifications: To automatically notify customers when their reservation time approaches.

• Update table statuses: To handle automatic updates of table availability.

Relationships

This section describes the relationships between and among actors and their use cases.

Associations

The table below shows the association relationship between actors and their use cases.