The Islamia University of Bahawalpur

Canteen Automa on System

BY

Faraz Ahmad
S22BDOCS1M01171
BACHELOUR OF COMPUTER SCIENCE
ti
 Canteen Automation System

The Islamia University of Bahawalpur

Canteen Automa on System

BY

Faraz Ahmad
S22BDOCS1M01171
A dissertation submitted to
Department of Computer Science

In partial fulfillment of the

requirements for the Degree of

BACHELOUR OF COMPUTER SCIENCE

ii
ti
 Canteen Automation System

The Islamia University of Bahawalpur

Canteen Automa on System

BY

Faraz Ahmad
S22BDOCS1M01171
______________________________________________________________________

A dissertation submitted to Department of Computer Science, in partial

fulfillment of the requirements for the degree of

BACHELOUR OF COMPUTER SCIENCE

____________________________________________________
Dissertation Committee:

____________________________
Head Of Department

____________________________
Final Year Project Coordinator

____________________________
Supervisor

iii
ti
 Canteen Automation System

DECLARATION

This is to certify that this research work has not been submitted for
obtaining similar degree from any other university/college.

(Faraz Ahmad)
Date

iv
 Canteen Automation System

Canteen Automa on System

SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT

20.05.2025

Faraz Ahmad S22BDOCS1M01171

SESSION: 2022 - 2026
Computer Science/ ISLAMIA UNIVERSITY OF BAHAWALPUR
v
ti
 Canteen Automation System

Document Approval
The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

Mr Akmal Supervisor

vi
 Canteen Automation System

Table of Contents
1. Introduction 1
1.1 Purpose 1
2. Scope 1
1.3 Definitions, Acronyms, and Abbreviations. 2
1.5 Overview 3
Core Features 3

2.The Overall Description 5

This section provides a high-level overview of the Canteen Automation System (CAS), explaining its general
background, how it fits into the larger operational framework, and its role compared to similar systems in the
market. 5

2.1Product Perspective 5
2.1.1 Operations 5
2.1.2 Site Adaptation Requirements 6

2.2 Product Functions 7

2.3 User Characteristics 7

Customers 7
Management 7
Users with the highest privileges, responsible for managing users, orders, menus, and system settings.
Moderate to advanced technical skills; familiar with database concepts and administrative tools. 7
2.4 General Constraints 7

2.5 Assumptions and Dependencies 8

2.5.1 Assumptions 8
2.5.2 Dependencies 8
3 Specific Requirements 10
3.1.1 User Interfaces 10
3.1.2 Hardware Interfaces 10
3.1.3 Software Interfaces 10
3.2 Functional Requirements 11
3.2.1 User Authentication and Access Control 11
3.2.2. Menu Management 11
3.2.3. Order Management 11
3.2.4. Inventory Management 11
3.2.5. Reporting and Analytics 12
3.2.6. Customer Feedback and Ratings 12
3.3 Non-Functional Requirements 12
3.4 Logical Database Requirements 14
3.5 Design Constraints 16
. 16
4.1 Use Case 19
2. Sequence Diagrams 19
4.2.1customer 19

vii
 Canteen Automation System

4.3 Data Flow Diagrams (DFD) 21

3. State-Transition Diagrams (STD) 24
4.3.1User 24
4.3 State-Transition Diagrams (STD) 25
4.3.2. Admin 25
4.5 Class Diagram (CD) 26

5. Supporting Information 28

6. Architecture 30

Chapter No 1

viii
1. Introduction
The Project "Canteen Automation System" enables the end users to register online, read and select the
food from e-menu and order food online by just selecting the food that the user want to have using
website.. The manual system involves paperwork in the form of maintaining various files and manuals.
Nowadays people don't have much time to spend in canteen by just there and waiting for the waiter to
take their order. Many customers visit the canteen in their lunch break and recess so they have limited
time to eat and return to their respective office and Class. So this website helps them to save time and
order food.

1.1 Purpose

The main objective of online food ordering system is to automate the existing manual
system with the help of advance computerized software so, that valuable data can be
stored for longer period with easy accessing and manipulation of the same. In Online
Food Ordering System Admin can handle the functionalities like add new food items,
edit/delete food items, Enable/Disable the food items according to season and
availability. Admin have authority to view order details and update the delivery status of
food. process of ordering, managing, and delivering food in a canteen environment,
providing efficiency, accuracy, and customer satisfaction.

2. Scope

