RESTAURANT MANAGEMENT SYSTEM

PREFACE
Today’s world is computer world because most of the work is doing with the help of
computer. Dependency on computer is behind the few reasons. We cannot easily
manage to store large number of data or information single handle. If we need some
information or data in urgency then we cannot manage in manually these works are very
difficult if we cannot use computers.

My website on RESTAURANT MANAGEMENT provides a perfect environment for online

booking of tables. The Restaurant Management is a web-based application which would
be used to provide online support to the restaurant owner and also the customers. The
web application would be much more helpful to get the information about the charge’s
availability of tables, hostel address etc. The management would fall that their good will
has increased by providing such an online application in market.

The project report provides all the detail view of the software RESTAURANT
MANAGEMENT. From my point of view there is no further system or subsystem explained
elsewhere this project report contains the introduction, objective, purpose scope, project
perspective, product feature, hardware and software requirement, front end and
backend tool process logic, logic diagram, data flow diagram, ER diagram, database detail
and database structure and bibliography.

I have exerted a conscious effort make website user oriented and user friendly. I hope the
users would find the website not only interested but also useful.

SHAURYA SINGH

BCA V SEM

2110720580015

SHAURYA SINGH 1 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

ACKNOWLEDGEMENT

Fifth semester project is a minor component of academic’s schedule of B.C.A. Hence, I

worked on RESTAURANT MANAGEMENT SYSTEM. The conceptual knowledge acquired by
management/computer student is best minified in the project. The present project gives
a complete overview of a brick company to sell their brick online. I wish to great fully
acknowledge my indebtedness to my teachers whose keen intellect invaluable
suggestions, his presence with my never endif queries made it possible for me to learn so
much and complete this project. Their generous help and missionary zeal where a source
of input, out strength to my whole developing the system.

I express my whole hearted gratitude towards Sherwood College of Professional

Management for giving me the opportunity to undergo my project in the field of website
development of great report and allowing me to gain invaluable experience. I express my
special thanks to all the staff who gave me their precious time and help me whenever
required. I am thankful to my parents who has always been supportive in my correct
decision and giving me useful advice. I also express my sincere thanks to all respondents
without whose help completion of this project is not possible.

SHAURYA SINGH 2 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

TABLE OF CONTENT
Title of the project…………………………………………………………………

Introduction & Objective of the Project…………………………………

Tools/ Environment Used………………………………………………………

Requirement and Analysis………………………………………………….….

Feasibility Study…………………………………………………………………….

Problem Definition…………………………………………………………….….

Project Scheduling………………………………………………………….….….
Data Flow Diagram………………………………………………………………..

Complete Structure……………………………………………………………….

Modules and their description……………………………………………….

Data structure………………………………………………………………………..
Process logic of the modules………………………………………………….
List of reports generated…………………………………………………………

Project Code…………………………………………………………………………..

Testing…………………………………………………………………………………….

Project Screenshot…………………………………………………………………

Implementation of Security……………………………………………………

Future scope and enhancement…………………………………………….

Conclusion……………………………………………………………………………...

SHAURYA SINGH 3 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

1. INTRODUCTION
1.1 Background
In the fast changing world, information technology and information management are
going to play an important role. We are living in the computer age during past some year.
The computer has gaining popularity. Computer revolution found its way into almost
every aspect of human life and living. A computer is admirably suited to handle any
information and hence is an information processor that is, it can receive data, perform
some basic operations on that data and produces results according to a predetermined
program.

The Restaurant Management System is a web-based application which would be used to

provide online support to the restaurant owner and also to the customers. The web
application would be much more helpful to get the information about the charge’s
availability of tables, hotel address etc. The management would fall that their good will
has increased by providing such an online application in market.

This proposed application will manage all the needs from both ends from customer end
as well as from management end. By using this application any organization can manage
its all on going processes and also can generate reports that are very much important and
fruitful in the growth of organization.

1.2 OBJECTIVE

Today’s world is computer world because most of work is doing with the help of
computer. Dependency on computer is behind the few reasons. We cannot easily
manage to store large number of data or information single handle. If we will be need
some information or data in urgency then we cannot manage in manually these works
are very difficult if we cannot use computer.
As the generic software it can be used by a wide verity of outlets (Institutes, Companies)
to automate the process of manually maintaining records related to the subject of
maintain the Subjects of Questions and Students.

SHAURYA SINGH 4 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

This software is basically updating the manual Testing Students Ability on a lot of Copies.
So that organization can manage their record in efficient and organize them.

 The main objective is to automate non computer environment.

 To save manpower.
 It will speed the processing of data and transaction.
 It will provide best security features such as provisions of passwords.

1.3 Purpose and Scope:-

1.3.1 Purpose
Today’s world is computer world because most of work is doing with the help of
computer. Dependency on computer is behind the few reasons. We cannot easily
manage to store large number of data or information single handle. If we will be need
some information or data in urgency then we cannot manage in manually these works
are very difficult if we cannot use computer.

