Ministry of Higher Education

Balkh University
Computer Science Faculty

Restaurant Management System

(RMS)

2024

Mentor: Mr. Naqibullah Alizada

Prepared: Khurshid Group
Abstract
The Restaurant Management System Database is a comprehensive system solution suitable for
efficient management of a restaurant's operations. By integrating features for handling food
inventory, employee management, customer interactions, and financial transactions, this system
aims to enhance productivity, accuracy, and profitability. Daily reporting capabilities enable
restaurant owners and managers to gain valuable insights into their business.
Design and develop a Restaurant Management System to streamline the operations and enhance
efficiency for both staff and customers. The system should provide a user-friendly interface for
managing orders, inventory, and employee schedules, while also facilitating seamless
communication between kitchen staff, waitstaff, and management.
We divided the requirements of our project into functional requirements and non-functional
requirements. And the tools that we used in our project are phpMyAdmin, MySQL, JDK, IntelliJ,
scene builder, computer, and Día for logical design of the project.

It's a special tool that helps make running a restaurant much easier. Choosing the write features
for this restaurant management system is according to the market. We chose and considered
these requirements for RMS to satisfy all the market needs,
Order management: Making it easy to take orders from customers and send them to the kitchen.

2
Table of Contents
Chapter 1 ...................................................................................................................................................... 5
Introduction .................................................................................................................................................. 5
1.1 Background .................................................................................... Error! Bookmark not defined.
1.2 Problem Statement ....................................................................... Error! Bookmark not defined.
1.3 Motivation ..................................................................................... Error! Bookmark not defined.
1.4 Requirement Specification ........................................................................................................... 7
1.5 Customer and Stockholder........................................................................................................... 7
1.5.1 customer ............................................................................................................................... 7
1.5.2 Stockholder ........................................................................................................................... 7
1.6 Team Members and Roles ........................................................................................................... 7
1.7 SWOT ANALYSIS ........................................................................................................................... 8
Chapter 2 ...................................................................................................................................................... 9
Literature Review ......................................................................................................................................... 9
2.1 Introduction ................................................................................................................................ 10
2.2 Restaurant management System (RMS) Strategy ..................................................................... 10
2.2.1 RMS for Manger ................................................................................................................. 10
2.3 Related work .............................................................................................................................. 10
2.3.1 Restaurant Reservation Software (RRS): ........................................................................... 10
2.3.2 Point of Sale System (POS): ................................................................................................ 10
2.3.3 Inventory Management Software (IMS): .......................................................................... 11
2.3.4 Restaurant Accounting Software (RAS): ............................................................................ 11
2.3.5 Comparison............................................................................ Error! Bookmark not defined.
2.4 Conclusion .................................................................................................................................. 12
Chapter 3 .................................................................................................................................................... 13
Methodology .............................................................................................................................................. 13
3 Introduction .................................................................................................................................... 14
3.1 methodology .............................................................................................................................. 14
3.2 prototype model ........................................................................................................................ 14
3.2.1 Advantages of Prototyping ................................................................................................ 14

3
 3.2.2 Process of Prototyping ....................................................................................................... 15
3.3 Reason of Using Prototype Model ............................................................................................. 15
3.4 Project Management.................................................................................................................. 16
3.4.1 Project plan......................................................................................................................... 16
3.5 Conclusion .................................................................................................................................. 16
Chapter 4 .................................................................................................................................................... 17
Design and Implementation ...................................................................................................................... 17
4 Introduction .................................................................................................................................... 18
4.1 Requirement Specification ......................................................................................................... 18
4.2 System design and architecture:................................................................................................ 18
4.2.1 ER Diagram Model .............................................................................................................. 18
4.3 Implementation phases ............................................................................................................. 19
5 Testing............................................................................................................................................. 23
5.1 Functionality and Performance Testing..................................................................................... 23
Chapter 5 .................................................................................................................................................... 24
Conclusion and Future Word ..................................................................................................................... 24
6 Conclusion ...................................................................................................................................... 25
6.1 Future work ................................................................................................................................ 25

Tables

table 1:stockholder table. ............................................................................................................................ 7

table 2: team members and role table. ....................................................................................................... 8
table 3: comparison table with related work............................................................................................. 12

Images

image 1: this image belongs to order page of RMS. ................................................................................... 20

image 2: employees page of RMS. .............................................................................................................. 20
image 3: Food page of RMS. ....................................................................................................................... 20
image 4:Drink page of RMS......................................................................................................................... 21
image 5:this image is about incomes .......................................................................................................... 21
image 6: sales order page of RMS............................................................................................................... 22
image 7 : consumption page of RMs. ......................................................................................................... 22

