SOFTWARE ENGINEERING

PROJECT TOPIC:

Restaurant management system

Submited by :- Anand Singh

 Certificate

This is to certify that the project entitled “Resturent Management System” is successfully
completed by Mr.Anand singh as per the syllabus and in partial fulfilment for the
completion of BSc. degree in Computer Science of University of Mumbai, it is also to certify
that this is the original work of the candidate done during the academic year 2021 – 2022.

Exam seat no: _____________

Place:
Date:

Signature of External Examiner :

Signature of Principal /Co-ordinator:

Guide :
Seal
 Acknowledgement

I’m Anand Singh student of PILLAI COLLEGE OF

ARTS, COMMERCE & SCIENCE would like to express my sincere
gratitude towards Computer Science Department.

I would like to thank lecturer Mrs. Shubhangi Pawar and

for their constant support during the project. Last but not least I thank
all my colleagues for being with me throughout the project, which
leads to a successful completion of my project. The project would not
have been completed without creativity and energy, which our friends
provided.

Your Faithfully:-

Anand Singh
 INTRODUCTION

The Restaurant Management System helps the

restaurant manager to manage the restaurant
more effectively and efficiently by computerizing
meal ordering, billing and inventory control.
The system processes transaction and stores the
resulting data. Reports will be generated from
these data which help the manager to make
appropriate business decisions for the restaurant.
For example, knowing the number of customers
for a particular time interval, the manager can
decide whether more waiters and chefs are
required.

FEASIBILITY STUDY
Technical Feasibility: -
The system has been designed keeping basic system requirements into
consideration related to hardware and software. The system experts
from the user and input in frame windows which can be subjected to
speeding up the process and is stored in database. The system
currently is employing DOS/WINDOWS based environment with a
small amount of memory and disk space requirement.
We need a software that work on a different devices at a time
smoothly to achieve smooth customer shopping experience. A very
efficient database to store all sells and purchase related data. A
payment getaway to confirmed payment through card or UPI. The
Software need to be handle manager, officer and staff login details
and the time of login and logout.
 POS Software (Point of Sale)
 Manages manager officer and staff login
 Have nice interface and easy to learn and use
 Payment gateways to confirm payment
 Barcode scanner facility to read product labels to identify the
different product while software enables to maintain the records
and update the inventory each time the sale is made
Hardware Requirements
 Minimum 2.4GHz Processer
 512 MB RAM
 Minimum 40GB of available hard-disk space to run software smoothly
 Barcode scanner
 Keyboard
 Mouse
 Swipe machine (wired, GPRS and Wi-Fi )
 Printer ( To print the bill)

Software Requirements

 Minimum Windows XP Operating System

 Visual Studio Code 1.39.1
 Python, PHP, MySQL Database Workbench

Supported Architectures:
 32-Bit (x86)
 64-Bit (x64) (WOW)

TECHNOLOGY USED
 Front end: Python
 Back end:  MySQL Server

Economical Feasibility:-
It considered the cost/benefit analysis of the proposed project. It also
helpful to find out the system development costs. The system is
economically feasible.
        Economic or financial feasibility is the second part of the
resource determination. The effectiveness of the system. Commonly
known as cost benefit analysis, it determining the benefits and savings
that are expected from the candidates system. This is an ongoing
process that improves accuracy at each phase of the system
development life cycle. The basic resources to be considered are as
follows:
 Cost of doing entire system study
 Estimate cost of hardware
 Estimated cost of software

Cost of Project: - 200000

Time Duration: - 4 months

Employees Required: -
Frontend: - 2 employees
Backend: - 2 employees
Tester : - 1 employees
As hardware and software resources are already available at quality
precision gauges, no additional expenditure to procedure then needs
to be incurred.
Operational Feasibility
It considered the acceptability of the system and checks whether
 System will be used if it is developed and implemented.
 The user will be able to handle the system easily
 Whether the proposed system will cause any trouble.
       The system is completely menu driven. The user friendliness of
