LNCT CANTEEN

A Minor Project Report (IT-508)

Submitted by:
SHESH NATH KUMAR (0103IT201159)
SANSKAR SHUBHAM (0103IT201152)
SUJEET SINGH (0103IT201176)
Group No.- 15
in partial fulfillment for the award of the degree
of

BACHELOR OF TECHNOLOGY

IN

INFORMATION TECHNOLOGY

Guided by

Prof. Medhavi Bhargava

Assistant Professor

Department of Information Technology

LAKSHMI NARAIN COLLEGE OF TECHNOLOGY

KALCHURI NAGAR, RAISEN ROAD, BHOPAL(INDIA) - 462021
SESSION JULY – DECEMBER 2022
1
 DECLARATION

We hereby declare that the project entitled “LNCT CANTEEN” submitted for the [Link]. (Information
Technology) degree is our original work and the project has not formed the basis for the award of any
other degree, diploma, fellowship or any other similar titles.

Place: Name & Signature of the students with date

Date: 1) Shesh Nath Kumar ………………………

2) Sanskar Shubham ………………………..

3) Sujeet Singh ……………………………..

2
 CERTIFICATE

This is to certify that the project titled “LNCT CANTEEN” is the bona fide work carried out by Shesh
Nath Kumar(0103IT201159), Sanskar Shubham(0103IT201152) & Sujeet Singh(0103IT201176)
are students of [Link] (Information Technology) of Lakshmi Narain College of Technology, Bhopal
affiliated to Rajiv Gandhi Proudyogiki Vishwavidyalay, Bhopal, Madhya Pradesh (India) during the
academic year 2022-23, in partial fulfillment of the requirements for the award of the degree of Bachelor
of Technology (Information Technology) and that the project has not formed the basis for the award
previously of any other degree, diploma, fellowship or any other similar title.

Signature & Seal Signature of the Guide with date

HOD, Information Technology Prof. Medhavi Bhargava
Lakshmi Narain College of Technology, Bhopal

3
 ACKNOWLEDGEMENT

We express our deep sense of gratitude to Prof. Medhavi Bhargava, Assistant Professor, Department
of Information Technology, Lakshmi Narain College of Technology, Bhopal, whose kindness &
valuable guidance and timely help encouraged us to complete this project.
A special thanks to Prof. Sushil Kumar, Head of Department, Information Technology, Lakshmi
Narain College of Technology, Bhopal who helped us by providing timely suggestions in completing
this project work. He exchanged his interesting ideas & thoughts which made this project work
successful.
We would also thank our institution and all the faculty members without whom this project work would
have been a distant reality.

Shesh Nath Kumar (0103IT201159)

Sanskar Shubham (0103IT171152)
Sujeet Singh (0103IT171125)

4
 ABSTRACT

In today’s age of fast food and take-out, many canteen have chosen to focus on quick preparation and
speedy delivery of orders rather than offering a rich dining experience. Until very recently, all of these
delivery orders were placed to the waiters or over the phone, but there are many disadvantages to this
system, including the inconvenience of the customer needing to have a physical copy of the menu, lack
of a visual confirmation that the order was placed correctly, and the necessity for the canteen to have an
employee answering the phone and taking orders. What, we propose is a Canteen Automation System,
which is a technique of ordering foods online applicable in any food delivery industry. The main
advantage of this system is that it greatly simplifies the ordering process for both the customer and the
canteen. When the customer visits the ordering webpage, they are presented with an interactive and up-
to-date menu, complete with all available options and dynamically adjusting prices based on the selected
options. After making a selection, the item is then added to their order, which the customer can review
the details of at any time before checking out. This provides instant visual confirmation of what was
selected and ensures that items in the order are, in fact, what was intended.
This system also greatly lightens the load on the canteen’s end, as the entire process of taking orders is
automated. Once an order is placed on the webpage, it is entered into the database and then retrieved, in
pretty much real-time, by a desktop application on the canteen’s end. Within this application, all items
in the order are displayed, along with their corresponding options and delivery details, in a concise and
easy to read manner. This allows canteen employees to quickly go through the orders as they are placed
and produce the necessary items with minimal delay and confusion.

5
 INDEX

