Restaurant Management System

Aim: WH Family Restaurant is a restaurant that provides services such like Dine-in,
Takeaway and delivery (online or on-call). The restaurant has many employees working as
waiters, chefs, cashier, managers and other staff working in the restaurant. Customers come
to the restaurant to either have a meal or for takeaway and also delivery services and in
order to support the smooth services of the restaurant, a database for a restaurant
management system is created.
The aim of this study is to design and develop a database for the restaurant to maintain the
daily functioning of the restaurant smoothly without hindering the providing of a high
quality service to their customers. The objective of this project is to build an electronic
database system using all of the skills and techniques from the restaurant industry ensuring
that no common development mistakes are reproduced. This database maintains the
regular attendance and the details of the employees, the food available and orders of
customers. It also includes a payroll management feature and an online delivery system
Description: In this restaurant, there are many employees working and thereby each
employee will be given an identification card upon joining the restaurant staff. When a
customer comes to the restaurant and orders a meal, a system will be in place to make sure
the customer will receive a hassle free experience. Initially the customer will be identified by
the customer ID (New customers will receive a unique new customer ID). The customer will
be given a menu and will have the option of selecting a meal according to his/her liking and
then will place an order with the waiter. Also if there are any promotions/offers, the
customer will be notified. After confirming the order, the waiter will send the order to the
chef who will be preparing the food. The chef will then call the server when the order is
ready upon which the waiter will serve the meal to the customer. The customer will eat the
ordered meal and then after finishing the meal, they have to pay the bill either by card or
cash, the payment will be accepted by the cashier. Also a delivery system will be in place
almost similar to the usual system in place. When the customer places an order over call or
online there would also have to deliver to the home address of the customer, in order to do
this there will be delivery staff to carry out the job. Also as the customer is ordering
remotely, he will be viewing the menu via an app/ a food delivery platform.
In addition there is an automated stock control system. Here the staff can check the stock
available and if there’s a deficiency in stock, the manager will place an order for more stock
with the supplier. The supplier will provide the stock and will help to manage the necessary
ingredients required for the meals to be prepared. The manager will be solely responsible
for ordering stock and managing the menu & ingredients. Also upon receiving stock, the
stock levels will be updated. Also in order to provide more security, only a few restricted
individuals will have access to the system and in order to maintain this a two code
verification system will be in place. Upon logging in, the user will be asked to verify the
password and an error message will be generated if the password is incorrect.
Table description:
Following are the tables along with constraints used in the restaurant management system
database.
1. STAFF:
This table consists of the details about all the details of the employees such as staff
ID, staff name, address, salary, phone number and date joined to the restaurant.

Constraint: Staff ID will be unique for each employee.

2. CUSTOMER
This table consists of details such as customer ID, customer name, phone number,
address, and loyalty details. The records in this table will be updated whenever when
a customer places an order. For new customers, a customer ID will be generated and
their details will be stored in this table. For existing customers, whenever they place
an order the loyalty details gets updated.

Constraint: Customer ID is unique for each customer

3. ORDER
The record in this table will be created when a customer comes to the restaurant
(Dine-in and takeaway) or when a customer orders remotely (online or on-call).
Details like customer ID from customer table, order ID and order details are
generated and table number is entered for dine-in orders.

Constraint: Order Id is unique for each order received. Also Customer ID from the
customer table is also be generated and it should be unique.

4. MEAL
When an order is received, it is sent to the kitchen for preparation. Each meal will
have a meal ID, meal name, price, quantity and availability. Also order ID is included
as each meal is prepared and served based on the order received.

Constraint: Meal ID is the ID included for each dish in the menu and it is unique. Also
order ID will be generated from the order table.

5. INGREDIENTS
In order to prepare a meal, ingredients are needed and thereby an inventory must
be maintained for this as well. This table will contain the details such as ingredient
code, ingredient name, available stock and the meal ID.

Constraint: Ingredient code is unique and meal ID should also be included and it is
generated from the meal table.
6. SUPPLIER
This table contains details such as supplier ID, supplier name/business, details of
supplier. As the supplier provides ingredients, the ingredient code will also be
included.

Constraint: Supplier ID is unique and also ingredient code from the ingredients table
included should also be valid. This table will be updated only when stock is provided
by the supplier.

7. PAYMENT
Details such as receipt number, amount, type of payment (cash/card) and the status
of payment will be displayed in this table. Also customer ID and meal ID details are
included in order to find the amount and apply offers/promotions if available.

Constraint: Receipt number is generated for each order and the customer ID and
order ID included should be valid. Also based on the customer ID, the loyalty details
in the customer table will be updated.

8. DELIVERY
As a restaurant striving to promote their business especially in these uncertain times,
this restaurant will have a delivery section for a certain area of their locale.
Customers will have the option of ordering over the phone or through a delivery app.
The records for this table would contain the order ID, delivery type (online or on-
call), delivery address, and the delivery employee/staff. Also customer ID is included.

Constraint: Order ID included should be unique and customer ID generated from the
customer table should be valid.