figure 1: this figure shoes the process of implementation phases; ............................................................ 19

4
 Chapter 1
Introduction

5
1.1 Introduction
The Restaurant Management System Database is designed to streamline the operations
of a restaurant by efficiently managing information about food items, employees, customers, and
financial transactions. It aims to automate tasks such as order management, inventory tracking,
and generating daily reports to optimize the restaurant's performance and enhance customer
satisfaction.

The Restaurant Management System Database is a comprehensive system solution suitable for
efficient management of a restaurant's operations. By integrating features for handling food
inventory, employee management, customer interactions, and financial transactions, this system
aims to enhance productivity, accuracy, and profitability. Daily reporting capabilities enable
restaurant owners and managers to gain valuable insights into their business performance.

Restaurant management database system is for khateraha restaurant. This database system
saves the entire information about foods, employees, customers, and calculate all incomes,
consumes, and make daily, and monthly reports of all incomes and consumptions. We have
decided to make this project for managing the Khateraha restaurant need to have a database
system for store, search, manage and process the information easily.

1.2 Problem Statement

Design and develop a Restaurant Management System to streamline the operations and
enhance efficiency for both staff and customers. The system should provide a user-friendly
interface for managing orders, inventory, reservations, and employee schedules, while also
facilitating seamless communication between kitchen staff, waitstaff, and management.

Key features should include order management, table management, inventory tracking,
employee management, reporting, and customer feedback integration. The goal is to improve
overall workflow, optimize resource utilization, reduce time consumption, and enhance the
dining experience for customers.

1.3 Motivation
The motivation behind developing a Restaurant Management System start from the
need to address various challenges faced by restaurant owners and staff in day-to-day
operations.

These challenges include inefficient order processing, inventory mismanagement, difficulties in

table management, scheduling conflicts, Additionally, with the increasing demand for dining-

6
experiences that are both efficient and enjoyable, there is a growing need for technology
solutions that can streamline restaurant operations and enhance customer satisfaction.

To meet these needs, the Restaurant Management System aims to provide a comprehensive
platform that automates and simplifies various tasks, such as order taking, inventory tracking,
table reservations, and employee scheduling.

By implementing this system, restaurant owners can optimize their workflow, minimize
problems, reduce operational costs, and ultimately improve the overall dining experience for
their customers.

1.4 Requirement Specification

Requirement specification is one of the most important part in a project to make a good
and most effective project. We divided the requirements of our project into functional
requirements and non-functional requirements. And the tools that we used in our project are
phpMyAdmin, MySQL, JDK, IntelliJ, scene builder, computer, and Día for logical design of the
project.

1.5 Customer and Stockholder

1.5.1 customer
We considered Khateraha Restaurant as customer first, it is a best suggestion to all, such
restaurants to use our project. Our project is not just a specific database whether it is a good and
totally complete database management system.

1.5.2 Stockholder

Stockholder Interested in

khatiraha Restaurant Database is designed to streamline the operations.

Developers Supported and encouraged

table 1:stockholder table.

1.6 Team Members and Roles

This project was created by a team of 7th grade students of Balkh University of computer
science to provide and make a better solution for management such operations. Database
management system project is a class activity project that has a project’s supervisor Mr.
Naqibullah Alizada. The members of this project consist of five students of Balkh University of
computer science faculty, every member of our team played deferent roles as following;

7
 ID Name Roles Topic
98-10-097 Mohammad Main page UI Design
Manager
Hussain
99-10-095 Sajjad Member Select Data from database and java Code
98-10-028 Mohammad Fetrat Member MySQL Database Design
98-10-0 Ali Mohammad Member Insert data to database java Code
98-10-0 Elias Member Insert new food and drink Ul
table 2: team members and role table.

1.7 SWOT ANALYSIS

S W O T
SRENGTH WEAKNESS OPPORTUNATY TREATS
❖ Provide best ❖ Do not ❖ Similar ❖ Changing the
way of support the database customer
calculating the attendances management attitudes about
incomes. of system might this Database
❖ Show all the employee. be available management
soled items, ❖ Do not print but not System
individuality the bill of secure and ❖ It needs to
and generally. soled items. efficient. develop and
❖ It is an think on it more
❖ user will be emerging deeply and add
authenticating need in our some more
when they are idea. properties to
going to use ❖ It is an provide more
database. emerging comprehensive
need in our software.
society.
Table 4: table of SWOT analysis.

8
 Chapter 2
Literature Review

9
2.1 Introduction
This chapter identify the concepts of restaurant management system, owner,
Customers, and staff. Also review the related work with it.

