An Internship Report

on

CANTEEN MANAGEMENT SYSTEM

An internship report submitted in partial fulfillment of requirements for

the Award of the Degree of

BACHELOR OF TECHNOLOGY
IN
ELECTRONICS AND COMMUNICATION ENGINEERING
By

PALADUGU SRUTHI (179X1A04B3)

Under the Esteemed Guidance of

Dr. M.V.R.VITTAL, M.Tech., Ph.D

Assistant Professor
Department of Electronics and Communication Engineering

G. PULLA REDDY ENGINEERING COLLEGE (AUTONOMOUS)

(Accredited by NBA and NAAC of UGC with A+ grade)
(AFFILIATED TO JNTUA, ANANTHAPURAMU)
KURNOOL - 518007
2020-2021
 G. PULLAREDDY ENGINEERING COLLEGE (Autonomous)
KURNOOL
(Accredited by NBA and NAAC of UGC with A+ grade)
Affiliated to JNTUA, Anantapuramu
(2020-2021)

CERTIFICATE

This is to certify that the preliminary internship project work entitled

CANTEEN MANAGEMENT SYSTEM

is a bona fide record of work carried
By
PALADUGU SRUTHI (179X1A04B3)

Under my guidance and supervision in fulfilment of the

requirements for the award of degree

BACHELOR OF TECHNOLOGY
IN
ELECTRONICS AND COMMUNICATION ENGINEERING

INTERNAL SUPERVISOR HEAD OF THE DEPARTMENT

Dr.M.V.R.VITTAL, M.Tech,Ph.D. Dr. S.NAGARAJA RAO M.Tech, Ph.D., MISTE.

Associate Professor, Professor and Head of the Department,

Department of ECE, Department of ECE,

G. Pulla Reddy Engineering College, G. Pulla Reddy Engineering College

(Autonomous), Kurnool. (Autonomous), Kurnool.

 Project Internship Completion Certificate

To whomsoever it may concern

June 09, 2021

This is to certify that Mr. Sruthi Paladugu studying B.Tech. in Electronics

and Communication and Engineering at G Pulla Reddy Engineering
College has successfully completed internship work from January 2021 to
April 2021 at Hexaware Technologies Limited.

For Hexaware Technologies,

( Muruganantham A. )
General Manager,
Hexaware Technologies Limited.

HEXAWARE TECHNOLOGIES LTD.

Plot No. H5, SIPCOT Information Technology Park, Navallur Post, Siruseri – 603103, Kanchipuram Dt.
Tel. : +91 – 44-4745 1000, Fax : +91 – 44- 47451111
Regd. office: #152, Millennium Business Park, Sector - lll, ‘A’ Block, TTC Industrial Area, Mahape, Navi Mumbai -400710, India
Tel. : +91 22 6791 9595, Fax : +91 22 6791 9500
Company Identity Number (CIN) : L72900MH1992PLC069662; URL: www.hexaware.com
 DECLARATION

I hereby declare that internship project titled “Canteen Management System”

submitted for the Department of Electronics and Communication Engineering. This

dissertation is our original work and the project has not formed the basis for the award of

any degree, associate-ship and fellowship or any other similar titles and no part of it has

been published or sent for publication at the time of submission.

PALADUGU SRUTHI

(179X1A04B3)
 ABSTRACT

The Online Food Delivery System is one of the fastest growing marketing strategies for
most of the Business people, in a way to gain the more profits. As we all know that the food
is the basic need in every human life, for which he/she is struggling. But even after their
struggles, if people are still not happy with their sustenance, then the effort given behind it is
useless. The reasons might be the people are busy with their schedules, they either can’t able
to cook in right time or not having time to go and order their food from outside.

Then here is the way, where Spicy and Delicious Restaurants and other food stuff points
have now started to deliver their food through the Apps as. Upon which, people can stop
starving and could start to eat healthier food, just by clicking on the menus served on the apps.
There are many more benefits offered by the Takeaway Food Delivery system.

The Objective of the project Canteen management system is the offer the services which
helps to create a user-friendly environment between the customers and the canteen vendors
that helps the customers to place the orders and the vendors to accept or reject the order of the
customers based on the availability of food in canteen through online.
 TABLE OF CONTENTS

1. INTRODUCTION ......................................................................................... 1

1.1 Introduction ............................................................................................. 3

1.2 Project Background ................................................................................. 3

1.3 Objective ................................................................................................. 3

1.4 Project Description .................................................................................. 3

2. LITERATURE REVIEW .............................................................................. 5

2.1 Review of related literatures ................................................................... 6

2.2 Review of existing systems ..................................................................... 7

3. SOFTWARE REQUIREMENTS SPECIFICATION ................................... 8

3.1 Requirement Analysis ............................................................................. 9

3.2 Problem Statement .................................................................................. 9

3.3 Functional Requirements ........................................................................ 9

3.4 Software Requirement Specification .................................................... 10

3.5 Software Requirements ......................................................................... 13

3.6 Hardware Requirements ........................................................................ 13

3.7 Functional Requirements (Modules)..................................................... 13

3.8 Non-Functional Requirements .............................................................. 16

3.9 External Interface Requirements ........................................................... 17

3.10 Feasibility study ................................................................................. 18

4. ANALYSIS & DESIGN .............................................................................. 19

4.1 Scope ..................................................................................................... 20

 4.2 System Overview .................................................................................. 21

4.3 System Architecture .............................................................................. 22

4.4 Data Design ........................................................................................... 26

5. MODELING ................................................................................................ 30

5.1 Design ................................................................................................... 31

6. IMPLEMENTATION .................................................................................. 37

6.1 Code Snippets ..................................................................................... 38

6.2 Screen Captures .................................................................................. 42

7. RESULTS AND CHALLENGES ............................................................... 48

7.1 Results ................................................................................................ 49

7.2 Challenges .......................................................................................... 49

8. CONCLUSION .......................................................................................... 50

8.1 Conclusions ........................................................................................ 51

8.2 Scope for future work ......................................................................... 52

8.3 Limitations .......................................................................................... 53

 LIST OF FIGURES

FIGURE NO. FIGURE NAME PAGE