This section clearly depicts the environment and boundaries of the Restaurant
Management System and the entities with which it interacts. It helps us see how the
system fits into the existing scheme of things. What the system will do by itself.

This Software must request Username and Password for access to data, only after
authentication will allow access to the system. The Software must allow input of products
data from administrator and secured access.

In this Software Input error will be returned in red with appropriate message box. System
should automatically update after every transaction.

1.3.2 Scope:-
This Desktop Software is good for any restaurant, In Future we can change this software
as web Application. The proposed system helps them in many ways. It helps them do

SHAURYA SINGH 5 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

billing very easily. Maintenance also becomes easier. They can keep track of their
contacts,

information, bills and records. The software is provided with all the master entries to
enter any new customer, or data, to add or modify and delete.

As this is generic software it can be used by a wide variety of outlets (Restaurants) to

automate the process of manually maintaining the records related to the subject of
maintaining the customers and Restaurant services. In future it can be modify, so that it
can be done online . In order to meet these facility this is the major change which can be
done in future regarding this project.

SHAURYA SINGH 6 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

2.SURVEY AND TECHNOLOGY:-

2.1 Introduction of MySQL:-

MySQL, a Relational Database Management System (RDBMS), works to efficiently

manage its resource, a database of information, among the multiple clients requesting
and sending data in the network. SQL SERVER has many important features that make it
not only an exceptional database management system but also an excellent database
server choice for client/server database computing. Here are some of these features:
1. The reasons to choose it as back-end are:
1.a It is very simple to maintain.
1.b It is highly secured.
1.c It can be integrated with Microsoft Visual Basic very easily.
It can support and manage a large amount of data.
1.e It is a very scalable product and can support as many number of users as 1.f
supported by the infrastructure.
1.g Supports all major operating systems for both clients and servers, including MS-DOS,
NETWARE, WINDOWS, NT MATCH OS/2 and UNIX.

2.2 Introduction of Java:-

Sun Micro System Company Started As:-

“Java is Simple, Object Oriented, Platform Independent(Architectural
Neural),Multi-Threaded, Robust, Secure, Portable, Compiled and Interpreted , Distributed,
High Performance & Dynamic Programming Language.”
Features of Java:-

1.Simple:-Java follows almost syntax of C and C++ that’s why it can learn by C and C++
Programmer easily.

2.Object Oriented:-As we know that C++ is partially object oriented programming

language that support some concept of OOP’s Language.

SHAURYA SINGH 7 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

For Example:- In C++ we can write program without class and object. But in java without
class and object we cannot use any statement.
Java Supports All Features of Object Oriented Programming.

3. Platform Independent:- A Java Application can run on any Operating System without
making any change. (.javac) java compiler covert a source code file into byte code (.java)
& (.class) file & this byte file can run on any operating system using java interpreter (java).

4. Multi-Threading:-Multi-Threading is a programming approach that improves the

performance of an application & software by maximum utilization of CPU.
In multi threading a large programs can be divided into independent part of program and
each part of a program is called or known as thread.
Now these thread can be executed simultaneously by the CPU to improve the
performance.

5. Robust:- A java software does not permits to acquire entire memory of computer
system.So a java application can not be cause of data crash. Another example of
robustness that java does not allow input from user without exception handling.

6. Secure:- Java does not support pointer, destructor and operator overloading due to
security reason. Another example of security that java. Contain class security manager
which is used to apply inbuilt security for java application.

7. Portable:- Java byte code are lightest weight that takes minimum memory that’s why it
can move from one machine to another machine by network. So it is called portable.

8. Compiled & Interpreted:- Java uses both the mechanism of compiler and interpreter.
Thats why it is called compiled and interpreted programming language.

9. Distributed:- A java software can run easily and effectively on a network. Thats why it
is called distributed programming language.

SHAURYA SINGH 8 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

10 .High Performance:-Java Uses JIT Compiler(Just In Time) this compiler is responsible

for conversion of byte code to machine code and execution of program simultaneously.
So, JIT Compiler reduces waiting time of conversion byte code to machine code make java
programming application make faster execution.

11.Dynamic:-As we know that in C/C++ by default Memory Allocation for variable will
proceed at the time of compilation but in java all variable allocates memory at the time of
execution.
i.e., dynamic memory allocation it is a reason that’s why java we can declare variable
anywhere in a program.

Java Software/Environment
A java environment can be classified into two types:-

1)JDK(Java Development Kit):-It is responsible compilation of java program after the

compilation of java program it creates byte code file.

2)JRE(Java Runtime Environment):-It is responsible for the execution of program and JRE
contains JVM(Java Virtual Machine) and JVM contains JIT(Just In Time) Compiler.

Classification of Java Technology:-

Java Technology comes into 3 flavors:-

1. J2ME(Java 2 Micro Edition):- It is used to development of application for electronic

embedded system. For ex:-Remote, ATMs, Smart TV, Washing Machine etc.

