CMS

Software Requirements
Specification
For

Canteen Management System

(CMS)
Version 1.0

February, 2012.

Prepared by,

S.Aishwarya

M.Fathima

E.Nivethetha

K.A.Punnakhai

1
CMS

Table of Contents
List of figures………………………………………………………………...4

List of tables………………………………………………………………....4
1. Introduction…………………………………………………………………………….5

1.1 Purpose……………………………………………………………………………..5

1.2 Scope……………………………………………………………………………….5

1.3 Definitions………………………………………………………………………….5

1.4 References………………………………………………………………………….6

1.5 Document Overview……………………………………………………………….6

2. Overall Description…………………………………………………………………….7

2.1 Product Perspective………………………………………………………………....7

2.2 User classes and Characteristics…………………………………………………….7

2.3 Operating environment…………………………………………………………….10

2.4 Design and Implementation constraints……………………………………………10

2.5 User Documentation…………………………………………………………….....10

2.6 Assumptions and Dependencies…………………………………………………...10

3. Functional Requirements……………………………………………………………..11

3.1 Bill Processing for staffs…………………………………………………………...11

3.2 Bill Processing for students………………………………………………………...13

3.3 Canteen inventory details…………………………………………………………..15

3.4 Account maintenance………………………………………………………………15

4. Specific Requirements……………………………………………………………........16

4.1 External Interfaces…………………………………………………………….........19

4.2 User Interfaces……………………………………………………………………...19

2
CMS

4.3 Software Interfaces………………………………………………………………20

4.4 Hardware Interfaces……………………………………………………………...20

4.5 Communication Interfaces………………………………………………………..20

5. Non-functional Requirements………………………………………………………20

5.1 Performance requirements………………………………………………………..20

5.2 Logical Database Requirements…………………………………………………..21

5.3 Reliability………………………………………………………………………….22

5.4 Availability………………………………………………………………………...22

5.5 Security…………………………………………………………………………….22

5.6 Maintainability…………………………………………………………………….22

5.7 Portability…………………………………………………………………………..22

APPENDIX………………………………………………………………………………23

3
CMS

LIST OF FIGURES:

2.1 Overall Architecture for Canteen Management System………………………….8

4.1 Use case Diagram…………………………………………………………………16

4.2 Sequence Diagram…………………………………………………………………17

LIST OF TABLES:

4.1 Canteen management system user interface system………………………………18

4
CMS

1. Introduction:

1.1 Purpose:
The Software Requirements Specification provides a complete description of all the
functions and specifications of PSG Institutions, Coimbatore for Canteen Management
System.
The expected Audience of this document is the students, faculties and management who
are part of the canteen of PSG Institutions.
This will also serve as the reference for managing tokens, rupees and billing services that
consumes much of the time for canteen.

1.2 Scope:
This canteen management system is designed to run-on the main canteen of PSG College
of technology and all sub groups that belong to the main canteen which includes the
PSGIM canteen, PSG school canteen and other sub groups available at A-block, I-block
and PSG hostels. Every detail of food sales in each canteen can be accessed in the main
canteen. All the details will be held in the Main canteen server.

1.3 Definitions:

Term Definitions

Customer students and staffs of PSG institutions

ODE oracle database engine
CI configuring items
Entry Customer details on the database
IEEE Institute of electrical and electronics
engineering
QA Quality assurance
SRS Software Requirements Specification
PSG tech PSG College of technology

5
CMS

PSGIM PSG institute of management

Website About PSG canteens

1.4 References:

[IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,” 2009
edition.

[Bruade] The principal source of textbook material is “Software Engineering: An Object-

Oriented Perspective” by Eric J. Bruade (Wiley 2001).

1.5 Document Overview:

The canteen management system contains four modules namely

 Student module
 Staff module
 Inventory module
 Administrative module.

Each module provides the details and unique identity of each customer and the amount of intake
by each person is deducted from the amount paid along with the fees or from salary.

6
CMS

2. Overall Description

2.1 Product Perspective

The Canteen Management System is an automated, stand alone system that replaces the existing
token system for ordering and picking up menus in college canteen. The System connects to all
its sub-canteens through internet, maintains the inventory details of all sub-canteens and the
authorization services of college staff and students.

2.2User Classes and Characteristics

2.2.1 Administrator

The Administrator maintains the staff and student database. The Administrator saves the details
of all the transactions, canteen inventory details at all the sub-canteens in a single server. The
Administrator performs the authorization of the staff and students.

2.2.2 The Canteen Reader

In the Canteen, User will show the card to the “Canteen reader”, and then if it is a valid card the
reader will send the card code to the server.

2.2.3Canteen Management System

Server stores the student and staff database, canteen inventory details and also the account details
of the canteen. All transactions details (order no, date, student roll no/employee id, and amount)
are also saved. Server will validate the card and will issue a Print Command directly to the
Printer in card reader. The bill is presented by the person to the canteen personnel.

2.2.4 Canteen Staff

The Canteen Staff delivers the food items to the customer.

7
CMS

2.2.5 Menu Manager

The Menu Manager is a canteen employee, perhaps the canteen manager, who is responsible for
establishing and maintaining daily menus of the food items available from the canteen and the
times of day that each item is available. Some menu items may not be available for delivery. The
Menu Manager will also define the canteen’s daily specials. The Menu Manager will need to edit
the menus periodically to reflect planned food items that are not available or price changes.

2.2.6 Customer

The staff/student swipes his card for verification. If he is a valid user, the card reader displays the
menu items and prices from which the customer places his order. The card reader generates the
bill, with which the customer can buy meals.

8
CMS

Overall Architecture for Canteen Management

System

login, choose items, confirm order/cancel order

Validates user, provides balance details

Canteen Card reader

customer

Manages database, user authorization, canteen inventory details

connects for validation

administrator

Menu Configuration

Canteen management system

Menu manager

Sub-canteen Sub-canteen
server1 server 2

FIGURE 2.1

9
CMS

2.3Operating Environment

OE-1: The Canteen Management System shall operate with the following Web browsers:
Microsoft Internet Explorer versions 5.0 and 6.0, Netscape Communicator version
4.7, and Netscape versions 6 and 7, Google chrome.
OE-2: The Canteen Management System shall operate on a server running the current
corporate approved versions of Microsoft Windows.
OE-3: The Canteen Management System 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 sub-canteens.

2.4Design and Implementation Constraints

CO-1: The system’s design, code, and maintenance documentation shall conform to the
Process Impact Intranet Development Standard, Version 1.3.
CO-2: The system shall use the current corporate standard Oracle or Microsoft Access
database.

2.5User Documentation

UD-1: The system shall provide an online hierarchical and cross-linked help system in
HTML that describes and illustrates all system functions.
UD-2: The first time a new user accesses the card reader system and on user demand
thereafter, the system shall provide an online tutorial to allow users to practice
ordering meals using a static tutorial menu.
UD-3: The canteen card reader system is not required to save the orders.
UD-4: The CMS Server saves the transaction details.

2.6Assumptions and Dependencies

AS-1: The canteen is open from 8am to 7pm on every working day of college.
DE-1: The operation of the CMS depends on changes being made in the Payroll System
to accept payment requests for menu ordered.
DE-2: The operation of the CMS depends on changes being made in the Canteen
Inventory System to update the availability of food items.

10
CMS

DE-3: The operation of CMS depends on the availability of balance in a student’s

canteen account.

3. Functional Requirements:

The functional requirements for the Canteen Management System is divided into four main
categories Canteen inventory, Bill Processing for students ,Bill Processing for staffs, Account
Maintenance.

3.1) Bill Processing for staffs:

3.1.1) Log-In:
The system shall let a staff to access their account after swiping their
ID-card in CMS card reader and entering a valid password.
3.1.2) Confirmation:
The system shall confirm that the staff is registered for payroll
deduction to place an order.
3.1.3) Menu Available:
The menu for the current date which is available in the canteen will be
displayed on the screen.
3.1.4) Order Item:
The system shall allow the staff to indicate the number of units of each
menu item that he wishes to order. If the amount of item ordered by the
person exceeds the availability then the system will inform the
available count and asks the customer to either cancel the item or place
another order.
3.1.5) Order Confirmation:
When the person indicates that he does not wish to order any more food
items, the system shall display the food items ordered, the individual
food item prices, and the payment amount.
3.1.6) Order Not Confirm:

11
CMS

If the person does not confirm the order, the person may either edit or
cancel the order. The system shall let the person to order additional
food item for the same date.
3.1.7) Order Payment:
If the person confirmed the order, then the system shall issue a
payment request to the CMS server. If the payment request is
accepted, the system shall display a message confirming acceptance
of the order with the bill number to the person.
3.1.8) Order Done Inventory:
A message is sent to the CMS server with the number of units of
each food item in the order.
3.1.9) Order Done Menu:
Update the menu to reflect any items that are now out of stock in
the canteen’s inventory.
3.1.10) Bill generation:
Bill will be generated for menu specified by the customer.
3.1.11) Order details:
The system shall permit the person to view his transactions
performed in previous month through intranet using login ID and
password.
3.1.12) Change password:
The person accessing Canteen Management system will be able to
change their password.

12
CMS

3.2) Bill Processing for Students:

3. 2.1) Log-In:
The system shall let a student to access their account after swiping their
ID-card in CMS card reader and giving a valid password.

3.2.2) Confirmation:
The system shall validate the student and shows the balance amount
available for the student after which he can place an order.
3.2.3) Menu Available:
The menu for the current date which is available in the canteen will be
displayed on the screen.
3. 2.4) Order Item:
The system shall allow the staff to indicate the number of units of each
menu item that he wishes to order. If the amount of item ordered by the
person exceeds the availability then the system will inform the
available count and asks the customer to either cancel the item or place
another order.

3.2.5) Order Confirmation:

When the person indicates that he does not wish to order any more food
items, the system shall display the food items ordered, the individual food
item prices, and the payment amount.

13
CMS

3. 2.6) Order Not Confirm:

If the person does not confirm the order, the person may either edit or
cancel the order. The system shall let the person to order additional
food item for the same date.

3.2.7) Order Payment:

If the person confirmed the order, the system shall issue a payment
request to the CMS server to check the balance. If the balance
amount is available then payment request is accepted, the system
shall display a message confirming acceptance of the order with
the Roll number. If not it rejects the order or requests the student
to cancel some items chosen.

3.2.8) Order Done Inventory:

A message is sent to the CMS server with the number of units of
each food item in the order.

3.2.9) Order Done Menu:

Update the menu to reflect any items that are now out of stock in
the canteen’s inventory.

3.2.10) Bill generation:

Bill will be generated for order specified by the customer.

3.2.11) Order details:

The system shall permit the student to view his transactions
performed in current semester through intranet using login ID and
password.
3.2.12) Change password:

14
CMS

The person accessing Canteen Management system will be able to

change their password.

3.3) Canteen inventory details:

3.3.1) Availability:
The system keeps track of the all food items available in the
canteen. The menu manager can access or modify the details
present in the menu.
3.3.2) Addition of information:
The system shall allow menu manager for adding the information
regarding menu items and prices.
3.3.3) Deletion of information:
The system shall allow menu manager for the deletion of
information regarding menu items and prices.

3.3.4) Assign password:

The system shall allow system administrator to assign
password to the student and staff initially.

15
CMS

3.4) Account Maintenance:

3.4.1) Student details:

The student name, roll number, purchase details, branch
details, and his balance details should be
maintained.

3.4.2) Staff details:

The staff name, employee id, purchase details, branch details and
amount to be paid should be maintained.
3.4.3) Profit details:
Outside sellers who have stalls in canteen must pay 16% of
amount from their profit.

3.4.4) Daily expense maintenance:

Details of daily sale in all the branches are saved in the CMS
server.

4.Specific Requirements
This section contains all the software requirements at a level of detail, that when combined with
the overall system architecture, use cases, and use case descriptions, is sufficient to enable
designers to design a system to satisfy those requirements, and testers to test that the system
satisfies those requirements.

16
CMS

USE CASE DIAGRAM

Login

Display menu
Customer

Select item

Check availability

Canteen card
reader
confirm order

generate bill

display balance

validate user

Canteen
Manageme...
transaction details

edit menu