NO.
Figure 4.1 A Directory structure for a java project auto generated by maven 22
Figure 4.2 Java Based web application architecture 25
Figure 5.1 Use Case Diagram for system 31
Figure 5.2 Sequence Diagram for Customers module 32
Figure 5.3 Sequence Diagram for Vendor module 33
Figure 5.4 Activity Diagram for CMS 33
Figure 5.5 Class Diagram for Offline CMS 34
Figure 5.6 Deployment Diagram of the System 35
Figure 5.7 ER Diagram 36
Figure 6.1 Customer Table 38
Figure 6.2 Menu Table 39
Figure 6.3 Orders Table 39
Figure 6.4 Vendor Table 40
Figure 6.5 Data Base Connection 40
Figure 6.6(a) Git Bash Implementation 41
Figure 6.6(b) Git Bash Implementation 41
Figure 6.7 Home Page 42
Figure 6.8 Login and Signup Page 42
Figure 6.9 Customer Home Page 43
Figure 6.10(a) Place Order Page 43
Figure 6.10(b) Order History Page 44
Figure 6.10(c) Add Money Page 44
Figure 6.10(d) Cancel Order Page 45
Figure 6.11 Vendor Home Page 45
Figure 6.12(a) Vendors Details Page 46
Figure 6.12(b) Vendor Pending Orders Page 46
Figure 6.12(c) Accept/Reject Order Page 47
Figure 6.12(d) Add Menu Page 47
 LIST OF TABLES

TABLE NO. TABLE NAME PAGE NO.

Table 3.1 Client Requirements 13
Table 3.2 Server Requirements 13
Table 4.1 List of Database Tables 26
Table 4.2 Structure of Vendor table of MySQL Database 26
Table 4.3 Structure of Customer table of MySQL Database 27
Table 4.4 Structure of Menu table of MYSQL Database 28
Table 4.5 Structure of Order table of MySQL Database 29
 ABBREIVATIONS

• ADS : ANDROID DATA SYNCHRONIZATION

• SDK : SOFTWARE DEVELOPMENT KIT
• ADT : ANDROID DEVELOPMENT KIT
• API : APPLICATION PROGRAMMING INTERFACE
• AOSP : ANDROID OPEN-SOURCE PROJECT
• AVD : ANDROID VIRTUAL DEVICE
• CRM : CUSTOMER RELATIONSHIP MANAGEMENT
• UI : USER INTERFACE
• JSON : JAVA SCRIPT OBJECT NOTATION
• XAMPP : WINDOWS/LINUX APACHE MYSQL PERL PHP
• PHP : HYPERTEXT PREPROCESSOR
• IDE : INTEGRATED DEVELOPMENT ENVIRONMENT
• HTML : HYPER TEXT MARKUP LANGUAGE
• JDK : JAVA DEVELOPMENT KIT
• XML : EXTENSIBLE MARKUP LANGUAGE
• WIFI : WIRELESS FIDELITY
• AVD : ANDROID VIRTUAL DEVICES
• ADB : ANDROID DEBUG BRIDGE
 CANTEEN MANAGEMENT SYSTEM

CHAPTER - 1

INTRODUCTION

DEPARTMENT OF CSE, GPREC, KURNOOL Page 1

 CANTEEN MANAGEMENT SYSTEM

1. INTRODUCTION
1.1 Introduction
The current project involves the development of a web application that let your
customers to order food anywhere, anytime, from the computer. The main aim of the
project is to help and lift the canteens business. In day to day life the is a lot of time wasting
due to these queue line in the canteen so this project will help the customers to order food
from anyplace anytime this project might also help to lift the food industry

In this website customer can know the canteen near to his place and he can choose the
canteen he wants. Then he can place order. Then the vendor gets the notification that has
been placed and he can deliver them to the customer.

In this project, we are going to create a website where there are two kinds of users namely
vendors and customer.

1.Vendor:
This user can sign in to our website and can enter his canteen details and then he can
enter what items he has in his canteen and the number of each item present in the
canteen.
If the ordered food item was not there in the canteen, then he can acknowledge the
customer about the non-availability of the food item

2.Customer:
This user can sign in and then log in to the website and so that he could see the

Canteen near to him and can place an order of food items he wants.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 2

 CANTEEN MANAGEMENT SYSTEM

1.2 Project Background

Most of the food industry was now at jeopardy the main problem comes under the
maintenance this was the major loss in order to restore the glory of the food industry we need
to automate and cloudify everything so through we are going to do that.

1.3 Objective
The objective of the system is to automate all the activities of the canteen right from
purchases to delivery of food/beverage items. The system should maintain a detailed account
of all provisions bought and food served at the canteen. In addition to this, it should also
maintain the daily expenses incurred by the staff. The system should provide an interface to
payroll for deductions. Several inquiry facilities should also be provided to view the
expenses incurred/ planned menus/cash payment etc.

1.4 Project Description

In this section all features in application are explained in brief.
• Vendor
- Sign in
(a) Log in
(b)Add items
(c) See orders
(d) Update order status

- logout of the Account

a) Sign in:

Here a new vendor can join our website by providing his details by enter his name,
canteen name, phone number, E-mail address, address, password for his account. After
signing into the website customer new account is created.

b) Login:
Here the customer has to enter the phone number and password for his account. If the
customer forgets his password then he could press on forgot password and receive the
password through the mail.
DEPARTMENT OF CSE, GPREC, KURNOOL Page 3
 CANTEEN MANAGEMENT SYSTEM

i. Add Items:

Here the vendor after logging in, he enters the categories he has in the canteen and also
the number of items in that category.

ii. See Orders:

Here the vendor can see the orders he/she has got.

iii.Update order status:

Here in this section if the selected food was not been available in the canteen, then the
vendor can acknowledge the customer about the order i.e, accepted or rejected.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 4

 CANTEEN MANAGEMENT SYSTEM

CHAPTER – 2

LITERATURE REVIEW

DEPARTMENT OF CSE, GPREC, KURNOOL Page 5

 CANTEEN MANAGEMENT SYSTEM

2. SOFTWARE REQUIREMENTS SPECIFICATION

2.1 Review of related literatures

[1] In-Time Billing Process for Canteen Management System

In-time billing technique for canteen management device indicates canteen admin will give
a RFID to their customers which can be either students or staffs and in case of an organization, it can
be employees. This system is very effective. It is very much useful for the people who go to canteen
regularly, may be daily. They do not have to bring the cash with them anymore. Each and every
registered customer will get a card and person can do recharge with whatever amount he wishes to
have. This project says that only invoice has to be produced for the canteen timings and other times
the consignment has to stop producing.
With this system we can entirely change the complete functioning of the canteen. Is it possible
to get refund of the amount remaining in the card? The report of individual user has to be prepared
on weekly basis or monthly basis. For this task to provide fine solution and also In-Time only
consignment need to be produced. To achieve that, the customers are allowed only in the specified
timings