This project aims to cater to two primary types of users: students and administrative staff.
1. Students:
o Browse food products and menus.
o Place and manage orders.
o View real-time updates on order status.
2. Administrative Users (Admins and Assigned Users):
o Monitor and manage all orders placed by students.
o Update the status of orders (e.g., pending, prepared, served).
o Manage menus and product listings.

SRS Page 1 2025-01-13

 o Assign specific roles and permissions to users based on their scope of work.
The system consists of two panels:
• Admin Panel: Accessible by administrators for managing users, orders, and product
menus.

• User Panel: Designed for students to interact with food product listings and place orders

1.3 Definitions, Acronyms, and Abbreviations.

• CAS: Canteen Automation System.

• React.js: A JavaScript library for building user interfaces.

• Firebase: A cloud platform for database management, authentication, and hosting.

• Admin Panel: The interface for administrators to control and monitor canteen operations.

• User Panel: The interface for students to browse and order food

1.4 REFERENCES
h ps://nevonprojects.com/canteen-automa on-system/
h ps://digiicampus.com/mess-canteen-automa on

h ps://skyservice.pro/en/automa on/canteen/

SRS Page 2 2025-01-13

tt
tt
tt
ti
ti
ti
 1.5 Overview

This report outlines the design, func onality, and development phases of the Canteen Automa on
System. It includes the system's architecture, func onal requirements, implementa on strategy, and
tes ng plan. The aim is to create a reliable, scalable, and user-friendly pla orm that meets the
opera onal needs of a modern canteen.

Core Features
1. User Management:
o Role-based authen ca on for Admins, Sta , and Students.
o Easy account crea on, secure login, and pro le management.

2. Menu and Product Management:

o Admins can add, edit, and remove products.
o Products categorized by meal type (e.g., breakfast, lunch, snacks).

3. Order Management:
o Students can place orders by selec ng items from the menu.
o Sta can view and update order statuses (e.g., Pending, Preparing, Completed).
o Real- me no ca ons for order updates.

4. Admin Dashboard:
o Manage all users and roles.
o Generate reports for orders, sales, and product performance.
o Monitor and control all canteen opera ons.

5. Real-Time Updates:
o Firebase ensures instant updates for orders, menus.

SRS Page 3 2025-01-13

ti
ff
ti
ti
ti
fi
ti
ti
ti
ti
ti
ti
ti
f
fi
ti
tf
ti
ti
 Chapter No 2

SRS Page 4 2025-01-13

 2.The Overall Description

This section provides a high-level overview of the Canteen Automation System (CAS),
explaining its general background, how it fits into the larger operational framework, and
its role compared to similar systems in the market.

2.1Product Perspective
The Canteen Automation System (CAS) is a standalone software product that operates
independently to enhance the efficiency of canteen operations. While it does not rely on external
systems for its core functionality, it leverages Firebase services for database management,
authentication, and real-time updates.
Context in Comparison with Other Systems
CAS differentiates itself by offering a dual-interface design:
1. Admin Panel: Designed for administra ve control over user roles, order management, and menu
updates.
2. User Panel: A user-friendly interface for students to browse menus and place orders seamlessly.

Compared to existing canteen or restaurant management systems.

• Real- me order tracking for students.
• Role-based access control for administra ve users.
.

2.1.1 Operations
i. User registration:
o Users can create accounts to access the system.
ii. Interac ve Opera ons:

SRS Page 5 2025-01-13

ti
ti
ti
ti
ti
 o Customers can interact web platforms to browse the menu orders, and
make payments.
o Admin receive orders in real-time via a dedicated display system, allowing
for efficient order preparation.
o Administrators can monitor transactions, and sales performance through
an intuitive dashboard.
iii. Una ended Opera ons:
o The system is capable of processing automated reports on sales, inventory
status, and performance metrics, which are sent to administrators
periodically.
o Scheduled inventory checks and updates ensure stock levels are
maintained without manual intervention.
iv. Data Processing Support:
o The system processes and stores customer orders, payment records, and
inventory transactions in a centralized database.
o Real-time synchronization ensures consistency across all interfaces,
including customer, kitchen, and administrative systems.
v. Backup and Recovery:
o Automatic data backups are performed daily to ensure minimal data loss
in the event of a system failure.
o Recovery protocols allow for quick restoration of operations with minimal
downtime.

2.1.2 Site Adaptation Requirements

• Internet connec on to allow real- me updates of orders and payments.

SRS Page 6 2025-01-13

tt
ti
ti
ti
 2.2 Product Functions

• Food order via web