1. CHAPTER 1 7

1.1 INTRODUCTION 7

1.2 OBJECTIVE 7

1.3 AIM 8

1.4 RELATED WORK 9

1.5 EXPECTED OUTPUT 10

2. CHAPTER 2 11

2.1 REQUIREMENTS 11

2.2 DIAGRAMS 13

2.2.1 USE-CASE DIAGRAMS 13

2.2.2 CLASS DIAGRAMS 15

2.2.3 SEQUENCE DIAGRAMS 18

3. CHAPTER 3 21

3.1 DESIGN TECHNIQUE 21

3.2 SOFTWARE PROCESS MODEL 23

4. CHAPTER 4 24

4.1 OUTPUT RESULT 24

5. CHAPTER 5 29

5.1 CONCLUSION AND FUTURE WORK 29

5.2 REFERENCES 30

5.3 LINKS 30

6
 CHAPTER 1
1. 1. INTRODUCTION:
In today’s age of fast canteen automation in the canteen, many canteens have
chosen to focus on quick preparation and speedy delivery of orders. Until very
recently, all of this delivery of orders were placed over the phone, but there are
many disadvantages to this system, including the inconvenience of the customer
needing to have a physical copy of the menu, lack of a visual confirmation that the
order was placed correctly, and the necessity for the canteen to have an employee
answering the phone and taking orders.

The main advantage of an online ordering system is that it greatly simplifies

the ordering process for both the customer and the canteen. When the customer
visits the ordering web page, they are presented with an interactive andup-to-date
menu, complete with all available options and adjusting prices based on the
selected options. After making a selection, the item is then added to their order,
which the customer can review the details at any time before checking [Link]
provides instant visual confirmation of what was selected.

This system also greatly lightens the load on the canteen’s end, as the entire
process of taking orders is automated. Once an order is placed on the web page, it
is entered into the database and then retrieved, in pretty much real-time, by a web-
based application on the canteen’s end. Within this application, all items in the
order are displayed, along with their corresponding options and delivery details, in
a concise and easy to read manner. This allows canteen employees to quickly go
through the orders as they are placed and produce the necessary items with
minimal delay and confusion.

1.2. OBJECTIVE :
Canteen Automation System is the system where customers order their food and
receive food in the canteen or at their doorstep. This system aims to accelerate

7
customer orders and customer order system used by employees to accept
customer order.

• The system requires very fewer time factors as compared to manual system.

• The system will provide fast and efficient automated environment instead of
slow and error prone manual system, thus reducing both time and manpower
spent in running the system.

• The system will have GUI interface and very less user training is required to learn
it.

1.3. AIM :
A complete canteen automation system makes canteen workers monitor
overall day to day business analytics more accurately with an ease. It increases the
presence of canteen fascinates core customers towards your food business leading
to increased sales.

By bringing all necessities in one place canteen automation system benefits

both the user as well as the canteen owner smartly. Ultimately all business
operation will be mad easier and single handed with the required inbuilt features.

The working of canteen automation system is similar to an e-commerce

website. Whenever your customers are busy with their work, instead of coming to
your canteen they can just open your website, choose the menu they like and can
simply order food.

As soon as order gets placed, you will be notified immediately, so that you
can start order processing. One of the main advantages of canteen automation
system is the order details are accurate when compared to the phone ordering
system or manual system.

This canteen automation system is useful for the canteen as well customer
because canteen automation system save the time of the canteen's workers as well
of the customers and as saves the manpower.

8
1.4 RELATED WORK:
• REQUIREMENT GATHERING & PLANNING
Planning identifies all deliverable services, describes the facilities, and defines
the working to provide details about lab details to the faculties. This planning
problem starts with a specification of user demand that is to be met by the
production plan. For this context, the facilities provided to the user faculties are
the major concern to be concentrated. This includes the easiest and efficient
way to make them available an unoccupied lab. Consequently, all the fields must
be kept while developing. Generally, a planning problem exists because there
are limited production resources that cannot be stored from period to period.
Choices must be made as to which resources to include and how to model their
capacity and behavior, and their costs. Also, there may be uncertainty
associated with the production function, such as uncertain yields or lead times.
One might only include the most critical or limiting resource in the planning
problem. Here comes the role of proper requirement gathering. If the
requirements of the user are clear then it is quite easier for the developer to
fulfill his all needs. As he can look into all the required resources, and with
proper planning and cost estimation, he can achieve his software. Thus, a proper
planning and requirement gathering leads to an efficient software system.