2.2 Restaurant management System (RMS) Strategy

A Restaurant Management System (RMS) is like having a magical helper for restaurant
owners and staff. It's a special tool that helps make running a restaurant much easier.
Choosing the write features for this restaurant management system is according to the market.
We chose and considered these requirements for RMS to satisfy all the market needs,
Order management: Making it easy to take orders from customers and send them to the kitchen.
Inventory tracking: Keeping track of what ingredients and supplies you have in stock.
Table reservations: Helping manage reservations and seating arrangements.
Employee scheduling: Making it easy to create schedules for your staff.
Reporting: Generating reports to see how your restaurant is doing financially and operationally.

2.2.1 RMS for Manger

- Manger has full control to manage this restaurant management system, can see all the
reports of incomes, consumptions, expenses and purchases. Manger is able to add, and
delete employees, see orders, close items stock.

2.3 Related work

2.3.1 Restaurant Reservation Software (RRS):
Using restaurant reservation software makes your day-to-day operation very easier and
creates a better user experience for your guests.
Features:

o Easily make reservations online.

o Manage inventory more efficiently.
o Allows you to allocate a certain number of tables for reservations to prevent
overbooking.
o Stores guest information to allow for future marketing activities such as emails,
or alerts on special occasions (birthdays and anniversaries).

2.3.2 Point of Sale System (POS):

Restaurant POS systems are one the most powerful forms of a restaurant
management system. POS systems act as a computer/cash register hybrid, with the

10
 ability to process credit card payments, print receipts, display information on a user-
friendly screen and operate as a service station.

Features:

o Ability to calculate cash for each order entered throughout the day.
o Make note of cash in and cash out.
o Create sales reports for various periods of time.
o Record payment methods of each guest.

2.3.3 Inventory Management Software (IMS):

Inventory Software automating the process, restaurants have more time to focus
on running their business rather than completing menial tasks and are guaranteed the
right stock at the right time. It helps you track ingredient usage, calculate recipe costs,
and monitor food waste.

Features:
oImproves the accuracy of inventory orders (Never overstock or understock).
oHelp keep the business organized.
oSaves time by automating the inventory process.
oSaves money by providing insight into which products are selling and which
aren’t.
o Can be integrated with POS and accounting software.
o
2.3.4 Restaurant Accounting Software (RAS):
It is easy to overlook one of the most important elements of restaurant
operations – restaurant accounting. Restaurant accounting software is often cheap
(sometimes even free) and easy to learn how to use.

Features:

o Gives you real-time insights into your restaurant's finances.

o Shows you both accounts payable and receivable.
o Can connect with another restaurant software (POS and payroll system).
o Can be accessed easily from wherever you are.

11
2.3.5 Comparison

Features RMS POS IMS RAS

Support large System yes no yes no
Cover Everything yes no no no
Easy to Use yes no yes yes
table 3: comparison table with related work.

2.4 Conclusion
We have identified the concepts of RMS system and the technique that have been used
with RMS, also the related systems and their advantages and disadvantages, comparison
between our system and other systems.

12
 Chapter 3
Methodology

13
3 Introduction
This chapter state the methodology used to reach the objectives of the project. The
framework in which software is designed, developed, and maintained is known as the Software
Development Life Cycle (SDLC).

It shows the steps, phases, milestones, and evolution of the software development process.
There are many types of models used in software design and development. Among them are
the spiral models, rapid development model, Evolutionary model, waterfall model, prototyping
model, etc.

3.1 methodology
Prototyping Model has been used to develop RMS. The Prototyping model is a technique for quickly
building a function but incomplete model of the information system. There are several kinds of
prototypes but they all intend to reduce risk by building a quick and dirty replica or mockup of the
intended system.

It can be used to demonstrate technical feasibility when the technical risk is high. It can also be used to
better understand and elicit user requirements. In either case, the goal is to reduce risk and limit costs
by increasing understanding of proposed solutions before committing more resources, as shown in
figure 1.

analize Design test

requirement
prototype impelement maintain
gathering

figure 1:prototype model process.

3.2 prototype model

3.2.1 Advantages of Prototyping
o Reduces development time.
o Reduces development costs.
o Requires user involvement.

14
 o Developers receive quantifiable user feedback.
o Facilitate system implementation since users know what to expect
o Results in higher user satisfaction.
o Exposes developers to potential future system enhancements.

3.2.2 Process of Prototyping

- Identify basic requirement: Determine basic requirements including the input and
output information desired. Details, such us security, can typically be ignored.
- Develop initial prototype: The initial prototype is developed that includes only user
interfaces.
- Review: The customers, users, examine the prototype and provide feedback on
additions or changes.
- Revise and enhancing the prototype: Using the feedback, both the specifications and
the prototype can be improved. This method involves a series of iterations and
refinement until the prototype product is a fully working system, and the user is
satisfied.