2. J2SE(Java 2 Standard Edition):- It is used to development window based application

that can run on a small distributed network i.e LAN(Local Area Network). For ex:-
Accounting software for a company
Attendance Automation
Billing Application for a store or Gaming Application

SHAURYA SINGH 9 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

3. J2EE(Java 2 Enterprise Edition):- It is used to develop application for a large distributed

network such as internet. For ex:- Online Banking, Railway Reservation System, Online
Examination etc.

Types of Java Programs:-

1. Application Program:- It is similar to C/C++ program that contain a main method,

usual compiler starts execution from this main method. In industry it also known as
Core Java Application.

2. Applet:- An Applet is pure GUI(Graphical User Interface) program which is used for
dynamic animation using applet programming we develop gamming application.
Applet programming is common in J2SE & J2EE.

3. Servlet:- Servlet is a server site program that always run under the web server and it is
used to develop web page application.

SHAURYA SINGH 10 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

REQUIREMENT AND ANALYSIS

3.1 PROBLEM DEFINITION

Introduction:-
Problem introduction or problem starting is the starting point of the software
development activity. The objective of this statement is to answer: Exactly what must the
system do? The software project is initiated by the client’s need. In the beginning, these
needs are on the minds of various people in the client’s organization. The analyst has to
identify the requirements by talking to the people and understanding to their needs. It
goes without saying that an accurate and through understanding of software
requirement are essentials to the success of software development effort. All further
development like system analysis. System design and coding will depends on how
accurate and well understood the requirements are poorly analyzed and specified
software will disappoint the user and will bring brief to the developer. No matter how
well designed and well appearances are often deceiving. Chances of misinterpretation are
very high, ambiguity is probable and communication gap between customer and
developer is bound to bring confusions. Requirements understanding begin with a clear
and concise heading stating in sentence the task to be performed. Then requirements are
describe in a technical manner precise statement.

Feasibility study:-
All projects are feasible given unlimited resources and infinite time! Unfortunately, the
development of computer based system is more likely to be plagued by a scarcity of
resources and difficult delivery dates. It is both necessary and prudent to evaluate the
feasibility of the project at the earliest possible time. Months or years of effort, Money
loss and untold professional embarrassment can be averted I few better understand the
project at its study time.

This type of study determines if an application can and should be developed. Once it has
been determining that, application is feasible. After that analyst can go ahead and
prepares the project specification, which finalizes project requirements. Feasibility
studies are undertaken within tight time constraints.

SHAURYA SINGH 11 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility
4. Legal Feasibility

 Technical Feasibility:-
As we know the technical feasibility is concerned with specifying equipment and software
that will successfully satisfy the user requirement. The technical needs of the system may
vary considerably, but might include:

 The facility to produce outputs of advertisements, shopping and mailing in a given time
for ease of use.
 Response time under certain condition is minimal.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distinct location.
In examining the technical feasibility, configuration of the system is given more
importance than the actual make of hardware. The configuration should give the
complete picture about the system’s requirements- how many workstations are required,
how these units are interconnected so that they could operate and communicate
smoothly.

 Operational Feasibility:-
Proposed projects are beneficial only if they can be turned into information system that
will meet the financial management requirements of the business/organization. This test
of feasibility asks if the system will work when it developed and installed. Are there major
barriers to implementation.

Some of the important questions that are useful to test the operational feasibility of a
project are given below:

 Is there sufficient support for the project from the implementation?

 From user? If the present system is well liked and used to the extent that persons will
not be able to see reasons for change, there may be resistance.

SHAURYA SINGH 12 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

 Are current business methods acceptable to the user? If they are not, user may welcome
a change that will bring about a more operational and useful system.
 Have the user been involved in the planning and development of the Project? If they are
involved at the earliest stage of project development, the chances of resistance can be
possibly reduced.
 Will the proposed system cause harm? Will it produce poorer result in any case or area?
 Will the performance of staff member fall down after implementation? Issue that
 Appears to be quite minor at the early stage can grow into major problem after
Implementation.

 Economical Feasibility:-
Economic analysis is the most frequently used technique for evaluating the effectiveness
of the proposed system. More commonly known as cost/benefits analysis, the procedure
is to determine the benefits and savings that are expected from the purposed system and
compared with costs.
If benefits outweigh cost, a decision is taken to design and implement the system.
Otherwise, further justification or alternative of the proposed system will have to be
made if it has a chance of being approved. This is an ongoing effort that improves in
accuracy at each phase of the system life cycle. The analysis part also clears the doubt of
economic problems which could be possible in developing the system. As already
mentioned that the company has to just pay the developed software cost and not other
investment is needed at the time of implementation of the new system as the
preliminary requirements already exist in the company.

 Legal Feasibility:-
In the legal feasibility is necessary to check that the software we are going to develop is
legally correct which means that the ideas which we have taken for the proposed system
will be legally implemented or not so, it is also an important step in feasibility study.

