BHAGWAN PARSHURAM INSTITUTE OF TECHNOLOGY

SOFTWARE ENGINEERING FILE

Submitted to-
Ms. Palak Girdhar

Submitted by-
Name: Aman Sharma
Class: CSE-A
Roll number: 35320802719
 INDEX

S. No. EXPERIMENTS DATE

1 PREPARE SOFTWARE REQUIREMENT SPECIFICATION 24-09-2021
(SRS) DOCUMENT OF THE RESTAURANT MANAGEMENT
SYSTEM
2 DRAW THE USE CASE DIAGRAM (COVERING ALL 27-09-2021
RELATIONSHIPS) OF THE RESTAURANT MANAGEMENT
SYSTEM
3 DRAW THE ENTITY RELATIONSHIP (ER) DIAGRAM OF 11-10-2021
THE RESTAURANT MANAGEMENT SYSTEM
4 DRAW DATA FLOW DIAGRAM (DFD) (LEVEL-0 AND 11-10-2021
LEVEL-1) OF THE RESTAURANT MANAGEMENT SYSTEM
5 DRAW LEVEL-2 DFD DIAGRAM OF THE RESTAURANT 18-10-2021
MANAGEMENT SYSTEM
6 DRAW THE ACTIVITY DIAGRAM OF THE RESTAURANT 01-11-2021
MANAGEMENT SYSTEM
7 DRAW THE SEQUENCE DIAGRAM OF THE RESTAURANT 13-12-2021
MANAGEMENT SYSTEM
SOFTWARE REQUIREMENT SPECIFICATION
FOR
RESTAURANT MANAGEMENT
SYSTEM
 CONTENTS

1. INTRODUCTION
1.1 Purpose of this Document
1.2 Scope of this Document
1.3 Overview
2. GENERAL DESCRIPTION
3. FUNCTIONAL REQUIREMENTS
4. INTERFACE REQUIREMENTS
5. DESIGN CONSTRAINTS
6. NON- FUNCTIONAL ATTRIBUTES
6.1 Performance Requirements
6.2 Safety and Security Requirements
6.3 Other Requirements
7. APPENDICES
 INTRODUCTION

PURPOSE OF THIS DOCUMENT –

This document presents a detailed explanation of the objectives, features, user interface and application of
Restaurant Management System in real life. It will also describe how the system will perform and under
which it must operate.

SCOPE OF THIS DOCUMENT –

This system will help the restaurant manager to manage and run the restaurant business systematically,
effectively and efficiently by computerizing meal ordering, billing and inventory control.
In this management system, we will provide an app that can be used by the customers to order food.
Customers can also give feedback using this app, so the owner of the restaurant can evaluate the whole
system. This will ultimately lead to hire less waiters and create an opportunity to appoint more chefs and
better kitchen place to serve food faster. Customers can also make a payment through debit or credit cards
using POS (Point of Sale) which will be integrated with the management software. Customers can see
current discount facility of the restaurant. Customers can also see the calorie chart which will increase
consciousness about their health. All the information about daily expenses and profit will be saved in the
system. Also, the required information’s about employees will be saved in the system which can be only
accessed by the system admin. These reports generated by the system will help the manager to make
appropriate business decisions for the restaurant. The whole management system is designed for a general
computerized digital restaurant.

OVERVIEW –
This document has a sequential overview of the whole project. By reading this document, the reader can
learn about what the project is implemented for and how it will present its basic ideas. This document is
intended for different types of readers such as restaurant owner, system designer, system developer and
tester.
 GENERAL DESCRIPTION

USERS AND CHARACTERISTICS –

The Restaurant Management System has five actors and one cooperating system. The customer can access
the system through wifi connection/ mobile data and order food. The Chef can see the order and after
preparing the food he will tell the system that the food is ready. The waiter can get the confirmation of food
from the system and deliver it to the right table. The cashier can access the system and receive the payment
from the customers. The admin can edit the price, count total earning and expenditure.

USE CASE VIEWS –

The use cases for each of the actors are described as follows –

1. CUSTOMER USE CASE: Order Food

The customer can order food, provide feedbacks and can see their payment receipt and pay.

2. CHEF USE CASE: Prepare Food

The chef can see the orders of the customers and checks whether this order can be taken or not and
then confirms the order and starts preparing the food. When the food is ready the chef alerts the
waiter to serve the food. He can also edit what ingredients are available and what ingredients are
demanded.

3. WAITER USE CASE: Serve Food

The waiter can see the food orders and the ready food in the kitchen to be served. After serving the
food, the waiter will mark the order as served.

4. CASHIER USE CASE: Take Payment

The cashier can only take payment from the customer and save it into the system database with
respect to the food item and also check if the customer is eligible for discount. If yes then take the
payment accordingly.

5. ADMIN USE CASE: Maintain System

The admin has full access to the system. He maintains the whole system to ensure better and secure
service and solves any error appeared in the system
 FUNCTIONAL REQUIREMENTS
1. FOOD ORDER VIA APP: The Customer can order food with the app with the help of internet
connection.

2. TAKE ORDER: The chef will take the order and if it is available to make then he will confirm the
order and start to prepare food.

3. SERVE FOOD: When the food is ready to be served then the chef will alert the waiter. After
serving the food, the waiter will mark the order as served.