• DESIGNING AND BACKEND

Designing is the most important and the most efficient function while software
development. Without a proper design, it is very difficult to develop appropriate
software that fulfills nearly all user demands. Therefore, managing designing
part in an organization is critical. A designer needs to ensure that the design
created by him can be easily understood by the all the members of developing
a team. A proper design will allow the coder to implement the system
development planning properly. Similarly, the backend part that includes the
database management plays a key role in any of the systems.

9
1.5 EXPECTED OUTPUT:
The product developed will provide an easy access to the user to manage and
alter the canteen automation according to the need.

Our application will be a platform independent application which will

maintain a database of all orders ordered from various sources. Established
canteen automation practices will provide the needed connectivity and
accountability between those two operational units, and when managed
properly, enhances the effectiveness of both operations.

• Registration

• Order

• Update

The above are the modules of canteen automation system.

10
 CHAPTER 2
2.1 REQUIREMENTS:
• Functional Requirements:
Users of the canteen automation system, namely canteen customers, must be
provided the following functionality:

• Create an account.

• Manage their account.

• Log into the system.

• Navigate the canteen’s menu.

• Select an item from the menu.

• Customize options for a selected item.

• Add an item to their current order.

• Review their current order.

• Remove an item/remove all items from their current order.

• Place an order.

• Receive confirmation in the form of an order number.

11
• NON- FUNCTIONAL REQUIREMENTS
PERFORMANCE CRITERIA:
▪ TIME COMPLEXITY: The elapsed time between the submission of order
process between the customer and cashier in a canteen should be as
minimum as possible.

▪ USER-FRIENDLY: Our canteen automation system should be more users

friendly. The user interface should be kept simple and uncluttered. Since the
different type of people will interact with this process so our project should
be very easy to them to understand.

▪ FLEXIBILITY: Our project should be so flexible that whenever we want

to make changes in it very easily it can be done.

▪ EXTENSIBILITY: It should be able to accommodate the variations like:

1. The different order should be handled easily.

2. It should be an option for cash on delivery, pay through card between

customer and canteen.

▪ PORTABLE: Our project should be portable on any platform and available

on websites easily and at a faster speed than others.

▪ REUSABLE: Our project should be portable on any platform and available

on websites easily and at a faster speed than others.

12
2.2. DIAGRAMS:
2.2.1. USE-CASE DIAGRAMS:
A use case is a description of how end-users will use a software code. It
describes a task or a series of tasks that users will accomplish using the
software and includes the responses of the software to user actions.

13
14
2.2.2. CLASS DIAGRAMS:
In the Unified Modeling Language (UML), a class diagram is a type of static
structure diagram that describes the structure of a system by showing the system's
classes, their attributes, and the relationships between the classes.

15
16
17
2.2.2. SEQUENCE DIAGRAMS:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order.
It is a construct of a Message Sequence Chart. Sequence diagrams are sometimes
called event diagrams, event scenarios, and timing diagrams.

18
19
Fig 3.4 Sequence Diagram for Menu Selection

20
 CHAPTER 3
3.1. DESIGN TECHNIQUES:
The design of the website has been done using the following technologies:-

• HTML

• CSS

• Java Script

• Netlify

• FIREBASE DATABASE

3.1.1 HTML: The HyperText Markup Language or HTML is the standard markup
language for documents designed to be displayed in a web browser. It can be assisted
by technologies such as Cascading Style Sheets (CSS) and scripting languages such
as JavaScript.
Web browsers receive HTML documents from a web server or from local storage
and render the documents into multimedia web pages. HTML describes the structure
of a web page semantically and originally included cues for the appearance of the
document.