SHAURYA SINGH 13 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

PROBLEM SPECIFICATION
The definition of our problem lies in manual system and a fully automated system.

1.Manual System:-The system is very time consuming and lazy. This system is more
prone to error and sometimes the approach to various problems is unstructured.

2.Technical System:-With the advent of latest technology if we do not update our

system then our business result in losses gradually with time. The technical system
contains the tools of latest trend i.e. computers, printers, FAX, Internet etc. the system
with the technology are very fast, accurate, user friendly and reliable.

3. Need of Restaurant Management System:-Restaurant Management System

software is very needy for Restaurants etc. This software helps them maintain every
Customer, Food management and Billing System in the computer .

4.The Proposed System:-The proposed system helps them in many ways. It helps
them to make billing very easily. Maintenance also becomes easier. They can keep track
of their Customer, Information and Bills. The software is provided with all the
management to enter again to modify the every detail.

5.Existing System:-At present Restaurant maintain their day to day Information

manually. These restaurant have thousands of customer they need to track of all these
customers to check their services, Data etc., If any data loses of any customer (Existing
customer) then it is a lost of restaurant losing Data. So it is very essential to track every
details like Name, Phone Number and their Bills, then only they can able to see recent
records. To find the specific is also another risky job. So proper system required. They
need full pledged software to maintain their day to day transactions and Feeding details.

ENTITY RELATION DIAGRAMS:-

The Entity Relation Model or Entity Relation Diagram (ERD) is a data model or diagram for
high-level description of conceptual data model, and it provides a graphical notation for
representing such data models in the form of entity relationship diagrams. Such models

SHAURYA SINGH 14 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

are typically used in the first stage of Management information system design; they are
used for example, to describe information needs and/or the type of information that is to
be stored in the Database during the requirement analysis. The data modeling technique,
however, can be used to describe any ontology (i.e. an overview and classification of used
term and their relationships) for a certain universe of discourse (i.e area of interest).

In the case of design a Management Information System that is based on a database, the
conceptual data model is, a later stage( usually called logical design), mapped to a logical
data model such as, relational data model; this is turn in mapped to a physical model
during physical design. Note that sometimes, both of the phases are referred a “physical
design”. There are number of convention for entity-relation diagrams (ERDs). The
classical notation is describe in the remainder of this article, and mainly related to the
conceptual modeling. There is a range of notation more typically employed in physical
and logical database design.

SHAURYA SINGH 15 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

ER Diagram

View Staff View

Add/Delete Customer
Food Item View
Booking

Manage uname

Change cont utype

Status

addr
uname pswd
Admin

mail

Register
Login

Cancel uname
Customer
Booking