4. PAYMENT: The cashier will receive the payment and if the customer is a member, he/she shall be
eligible for discount.

5. AVAILABLE GOOD: The Chef will add what goods are available and the admin can see that data.

6. REQUIRED GOODS: The Chef will add what goods are required.

7. CUSTOMER INFORMATION: The customer will get registered and can enquire whether they are
special customers or not and can register for the same.

8. CUSTOMER REVIEW: Customer can give overall review about the food and services.
 INTERFACE REQUIREMENTS

There are many types of interfaces which are supported by this system software namely:

1. USER INTERFACE: The User Interface will be implemented using any android smartphone app
browser. This interface will be user-friendly so that every kind of customer can place their food order
easily. Customers can also give feedback through it easily with some demo comment or if they are
keen to write the review on their own, they can do it.

2. HARDWARE INTERFACE: There shall be logical address of the system in the IPv6 format.

3. SOFTWARE INTERFACE: The system shall communicate with the Configurator to identify all
the available components to configure the product. The system shall communicate with the content
manager to get the product specifications.

4. COMMUNICATIONS INTERFACE: Communication function required the Internet Protocol

version 6 and it will follow HTTPS. It will use FTP for whole system with local system and email
communication for device to device system.
 NON FUNCTIONAL REQUIREMENTS

1. PERFORMANCE REQUIREMENTS –

OPERATING SYSTEM: Smartphones, Tablets and for pcs minimum Windows XP or Windows VISTA.
Better environment with Windows 7, 8, 10 and above, and all iOS devices.
LANGUAGE: JAVA

Some other points regarding performance requirements are listed below:

 The product will be based on local server.
 The product will take initial load time.
 The performance will depend on the hardware components.
 Different database for employees

2. SAFETY AND SECURITY REQUIREMENTS –

 The source code developed for this system shall be maintained in configuration management
tool.
 The whole system is secured. Only admin can access all the data.
 Payment system will be fully secured via POS system
 This system will use HTTPS which makes it more secure.

3. OTHER REQUIREMENTS –

 LICENSING REQUIREMENT - Not Applicable

 LEGAL, COPYRIGHT AND OTHER NOTICES – All rights reserved by our team

 APPLICABLE STANDARDS - As per industry standard

 DESIGN CONSTRAINTS

There are some constraints which may cost more for the system. If those constraints can overcome, then this
whole system will perform best. Some are discussed below:

 iOS app and Windows app

 Information flow or data flow can be controlled and made more effective
 Faster server system such as LINUX server
 Hindi language for Indians and various other languages for other countries
 Strong programming languages for much more security
 APPENDICES

In this document, we have used certain acronyms. Abbreviations and definition of those terms are discussed
below –
Term Definition
System Admin Person who is responsible for managing the whole
system and has access to the whole system
System User Person who is using or operating the system but with
a limited privilege
Database Collection of all the information monitored by the
system
Field A cell within a form
Software Requirement Specification (SRS) A document that completely describes all of the
functions of a proposed system and the constraints
under which it must operate.
Stakeholder Any person who is involved in the development
process of this software
Point of Sale (POS) It is either a stand-alone machine or a network of
input and output devices used by restaurant
employees to accomplish their daily activities
including food and beverages orders, transmission of
tasks to the kitchen and other remote areas, guest
check settlement, credit card transaction processing
and charge posting folios.
RMS Restaurant Management System

REFERENCES –
 www.google.com
 www.wikipedia.com
 www.cnet.com
 USE CASE DIAGRAM
FOR
RESTAURANT MANAGEMENT SYSTEM

SUBMITTED BY:
AMAN SHARMA (107)
ISHIKA GUPTA (111)
ISHA BHANOT (115)
 ENTITY RELATIONSHIP
DIAGRAM FOR RESTAURANT
MANAGEMENT

SUBMITTED BY-
AMAN SHARMA (107)
ISHIKA GUPTA (111)
ISHA BHANOT (115)
 RESTAURANT MANAGEMENT SYSTEM
DATA FLOW DIAGRAM
{LEVEL 0 AND LEVEL 1}

Submitted By :-
AMAN SHARMA (107)
ISHIKA GUPTA (111)
ISHA BHANOT (115)

DFD LEVEL 0

Restaurant Management

Orders Management Employee Management

Restaurant
Management
System

Payments Management Items Management

Sales Management
 DFD LEVEL 1

Restaurant Management Generate Restaurant Report

Employee Management Generate Employees Report

Items Management Restaurant Generate Items Report

Management
System

Sales Management Generate Sales Report

Payments Management Check Payment Details

Orders Management Generate Orders Report

 DATA FLOW DIAGRAM (LEVEL-2)
FOR
RESTAURANT MANAGEMENT SYSTEM

SUBMITTED BY:
AMAN SHARMA (107)
ISHIKA GUPTA (111)
ISHA BHANOT (115)
 ACTIVITY DIAGRAM
FOR
RESTAURANT MANAGEMENT SYSTEM

SUBMITTED BY:
ISHA BHANOT(115)
ISHIKA GUPTA(111)
AMAN SHARMA(107)
 SEQUENCE DIAGRAM
FOR
RESTAURANT MANAGEMENT SYSTEM

SUBMITTED BY:
ISHA BHANOT(115)
ISHIKA GUPTA(111)
AMAN SHARMA(107)