3.3 Reason of Using Prototype Model

- Users are actively involved in the development.
- Since in this methodology a working model of the system is provided, the users get a
better understanding of the system being developed.
- Errors can be detected much earlier.
- Quicker user feedback is available leading to better solutions.
- Missing functionality can be identified easily.
- Confusing or difficult functions can be identified requirements validation, quick
implementation of incomplete, but functional application.

15
3.4 Project Management
3.4.1 Project plan
F.
s.
Requirement gathering design Implementing Testing date:2024/03/1
date:2023/12/22
5
week1 week 2 week 3 week 4 week 5 week 6 week 7 week 8 week 9 week 10 week 11 week 12 week 13 week 14
Requirement
gathering
Requirement
anlyze
Design
Starting initial
design
design
revision
final design
First step of
implementing
Second step
Third step
Testing

table 1: shows the process phases of implementation.

3.5 Conclusion
We used Prototyping Model as our methodology for developing this system, and we described
the advantages of prototyping, its process, it’s phases and reasons of using its model.

16
 Chapter 4
Design and Implementation

17
4 Introduction
This chapter explains the design and implementation phases of the system. It depicts
the class diagram, ER diagram and database schema the System. Moreover, the
implementation phase combines the requirements, design phase outputs, and process them
using the appropriate technologies.
4.1 Requirement Specification
Requirement specification is one of the most important part in a project to make a good
and most effective project. We divided the requirements of our project into functional
requirements and non-functional requirements. And the tools that we used in our project are
phpMyAdmin, MySQL, JDK, IntelliJ, scene builder, computer, and Día for logical design of the
project.

4.2 System design and architecture:

4.2.1 ER Diagram Model

18
4.3 Implementation phases
Project implementation consists of carrying out the activities with the aim of
delivering the outputs and monitoring progress compared to the work plan. After
developing the database of the system, the implementation phase emerges and through
this phase, several activities and techniques were used to develop the website as shown
in below.
Developing of the system starts with designing the website structure with JavaFX scene
builder, and then the style of the system was designed using CSS and JavaFX.
After that, enhanced user interfaces and dynamic system developed by java code. Later
on, the system contents and database were managed through java as well.

Logical design the Database

Design RMS structure suing JavaFX Scene Builder

Design Style of the RMS including the design and layout using CSS, javaFX

user interface and dynamic system using JAVA

database and session tracking using JAVA

figure 1: this figure shoes the process of implementation phases;

4.4 Order page

19
image 1: this image belongs to order page of RMS.

4.5 Staffs page

image 2: employees page of RMS.

4.6 Food page

image 3: Food page of RMS.

20
4.7 Drinks

image 4:Drink page of RMS.

4.8 Income calculation’s page

image 5:this image is about incomes

21
4.9 Sales order

image 6: sales order page of RMS.

4.10 consumption Calculation

image 7 : consumption page of RMs.

22
5 Testing
Testing is a type of system test that checks the schema, content, triggers, etc. of
the Database system under test. It also checks data integrity and consistency. It may
involve creating complex queries to load/stress test the Database and check its
responsiveness. We have tested our database to ensures data values and information
received and stored into database are valid or not. The types of testing that we tested
our project are as follow:
5.1 Functionality and Performance Testing
All Functions in RMS, database connection, Form used to inter data, adding, getting
or deleting information from users were tested, Developers performed the test of RMS.
Some functionality requirements were tested during test.
❖ Data entry into deferent table and (inserting data into database).
❖ Retrieved data from database and show them in user views.
❖ Evaluated data is valid.
❖ Transaction testing.
❖ No information is lost in the process.
❖ No unauthorized individual is allowed to access the sensitive data.
❖ Save and display the data correctly.

23
 Chapter 5
Conclusion and Future Word

24
6 Conclusion
This restaurant database management system provides a beneficial way for
restaurant to manage incomes and consumptions better and save their information
securely. It is a best database management system to insert the information of foods into
foods table and we can retrieve them again to show in user view, and save the entire
information about foods, employee, customers, in deferent tables. The database
management system’s manager will be able to work on the whole of system.

6.1 Future work

Some ideas and features can be considered as a future work for this project. These
features can be summarized in the following points:
- Making attendance for staffs.
- Automation the staff salary payment by system.
- Make it usable in small frameworks, OS, android,
- Make separate interface for staff to add or items,
- Develop to expand and add the feature of ordering foods and book the table
customers from home.

25