the system result in simplicity in the operation. The long term benefit
of the system would enhance the working style of the operational
user.

STAKE HOLDERS
Stake holders are the people or persons who have an interest in the
success of a new system.  Stakeholders are divided into 3 groups:    
1) The user who actually use a system on a daily basis.
2) The clients those who pay for an own the system.
3) Technical staff, which must ensure that the system operates in the
computing environment of the organisation.
1) User stakeholders:
In the Dairy, there is the management, staff, operators and who work
with the system like the user.  There is advantage to that user for
keeping the old records of the production.  The management of the
shop help to a user for their queries.
2) Client stakeholders:
       Client is a person or group who is providing the funds for the
projects. It can be a board of trusties.
3) Technical stakeholders:
  The technical staff includes the people who establish and maintain
the computing environment of the organisation.  They provide
guidance in areas such as programming languages, computer
platforms and equipment.

SYSTEM DESIGNING
FOR Restaurant Management System
System Design is the process of designing the architecture,
components, and interfaces for a system so that it meets the end-user
requirements.
It’s a wide field of study in Engineering and includes various concepts
and principles that will help you in designing scalable systems. These
concepts are extensively asked in the Interview Rounds for SDE 2 and
SDE 3 Positions at various tech companies. These senior roles
demand a better understanding of how you solve a particular design
problem, how you respond when there is more than expected traffic
on your system, how you design the database of your system and
many more. All these decisions are required to be taken carefully
keeping in mind Scalability, Reliability, Availability, and
Maintainability. We will be covering all of these terminologies in this
article.

We'll cover the following:

 System Requirements
 Use Case Diagram
 Er Diagram
 Sequence Diagram
 Class Diagram
 Object Diagram
 Activity Diagram
 Package Diagram
 Deployement Diagram
 System Requirements
We will focus on the following set of requirements
while designing the Restaurant Management System:

1. Restaurant will have a menu.

2. The menu will have different menu sections,
containing different menu items.
3. The waiter should be able to create an order for a
table and add meals for each seat.
4. The system should be able to retrieve information
about tables currently available to seat walk-in
customers.
5. The system should support the reservation of
tables.
6. The receptionist should be able to search for
available tables by date/time and reserve a table.
7. The system should allow customers to cancel their
reservation.
8. The system should be able to send notifications
whenever the reservation time is approaching.
9. Customers should be able to pay their bills through
credit card, check or cash.
 SDLC Model Use

RAD Model: -

AD Model or Rapid Application Development model is a

software development process based on prototyping
without any specific planning. In RAD model, there is
less attention paid to the planning and more priority is
given to the development tasks. It targets at developing
software in a short span of time.
Activities performed in RAD Modelling
 On basis of the flow of information and distribution
between various business channels, the product is
designed
 The information collected from business modelling is
refined into a set of data objects that are significant for the
business
 The data object that is declared in the data modelling
phase is transformed to achieve the information flow
necessary to implement a business function
 Automated tools are used for the construction of the
software, to convert process and data models into
prototypes
 As prototypes are individually tested during every iteration,
the overall testing time is reduced in RAD.

Disadvantages of RAD Model

 It can’t be used for smaller projects
 Not all application is compatible with RAD
 When technical risk is high, it is not suitable
 If developers are not committed to delivering
software on time, RAD projects can fail
 Reduced features due to time boxing, where
features are pushed to a later version to finish
a release in short period
  Reduced scalability occurs because a RAD
developed application begins as a prototype
and evolves into a finished application

USE CASE DIAGRAM

It’s the basic diagram which represent number of
peoples involved in process and there action. A use case
diagram can summarize the details of your system's
users (also known as actors) and their interactions with
the system. To build one, you'll use a set of specialized
symbols and connectors. An effective use case diagram
can help your team discuss and represent:
 Scenarios in which your system or application
interacts with people, organizations, or external
systems
 Goals that your system or application helps those
