Software Requirements

Specification
Canteen Management System

Group 8
Sakshi Gite
Harshal Vavale
Abhishek Tupe
Shruti Wagh

16\09\2021
Structure of SRS document 

1.Introduction
   1.1 Purpose.
   1.2 Scope. 
   1.3 Definitions, Acronyms, and Abbreviations
   1.4 Overview
  
 2.Overall Description 
   2.1 Product Perspective.
   2.2 Product Features.
   2.3 User Classes and Characteristics.
   2.4 Operating Environment.
   2.5 Design and Implementation Constraints.
   2.6 Assumptions and Dependencies.  

3.External Interface Requirements 

   3.1 User Interfaces .
   3.2 Hardware Interfaces .
   3.3 Software Interfaces . 

2
4.Other Non functional Requirements 
  4.1 Performance Requirements
  4.2 Security Requirements 
 4.3 Usability Requirements 
  4.4 Software Quality Attributes 
  4.5 Business Rules 

5.Diagrams . 
5.1 DFD 
5.2 Use Case Diagram

3
ABSTRACT

Cafeteria Management System is computer that system that help cafeteria to

manage their cafeteria dairy process, such as order, reservation, redemption and
etc. The entire system consists of back end and front end, which back end was an
offline application and front end was a web site. The offline application allow
cafeteria to manage the cafeteria information and managing the dairy process
such as seat admission and order. And the system allow cafeteria to manage their
meal menu and promotion. And all the updated meal menu and promotion will be
show on the web page automatically upon the completion of updating.
Cafeteria Management System is developed by using Microsoft Visual 2010. The
offline application is developed by using VB.net with object-oriented
programming method, and the web site is developed by using c#. The database is
design and managed by using Microsoft SQL 2007.The current cafeteria is
currently working by using manual way which means fully paperwork, which
consist a lot of man power and time in managing the record and dairy process.
And human mistake is unavoidable while the workload is increasing. Therefore
they request for the developing of Cafeteria Management System, which making
their dairy process form paperwork into automate system. Cafeteria Management
System other than replace their manual dairy work such as enter order, make
reservation and payment, also including new function such as online reservation
and ordering, online meal and promotion viewing, report generating and
reservation notification. With the developing of Cafeteria Management System, it
increases the efficiency of Cafeteria and improves the service, automate system
process able reduce dairy worker, also save time and also cost in long term.

4
 1

Chapter 1 2

This chapter provides the whole

3
project with an introduction.

4
1.Introduction
The Title of our project is CANTEEN MANAGEMENT SYSTEM

As we know a canteen is common for Offices, Factories, Call Centres, Hostels,

Schools, Clubs and Hospitals to operate their own cafeterias for their employees and
students. However, managing the cafeteria menu, attendance and consumption is a
challenging process. Manual and paper based processes are cumbersome and error-
prone, leading to inaccuracies and wastage of time and material. A canteen
management system is essential for keeping track of food consumption. Our project
will offer a canteen management software that tracks item-wise food consumption
and also for a group of users. Different menus can be planned for breakfast, lunch,
dinner, special days and different occasions. This software allows tracking menu
items, speedy transactions and prevents accounting errors. It will also allow users to
select menu items from any android device. 

Purpose  
This SRS describes the functional and non-functional requirements for  the project
Canteen management system. To implement and verify the functionality required by
the user this document is prepared . This document presents a detailed explanation
of the objectives, features, product scope ,design and implementation constraints of
canteen management system. It will also describe how the system will perform and
how it will behave under certain circumstances. Also the required information about
customers will be saved in the system which can be accessed by the system admin. 
6
Scope 
This system will help to manage and run the canteen business
systematically. In this system customers can  easily order their food.
Feedback feature is also implemented so that customers can share their
feedback through which the owner of the canteen can evaluate and make
required changes to the system. All the information about daily expenses
and profit will be saved in the system

Overview 
This document is intended for different types of readers such as canteen
owner i.e. client, system design, system developer as well as tester. This
document has a sequential overview of the whole project starting from
introduction which includes sub parts such as purpose of the document,
scope of the product being implemented, intended audience and many
such related sub parts. The document further describes overall
description of the product which covers sub topics such as perspective
and functionality of the product, operating system characteristics
supported by the system and includes some design and implementation
constraints. The flow of the document then covers some functional and
non-functional requirements of the system.

7
 SRS
Software Requirement Specification is a document that completely describes all of the
Definitions functions of a proposed system and the constraints under which it must operate.

CMS Canteen Management System

SI Software Interfaces

SR Security Requirements

CI Communication Interface

PR Performance Requirements

UI User Interface

8
Few Online Canteen websites

https://www.smunch.com/en/canteen 
https://www.swiggy.com/restaurants/cantee
n-central-erandwane-kothrud-pune-85298
 
https://canteentaco.com/ 

9
 1

Chapter 2
This chapter includes overall product perpectives / 3
features, user characteristics, its operating environment 
.​
4
2 . Overall Description 

2.1 Product Perspective 

The Canteen Management System helps the canteen manager to manage the canteen more
efficiently and effectively, by computerizing meal ordering, billing and inventory controls. The
system, processes transactions and stores the resulting data that will help the manager
generate reports in order to make appropriate business decisions for the canteen. For
example, knowing the number of customers for a particular time interval, the manager can
decide whether more chefs or waiters are required. Moreover, he can easily calculate the
daily expenditure and profit. The whole management system is designed for a general
Computerized, Digital Canteen. So that any canteen owner can use to start an automated
process in his canteen. Implementing this system will 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 and credit cards.

2.2 Product Functionality

All of the functions will be performed in the order given below:
      a. Food order via app 
      b. Confirm order 
      c. Online Payment 
      d. Serve food 
      e. Available good
      f. Required goods 
      g. Customer information 
      h. Customer review 11
