RESTAURANT MANAGEMENT

SYSTEM
SYNOPSIS
OF MINI PROJECT

BACHELOR OF COMPUTER APPLICATIONS

SUBMITTED BY

Sagar Tripathi

Batch Year- 2020-2023

Enrollment no.-U2046057

PROJECT GUIDE- Ms. SUNITA TRIPATHI

Center of Computer Education & Traning

Institute of Professional Studies

University of Allahabad, Prayagraj

Uttar Pradesh
 INTRODUCTION
The Project “Restaurant Management System” helps the restaurant manager to manage the restaurant
more efficiently by computerizing metal ordering and inventory control.

Restaurant is an easy to use software available in both DOS & WINDOW platform. It has various
features and it was help in day-to-day functioning of a restaurant in a proper manner. Essentially, a
restaurant manager’s job is to balance the various needs of the business, provide leadership, set strategic
objectives, make use of restaurant management software, and ensure all departments are functioning as
they should. Ultimately, restaurant management is concerned with guiding a restaurant to long- term
success.
 PROBLEM DEFINITION
Traditionally the method in which customers specify their desired menu to the waiter who takes the
order on a paper. Personally, he then takes the order to the kitchen department and then he supply the
food item to the customer. So, it was a time-consuming process. It leads to wastage of paper and also it
requires reprinting of all menu cards. Also, in many cases for small change to be making in menu card it
is not convenient to print all menu cards again and again. Simply saying that the menu card once printed
can’t be changed. After some days, the menu card lost its worthy look and attractiveness.

Many of the hotel are managed their workflow and services by paper work and manually which take
time and high budget for management. busy day of people schedule and value of time become important
day by day so Smart Restaurant handle the system as booking and ordering by digitally which become
save manpower and time of staff of hotel. Generating KOT by application is easy to save paper, staff
and time. The hotel are services and facilized in a traditional way, from waiters to kitchen also on
account. More recently, these system is one of the major problem for hotel to manage their manpower
and guests.
 MOTIVATION
The motivation of this project comes with observing their difficulties in busy situation while I was there
as I usually visit the place to order food. Personally I don’t have much time to wait in long queues.

This restaurant is also very crowded during lunch & dinner time. Although this restaurant is not very
large they have to provide service to enormous number of customers. Without a system it’s very
difficult.
 OBJECTIVE(S)
The objective of this project is to build an restaurant management system using all the skills and
techniques from the field ensuring that no common development mistake are reproduced.

One of the main objective of any business is to maximize profit by increasing efficiency and decreasing
overhead without compromising customer satisfaction . Currently many restaurants use a paper based
system to communicate between the restaurant and kitchen which can be shown to be one of the least
efficient approaches. These are several problem which could be seen as reducing the restaurant’s
efficiency.

1- Miscommunication caused by handwriting.

2- Unmanageable order logging.
3- Inefficient restaurant- kitchen communication.
4- Difficult order tracking.
5- Difficult stock management.
 USER CHARACTERISTICS
The restaurant management system has active actor and one cooperating system. The customer can
access the system through wifi-connection and order food. The chef can see the order & after preparing
the food he will tell the food is ready. The waiter get confirmation of food and deliver it to right table.

REQUIREMENT ANALYSIS
The proposed System has the following requirements:

1- System need to maintain quantity record.

2- System need to keep the record of Customer.
3- System need to update and delete the record.
4- System also needs a search area.
5- It also needs a security system to prevent data.
6- System need stores information about new customer of restaurant.

HARDWARE REQUIREMENTS
The section of hardware configuration is a important task related to the software development
Insufficient Random Access Memory may affect adversely on the speed and efficiency of the entire
system The process should be powerful to handle the entire operations The hard disk should have
sufficient capacity to store the file and applications.
Processor : i3 and above .
Processor speed : 1.4 GHz Onwards.
System Memory : 128 Mb Minimum 256 Mb Recommended.
Display : Graphics Card Capable of Produce 1024,768 Resolution .
Cache Size : 512 KB.
RAM : 512 MB (Minimum).
 SOFTWARE ANALYSIS
A major element in building a system is the selection of compatible software since the software in the
market is experiencing a geometric progression Selected software should be acceptable by the firm and
one users as well as it should be feasible for the system.
Tools : IntelliJ Idea , Eclipse IDE for Java.
Operating System : Windows , MacOS.
The purpose of having a software requirement specification document is to have an understandable,
unambiguous and complete specifications documentation requirement for the project.

PROJECT DEVELOPMENT APPROACH

Software process model:

To solve actual problems in an industry, software developer or a team of developers must incorporate a
development strategy that encompasses the process, methods and tools layers and generic phases. This
strategy is often referred to as process model or 3 software developing paradigm. A process model for
software developing is chosen based on the nature of project and application, the methods and tools to
be used, and the controls and deliverables that are required. All software development can be
characterized as a problem solving loop in which four distinct stages are encountered: Status quo,
problem definition, technical development and solution integration. Regardless of the process model
that is chosen for a software project all of the stages coexist simultaneously at some level of detail.
Our project follows the waterfall model

THE WATERFALL MODEL

The steps of the typical waterfall model are:

1) Requirement definition
2) System & software design
3) Implementation
4) Integration & system testing
5) Operation and maintenance
 STUDY DESIGN
In this phase, a logical system is built which fulfils the given requirements. Design phase of software
development deals with transforming the clients's requirements into a logically working system.
Normally, design is performed in the following in the following two steps:

1. Primary Design Phase

In this phase, the system is designed at block level. The blocks are created on the basis of analysis
done in the problem identification phase. Different blocks are created for different functions emphasis
is put on minimising the information flow between blocks. Thus, all activities which require more
interaction are kept in one block.

2. Secondary Design:

In the secondary phase the detailed design of every block is performed.

The general tasks involved in the design process are the following:
1. Design various database structures.
2. Design various blocks for overall system processes.
3. Specify details of programs to achieve desired functionality.
4. Design the form of inputs, and outputs of the system.
5. Perform documentation of the design.
6. System reviews.
 Testing Strategy used
System testing is actually a series of different whose primary purpose is to fully exercise the computer
based system. Software testing is critical element of software quality assurance and represent the
ultimate review of the specification, design and coding. System testing makes a logical assumption that
all the part of the system is correct; the goal will be successfully achieved. Testing is the final
verification and validation activity within the organization itself. During testing the major activities are
concerned on the examinations and modification of the source code.

Testing is a process of executing a program with the intend of finding an error. A good test is one that
uncovers an as yet undiscovered error. Testing objectives are;
• Unit testing
• Integration testing
• System testing
• Validation testing
• User acceptance testing

Project Aspect

After connecting the back-end and the front-end as whole module, the data entered in the front-end
once submitted were successfully entered in the Database. On request, data were successfully retrieved
in to forms.

Test Case Design Methods:

The primary objective of test case design methods is to derive a set of test that has of highest likelihood
of uncovering the defects. To accomplish this objective, two categories of test case design techniques
are used Black box testing and white box testing.
S.No. Project Activity Estimated Start Date Estimated End Date
1. Synopsis submission 25/07/2022 1/08/2022
Bibliography & References

Google for problem solving

http://www.javaworld.com/
http://www.jdbc-tutorial.com/
https://www.tutorialspoint.com/java/
http://www.javatpoint.com/java-tutorial