addr
See
Menu Manage
utype
Book `
Table
cont mail
See
Booking

SHAURYA SINGH 16 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

DATA FLOW DIAGRAM

The data flow diagram shows the flow of data within any system. It is an important tool
for designing phase of software engineering. Larry Constantine first developed it. It
represents graphical view of flow of data. It’s also known as BUBBLE CHART. The purpose
of DFD is major transformation that will become in system design symbols used in DFD.

In the DFD, four symbols are used and they are as follows.

1. A square defines a source (originator) or destination of system data.

2. An arrow identifies data flow-data in motion. It is 2a pipeline through which information

flows.

3. A circle or a “bubble “(Some people use an oval bubble) represents a process that
transfers informing data flows into outgoing data flows.

4.An open rectangle is a data store-data at rest, or a temporary

Repository of data.

SHAURYA SINGH 17 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Context Level Data Flow Diagram

This level shows the overall context of the system and its operating environment and
shows the whole system as just one process. Online book store is shown as one process
in the context diagram; which is also known as 0-level DFD, shown below. The context
diagram plays important role in understanding the system and determining the
boundaries. The main process can be broken into sub-processes and system can be
studied with more detail; this is where 1st level DFD comes into play.

Restaurant
Management
Customer System Administrator

SHAURYA SINGH 18 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

First Level DFD:-

This level (level 1) shows all processes at the first level of numbering, data stores,
external entities and the data flows between them. The purpose of this level is to show
the major high-level processes of the system and their interrelation. A process model will
have one, and only one, level-1 diagram. A level-1 diagram must be balanced with its
parent context level diagram, i.e. there must be the same external entities and the same
data flows, these can be broken down to more detail in the level 1.

MENU
Check food
availability

Manage Confirm
CUSTOMER
ADMIN
order
CCdffCCUST
OME
Order
Billing

SHAURYA SINGH 19 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Data Tables:-

Login :

FIELDS DATA TYPE LENGTH

uid int 5
uname varchar 30
pswd varchar 30
cont varchar 30
addr varchar 30
mail varchar 30
utyp varchar 30

Feedback:-

FIELDS DATATYPE LENGTH

ser int 1
foq int 1
din int 1
txt varchar 100

Booking :

FIELDS DATATYPE LENGTH

bid int 5
name varchar 30
no_per int 2
ar_date varchar 10
b_stat varchar 10

SHAURYA SINGH 20 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Food_list :

FIELDS DATATYPE LENGTH

fid Int 5
fname varchar 30
fprice int 10

Table :

FIELDS DATATYPE LENGTH

tab_no int 5
person varchar 20
tab_stat varchar 20

SHAURYA SINGH 21 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

3.2 REQUIREMENTS SPECIFICATION

3.2.1 Software Requirements:-

Java/JDK
NetBeans
SQL YOG

3.2.2 Hardware Requirements:-

Pentium IV Processor
512 MB RAM
40 GB HDD
Color Monitor
Keyboard
Mouse

3.3 PRELIMINRY PRODUCT DESCRPTION

There are mainly t wo modules in the project: -

1) Admin

2)Customer

Admin Features:
Can add Food items to menu.
Can see staff members.
See customers personal records.
Can see feedback.

SHAURYA SINGH 22 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Can see all bookings.

Can change booking status.
Can see feedback.

Customer Features:-

Can See food items.

Can online book slots.

Can give feedback.
Can check their bookings.

3.4 COCEPTUAL MODEL

Waterfall approach was first SDLC Model to be used widely in Software Engineering to
ensure success of the project. In "The Waterfall" approach, the whole process of software
development is divided into separate phases. In this Waterfall model, typically, the
outcome of one phase acts as the input for the next phase sequentially.
The following illustration is a representation of the different phases of the Waterfall
Model.
 Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification
document.
 System Design − The requirement specifications from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.
 Implementation − With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.

SHAURYA SINGH 23 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
 Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
 Maintenance − There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better
 versions are released. Maintenance is done to deliver these changes in the customer
environment.

All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the
defined set of goals are achieved for previous phase and it is signed off, so the name
"Waterfall Model". In this model, phases do not overlap.

SHAURYA SINGH 24 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

WATERFALL MODEL

Requirement Analysis

System Design

Implementation

Testing

Deployment

Maintenance

SHAURYA SINGH 25 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Waterfall Model – Application

Every software developed is different and requires a suitable SDLC approach to be
followed based on the internal and external factors. Some situations where the use of
Waterfall model is most appropriate are –

 Requirements are very well documented, clear and fixed.

 Product definition is stable.
 There are no ambiguous requirements.
 Ample resources with required expertise are available to support the product.
 The project is short

Waterfall Model – Advantages:-

The advantages of waterfall development are that it allows for departmentalization and
control. A schedule can be set with deadlines for each stage of development and a
product can proceed through the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order.
Some of the major advantages of the Waterfall Model are as follows –
 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has specific deliverables and
a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.
 Easy to arrange tasks.
 Process and results are well documented.

SHAURYA SINGH 26 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Waterfall Model – Disadvantages: -

The disadvantage of waterfall development is that it does not allow much reflection or
revision. Once an application is in the testing stage, it is very difficult to go back and
change something that was not well-documented or thought upon in the concept stage.
The major disadvantages of the Waterfall Model are as follows −
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of
changing. So, risk and uncertainty is high with this process model.
 It is difficult to measure progress within stages.
 Cannot accommodate changing requirements.
 Adjusting scope during the life cycle can end a project.
 Integration is done as a "big-bang. at the very end, which doesn't allow identifying any
technological or business bottleneck or challenges early.

SHAURYA SINGH 27 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Coding:-
LOGIN PAGE:-
try{ String utyp= (String) jComboBox1.getSelectedItem();

String user=jTextField1.getText();

String pswd=jPasswordField1.getText();

String mail=jTextField2.getText();

DB.DBCon db=new DB.DBCon();

db.pstmt=db.con.prepareStatement("select * From login where utyp=? and

uname=? and pswd=? and mail=?");

db.pstmt.setString(1,utyp);

db.pstmt.setString(2,user);

db.pstmt.setString(3,pswd);

db.pstmt.setString(4,mail);

String ut="Admin";

String mem="Member";

String usr="User";

db.rst=db.pstmt.executeQuery();

if(db.rst.next())

{ if(jComboBox1.getSelectedItem().equals(ut)) {

new MainWindowA().setVisible(true);

this.setVisible(false); }

SHAURYA SINGH 28 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

else if(jComboBox1.getSelectedItem().equals(mem))

{ new MainWindowS().setVisible(true);

this.setVisible(false); }

else if(jComboBox1.getSelectedItem().equals(usr))
{ new MainWindowC().setVisible(true);
this.setVisible(false); }
else { JOptionPane.showMessageDialog(this,"Incorrect User Or Password");
} } } catch(Exception e)
{ e.printStackTrace(); }

SIGNUP PAGE:-
try{ String uname=jTextField1.getText();

String pswd=jPasswordField1.getText();

String cont=jTextField2.getText();

String addr=jTextField3.getText();

String mail=jTextField4.getText();

String utyp= (String) jComboBox1.getSelectedItem();

DB.DBCon db=new DB.DBCon();

db.pstmt=db.con.prepareStatement("insert into login

(uname,pswd,cont,addr,mail,utyp) values(?,?,?,?,?,?)");

db.pstmt.setString(1, uname);

db.pstmt.setString(2, pswd);

db.pstmt.setString(3, cont);

SHAURYA SINGH 29 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

db.pstmt.setString(4, addr);

db.pstmt.setString(5, mail);

db.pstmt.setString(6, utyp);

int i=db.pstmt.executeUpdate();

if(i>0)

{ javax.swing.JOptionPane.showMessageDialog(this,mail);

new Login().setVisible(true);

this.setVisible(false); } }

catch(Exception e) { e.printStackTrace(); }

FEEDBACK(Admin):-
try{ Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

header.add("Service");

header.add("Food Quality");

header.add("Dining");

header.add("Feedback");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from feedback ");

db.rst=db.pstmt.executeQuery();

while(db.rst.next())

{ Vector<String> temp=new Vector<String>();

SHAURYA SINGH 30 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

temp.add(db.rst.getString(1));

temp.add(db.rst.getString(2));

temp.add(db.rst.getString(3));

temp.add(db.rst.getString(4));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e) { e.printStackTrace(); }

Menu:-Add Item(Admin):-
try{ String name=jTextField1.getText();

String price=jTextField2.getText();

java.util.Random r=new java.util.Random();

int num=Math.abs(r.nextInt()%100);

String ran=Integer.toString(num);

DB.DBCon db=new DB.DBCon();

db.pstmt=db.con.prepareStatement("insert into food_list(fid,fname,price)

values(?,?,?)");

db.pstmt.setString(2, name);

db.pstmt.setString(3, price);

db.pstmt.setString(1, ran);

int i=db.pstmt.executeUpdate();

if(i>0) {

SHAURYA SINGH 31 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

javax.swing.JOptionPane.showMessageDialog(this,"Food Item Added

Succefully");

jTextField1.setText("");

jTextField2.setText(""); } }

catch(Exception e){ e.printStackTrace(); }

Menu:-Search Item(Admin):-
try{ Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

header.add("Food id");

header.add("Food name");

header.add("Price");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from food_list");

db.rst=db.pstmt.executeQuery();

while(db.rst.next())

{ Vector<String> temp=new Vector<String>();

temp.add(db.rst.getString(1));

temp.add(db.rst.getString(2));

temp.add(db.rst.getString(3));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e){ e.printStackTrace(); }

SHAURYA SINGH 32 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Menu:-Delete Item(Admin):-
try{ String foodid=jTextField1.getText();

String name=jTextField2.getText();

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("delete from food_list where fid=? and

fname=?");

db.pstmt.setString(1, foodid);

db.pstmt.setString(2, name);

int i=db.pstmt.executeUpdate();

if(i>0) {

JOptionPane.showMessageDialog(this,"Record Deleted Successfully");

jTextField1.setText(""); } }

catch(Exception e){ e.printStackTrace(); }

Staffs(Admin):-
try{Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

String utype=jComboBox1.getSelectedItem().toString();

header.add("User Id");

header.add("User Name");

header.add("Contact");

header.add("Address");

header.add("E-mail");

SHAURYA SINGH 33 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

header.add("User Type");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from login where utyp=?");

db.pstmt.setString(1,utype);

db.rst=db.pstmt.executeQuery();

while(db.rst.next())

{ Vector<String> temp=new Vector<String>();

temp.add(db.rst.getString(1));

temp.add(db.rst.getString(2));

temp.add(db.rst.getString(4));

temp.add(db.rst.getString(5));

temp.add(db.rst.getString(6));

temp.add(db.rst.getString(7));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e) { e.printStackTrace(); }

Customers(Admin):-
try{ Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

String utype=jComboBox1.getSelectedItem().toString();

header.add("User ID");

SHAURYA SINGH 34 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

header.add("User Name");

header.add("Contact");

header.add("Address");

header.add("E-mail");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from login where utyp=?");

db.pstmt.setString(1,utype);

db.rst=db.pstmt.executeQuery();

while(db.rst.next())

{ Vector<String> temp=new Vector<String>();

temp.add(db.rst.getString(1));

temp.add(db.rst.getString(2));

temp.add(db.rst.getString(4));

temp.add(db.rst.getString(5));

temp.add(db.rst.getString(6));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e) { e.printStackTrace(); }

Bookings(Admin):-
try{Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

SHAURYA SINGH 35 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

header.add("Booking ID");

header.add("Name");

header.add("No. Of Persons");

header.add("Arriving Date");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from booking");

db.rst=db.pstmt.executeQuery();

while(db.rst.next())

{ Vector<String> temp=new Vector<String>();

temp.add(db.rst.getString(1));

temp.add(db.rst.getString(2));

temp.add(db.rst.getString(3));

temp.add(db.rst.getString(4));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e) { e.printStackTrace(); }

BookNow(Customers):-
try{ String nam=jTextField2.getText();

String per=jTextField3.getText();

String dat=jTextField4.getText();

java.util.Random r=new java.util.Random();

SHAURYA SINGH 36 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

int num=Math.abs(r.nextInt()%100);

String ran=Integer.toString(num);

DB.DBCon db=new DB.DBCon();

db.pstmt=db.con.prepareStatement("insert into booking

(bid,name,no_per,ar_date) values(?,?,?,?)");

db.pstmt.setString(1, ran);

db.pstmt.setString(2, nam);

db.pstmt.setString(3, per);

db.pstmt.setString(4, dat);

int i=db.pstmt.executeUpdate();

if(i>0)

{ javax.swing.JOptionPane.showMessageDialog(this,"Your table has been Booked!

Visit When you Desire");

jTextField2.setText("");

jTextField3.setText("");

jTextField4.setText(""); }

else{ javax.swing.JOptionPane.showMessageDialog(this,"An Error Occured");

} } catch(Exception e){ e.printStackTrace(); }

Feedback(Customers):-
try { String ser=(String) jComboBox1.getSelectedItem();

String foq=(String) jComboBox2.getSelectedItem();

String din=(String) jComboBox3.getSelectedItem();

SHAURYA SINGH 37 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

String txt=jTextField1.getText();

DB.DBCon db=new DB.DBCon();

db.pstmt=db.con.prepareStatement("insert into feedback (ser,foq,din,txt)

values(?,?,?,?)");

db.pstmt.setString(1, ser);

db.pstmt.setString(2, foq);

db.pstmt.setString(3, din);

db.pstmt.setString(4, txt);

int i=db.pstmt.executeUpdate();

if(i>0)

{ javax.swing.JOptionPane.showMessageDialog(this,"Feedback Sent
Successfully");

new Feedback().setVisible(true); } }

catch(Exception e){ e.printStackTrace(); }

Menu:-Search Food Item(Customers):-

try{ Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

header.add("Food name");

header.add("Price");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from food_list");

db.rst=db.pstmt.executeQuery();

SHAURYA SINGH 38 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

while(db.rst.next()) {

Vector<String> temp=new Vector<String>();

temp.add(db.rst.getString(1));

temp.add(db.rst.getString(2));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e) { e.printStackTrace(); }

Bookings(Customers):-
try { Vector<String> header=new Vector<String>();

Vector<Vector<String>> data=new Vector<Vector<String>>();

header.add("Booking ID");

header.add("name");

header.add("Persons");

header.add("Arriving Date");

header.add("Status");

DBCon db=new DBCon();

db.pstmt=db.con.prepareStatement("select * from booking");

db.rst=db.pstmt.executeQuery();

while(db.rst.next()) {

Vector<String> temp=new Vector<String>();

temp.add(db.rst.getString(1));

SHAURYA SINGH 39 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

temp.add(db.rst.getString(2));

temp.add(db.rst.getString(3));

temp.add(db.rst.getString(4));

temp.add(db.rst.getString(5));

data.add(temp); }

jTable1.setModel(new DefaultTableModel(data,header)); }

catch(Exception e) { e.printStackTrace(); }

SHAURYA SINGH 40 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

TESTING
System Testing: -

Black box testing method was used for system testing. The black box testing usually
demonstrates that software functions are operational; that the input is properly accepted
and the output is correctly produced; and that integrity of external information
(databases) is maintained.

Why testing is done-

Testing is the process of running a system with the intention of finding errors.
Testing enhances the integrity of a system by detecting deviations in design and errors
in the system.
Testing aims at detecting error-prone areas. This helps in the prevention of errors in a
system.
Testing also add value to the product by confirming to the user requirements.
Causes of Errors

The most common causes of errors in a software system are:

 Communication gap between the developer and the business decisionmaker: A

communication gap between the developer and the business decision maker is normally
due to subtle differences between them. The differences can be classified into five broad
areas: Thought process, Background and Experience, Interest, Priorities, Language.
 Time provided to a developer to complete the project: A common source of errors in
projects comes from time constraints in delivering a product. To keep to the schedule,
features can be cut. To keep the features, the schedule can be slipped.
 the feature set or schedule when problems are discovered can lead to rushed work and
flawed systems.
 Over Commitment by the developer: High enthusiasm can lead to over commitment by
the developer. In these situations, developers are usually unable to adhere to deadlines
or quality due to lack of resources or required skills on the team.

SHAURYA SINGH 41 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

 Insufficient testing and quality control: Insufficient testing is also a major source of
breakdown of e-commerce systems during operations, as testing must be done during all
phases of development.
 Inadequate requirements gathering: A short time to market results in developers
starting work on the Web site development without truly understanding the business and
technical requirements. Also, developers may create client-side scripts using language
that may not work on some client browsers.
 Keeping pace with the fast changing Technology: New technologies are constantly
introduced. There may not be adequate time to develop expertise in the new
technologies. This is a problem for two reasons. First, the technology may not be properly
implemented. Second, the technology may not integrate well with the existing
environment.

Testing Principles
To discover as yet undiscovered errors.
All tests should be traceable to customer’s requirement.
Tests should be planned long before the testing actually begins.
Testing should begin “in the small” & progress towards “testing in the large”.
Exhaustive Testing is not possible.
To be most effective training should be conducted by an Independent Third Party.
Testing Objectives

Testing is a process of executing a program with the intent of finding errors.

A good test case is one that has a high probability of finding an as yet undiscovered error.
A successful test is one that uncovers an as yet undiscovered error.

Kinds of Testing:-
Black Box Testing- based on any knowledge of internal designs or code. Tests are based
on requirements and functionality.

White Box Testing- Based on the knowledge of the internal logic of an application’s code.
Tests are based on coverage of code statements, branches, paths and statements.

SHAURYA SINGH 42 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Unit Testing- The most ‘micro’ scale of testing; to test particular functions and code
modules. Typically done by the programmer and not by the testers, as it requires detailed
knowledge of the internal program design and code. Not always easily done unless the
application has a well-designed architecture with tight code; may require developing test
driver modules or test harnesses.

Integration Testing- Testing of combined parts of an application to determine if they

function together correctly. The ‘parts’ can be code modules, individual applications,
client and server applications on a network, etc. This type of testing is especially relevant
to client/ server and distributed systems.

Functional Testing- Black-box type testing geared to functional requirements of an

application; testers should do this type of testing. This doesn’t mean that the
programmers shouldn’t check that their code works before releasing it.

Regression Testing- Re-testing after fixes or modifications of the software or its

environment. It is difficult to determine how much re testing is needed, especially near

the end of the development cycle. Automated testing tools can be especially useful for
this type of testing.

Acceptance Testing- Final testing based on the specifications of the end user or customer
or based on use by end-users/ customers over some limited period of time.

User Acceptance Testing- Determining if software is satisfactory to an end user customer

SHAURYA SINGH 43 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

PROJECT SCREENSHOT
HOME PAGE:-

CONTACT US:-

SHAURYA SINGH 44 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

ABOUT US:-

LOGIN PAGE:-

SHAURYA SINGH 45 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

SIGNUP PAGE:-

HOME PAGE(Admin):-

SHAURYA SINGH 46 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

MENU PAGE(Admin):-

STAFF(Admin):-

SHAURYA SINGH 47 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

CUSTOMERS PAGE(Admin):--

BOOKINGS PAGE(Admin):-

SHAURYA SINGH 48 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

ALL BOOKINGS(Admin):-

STAFF(Admin):-

SHAURYA SINGH 49 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

FEEDBACK(Admin):-

STAFF(Admin):-

SHAURYA SINGH 50 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

Home(Customers):-

Home(Customers):-

SHAURYA SINGH 51 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

MY BOOKINGS(Customers):-

FEEDBACK(Customers):-

SHAURYA SINGH 52 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

CHANGE PASSWORD(Customers):-

SHAURYA SINGH 53 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

FUTURE SCOPE AND ENHANCEMENT OF THE PROJECT

This software is very flexibility to modify itself with the needs of users and customers in
future. Yet the software is capable of enhancement.

Here we describe some features, which can be later introduced in the software for
enhancing it.

We can add some new module like online payment gateways modules.

We can provide an authorization facility. Determining whether client is permitted to

access the service. From which we can hide confidential information to the users.

More authentication responsibilities can be added in existing system through better

automation offer.

We can improve several level of security.

We can add some extra utilities like notepad, online help etc, in my software.

References
Reference Books:-
1)Herbert Schildt, JAVA2 COMPLETE REFERENCE, 5TH edition, Pregti
publication, April 2004.
2)Pankaj Sharma, INTRODUCTION TO WEB TECHNOLOGY, 2nd edition S.K.
Kataria& Sons publication, April 2007.
3)Shrika Jain, INFORMATION SYSTEM, 3rd edition, Pregti publication, April
2004.

Reference websites:-
www.javaskyline.com
www.javaworld.com

SHAURYA SINGH 54 2110720580015

 RESTAURANT MANAGEMENT SYSTEM

CONCLUSION
The software will be developed by implementing the concept of modularity which in turn
reduces the complexity involved in maintaining it. The administrator should have a sound
technical knowledge about maintaining it. The administration should have a sound
technical knowledge about maintaining the software and further enhancements will be
undertaken by the developers.

The application is portable which ensure its adaptability for use on different computer
terminals with different operating system and standards.

The factors guarantee the software’s availability includes proper terminal and correct
input details. Also, the resource used for the project development are Microsoft certified
which speaks of its high-quality standards.

Hence, we may conclude that the application system being developed helps in modifying
the computerized Restaurant Management System.

SHAURYA SINGH 55 2110720580015