Menu manager
generate menu

Authourize users
Administrator

maintain database

inventory management

FIGURE 4.1

17
CMS

SEQUENCE DIAGRAM

customer canteen card Canteen Management

reader System
login

validate user

Displays menu

Choose food items

Checks availability

asks for order confirmation

confirms order

issues print command

print bill

takes bill

FIGURE 4.2

18
CMS

4.1 External Interfaces

The Canteen Management System will use the standard input/output devices for a personal
computer. This includes the following:

 Keyboard
 Monitor
 Printer

4.2 User Interfaces

The User Interface Screens are described in table 4.1.

Table 4.1: Canteen Management System User Interface Screens

Screen Name Description

Login Log into the system as a Customer, administrator or menu

manager

Services offered Create order, modify order, view order, cancel order, generate bill

Customer Record Add or update customer records (student and staff)

Administer Menu Availability of food items and rates.

Administer User Create, modify, and delete users, change password

Administer Meals Create, modify, and delete meal items and prices

Reports Select, view, save, and delete reports

19
CMS

4.3 Software Interfaces

The system shall interface with an Oracle or Access database.

4.4 Hardware Interfaces

The system shall run on a Microsoft Windows based system.

4.5 Communication Interfaces

The system shall be a standalone product that does not require any communication interfaces.

5. Non-functional Requirements

Nonfunctional requirements define the needs in terms of performance, logical database

requirements, reliability, availability, security, maintainability, and portability.

5.1 Performance Requirements

Performance requirements define acceptable response times for system functionality.

 The load time for user interface screens shall take no longer than two seconds.
 The log in information shall be verified within five seconds.
 Responses to queries shall take no longer than 4 seconds to load onto the screen after the
user submits the query.
 The system shall display confirmation messages to users within 4 seconds after the user
submits information to the system.
 The system shall accommodate 10 users during the peak usage time window of 8:00am to
10:00am, 12:00pm to 2:00pm, 3:00pm to 6:00pm local time, with estimated average
session duration of 8 minutes.
 The generation of bill takes not more than 10 seconds.

20
CMS

5.2 Logical Database Requirements

The logical database requirements include the retention of the following data elements. This list
is not a complete list and is designed as a starting point for development.

5.2.1 Ordering system

 Customer name
 Customer identity(Roll number/employee id)
 Customer phone number
 Rate description
 Bill number
 order date/time
 Payment received (yes/no)
 Payment reduction type
 Total Bill
5.2.2 Food Services

 Food
 Food type
 Food item
 Food order
 Food payment
 Food availability
 Food rate

21
CMS

5.3 Reliability

 The system allows the details of the transactions to be reflected in the respective
databases and hence it remains consistent.
 The system updates the menu details after each ordering which allows the
customer to order items which is available in the canteen at that particular time.

5.4 Availability

The system shall be available during normal canteen operating hours.

5.5 Security

Administrator and Mess Manager will be able to log in to the Canteen Management System.
Administrator will have access to the various databases and other canteen sub-systems. Menu
Manager will have access to the Food subsystems in order to frame the menu for that particular
day. Access to the various other subsystems will be protected by a user log in screen that requires
a user name and password.

5.6 Maintainability

The Canteen Management System is being developed in Java. Java is an object oriented
programming language and shall be easy to maintain. Administrator is responsible for the
maintenance of the entire system.

5.7 Portability

The Canteen Management System shall run in any Microsoft Windows environment that
contains Java Runtime and the Microsoft Access database.

22
CMS

APPENDIX

account 7,10,11,13,15
administrator 7,15,22
architecture 9
assumptions 10
availability 21
canteen card reader 10,11
5,7,10,11,12,14,19,2
canteen management system 2
canteen staff 7
CMS server 10,12,14,16
communication 20
constraints 10
dependency 10
documentation 10
external 19
functional requirements 11
hardware 20
interface 19
inventory 6,7,10,11,12,14,15
logical 21
maintainability 22
menu manager 8,15,22
nonfunctional requirements 20
operating environment 10
performance 21
portability 22
reliability 21
security 22
software 20
software requirement specification 5
specific requirements 16
user 19

23
CMS

24
CMS

25