entities (known as actors) achieve
 The scope of your system
ENTITY RELATIONSHIP DIAGRAM
(E R DAIGRAM)

ER Diagram stands for Entity Relationship Diagram,

also known as ERD is a diagram that displays the
relationship of entity sets stored in a database. In other
words, ER diagrams help to explain the logical structure
of databases. ER diagrams are created based on three
basic concepts: entities, attributes and relationships.
ER Diagrams contain different symbols that use
rectangles to represent entities, ovals to define attributes
and diamond
 SEQUENCE DIAGRAM

A sequence diagram or system sequence diagram (SSD) shows

object interactions arranged in time sequence in the field of software
engineering. It depicts the objects involved in the scenario and the
sequence of messages exchanged between the objects needed to carry
out the functionality of scenario. Sequence
diagrams are typically associated with use case realizations in
the logical view of the system under development. Sequence diagrams
are sometimes called event diagrams or event scenarios.
So the purpose of sequence diagram can be describes as:
 To CAPTURE DYNAMIC BEHAVIOUR of a system
 To DESCRIBE THE MESSAGE FLOW in the system
 To DESCRIBE STRUCTURAL ORGANIZATION of the
object
 To DESCRIBE INTERACTION among OBJECTS
 ACTIVITY DIAGRAM

We use Activity Diagrams to illustrate the flow of

control in a system and refer to the steps involved in the
execution of a use case. We model sequential and
concurrent activities using activity diagrams. So, we
basically depict workflows visually using an activity
diagram. An activity diagram focuses on condition
of flow and the sequence in which it happens. We
describe or depict what causes a particular event using
an activity diagram.

UML models basically three types of diagrams, namely,

structure diagrams, interaction diagrams, and behaviour
diagrams. An activity diagram is a behavioural diagram
i.e. it depicts the behaviour of a system.
 Object Diagram
Object is an instance of a class in a particular moment
in runtime that can have its own state and data values.
Likewise a static UML object diagram is an instance of
a class diagram; it shows a snapshot of the detailed
state of a system at a point in time, thus an object
diagram encompasses objects and their relationships
which may be considered a special case of a class
diagram or a communication diagram.
 Class Diagram
In software engineering, a class diagram in the Unified
Modeling Language (UML) is a type of static structure
diagram that describes the structure of a system by
showing the system's classes, their attributes,
operations (or methods), and the relationships among
objects.
 Package Diagram
Package diagram, a kind of structural diagram, shows
the arrangement and organization of model elements in
middle to large scale project. Package diagram can
show both structure and dependencies between sub-
systems or modules, showing different views of a
system, for example, as multi-layered (aka multi-
tiered) application - multi-layered application model.

Package

Dependency

TotalDependency
 Deployment Diagram
A UML deployment diagram is a diagram that shows
the configuration of run time processing nodes and the
components that live on them. Deployment diagrams is
a kind of structure diagram used in modeling the
physical aspects of an object-oriented system. They are
often be used to model the static deployment view of a
system (topology of the hardware).
 All Details

In this the project of Restaurant Management System

first I give the introduction of my project
And shows the Feasibility Study of the project .In
which there is requirements of Hardware, Software and
which technology is used
There are two type of feasibility study
1 Economical feasibility
2 Operational feasibility
And then there is a Stack holder which have three type
1 User stack holder
2 Client stack holder
3 Technical stack holder
After Stack holders there is System Designing and
System Requirement of restaurant management system

There is RAD model is known as Rapid Application

Development model. In which there is Activity performed
in RAD Modelling and the Disadvantage of RAD model.
After that there is all UML Diagram
The UML Diagrams are
1. USE CASE DIAGRAM
2. ER DIAGRAM
3. SEQUENCE DIAGRAM
4. ACTIVITY DIAGRAM
5. OBJECT DIAGRAM
6. CLASS DIAGRAM
7. PACKAGE DIAGRAM
8. DEPLOYEMENT DIAGRAM.

***