2.3 Users and Characteristics

The CMS has three active actors and one cooperating system. The
customers can access the system using their smartphones to order food.
The online payment portal is accessed by the customer to complete the
payment transactions. The chef checks the order, and sends a
confirmation once the customer has paid for his order. After this the chef
starts preparing the food and tells the system if it’s ready. The customer
can then go and collect the food from the collection counter. The admin
can add or delete contents from the menu, edit the price, count total
earnings and expenditure, and take feedback from the customer .

2.4 Operating Environment

The CMS shall operate with the following Web browsers: Microsoft
Internet Explorer and ,Chrome, The CMS shall operate on a server
running the current corporate approved versions of Red Hat Linux and
Apache WebServer.
The CMS shall permit user access from the corporate Intranet and, if a
user is authorized for outside access through the corporate firewall, from
an Internet connection at the user’s home.

12
2.5 Design and Implementation Constraints
There are some constraints that cost the system a-lot. A barrier
that once crossed can optimize the system to its best. Few such
barriers are:
1. IOS App, Android and Windows App
2. Information flow or data flow can be controlled to be more
effective
3. Faster servers such as Linux can be used
4. English language can be used for India
5. C# can be used for more security.

2.6 User Documentation

It will provide specific guidelines to a user for using the CMS. A
video will be provided to demonstrate the functioning of the entire
system

2.7 Assumptions and Dependencies

The canteen is open for breakfast, lunch, and dinner every working
business day in which employees are expected to be on site.
The operation of the CMS depends on changes being made in
System to accept payment requests for meals ordered with the
CMS.
The operation of the CMS depends on changes being made in the
Canteen Inventory System to update the availability of food items
as CMS orders are accepted.
13
 1

Chapter 3
The third chapter records the study process 3
of systems, specifications of requirements
and the design phase of systems for this
project.​ 4

14

3.1 External Interface Requirements
3.1.1 User Interfaces
The CMS screen displays shall
conform to the Process Impact
Internet Application User Interface
Standard, Version 1.0.
The system shall provide a help
link from each displayed HTML
page to explain how to use that
page.
The Web pages shall permit
complete navigation and food item
selection using the keyboard
alone, in addition to using mouse
and keyboard combinations.
3. Specific Requirements
3.1.2 Hardware Interfaces
Windows version 7 or more MAC: OS X
v10.7 or higherLinux: Ubuntu
Processor: Minimum 1 GHz;
Recommended 2GHz or more
Ethernet connection (LAN) OR a wireless
adapter (Wi-Fi)
Hard Drive: Minimum 32 GB;
Recommended 64 GB or more
Memory (RAM): Minimum 1 GB;
Recommended 4 GB or above
Sound card w/speakers
Some classes require a camera and
microphone.
Supported browser chrome play store or
Mozilla Firefox
Another important browser are Adobe
Flash,Adobe reader,Java.
3.1.3 Software Interfaces
Canteen Management System
The CMS shall transmit the quantities
of food items ordered to the CMS
through a programmatic interface.
The CMS shall poll the CMS to
determine whether a requested food
item is available.
When the CMS notifies the CMS that a
specific food item is no longer
available, the CMS shall remove that
food item from the menu for the
current date.
15
 3.1.4 Communications Interfaces

The CMS shall send an message to the customer to confirm acceptance of an order, price, and delivery instructions.
The CMS shall send an message to the admin to report any problems with the meal order or delivery after the order is accepted.

3.2 Functional Requirements

1. Registration and 2. Menu and Ordering 3. Payment System 4. Chef’s Portal 5. Feedback System
Login System System System

a. Enable a new user to a. Enable the customers a. Display the payment a. Enable the Chef to a. Enable a registered
register to the to go through the bill to the customer. check all placed user to submit a
system. menu and add his b. Enable the customer orders. Feedback on the CMS,
b. Authenticate and choices to the cart. to pay for the placed b. Enable him/her to which contains a
allow user to login on b. Enable him/her to order by credit/debit display the status of detailed explanation
the web app. c. edit his choices card, GooglePay or each order either to his problem if any.
Enable a registered before proceeding to Paytm. c. Enable the “Preparing order” b. Enable the admin to
user to change his place the order. system to notify the or “Ready to pick view, open and closed
password if forgotten. admin of the up”. the submitted
successful Feedback.
transaction. c. Enable the admin to
post a reply to the
Feedback given.
3.2 Non Functional Requirements 

The web application Non-registered members

shall ensure sensitive will not be able to access
information is secure. the functionalities.
Performance Security Usability  Security  Configuration
When the URL is  The web application The web application
searched, the web shall be user-friendly  shall run well on
application will run desktop and mobile
unless the user is not devices
connected to the
internet.

17
 1

Chapter 4 2

A brief explanation with the help of DFD

Diagram , Use case Diagram and class
3
diagram.

18
 Employee
Management

Canteen Meal Type

Management management
DFD LEVWL 0

Canteen
Management
System

Company System user

management management

Login
management
19
 Order status Order status

Order status
Customer details Register
Customer
Confirmation Chef
Order

Order details
Menu details

Food ordering Order details Admin

Bill/receipt Order details

Bill generation Bill/receipt Invoice creation Menu items and prices

20
 Register

Order details
USE CASE DIAGRAM Customer details

Menu items &

chef
prices

Menu details

Food ordering
Customer 
Confirmation
Order
Admin\manager 
Bill generation
Order status

Bill/receipt

Invoice creation

21
USE CASE DIAGRAM OF MEAL ORDERING
View order 

Add meal order chef

Includes 
Check details 
Customer 

Edit meal order 

Admin\manager 
Confirm order  

22
24