3.1.2 CSS: Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language such
as HTML or XML (including XML dialects such as SVG, MathML or XHTML). CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript.
CSS is designed to enable the separation of content and presentation,
including layout, colors, and fonts. This separation can improve content accessibility;
provide more flexibility and control in the specification of presentation characteristics;
enable multiple web pages to share formatting by specifying the relevant CSS in a
separate .css file, which reduces complexity and repetition in the structural content;
and enable the .css file to be cached to improve the page load speed between the
pages that share the file and its formatting.
21
3.1.3 JavaScript: JavaScript, often abbreviated as JS, is a programming
language that is one of the core technologies of the World Wide Web,
alongside HTML and CSS. As of 2022, 98% of websites use JavaScript on the client side
for webpage behaviour, often incorporating third-party libraries. All major web
browsers have a dedicated JavaScript engine to execute the code on users' devices.
JavaScript is a high-level, often just-in-time compiled language that conforms to
the ECMAScript standard. It has dynamic typing, prototype-based object-orientation,
and first-class functions. It is multi-paradigm, supporting event-driven, functional,
and imperative programming styles. It has application programming interfaces (APIs)
for working with text, dates, regular expressions, standard data structures, and
the Document Object Model (DOM).

3.1.4 Netlify: Netlify is a remote-first cloud computing company that offers a

development platform that includes build, deploy, and serverless backend services for
web applications and dynamic websites. The platform is built on open web standards,
making it possible to integrate build tools, web frameworks, APIs, and various web
technologies into a unified developer workflow.

3.1.5 Firebase Database: Firebase evolved from Envolve, a prior startup founded by
James Tamplin and Andrew Lee in 2011. Envolve provided developers an API that
enables the integration of online chat functionality into their websites. After releasing
the chat service, Tamplin and Lee found that it was being used to pass application data
that were not chat messages. Developers were using Envolve to sync application data
such as game state in real time across their users. Tamplin and Lee decided to separate
the chat system and the real-time architecture that powered it. They founded Firebase
as a separate company in 2011 and it launched to the public in April 2012.
Firebase's first product was the Firebase Realtime Database, an API that synchronizes
application data across iOS, Android, and Web devices, and stores it on Firebase's
cloud. The product assists software developers in building real-time, collaborative
applications.

22
3.2. SOFTWARE PROCESS MODEL:
We are using RAD model for developing this application. The striking feature of the
incremental model is that each module can be completed and released as andwhen
the requirement arises because of lack of time.

The user can thus get a feel of these modules and give his feedback which
can be utilized for making the software more user-friendly and in line with the user
requirements.

Not only that the deadline set for this project is 6 months and we need a high
Adaptation model and again will be concentrating on parallelism because ourteam
will be working on the different module at the same time. Moreover, we willbe
using latest tools such as Visio, Project Manager as a result of which we can work
much faster. So looking into all these requirements we find Incremental RADmodel
is best suited for our system because it enables the development team to create a
fully functional system within a very short period of time.

Why not Waterfall model?

Waterfall model can be adopted because in our case because requirements are
known in advance but there are some limitations of waterfall model due to which
it is not feasible to adopt:

• No parallelism of work.
• Time consuming.

Why not Evolutionary models?

These models are best suited where requirements are fuzzy. These models are best
suited for the systems where requirements keep on changing. But for our system
requirements are crystal clear so it is not feasible to adopt any of the evolutionary
models.

23
 CHAPTER 4
The final product will be a website using which you can order your food from canteen
menu.

Fig: Home Page

24
Fig. Sign up and Login Page

25
Fig : Menu

26
Fig : Cart

27
Fig. Order History

28
 CHAPTER 5

5.1. CONCLUSION AND FUTURE WORK:

With this project we are trying to reduce the distance between your room
and canteen. Here all the order details like the order types are stored daily
which reduces manual work. Use of Real-time database makes it one of a
kind as all the data will be saved in the database and administrator can
view all the data on time.

Add different payment options such as Paytm, PayPal, UPI etc.

Enhance user interface by adding more user interactive features. Allow to
process order as a guest.

29
5.2 REFERENCES:
• GitHub

• YouTube

• Udemy

• Coursera

• Wikipedia

• Seniors

5.3 Links:
• Website Link: [Link]

• Developers Profile:

Sanskar Shubham: [Link]

Shesh Nath Kumar : [Link]

Sujeet Singh: [Link]

30