[2] Cloud Based Canteen Management System

This paper suggests a platform for automating the whole process more conveniently for both
the canteen and the buyers on the cloud. There is no hardware components and installations are
required with the help of Cloud Computing technology. Cloud computing is extremely cost effective
relative to the ownership of individual parts. The proposed cloud-based program fills the gap between
the canteen and its use. The system provides a Radio Frequency Identification card, which will be
used for each customer’s purchases at the counter. In addition, a new form of buying and paying
through a mobile device, where deductions are made directly from the customer’s account, which is
helpful in reducing the queues. Accounts can be recharged through online transfers and e-wallets.
The web application and mobile application will be hosted on the cloud.
The overall tiring administration of a canteen business can be accomplished easily. There is no
need for long delays in queue, orders can be placed more easily accordingly. There is no need to be
maintain paper-based records. Data migration to the cloud is only required once.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 6

 CANTEEN MANAGEMENT SYSTEM

Entire Canteen Business is automated.

[3] Canteen management system using the E-wallet

In this paper, system can take orders at the counter and through online application and display
them on monitors in the kitchen. The internet application would make use of HTML5, two Java
script, two and Boot Strap for frontend and JSP for the backend. Appropriate protection aspects shall
be implemented to prevent attacks the usage of 2048 bit El-Gamal encryption scheme. For placing
orders in advance, we will create a web application. The orders placed in enhance will have an
ORDER ID which shall be used to get the order delivered at once to the serving counter. Payments
can be made through cash or e-wallet at the counter.
After the operation is done the values are again encrypted and stored in the database. A 2048-
bit key is used for encryption. On the consumer side, an Ajax call is made for a servlet to get cipher-
text in order to encrypt the sensitive data transmission between consumer and server. An SSL
certificate also installed on the website to ensure further secure transmission of data sent and received
through the web application.

2.2 Review of existing systems

[1] Online Canteen System

The project online canteen system helps the users to book their food earlier. The users have to book
their food on the e – menu card. As soon as they book their food the order will be sent to the chef for
preparing it. The present system consists of the manual system that involves the paper work of the
billing system and maintaining the files too. In the proposed system the payment is online and the e-
menu will be available for the user. The users will have the username and the password through
which they can book. This project will help in demonstrating the route from adapting materials to
developing an online environment. This brings all necessities in one place that benefits both the user
and the canteen owner smartly.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 7

 CANTEEN MANAGEMENT SYSTEM

CHAPTER – 3

SOFTWARE REQUIREMENT
SPECIFICATION

DEPARTMENT OF CSE, GPREC, KURNOOL Page 8

 CANTEEN MANAGEMENT SYSTEM

3. SOFTWARE REQUIREMENTS SPECIFICATION

3.1 Requirement Analysis
For the purpose of easy access and portability we proposed to develop a web-
based system with windows or ubuntu as a platform because they are mostly used
operating systems on the market. As a part of this system, we are going to develop web-
based software in which data can be accessed and retrieved easily. The required
documents for these processes are as follows.
1. Problem statement
2. Data flow diagrams
3. Use case diagram
4. Other UML diagrams.
The above-mentioned documents give us diagrammatical view of the system
what we are going to develop.

3.2 Problem Statement

The problem statement concentrates on data storage in a MYSQL database and
syncing the data to the MYSQL server.
3.3 Functional Requirements
• Adding customer to canteen
- The website shows up sign in and login options. If customer is not
registered into our website then he can sign in to our website.
- Our website takes first name.
- Our website takes phone number.
- Our website takes email address.
- Our website takes password.
- Our website asks again to retype the password for confirmation of the
password
- Our website takes location (name of the place he lives).

DEPARTMENT OF CSE, GPREC, KURNOOL Page 9

 CANTEEN MANAGEMENT SYSTEM

• Adding vendor to our website

- The website shows up sign in and login options. If vendor is not yet
registered into our website then he can sign in to our website.
- Our website takes first name of vendor.
- Our website takes last name of vendor.
- Our website takes name of the canteen.
- Our website takes vendor’s phone number.
- Our website takes vendor’s email address.
- Our website takes address of the canteen.
- Our website takes location (name of the place he lives).
- Updating of items by vendor
- If the vendor buys additional items, then he can add them to his item list
and number of items in that category.
3.4 Software Requirement Specification
The project is developed in Java Programming Language by using the visual studio.
We use the Azure Extension which includes a variety of custom tools that help us to deploy
web applications on the azure cloud platform. At the Server-side Apache Tomcat Server is
used. Apache Web Server, MySQL is used at the back-end and angular is used for the front
end.

• Purpose
The purpose of this document is to present a detailed description of “Canteen
management system” application. It will explain the purpose and features of the system
that it will provide, constraints under which it must operate and how the system will react.
The document also describes the non functional requirements of the system.

• Scope of the project

In the project we are going to create a website which consist of two kinds of Users
they are Customers and Vendors

DEPARTMENT OF CSE, GPREC, KURNOOL Page 10

 CANTEEN MANAGEMENT SYSTEM

➢ Vendors:
This user will be signed up first if the user was new user by providing basic
details like name, phone number, mail-address, location of the canteen and the
preferred password later he was asked to login in the vendor page where the user can
update availability of food and the vendor provide the acknowledgement about the
customer order status by considering the availability of food in canteen

➢ Customers
This user also asked for the sign-up if the user was the new user by providing
basic details like name, phone number, mail address, gender, preferred delivery
location
After sign up the user will be asked to login then the user will be able to order the food
from the list of available canteen and the user can see the previous orders through order
history

➢ Technologies Used

• JAVA
Java is an object-oriented programming language developed by Sun Micro Systems,
a company best known for its high end UNIX workstations. Java language was designed
to be small, simple, and portable across platforms, operating systems, both at the source
and at the binary level, which means that Java programs (applet and application) can run
on any machine that has the Java virtual machine (JVM) installed.
• ANGULAR
Angular is a Type Script-based open-source web application framework and also
Angular is a development platform that aims to make web development feel effortless,
focused on developer productivity, speed and testability. Applications built with Angular
can be deployed to mobile devices and desktops as websites and native applications.
• HTML
Hypertext Markup Language is the main markup language for displaying web
pages and other information that can be displayed in a web browser.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 11

 CANTEEN MANAGEMENT SYSTEM