• Confirm order
• Available good
• Required goods
• Customer information
• Customer Review
• Inventory Management

2.3 User Characteristics

Customers
Primary users of the system, responsible for placing orders and tracking their status.. Basic
computer or smartphone skills, such as naviga ng a website knowledge.

Management

Users with the highest privileges, responsible for managing users, orders, menus, and system
se ngs. Moderate to advanced technical skills; familiar with database concepts and
administra ve tools.

2.4 General Constraints

• The system must adhere to data protec on regula ons.
• The system must support high tra c during peak hours in the canteen.

SRS Page 7 2025-01-13

tti
ti
ffi
ti
ti
ti
 2.5 Assumptions and Dependencies
2.5.1 Assumptions
1. Opera onal Hours:

o The canteen is assumed to operate during breakfast, lunch, and dinner hours on all
working business days when employees are expected to be on-site.

2. User Engagement:

o It is assumed that users will ac vely interact with the system, using features such as
menu browsing, order customiza on, and feedback submission. For speci c learning
components, such as quizzes on tra c rules, it is expected that users will genuinely
engage to improve their knowledge.

2.5.2 Dependencies
1. External Systems and Infrastructure:
o The CAS requires stable internet connec vity for real- me opera ons, including order
processing, payment gateway communica on, and inventory updates.

SRS Page 8 2025-01-13

ti
ti
ti
ffi
ti
ti
ti
ti
fi
 Chapter No 3

SRS Page 9 2025-01-13

3 Specific Requirements
3.1.1 User Interfaces

• The system will provide a web applica on compatible with major browsers, including

Chrome, Firefox, and Safari.

3.1.2 Hardware Interfaces

• Computers,Tablet,Mobile,etc

3.1.3 Software Interfaces

• The system will integrate with notification services, such as Firebase, to provide timely

alerts for orders, inventory updates, and administrative tasks.

SRS Page 10 2025-01-13

ti
 3.2 Functional Requirements

3.2.1 User Authentication and Access Control

• Login/Registra on:
o customers, and administrators can log in or register.
o Password reset func onality for all users.

3.2.2. Menu Management

• Menu Display:
o Customers can view the menu with details like price, descrip on, and availability.
• Menu Updates:
o Admins can add, edit, or remove items from the menu.
o Real- me updates to re ect changes in inventory or pricing.

3.2.3. Order Management

• Order Placement:
o Customers can select items from the menu and place an order.
• Order Processing:
o Sta receive no ca ons for new orders and update their status (e.g., “Preparing,”
“Ready,” or “Delivered”).
• Order Tracking:
o Customers can track the status of their orders in real- me.
• Payment Integra on:
o Mul ple payment op ons (e.g., cash, credit/debit cards, mobile wallets).
o Provide invoice/receipt a er payment.

3.2.4. Inventory Management

• Stock Monitoring:
o Track available stock for each menu item in real- me.
• Restocking:
o Admins/sta can update stock details in the system.

SRS Page 11 2025-01-13

ff
ti
ti
ff
ti
ti
ti
fi
ti
ti
ti
fl
ft
ti
ti
ti
 3.2.5. Reporting and Analytics
• Sales Reports:
o Generate daily, weekly, and monthly sales reports.

3.2.6. Customer Feedback and Ratings

• Feedback System:
o Customers can rate their experience and provide feedback for improvement.
• Feedback Analysis:
o Admins/ can analyze feedback to improve service quality.

3.2.7. Billing
The billing functionality is designed to automate the process of calculating the total cost of an
order, including taxes, discounts, and providing receipts for customers.

3.3 Non-Functional Requirements

Non-functional requirements describe the system's attributes, performance, and constraints. They
define how the system should operate rather than what it should do. For the Canteen Automation
System, these non-functional requirements are critical in ensuring reliability, security, user
satisfaction, and system efficiency. Below are the key non-functional requirements for the
system:

3.3.1 Performance
Performance defines the system's ability to handle various tasks efficiently and in a timely
manner.
1. Response Time:

o The system must respond to user ac ons (such as menu browsing, order placement, and
checkout) to ensure a smooth user experience.

2. Scalability:

o The system should support scalability for future expansion, allowing new features or
addi onal users to be added without a signi cant drop in performance.

3.3.2 Reliability

SRS Page 12 2025-01-13

ti
ti
fi
 Reliability ensures the system functions as expected and remains operational under various
conditions.
1. Availability:

o The system should be available 99.9% of the me, with scheduled maintenance periods
clearly communicated to users in advance.

