Software Requirements Specification for restaurant management system

Software Requirements
Specification
for
Restaurant Management
System
Final Version
Prepared by-
S.M.Sadman Sadid
ID: 2013-1-60-065
Akib-An-Noor
ID: 2013-1-60-056
Instructor: MD. Habibullah Rana
Course: CSE 411
Section: 02
Date: 06-10-2016

Contents
1 INTRODUCTION
1.1 DOCUMENT PURPOSE
1.2 PRODUCT SCOPE
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
1.5 REFERENCES AND ACKNOWLEDGMENTS
2 OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
2.2 PRODUCT FUNCTIONALITY
2.3 USERS AND CHARACTERISTICS
2.4 OPERATING ENVIRONMENT
2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS
2.6 USER DOCUMENTATION
2.7 ASSUMPTIONS AND DEPENDENCIES
3 SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENTS
3.2 FUNCTIONAL REQUIREMENTS
3.3 BEHAVIOUR REQUIREMENTS
4 OTHER NON-FUNCTIONAL REQUIREMENTS
4.1 PERFORMANCE REQUIREMENTS
4.2 SAFETY AND SECURITY REQUIREMENTS
4.3 SOFTWARE QUALITY ATTRIBUTES
5 OTHER REQUIREMENTS

SRS for Restaurant Management System
1.1 Document Purpose
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. In this
document it will be also shown user interface. Both the stakeholders and the
developers of the system can benefit from this document.
1.2 Product Scope
This system will help to manage and run the restaurant business systematically. In this
management system, we will provide an app that can be used by the customers to
order food. Customers can also give feedback through this app. So that 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 payment through debit or credit cards using POS
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.
1.3 Intended Audience and Document Overview
This document is intended for different types of readers such as restaurant owner,
system designer, system developer and tester. By reading this document a reader can
learn about what the project is implemented for and how it will present it’s basic ideas.

This document has a sequential overview of the whole project so if a reader reads the
document from top to bottom, he will get a clear idea about the project.
1.4 Definitions, Acronyms and Abbreviations
We will also use bold letter to emphasis main topics and for all the major functions of
the system. Underline will represent hyperlink. Italic will represent acronyms and
useful notes.
We will use some acronyms through this document. Abbreviations and definition of
some useful terms we will use are given below :
Term Definition
System Admin System admin is a person who is responsible for managing
the whole system and who has full access to the system.
System User A person who is using or operating the system but with a
limited privilege.
Database Collection of all the information monitored by this system.
Field A cell within a form.
Software Requirements
Specification (SRS)
A document that completely describes all of the functions
of a proposed system and the constraints under which it
must operate. For example, this document.
Stakeholder Any person who is involved in the development process of
the software.
Point of Sale (POS) A point of sale system 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 beverage 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.
1.5 References
www.google.com-the world's information.
www.wikipedia.com-free online encyclopedia.
www.cnet.com -technology portal.
www.slideshare.net-the world's largest professional content sharing
community.
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software
Requirements Specifications. IEEE Computer Society, 1998.
2.1 Product Perspective
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. Moreover, easily calculate daily expenditure and profit.
The whole management system is designed for a general ComputerizedDigital
Restaurant. So that any restaurant owner can get it and can start automated process to
his restaurant.
2.2 Product Functionality
Whole functions will performed through this order.
 Food Order via App
 Take Order
 Serve Food
 Payment
 Available Good
 Required Goods
 Customer Information
 Customer Review
2.3 Users and Characteristics
The Restaurant Management System has five active actors and one cooperating

system. The customer can access the system through wifi connection 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 chef through the
system and deliver it to the right table. The cashier can access the system and receive
the payment from customers. The Admin can edit the price, count total earning and
expenditure.
2.4 Operating Environment
Operating System : Minimum Windows XP or Windows VISTA. Better
environment Windows 7, 8, 8.1, 10.
Language : Java
It is need to use Smartphoneto place food order in this system. Which will running on
Android Operating System. (We will provide the android app to place order with the
system.) Whole system should be covered by WiFi connection. And a display for Chef
in kitchen.
To maintain whole system these requirement can be followed to provide best
environment(Not mandatory):
>> 3 computer. (One for owner, one for cashier, one for manager)
>> 2-3 Tablets with android operating system. (These are for those customer who
haven’t android smartphone)

2.5 Design and Implementation Constraints
There are some constraints which costs more for the system. If those constraints can
overcome then this whole system will perform best. They are-
1. IOS App and Windows App.
2. Information flow or data flow can be controled and more effective.
3. Faster server system such as LINUX server.
4. Bengali language for Bangladesh and Other language for other countries.
5. C# can be use for more security.
2.6 User Documentation
It will provide specific guidelines to a user for using the Restaurant management
system. Further more a Video (Slide Show) will be provided which will represent the
whole system function and how it works.
2.7 Assumptions and Dependencies
If this system have IOS and Windows app then customers who use such kind of
smartphone (windows and ios) will be more benefited. If there are more Tablets for
each tables the whole system performance will be better. For more secure system it is
beneficial to use CC camera and TV.

3.1 External Interface Requirements
There are many types of interfaces as such supported by this software system namely;
User Interface, Software Interface and Hardware Interface.
3.1.1 User Interfaces
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 the food
order easily. Customers can also give feedback through it easily with some demo
comment or if they are keen to write their review by own they can do it.
3.1.2 Hardware Interfaces
There shall be logical address of the system in IPv6 format.
3.1.3 Software Interfaces
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.

3.1.4 Communications Interfaces
Communication function required the Internet protocol version 6 and it will follow
HTTPS. It will use FTP for whole system with local server. And email
communication to device to device of the system.
3.2 Functional Requirements
3.2.1 Food Order via App
Customer can order food with the app but it needs specific wifi connection.
3.2.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.2.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 insure the order as served.
3.2.4 Payment
The cashier will receive the payment if the customer is a member he or she will
get discount.

3.2.5 Available Good
The Chef will add what goods are available and the admin can see that data.
3.2.6 Required Goods
The chef will add what goods are required.
3.2.7 Customer Information
The customer will be get registered and be the member of special customer.
3.2.8 Customer Review
Customer can give overall review about the food and services.
3.3 Behaviour Requirements
3.3.1 Use Case View
The use cases for each of the actors are described in this section.
Customer Use Case
Use case: Order Food
Description
The Customer can order food and see their payment receipt and pay.

Chef Use Case
Use case: Prepare Food
Description
The chef can see the orders of 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.
Waiter Use Case
Use case: Serve Food
Description
The waiter can see the food orders and the ready foods in the kitchen to be
served. After serving the food the waiter will mark the order as served.
Cashier Use Case
Use case: Take Payment
Description
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.

Admin Use Case
Use case: Maintain System
Description
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.
4.1 Performance Requirements
 The product will be based on local server.
 The product will take initial load time.
 The performance will depend upon hardware components.
 Payment system will be fully secure through POS system.
 Different database for employee.
4.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.

 This system will use HTTPS. Because of this protocol this is more secure.
 This system will use secured POS system.
5. Other Requirements
5.1 Licensing Requirements
Not Applicable
5.2 Legal, Copyright, and Other Notices
All right reserved by our team.
5.3 Applicable Standards
It should be as per the industry standard.

Software Requirements Specification for restaurant management system

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Software Requirements Specification for restaurant management system

Similar to Software Requirements Specification for restaurant management system (20)

More from SM. Aurnob

More from SM. Aurnob (15)

Recently uploaded

Recently uploaded (20)

Software Requirements Specification for restaurant management system