• JAVASCRIPT
JavaScript is a scripting language commonly implemented as part of a web
browser in order to create enhanced user interfaces and dynamic websites.
• APACHE WEB SERVER
Apache is generally recognized as the world’s most popular web Server (HTTP
server).It provides a full range of web server features, including CGI, SSL, and virtual
domains. Apache also supports plug-in modules for extensibility.
• RESTFULSERVIES
REST has become one of the most important technologies for Web applications.
REST stands for Representational State Transfer, which is an architectural style for
networked hypermedia applications, it is primarily used to build Web services that are
lightweight, maintainable, and scalable. A service based on REST is called a RESTFUL service.
REST is not dependent on any protocol, but almost every RESTFUL service uses HTTP as its
underlying protocol.
• MySQL
MySQL is one of the most popular relational database management systems on
the web. MySQL is used for the internet applications as it provides good speed and is
very secure. MySQL was developed to manage large volumes of data at very high speed
to overcome the problems of existing solutions.

➢ Overview
The application is based on both windows and ubuntu platform an application
which communicates with the server allowing the collection of sales visit data offline
and then syncs the data with that of the corporate server when there is access to the
internet.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 12

 CANTEEN MANAGEMENT SYSTEM

3.5 Software Requirements

The software interface is the operating system, and application programming
interface used for the development of the software.
• Operating System - Windows XP or above
• Stack - Java 8
• Major version - Tomcat 8.5.50
• HTTP version - 1.1
• Back End - MySQL 8.0.19
• Cloud Platform - AMAZON WEB SERVICES
• Technologies - Java, Angular, Rest.

3.6 Hardware Requirements

CLIENT
OPERATING SOFTWARE DISK SPACE RAM
SYSTEM
Any operating Any Web Minimum 256
sytem Broswer 250 MB MB

Table 3.1 Client Requirements

SERVER
OPERATING SOFTWARE PROCESSOR RAM DISK
SYSTEM SPACE
Ubuntu 12.04 Apache 2.2.22 IntelI XeonI 256Mb Minimum
LTS MySQL 5.5.2 CPU E31220 250Mb

Table 3.2 Server Requirements

3.7 Functional Requirements (Modules)

The project has two main modes Vendor and Customer each having its own respective
specific functionality.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 13

 CANTEEN MANAGEMENT SYSTEM

1. Customer

• Sign in
• Log in
• Place order
• View order status
• Log out

1) Sign in:

Here a new customer can join our website and enter his name, phone

number, E-mail address, address, password for his account. After signing in

customer new account is created.

b) Login:

Here the customer has to enter the phone number and password for his

account. If the customer forgets his password then he could press on forgot

password and receive the password through the mail.

i. Place order:
After pressing the place order button customer can see the menu
from different canteens present near to his/her location.
Customer can select the food item he likes and select the items
customer wants.
ii. View Order status:
After placing the order if the customer wants to check the
status he can by track status option

c) Logout:

if the ordering is done by the customer then the customer can now logout of the account

DEPARTMENT OF CSE, GPREC, KURNOOL Page 14

 CANTEEN MANAGEMENT SYSTEM

2. Vendor

1.Sign in
2.Log in
(a) add items

(b) check order

(c) change order status

a) Sign in:
Here a new owner can join our website and enter his name, Canteen
name, phone number, E-mail address, address, password for his account.
After signing in customer new account is created
b) Login:
c) Here the customer has to enter the phone number and password for his
account. If the customer forgets his password then he could press on forgot
password and receive the password through the mail.
i. Add Items:
Here the owner after logging in, he enters the categories he
has in the canteen and also the number of items in that
category.
ii. check Orders:
Here the owner can check the orders he/she has got.
iii. Update order status:
Here in this section if the vendor changes the order status
based on the availability of the food items in canteen
c) Logout:
If the vendor was done with the work now the Vendor can logout of the
application by using this logout option.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 15

 CANTEEN MANAGEMENT SYSTEM

3.8 Non-Functional Requirements

3.8.1 Performance requirements:
Performance requirements define acceptable response times for system
functionality. The load time for user interface screens shall take no longer than
10 seconds. The log in information shall be verified within 10 seconds. Queries
shall return results within 10 seconds.

3.8.2 Design Constraints:

The online canteen management shall be a stand-alone system running
in a Windows environment. The system shall be developed using ANGULAR
and connected to Oracle database.

3.8.3 Standards Compliance:

There shall be consistency in variable names within the system. The
graphical user interface shall have a consistent look and feel.

3.8.4 Availability:
The system shall be available during normal Canteen operating hours.

3.8.5 Portability:
The Canteen Management System shall run in any Microsoft Windows
environment that contains browser and be able to available to all users all the
time while they have the internet.

3.8.6 Reliability:
Since the application is being developed through java, the most famous,
efficient and reliable language, so it is reliable in every aspect until and unless there is
an error in the programming side. Thus the application can be a compatible and reliable
one.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 16

 CANTEEN MANAGEMENT SYSTEM

3.9 External Interface Requirements

3.9.1 User Interface
A critical aspect of this project was examining how the app would look and its
usability. The layout of web applications is defined in a HTML and JSP files.
When the App is launched, it displays the First Screen- an activity that contains
the layout displays buttons for Owner activity and Customer activity. The application
has a user-friendly interface.

3.9.2 Event log/database

vendor table:
3.9.2.1 Name
3.9.2.2 Phone number
3.9.2.3 Address
3.9.2.4 Email address
3.9.2.5 Canteen name
3.9.2.6 Vendor -id

Menu Table:
1. Item name
2. Item type
3. Cost of each item
4. Item category
5. Item calories
6. Vendor -id

Customer Table:

1. Name

2. Phone number

3. Email address

4. Date of birth

5. Customer-id

DEPARTMENT OF CSE, GPREC, KURNOOL Page 17

 CANTEEN MANAGEMENT SYSTEM

Order Table:
1. Order-id
2. Order status
3. Token number

3.10 Feasibility study

A key part of the preliminary investigation that reviews anticipated costs and
benefits and recommends a course of action based on operational, technical, economic,
and time factors. The purpose of the study is to determine if the systems request should
proceed further.

3.10.1 Organizational Feasibility

The application would contribute to the overall objectives of the organization.
It would provide a quick, error free and cost effective solution to the current process
CRM marketing. It would provide a solution to many issues in the current system. As
the new system is flexible and scalable it can also be upgraded and extended to meet
other complex requirements which may be raised in the future. However it is up to the
organization to upgrade or extend it.

3.10.2 Economic Feasibility