2. Fault Tolerance:

o The system should be capable of recovering from failures (e.g., network disrup ons,
hardware failure) minimize down me.

3.3.3 Availability
Availability ensures the system is reliably accessible when needed.
1. Redundancy:

o The system should incorporate redundancy in cri cal components (e.g., load balancers,
web servers, rebases) to ensure con nuous service even during hardware failures.

o A backup system should be available to restore service quickly if the primary system
goes down.

3.3.4 Security
Security defines the measures in place to protect user data.
o User roles (e.g., Admin, Kitchen Sta , Cashier) should be implemented with speci c
access rights to ensure proper authoriza on for sensi ve data and ac ons.

1.Data Encryp on:

o All sensi ve data (e.g., user informa on, payment details) should be encrypted both at
rest (in the database) and in transit (during communica on between the client and
server) using industry-standard encryp on protocols (e.g., TLS 1.2 or higher).

3.3.5 Maintainability
• Code Maintainability:

SRS Page 13 2025-01-13

ti
fi
ti
ti
ti
ti
ff
ti
ti
ti
ti
ti
ti
ti
ti
fi
 o The codebase should follow industry standards and be modular to facilitate future
updates or bug xes.
• System Updates:
o New features or updates should be deployed without disrup ng ongoing opera ons
(e.g., using con nuous deployment pipelines).
• Scalability:
o The system must be designed to handle increased user loads and extended func onality,
such as adding more menu categories or new user roles

3.3.6 Portability
Portability ensures the system can be deployed on different platforms or environments without
major reconfiguration.
1. Cross-pla orm Compa bility:
o The system should be compa ble with mul ple opera ng systems, including Windows,
macOS, and Linux, where appropriate.
o The Canteen Automa on System's web applica on should be browser-agnos c and
support modern browsers like Google Chrome, Firefox, Safari, and Edge.
2. Mobile Compa bility:
o The system should be responsive and accessible on mobile devices (smartphones and
tablets). The interface should adjust to di erent screen sizes, ensuring usability across
pla orms.

3.4 Logical Database Requirements

Logical database requirements define the structure and organization of the data to ensure that it is
stored, accessed, and manipulated efficiently while supporting the system’s functional
requirements. The design needs to facilitate smooth operations like order processing, inventory
management, and billing, while ensuring data consistency, integrity, and security.

3.4.1 Entities and Relationships

SRS Page 14 2025-01-13

tf
tf
ti
fi
ti
ti
ti
ti
ff
ti
ti
ti
ti
ti
ti
ti
 The system will require the creation of several en es (tables) to represent various components
of the canteen management process. These entities must be structured to store relevant data and
relate to each other in a way that maintains data integrity and supports efficient query processing.
Main En es:
1. Customer:
o Stores customer details like name, contact informa on, account ID, etc.
2. Menu:
o Stores informa on about the food items or beverages o ered in the canteen.
3. Order:
o Represents an order placed by the customer, linking customers to the items they order.
4. Order_Item:
o Stores the individual items in an order (since an order can contain mul ple items).
5. Inventory:
o Manages the stock levels of ingredients or supplies used to prepare menu items.
6. Billing:
o Stores the billing details for each order, including taxes and any applicable discounts.
7. Admin/Sta :
o Stores informa on about sta members managing the canteen’s opera ons.
8. Report:
o Stores generated reports about sales, inventory, and other opera onal metrics.

3.4.2 Relationships Between Entities

1. Customer to Order (1:N):

o One customer can place mul ple orders, but each order belongs to one customer.

2. Order to Order_Item (1:N):

o An order can have mul ple items, but each item belongs to only one order.

3. Menu to Order_Item (1:N):

o One menu item can appear in mul ple orders, but each order item corresponds to one
menu item.

4. Sta /Admin to Order (1:N):

o One sta member (e.g., cashier, kitchen sta ) can process mul ple orders.

5. Sta /Admin to Report (1:N):

SRS Page 15 2025-01-13

ff
ff
ff
ti
ti
ff
ti
ti
ti
ti
ff
ti
ff
ti
ti
ff
ti
ti
ti
ti
ti
 o One sta member generates mul ple reports, but each report is generated by one sta
member.

3.5 Design Constraints

.•Technology Constraints: Limits on the choice of database, opera ng systems, and programming

languages.

• Performance Constraints: Response me, scalability, and concurrent request handling.

• Security Constraints: Data encryp on, authen ca on, compliance, and session management.