The project is economically feasible as it only requires a computer with Any
operating system. The application is free to download once released into market. The
users should be able to connect to internet through computer and this would be the only
cost incurred on the project.
3.10.3Technical Feasibility
To develop this application, a high speed internet connection, a database server,
a web server and software are required. The current project is technically feasible as
the application was successfully deployed on AWS.
3.10.4Behavioural Feasibility
The application is behaviourally feasible since it requires no technical guidance,
all the modules are user friendly and execute in a manner they were designed to.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 18

 CANTEEN MANAGEMENT SYSTEM

CHAPTER - 4

ANALYSIS & DESIGN

DEPARTMENT OF CSE, GPREC, KURNOOL Page 19

 CANTEEN MANAGEMENT SYSTEM

4. ANALYSIS & DESIGN

4.1 Scope
In this section the scope of the document and the project is explained in brief.

4.1.1 Document Scope

This document contains a thorough description of the high level architecture that will be
used in developing the system. Communicating at a purposefully high level, it will only form
the basis for the Software Detailed Design and implementation. However, the SDD itself
will not be in sufficient detail to implement the code. It will convey the overall system design
of the system, the user interface design and higher level module design (including android
development tools) and the architecture of the Linux kernel and the working of the Dalvik
Virtual Machine. Design details that will not be included in the SDD are:
• Low level classes that will be used in the implementation. The full description of
the implementation of each module is not needed, but the public modules that will
be interfaced will be described.
• Exact detailed description of interactions within each module.

4.1.2 Project Scope

CMS application mainly consists of two modules with each having definite
functionality. The purpose of module one, VENDOR is to add, view and edit the MENU
details and customer order details when there is access to the internet. Module two
CUSTOMER works when there is an internet access. The customer details can be stored
in the remote servers. A view to the records in the Mysql database can be seen. This
data can be synced to the server whenever there is access to the internet.

1. VENDOR:

This user can sign in to our website and can enter his canteen details and then
he can enter what food items he has in his canteen and the number of each item present
in the canteen. He can also update the number of items in the canteen and he can also
modify the order status based on the availability of the food items

DEPARTMENT OF CSE, GPREC, KURNOOL Page 20

 CANTEEN MANAGEMENT SYSTEM

2. CUSTOMER:

This user can sign in and then log in to the website and so that he could see the
canteen near to him and can place an order of items he wants.

4.2 System Overview

Cloud deployment framework uses certain development tools which are as follows:

4.2.1 Visual Studio Code

Visual Studio Code is a lightweight but powerful source code editor which runs on your
desktop and is available for Windows, mac-OS and Linux. It comes with built-in
support for JavaScript, Type-Script and Node.js and has a rich ecosystem of extensions
for other languages (such as C++, C#, Java, Python, PHP, Go) and run-times (such as
.NET and Unity).

4.2.2 Java Development Kit (JDk)

The Java Development Kit (JDK) is an implementation of either one of the Java
Platform, Standard Edition, Java Platform, Enterprise Edition, or Java Platform, Micro
Edition platforms released by Oracle Corporation in the form of a binary product aimed
at Java developers on Solaris, Linux, macOS or Windows. The JDK includes a private
JVM and a few other resources to finish the development of a Java Application. Since
the introduction of the Java platform, it has been by far the most widely used Software
Development Kit.

4.2.3 Maven
Maven is a build automation tool used primarily for Java projects. Maven can
also be used to build and manage projects written in C#, Ruby, Scala, and other
languages. The Maven project is hosted by the Apache Software Foundation.
Maven addresses two aspects of building software: how software is built, and
its dependencies. An XML file describes the software project being built, its
dependencies on other external modules and components, the build order, directories,
and required plug-ins.
DEPARTMENT OF CSE, GPREC, KURNOOL Page 21
 CANTEEN MANAGEMENT SYSTEM

Maven dynamically downloads Java libraries and Maven plug- ins from one or
more repositories such as the Maven 2 Central Repository, and stores them in a local
cache. Maven projects are configured using a Project Object Model, which is stored in
a pom.xml-file.

Figure 4.1 A directory structure for a Java project auto-generated by Maven

4.3System Architecture
4.3.1 Architectural Design
Web application architecture is a framework connecting different elements to enable a
web experience. It is the backbone of our daily internet browsing: typing in a URL and
viewing and interacting with the website while the browser communicates with the
server is one of the ways to describe what is web application architecture.

Attributes of a well-built web application architecture:

• Solves business problems

• Supports visual aesthetic
• Enables A/B testing and analytics
• Ensures fast user experience
• Provides security
• Sustainable and self-regulating
DEPARTMENT OF CSE, GPREC, KURNOOL Page 22
 CANTEEN MANAGEMENT SYSTEM

• Scales out and logs errors in an easy way

• Guarantees a high level of automation

Components of Web Application Architecture

Web application architectures consist of application components, middleware systems,
and databases. They can be divided into two groups:

• UI/UX components
• Structural components

UI/UX components include dashboards, statistical data, notification elements, layouts,

activity tracking, and other elements. These components create the visuals of a web
page and lay the foundation for user experience.

Meanwhile, structural components include the web application server and the
database server. knowledge of HTML, JavaScript, and CSS, as well as Python, PHP,
Java, Ruby, .NET and Node.js are required to create them.

When it comes to building the components, there are several models to choose from:

• 1 web server and 1 database

• web servers and 2 databases
• More than 2 web servers and databases

One web server with one database is the simplest model. With this web server
architecture, the successful operation of an application depends on server stability. In
other words, if there is a problem with the server, the app will not work. Still, the model
is sufficient for testing and private sessions.
Using one database for two web servers is a more reliable model, as there is a backup
server. On the other hand, ensuring the database is secure and always running is
important.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 23

 CANTEEN MANAGEMENT SYSTEM

4.3.2 Deployment to a Web App in cloud

The deploy process leverages the Azure Account extension (installed along with the
Azure Functions extension as a dependency) and you need to sign in with your Azure
subscription. Or in the Amazon web services through the AWS account extension and
you need to sign in with your AWS subscription.

Once you have signed in, you can open the command prompt or terminal window and
build the project using Maven commands. This will generate a new
name.war or name.jar file in the target directory.

mvn clean package

After building the project, open the target directory in VS Code Explorer. Right-click on
the name.war or name.jar file and choose Deploy to Web App, and follow the prompts to
choose the Web App for your deployment.

Open the Output window in VS Code to view the deployment logs. Once the
deployment is completed, it will print out the URL for your Web App. Click the link to
open it in a browser, you can see the web app running on Azure or Aws.
4.3.3 Application Components

Any web application, big or small, contains four major components:

View Layer
When you consider an MVC application, the View layer component gives an interface
to the application. Regardless if it is for users with a browser or for another application
using Web services. View layer is the bridge for getting the data in and out of the
application.
It does not have business logic, like calculating interest for a banking application or
storing items in a shopping cart for an online catalogue. It also does not contain any
code for existing data to or retrieving data from a data source. Business logic is managed
by the Model layer. View layer is more focused on the interface.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 24

 CANTEEN MANAGEMENT SYSTEM

Business Layer
It is also known as Business Logic or Domain Logic or Application Layer. The function
of the business layer is to accept user requests from the browser, processes them, and
determine the routes through which the data will be accessed. The workflows by which
the data and requests travel through the back end lay encoded in a business layer.
Data Access Layer
This layer is built to keep the code you use to pull data from your data store like
database, flat files, or web services separate from business logic and presentation code.
So even if you have to change data stores, you don’t end up rewriting the whole thing.
There are many ORM frameworks that are blending the DAL with other layers which
makes development easy during web application development services.
Error handling, security, logging
When you build a web application, people generally tend to focus on the end-goal,
building and testing only for situations when things go right. Alas! things rarely go right
all the time in the real world.
This is where error handling is a vital part of any application’s user experience. And, if
it is done well, it can leave your users feeling informed and properly considered.

4.3.4 Overall Software Architecture

Figure 4.2 Java-based web application architecture

The architecture shown in above figure is used in the sync operation where the
data from web pages goes to web server (Apache Tomcat) to database server (MySQL).

DEPARTMENT OF CSE, GPREC, KURNOOL Page 25

 CANTEEN MANAGEMENT SYSTEM

JSP is used here because of the interaction it can offer with the databases and it is easy
to deploy on the XAMPP web server and here it sits in middle as shown in figure. SQL
insert query is written in JSP script to insert this data into MySQL database server.

4.4 Data Design

4.4.1 Database

My SQL

4.4.2 Tables

Name Description
Vendor To store the vendor details
Customer To store customer details
Menu To store menu details
Orders To store order details

Table 4.1 List of Database Tables

(1) Database: CMS Table: vendor
Description
To store the vendor details
Columns
Name Type Null Default Index
Vendor-id Int No Primary Key Auto Increment
Name Varchar(25) Yes NULL

Phone number bigInt Yes NULL Unique Key

Wallet balance Float Yes NULL

password Varchar(25) No

Table 4.2 Structure of vendor table of MySQL Database

DEPARTMENT OF CSE, GPREC, KURNOOL Page 26

 CANTEEN MANAGEMENT SYSTEM

Definition
create table VENDOR(VEN_ID INT auto_increment,
VEN_NAME VARCHAR(25),
VEN_PHNO BIGINT,
VEN_WALBALANCE FLOAT,
VEN_PWD VARCHAR(20),
CONSTRAINT VEN_Id_PK PRIMARY KEY(VEN_ID));
(2) Database: CMS Table: CUSTOMER
Description:
To store customer details
Columns:
Name Type Null Default Index
Id INT No Primary Key, auto increment
Name Varchar(25) No
Phonenumber long No Unique Key
Email Varchar(30) No
Date of birth date No
Password Varchar(20) No
Wallet balance float yes 0

Table 4.3 Structure of customer table MYSQL Database

Definition:
create table CUSTOMER
(CUS_ID int auto_increment,
CUS_NAME varchar(25) not null,
CUS_PHNO long not null,
CUS_EMAIL varchar(30) not null,
CUS_DOB date not null,
CUS_PWD varchar(20) not null,
CUS_WAL_BAL float,
constraint cus_id_pk primary key (CUS_ID));

DEPARTMENT OF CSE, GPREC, KURNOOL Page 27

 CANTEEN MANAGEMENT SYSTEM

(3) Database: CMS Table: MENU

Description: To store details about the
menu Columns:
Name Type Null Default Index
food_id INT No Primary Key Auto Increment
Food name VARCHAR(30) No
Food type VARCHAR(20) No NULL

Food price INT No NULL

Food category VARCHAR(20) No NULL

Food calories INT No NULL

Ven id INT No NULL FOREIGN KEY

Table 4.4 Structure of Menu table of MySQL Database

Definition:
create table MENU(MEN_FOOD_ID INT primary key,
MEN_FOOD_NAME VARCHAR(30),
MEN_FOOD_TYPE VARCHAR(20),
MEN_FOOD_PRICE INT,
MEN_FOOD_CATEGORY VARCHAR(20),
MEN_FOOD_CALORIES INT,
VEN_ID INT);

DEPARTMENT OF CSE, GPREC, KURNOOL Page 28

 CANTEEN MANAGEMENT SYSTEM

(4) Database: CMS Table: ORDERS

Description:
To store details about the order
Columns:
Name Type Null Default Index
Order id Int No Primary Key , Unique Key
Customer id Int No Foreign key
Vendor id Int No Foreign key
Order status varchar(50) Yes Ordered
Total cost float No
Order token int No
number
Order date Date No

Table 4.5 Structure of orders table MYSQL Database

Definition

create table ORDERS(ORD_ID INT primary KEY auto_increment not null,CUS_ID

INT not null,VEN_ID int NOT NULL,

ORD_STATUS VARCHAR(20) not null,TOTAL_COST float NOT

NULL,ORD_TOKEN_NUMBER INT NOT NULL,ORD_DATE datetime,

CONSTRAINT CUS_ID_FK FOREIGN KEY(CUS_ID)

REFERENCES CUSTOMER(CUS_ID)ON UPDATE CASCADE,

CONSTRAINT VEN_ID_FK FOREIGN KEY(VEN_ID)

REFERENCES VENDOR(VEN_ID) ON UPDATE CASCADE);

DEPARTMENT OF CSE, GPREC, KURNOOL Page 29

 CANTEEN MANAGEMENT SYSTEM

CHAPTER - 5

MODELING

DEPARTMENT OF CSE, GPREC, KURNOOL Page 30

 CANTEEN MANAGEMENT SYSTEM

5.MODELING
5.1Design
Requirements gathering followed by careful analysis leads to a systematic
Object-Oriented Design (OOAD). Various activities have been identified and are
represented using Unified Modeling Language (UML) diagrams. UML is used to
specify, visualize, modify, construct and document the artifacts of an object-oriented
software-intensive system under development.

5.1.1 Use Case Diagram