• Usability Constraints: UI design, accessibility, and language support.

• Data Integrity and Valida on Constraints: Data valida on, referen al integrity, and transac onal

integrity.

Chapter No 4
SRS Page 16 2025-01-13
ff
ti
ti
ti
ti
ti
ti
ti
ti
ti
ff
ti
SRS Page 17 2025-01-13
4. Analysis Models
i. Analysis models are a key component of system design and development. These
models help visualize, understand, and specify the functionality, behavior, and
interaction of various system components from a user and business perspective.
For the Canteen Automa on System.

SRS Page 18 2025-01-13

ti
4.1 Use Case

2. Sequence Diagrams

4.2.1customer

login Menu select Order infoma on Payment

SRS Page 19 2025-01-13

ti
 4.2.2 Admin

Login Menu select

Login Order infoma on Payment
Admin

Con rm order
Add/delete

SRS Page 20 2025-01-13

fi
ti
 Sequence Diagram (2/2)

4.3 Data Flow Diagrams (DFD)

LEVEL-0

SRS Page 21 2025-01-13

LEVEL-1

SRS Page 22 2025-01-13

LEVEL-2

SRS Page 23 2025-01-13

3. State-Transition Diagrams (STD)

4.3.1User

SRS Page 24 2025-01-13

4.3 State-Transition Diagrams (STD)

4.3.2. Admin

SRS Page 25 2025-01-13

4.5 Class Diagram (CD)

SRS Page 26 2025-01-13

 Chapter No 5

SRS Page 27 2025-01-13

5. Supporting Information

• User Manual:

• A detailed guide for users (students and administrators) explaining how to interact with
the system, from placing an order to managing menu items and tracking order status.

• Topics Included:

o Logging in and user roles.

o Ordering food and viewing order status.

o Admin panel overview for order and user management.

o Updating the menu and managing food availability.

• Developer Documentation:

• A reference for developers working on the CAS, explaining the system architecture,
libraries used, and code structure.

• Topics Included:

o Project setup instructions.

o Overview of the frontend (React.js) and backend (Firebase).

o Code conventions and structure.

o Explanation of Auto Mapper and version control strategies

SRS Page 28 2025-01-13

 Chapter No 6

SRS Page 29 2025-01-13

 6. Architecture
1. Presentation Layer:
The Presentation Layer is responsible for the user interface and user experience, serving as the
interaction point between users and the system.
• Components:
o User Panel:
▪ Displays the menu of food items and allows students to browse, select, and
place orders.
▪ Provides real- me updates on order status.
o Admin Panel:
▪ O ers a dashboard for administrators to monitor and manage orders, menus,
and user roles.
▪ Displays analy cs (if implemented) for opera onal insights.
• Technologies Used:
o Html
o React.js.
o CSS/Bootstrap:
2. Application Layer:
• Order Processing: Handles order placement, status updates, and notifications.
• Role Management: Enforces role-based access to functionalities (e.g., student vs. admin
capabilities).
• Menu Management: Allows admins to update product listings and their availability
dynamically.
• Technologies Used:
• JavaScript/: For implementing business logic and client-side operations.
3. Data Access Layer:
The Data Access Layer serves as the intermediary between the application and the database,
ensuring secure and efficient data handling.

i. Responsibili es:

o Fetching and upda ng user, order, and menu data from the database.

SRS Page 30 2025-01-13

ff
ti
ti
ti
ti
ti
 o Ensuring data consistency and integrity during read and write opera ons.

ii. Technologies Used:

o Firebase Real me Database:

▪ Stores structured data for orders, menus, and users.

▪ Provides real- me synchroniza on between users and administrators.

o Firebase Security Rules: Enforces access controls based on user roles to protect
sensi ve data.

iii. The data access layer manages data models, performs database queries, and
handles data persistence.

4. Integration Layer:
• Responsibili es:
• Handling authen ca on via Firebase Authen ca on for secure user login.
• Integra ng cloud hos ng through Firebase Hos ng for website deployment.
• Technologies Used:
• Firebase Authen ca on: For user login and role management.
• Firebase Hos ng: Ensures fast and reliable access to the CAS.
5. Version Control:
The CAS uses Git, a distributed version control system, to manage the project's source code.
All changes are tracked and stored in a centralized remote repository hosted on GitHub
.

SRS Page 31 2025-01-13

ti
ti
ti
ti
ti
ti
ti
ti
ti
ti
ti
ti
ti
ti
ti
ti