In the Unified Modeling Language (UML), the use case diagram is a type of
behavioral diagram defined by and created from a use-case analysis. It represents a
graphical over view of the functionality of the system in terms of actors, which are
persons, organizations or external system that plays a role in one or more interaction
with the system. These are drawn as stick figures. The goals of these actors are
represented as use cases, which describe a sequence of actions that provide something
of measurable value to an actor and any dependencies between those use cases.

Figure 5.1 Use Case Diagram for System

DEPARTMENT OF CSE, GPREC, KURNOOL Page 31

 CANTEEN MANAGEMENT SYSTEM

5.1.2 Sequence Diagram

UML sequence diagrams are used to show how objects interact in a given
situation. An important characteristic of a sequence diagram is that time passes from
top to bottom: the interaction starts near the top of the diagram and ends at the bottom
(i.e. Lower equals later).

A popular use for them is to document the dynamics in an object-oriented

system. For each key, collaboration diagrams are created that show how objects interact
in various representative scenarios for that collaboration.

Sequence diagram is the most common kind of interaction diagram, which

focuses on the message interchange between a numbers of lifelines.

The following nodes and edges are typically drawn in a UML sequence
diagram: lifeline, execution specification, message, combined fragment, interaction
use, state invariant, continuation, destruction occurrence.

Figure 5.2 Sequence Diagram for Customers Module

DEPARTMENT OF CSE, GPREC, KURNOOL Page 32

 CANTEEN MANAGEMENT SYSTEM

Figure 5.3 Sequence Diagram for Vendors Module

5.1.3 Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic
aspects of the system. Activity diagram is basically a flow chart to represent the flow
form one activity to another activity. The activity can be described as an operation of
the system.So the control flow is drawn from one operation to another. This flow can
be sequential, branched or concurrent. Activity diagrams deals with all type of flow
control by using different elements like fork, join etc.Activity is a particular operation
of the system.

Fig 4.4 Activity Diagram for Canteen Management System

DEPARTMENT OF CSE, GPREC, KURNOOL Page 33

 CANTEEN MANAGEMENT SYSTEM

5.1.4 Class Diagram

In software engineering, a class diagram in the Unified Modeling Language
(UML) is a type of static structure diagram that describes the structure of a system by
showing the system’s classes, their attributes, operations (or methods), and the
relationships among the classes.
The class diagram is the main building block of object oriented 32odeling. It is
used both for general conceptual 32odeling of the 32odeling32c of the application, and
for detailed 32odeling translating the models into programming code. Class diagrams
can also be used for data modeling. The classes in a class diagram represent both the
main objects, interactions in the application and the classes to be programmed.

Figure 5.5 Class Diagram for CMS

DEPARTMENT OF CSE, GPREC, KURNOOL Page 34

 CANTEEN MANAGEMENT SYSTEM

5.1.5 Deployment Diagram

Deployment diagram shows execution architecture of systems that represent the
assignment (deployment) of software artifacts to deployment targets (usually nodes).
Nodes represent either hardware devices or software execution environments. They
could be connected through communication paths to create network systems of arbitrary
complexity. Artifacts represent concrete elements in the physical world that are the
result of a development process and are deployed on nodes.

Figure 5.6 Deployment Diagram of the system

5.1.6 ER Diagram
An ER model is an abstract way to describe a database. Describing a database
usually starts with a relational database, which stores data in tables. Some of the data
in these tables point to data in other tables - for instance, your entry in the database
could point to several entries for each of the phone numbers that are yours. The ER
model would say that you are an entity, and each phone number is an entity, and the
relationship between you and the phone numbers is 'has a phone number'. Diagrams
created to design these entities and relationships are called entity–relationship diagrams
or ER diagrams.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 35

 CANTEEN MANAGEMENT SYSTEM

Figure 5.7 ER Diagram

DEPARTMENT OF CSE, GPREC, KURNOOL Page 36

 CANTEEN MANAGEMENT SYSTEM

CHAPTER - 6

IMPLEMENTATION

DEPARTMENT OF CSE, GPREC, KURNOOL Page 37

 CANTEEN MANAGEMENT SYSTEM

6. IMPLEMENTATION
6.1 Code Snippets
• Database
The first step to start the project execution is to implement database commands and
check whether the database created. The next step should be entering some data in the
tables by using DML Commands.

The Customer table from the SQL Workbench can be as shown in Fig 6.1.

Fig 6.1 Customer Table

DEPARTMENT OF CSE, GPREC, KURNOOL Page 38

 CANTEEN MANAGEMENT SYSTEM

The Menu table from the SQL Workbench can be as shown in Fig 6.2.

Fig 6.2 Menu Table

The Orders table from the SQL Workbench can be as shown in Fig 6.3.

Fig 6.3 Orders Table

DEPARTMENT OF CSE, GPREC, KURNOOL Page 39

 CANTEEN MANAGEMENT SYSTEM

The Vendors table from the SQL Workbench can be as shown in Fig 6.4.

Fig 6.4 Vendors Table

• DB Connection
The project code written in java will be connected to Database through DB Connection file. It is
shown in Fig 6.5.

Fig 6.5 Data Base Connection

DEPARTMENT OF CSE, GPREC, KURNOOL Page 40

 CANTEEN MANAGEMENT SYSTEM

In order to run the program, we will use maven commands in Git Bash and invoke the main program
of the project. The Git bash implementation can be shown in Fig.6.6(a) and Fig.6.6(b).

Fig 6.6(a) Git Bash Implementation

Fig 6.6(b) Git Bash Implementation

DEPARTMENT OF CSE, GPREC, KURNOOL Page 41

 CANTEEN MANAGEMENT SYSTEM

6.2. Screen Captures

The main page that will be displayed in web by giving localhost will be as shown in Fig. 6.7

Fig 6.7 Home Page

While we scroll the homepage, we can see four options to Customer Login, Customer Signup,
Vendor Login and Vendor Signup as shown in Fig.6.8

Fig 6.8 Login and Signup Page

DEPARTMENT OF CSE, GPREC, KURNOOL Page 42

 CANTEEN MANAGEMENT SYSTEM

Whenever a customer signed in, He/she must login. After login the Customer Dashboard will
be appeared as shown in Fig.6.9

Fig 6.9 Customer Home Page

The options like Place Order, Order History, Add Money, Cancel Order can be appeared. Each
button displays separate page as shown in Fig.6.10(a), Fig.6.10(b), Fig.3.10(c), Fig.6.10(d).

Fig 6.10(a) Place Order Page

DEPARTMENT OF CSE, GPREC, KURNOOL Page 43

 CANTEEN MANAGEMENT SYSTEM

Fig 6.10(b) Order History Page

The order history page displays all the orders placed by the customers. As shown in Fig.6.10(b).

Fig 6.10(c) Add Money Page

When a customer presses the button to add money, he/she must enter their Id and amount they want
to add and submit. A popup will be displayed as shown in Fig.6.10(c).

DEPARTMENT OF CSE, GPREC, KURNOOL Page 44

 CANTEEN MANAGEMENT SYSTEM

If the customer wants to cancel their order, a form will get displayed to enter their Id, Order Id, its
status to cancel the order as shown in Fig.6.10(d).

Fig 6.10(d) Cancel Order Page

If a vendor signed up and login through their credentials, he/she will get into Vendor home page
which will be a shown in Fig.6.11.

Fig 6.11 Vendor Home Page

DEPARTMENT OF CSE, GPREC, KURNOOL Page 45

 CANTEEN MANAGEMENT SYSTEM

If the vendor wants to see all the vendors details, he can press the first button in the home page and
he can view as shown in Fig. 6.12(a)

Fig 6.12(a) Vendor Details Page

A vendor can see the pending orders through the button Vendor Pending Orders and the view can
be as shown in Fig.6.12(b).

Fig 6.12(b) Vendor Pending Orders Page

DEPARTMENT OF CSE, GPREC, KURNOOL Page 46

 CANTEEN MANAGEMENT SYSTEM

A vendor can see the orders and he can change the status of the order through the button
Accept/Reject Order and the view can be as shown in Fig.6.12(c).

Fig 6.12(c) Accept/Reject Order Page

A vendor can also add items into the menu by choosing button Add Menu and then he can see a
form to enter respective details of food. It is shown in Fig 6.12(d).

Fig 6.12(d) Add Menu Page

DEPARTMENT OF CSE, GPREC, KURNOOL Page 47

 CANTEEN MANAGEMENT SYSTEM

CHAPTER - 7
RESULTS &CHALLENGES

DEPARTMENT OF CSE, GPREC, KURNOOL Page 48

 CANTEEN MANAGEMENT SYSTEM

7. RESULTS AND CHALLENGES

7.1 Results
In this website user can know the canteen near by location and he can choose the
canteen he wants. Then he can place order. Then the vendor gets the notification that
the order has been placed and he can deliver them to the customer.
In this project, we are going to create a website where there are 2 kinds of users namely
vendors and customers.

1. Owner:
This user can sign in to our website and can enter his canteen details and then
he can enter what food items he has in his canteen and the number of each item
present in the canteen. He can also update the number of items in the canteen.
The vendor can also accept or reject the order of the customer based on the stock
availability

2. Customer:
This user can sign in and then log in to the website and so that he could see the
canteen near to him and can place an order of items he wants.

7.2 Challenges
• Understanding the client requirements was one of the crucial tasks of the whole
project.
• Graphic User Interface (GUI) design was a difficult task as there are many types
of Android devices with varying screen size and resolutions unlike iPhone.
• Implementing synchronization with server on Android was a challenging task.
• Learning different technologies and frameworks with little guidance.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 49

 CANTEEN MANAGEMENT SYSTEM

CHAPTER - 8

CONCLUSIONS & FUTURE WORK

DEPARTMENT OF CSE, GPREC, KURNOOL Page 50

 CANTEEN MANAGEMENT SYSTEM

8. CONCLUSION
8.1 Conclusions
The application has been designed successfully to meet all the user
requirements. I found this project to be far more difficult than I ever anticipated.
Without doubt, this has been the most challenging and at the same time rewarding
programming project I have undertaken since I started college.

8.2 Scope for future work

The application can further be modified in the following ways:
• Finish the implementation of syncing the customer visit details to server.
• Additional features like tracking the order can be implemented.
• Introduce a feature to call contacts directly from within the app.
• Integrate with built-in Google Maps API, SMS, and Email.
• Fix all existing bugs

8.3 Limitations
The current application does have the feature of the tracking order hence the
customers might feel inconvenience sometimes and if the tracking of the order was
implemented then the customer knows the exact location of the order

DEPARTMENT OF CSE, GPREC, KURNOOL Page 51

 CANTEEN MANAGEMENT SYSTEM

REFERENCES

[1] Student Card System Using Smart Card Technology -Information Technology
Based Higher Education and Training, 2004. ITHET 2004.Proceedings of the
Fifth International Conference in January 2004 from the University of New South
Wales UNSW, Sydney, NSW 2052, Australia. 8.
[2] S SumitaNainan1, Romin Parekh, Tanvi Shah - RFID Technology Based
Attendance Management System from NMIMS University Mumbai, Maharashtra.
[3] Ms. Shilpa D.More1, Prof. Arti Mohanpurkar - LOAD BALANCING
STRATEGY BASED ON CLOUD PARTITIONING CONCEPT -
Multidisciplinary Journal of Research in Engineering and Technology, Volume 2,
Issue 10. Pg.424-431 from DYPSOET, Pune, India.
[4] Canteen Food Ordering Android System, Abhishek Singh, Amit Tanwar, Aditya
Sawant, Chaitanya Parulekar, Kunal Yadav, IT Department, MUMBAI
University, Journal on Recent and Innovation Trends in Computing and
Communication, ISSN: 2321-8169.
[5] Shweta Shashikant Tanpure, Priyanka R. Shidankar, Madhura M. Joshi,
“Automated Food Ordering System with Real-Time Customer Feedback”, in
International Journal of Advanced Research in Computer Science and Software
Engineering, Vol. 3, Issue 2, February 2013.
[6] S. B. Patil, Srikantha Rao, P. S. Patil 2001 ‘Canteen Management Design
Principles’ Proceedings of the International Conference & Workshop on Trades
in Technology, pp. 765-766, viewed 7 October 2001.
[7] Tan-Hsu Tan, Ching-Su Chang, Yung-Fu Chen, Yung-Fa Huang, Tsung-Yu Liu,
“Developing an Intelligent-Restaurant with a Menu Recommender for Customer-
Centric Service”, Systems, Man, and Cybernetics, Part C: Applications and
Reviews, IEEE Transactions.
[8] Ashik, Sumanth & Gopi, Teja & Asst, Krishna & Professor, & Sanjudharan, M S
Minu. (2018). ONLINE CANTEEN SYSTEM. 5. 218-223.

DEPARTMENT OF CSE, GPREC, KURNOOL Page 52