PROJECT REPORT

ON

ONLINE FOOD ORDERING APPLICAATION

(An Online Food Management System)

Submitted for partial fulfillment of award of

Degree

In

BACHELORS OF COMPUTER APPLICATION

Submitted by

Fahad

Roll No - 200934106083

Under the Supervision of

Prof. Shweta Kumar

INSTITUTE OF TECHNOLOGY & SCIENCE

MOHAN NAGAR, GHAZIABAD

 CERTIFICATE
This is to certify that Fahad Ahmed of Roll No. 200934106083 has
carried out the project work presented in this report entitled “Web
Application” for the award of Bachelors of Computer Application from
Institute of Technology and Science, Mohan Nagar, Ghaziabad, under
my supervision.

The report embodies result of original work and studies carried out by
student himself and the content of the report do not form the basis for
the award of any other degree to the candidate or to anybody else.

Date:

Prof. Shweta Kumar

Institute of Technology
& Science, Mohan
Nagar, Ghaziabad
 ACKNOWLEDGEMENT

I would like to express my special thanks of gratitude to my teacher

Miss. Shweta Kumar as well as our Institute of Technology & Science
Mohan Nagar Ghaziabad who gave me the golden opportunity to do
this wonderful project on the topic Food ordering web Application
which also helped me in doing a lot of research and I came to know
about so many new things. I am really thankful to them.

Secondly, I would also like to thank my group mates Bablu Pal, Pankaj
Yadav, Yash pandit who also helped me a lot in finalizing this project
within the limited time frame.

Fahad Ahmed
200934106083
 ABSTRACT

This project is aimed at developing a complete online ordering system

application for use in the foodservice industry which will allow the
restaurants to quickly and easily manage an online menu which
customer can browse and use to place orders with just a few clicks.
The customers will have to choose whether they want the food to be
delivered to them and the payment method will be upon delivery. There
will be a system administrator who will have the right to add and
manage user accounts, a manager who will be managing product and
others and last but not least a meal deliverer who will be dealing
specifically with pending deliveries. The customer will be in a position to
view the products, register and place an order.
The development of this system will be based on SDLC with HTML,CSS
and JAVA SCRIPT as the programming languages while MYSQL server as
the database of the system.
HTML language is advantageous due to its easy to use and learn
validation properties while MySQL has better advanced features and
properties, has good security, is open source and has cross platform
operability.
 CONTENT OF PROJECT

Chapter: -1
Introduction.
Chapter: -2
Main Objectives and Purpose.
Chapter: -3
Technical Details of Project.
Chapter: -4
System Analysis/Requirements.
Chapter: -5
Preliminary Investigation.
Chapter: -6
Feasibility Study.
Chapter: -6.1
Technical Feasibility.
Chapter: -6.2
Economical Feasibility.
Chapter: -6.3
Operational Feasibility.
Chapter: -7
 Software Requirement Specification.

Chapter: -8
Design.
Chapter: -8.1
Project Architecture and Navigation.
Chapter: -8.2
USE Case.
Chapter: -8.3
Data Flow Diagram.
Chapter: -8.4
ER Diagram.
Chapter: -9
UI Testing.
Chapter: -10
Forms.
Chapter: -11
Glossary.
Chapter: -12
Conclusion.
Chapter: -13
Bibliography.
 CHAPTER:-1
INTRODUCTION.
The “ s r pp” is an Online Food Supply
Management System is a process in which one can order
various foods and beverages from some local restaurants and
hotels through the use of internet, just by sitting at home or
any other place. And the order is delivered to the told location.
Nowadays everyone is having busy schedule whether it is urban
area or rural. But talking specifically about the urban areas and
deeply about the big cities, people out there are so busy in
their life that they don’t get enough of time to have their meals
properly. So food ordering system these days has one of the
fastest growing market, though being a new idea. In this project
we have developed something like the same to earn from and
serve the nation in a much better way possible.

In the management of food supply chains, criteria including

the incoming quality of materials, processing methodology,
storage conditions, outgoing quality, and much more must be
documented at each link in the chain. Synchronizing and
sharing this information among all of the parties along the
chain is critical for enabling lot traceability, collaborative
coordination and optimization of operations, product
consistency and quality management, regulatory compliance,
and ultimately, customer safety and satisfaction.
 CHAPTER:-2

MAIN OBJECTIVE AND PURPOSE.

The purpose of an online ordering system is to make itself

beneficial for the customer and the business so that they can
stay afloat while also serving customers their favorite dishes.
With Food Aggregators increasing their commission every
quarter, it is unsustainable for the restaurant to manage their
restaurant while depending on food delivery orders.
The customers will have to choose whether they want the food
to be delivered to them and the payment method will be upon
delivery. There will be a system administrator who will have the
right to add and manage user accounts, a manager who will be
managing product and others and last but not least a meal
deliverer who will be dealing specifically with pending
deliveries. The customer will be in a position to view the
products, register and place an order.
This project is aimed at developing a complete online ordering
system application for use in the foodservice industry which
will allow the restaurants to quickly and easily manage an
online menu which customer can browse and use to place
orders with just a few clicks.
 CHAPTER:-3

TECHNICAL DETAILS OF PROJECT.

Microsoft Edge:-
Microsoft Edge is a proprietary, cross-platform web browser created
by Microsoft. It was first released in 2015 as part of Windows
10 and Xbox One and later ported to other platforms as a fork
of Google's Chromium open-source project: Android and iOS, macOS,
older Windows versions (Windows 7 and later), and most recently Linux.
It was created as the successor to Internet Explorer (IE).
Edge was initially built with Microsoft's own proprietary browser
engine, Edge HTML, and their Chakra JavaScript engine. In late 2018, it
was announced that Edge would be completely rebuilt as a Chromium-
based browser with Blink and V8 engines. The new Edge was publicly
released in January 2020, and on Xbox platforms in 2021. Microsoft has
since terminated security support for the original browser (now referred
to as Microsoft Edge Legacy), and in Windows 11 it is the default web
browser (for compatibility with Google Chrome).

Google Chrome:-
Google Chrome is a cross-platform web browser developed by Google. It
was first released in 2008 for Microsoft Windows, built with free
software components from Apple Web Kit and Mozilla Firefox. Versions
were later released for Linux, macOS, iOS, and also for Android, where it
is the default browser. The browser is also the main component
of Chrome OS, where it serves as the platform for web applications.
Most of Chrome's source code comes from Google's free and open-
source software project Chromium, but Chrome is licensed as
proprietary freeware. Web Kit was the original rendering engine, but
Google eventually forked it to create the Blink engine; all Chrome
variants except iOS now use Blink.
As of October 2022, Stat Counter estimates that Chrome has a 67%
worldwide browser market share (after peaking at 72.38% in November
2018) on personal computers (PC), is most used on tablets (having
surpassed Safari), and is also dominant on smartphones and at 65%
across all platforms combined. Because of this success, Google has
expanded the "Chrome" brand name to other products: Chrome
OS, Chromecast, Chromebook, Chromebit, Chromebox,
and Chromebase.
Microsoft Word:-
Microsoft Word Word for Windows is available stand-alone or as part of
the Microsoft Office suite. Word contains rudimentary desktop
publishing capabilities and is the most widely used word processing
program on the market. Word files are commonly used as the format for
sending text documents via e-mail because almost every user with a
computer can read a Word document by using the Word application, a
Word viewer or a word processor that imports the Word format
(see Microsoft Word Viewer).
Word 6 for Windows NT was the first 32-bit version of the
product, released with Microsoft Office for Windows NT around the
same time as Windows 95. It was a straightforward port of Word 6.0.
Starting with Word 95, each release of Word was named after the year
of its release, instead of its version number.
Word 2007 introduced a redesigned user interface that emphasized the
most common controls, dividing them into tabs, and adding specific
options depending on the context, such as selecting an image or editing
a table. This user interface, called Ribbon, was included in Excel,
PowerPoint and Access 2007, and would be later introduced to other
Office applications with Office 2010 and Windows applications such as
Paint and WordPad with Windows 7, respectively.
The redesigned interface also includes a toolbar that appears when
selecting text, with options for formatting included.

CHAPTER:-4

SYSTEM ANALYSIS/REQUIREMENTS
This chapter presents system requirements analysis. The purpose of
the system requirements analysis is to structure the system
independent of any implementation environment. This phase can
determine system behavior and limitations. The system requirements
analysis activity represents the second major development phase of
the overall process. A common approach to object-oriented methods
is to focus exclusively on objects and their relations. A scenario is a
sequence of actions that takes place within the system. The starting
point is a stimulus from an external source. Each time a user activates
the system, a sequence of actions takes place within the system. This
sequence represents a scenario. A significant difference between a
user and objects within the system is that user actions are
nondeterministic. Scenarios are determined by first establishing the
user interfaces with the system. Scenarios can be identified through
the actors of the system. Various forms for documenting scenarios
are used depending on the level of abstraction. The highest level of
abstraction describes the set of scenarios and the actors that
stimulate those scenarios.

 1 GHz processor or faster 32-bit (x86) or 64-bit (x64).

 1 GB of RAM for 32-bit or 2 GB of RAM for 64-bit.
 16 GB of hard drive space for 32-bit or 20 GB for 64-bit.
 DirectX 9 graphics device with WDDM 1.0 or higher.
The following configurations are required to complete this project.

CHAPTER:-5

PRELIMINARY INVESTIGATION.
The first step in the system development life cycle is the
preliminary investigation to determine the feasibility of the
system. The purpose of the preliminary investigation is to
evaluate project requests. It is not a design study nor does it
includes the collection of details to describe the business
system in all respects.

● Planning the Preliminary Investigation

– During a preliminary investigation, a systems analyst

typically follows a series of steps

– The exact procedure depends on the nature of the

request, the size of the project, and the degree of urgency

● Step 1: Understand the Problem or Opportunity

– Determine which departments, users, and business

processes are involved

– A popular technique for investigating causes and effects is

called a fishbone diagram, or Ishikawa diagram

● Step 2: Define the Project Scope and Constraints

 – Project scope

– Project creep

– Constraint

– Present versus future

– Internal versus external

– Mandatory versus Desirable

– Regardless of the type, all constraints should be identified

as early as possible to avoid future problems and surprises

● Step 3: Perform Fact-Finding

– Fact-finding involves various techniques

– Depending on what information is needed to investigate

the systems request, fact-finding might consume several
hours, days, or weeks

– Analyze Organization Charts

● Obtain organization charts to understand how the

department functions

– Conduct interviews

● Determine the people to interview

● Establish objectives for the interview

● Develop interview questions

 ● Prepare for the interview

● Conduct the interview

● Document the interview

● Evaluate the interview

– Review documentation

– Observe operations

– Conduct a user survey

● Step 4: Evaluate Feasibility

– Evaluate the project’s operational, technical, economic,

and schedule feasibility

● Step 5: Estimate Project Development Time and Cost

– What information must you obtain, and how will you

gather and analyze the information?

– What sources of information will you use, and what

difficulties will you encounter in obtaining information?

– Will you conduct interviews? How many people will you

interview, and how much time will you need to meet with
the people and summarize their responses?

– Will you conduct a survey? Who will be involved? How

much time will it take people to complete it? How much
time will it take to prepare it and tabulate the results?
 – How much will it cost to analyze the information gathered
and to prepare a report with findings and
recommendations?

– You should provide an estimate for the overall project, so

managers can understand the full cost impact and
timetable

● Step 6: Present Results and Recommendations to

Management

– The final task in the preliminary investigation is to prepare

a report to management

– The format of the preliminary investigation report varies

from one company to another

● Step 6: Present Results and Recommendations to

Management

● Introduction

● Systems request summary

● Findings

● Recommendations

● Project roles

● Time and cost estimates

● Expected benefits
 ● Appendix

CHAPTER:-6

FEASIBILITY STUDY.
A feasibility study is conducted to find out whether the proposed
system is possible, affordable and acceptable for organization. The
financial, political, social and time constraints must be considered during
this study.
It is important to be reasonably sure of the success of proposed system
before initiating work on it. A feasibility study is a study to find out
whether the proposed system is:

· Possible—to build it with the given technology and

resources
· Affordable—given the time and cost constraints of the
organization
· Acceptable—for use by the eventual users of the system.

Purpose of Feasibility Study

A feasibility study is initiated by an organization when a change is

required in the current system. A feasibility study is needed to ascertain
the advantages and disadvantages of the new system. Following are the
important purposes of feasibility study:

· Need Analysis—Determine the need for change within an

organization
· Cost Benefit Analysis—Study the effect of change on the
economics of organization
 · Technical Feasibility—Evaluate various technologies that
can be used to implements the suggested change given the
cost and resource constraints of an organization
· Legal Feasibility—Evaluate the possible legal procedures
to implement the change
· Evaluating Alternatives—Evaluate various alternatives to
resolve the problems of an organization and recommend the
best one
A feasibility study is not justified for projects where benefits
out-weight costs, technical risks are not high and there are
no alternatives. For such projects, conducting a feasibility
study will add to unnecessary expenditure of time and money
for the study itself.

1.1 Technical Feasibility.

Technical feasibility helps in understanding the level and kind of

technology needed for a system. It includes performance issues and
constraints that may affect the ability to achieve an acceptable system.
Technical feasibility entails an understanding of the following:
· Different technologies involved in the proposed system
such s hardware platform and software environment
· Existing technology levels within the organization
· The level of expertise required to use the suggested
technology. It may determine the need for user training and
therefore affect the costs of the system.
This includes the study of function, performance and
constraints that may affect the ability to achieve an acceptable
system. For the feasibility study, we studied the complete
functionality to be provided in the system.
1.2 Economical Feasibility.
Economic Feasibility determines the costs of developing and
implementing a new system as well as the benefits of the new
system. The study of costs and benefits is also known as Cost Benefit
analysis.
A system is said to be economically feasible if benefits are more than
costs. It includes tangible and intangible benefits. Tangible benefit is
the benefit that can be measured in money value. It results increased
revenue and decreased cost. Intangible benefit is difficult to quantify
but its effect is realized as follows:

· Better market position in comparison to the competition

· Improved service to customers due to correct information on
time
· Improved service to customers results in better good will
resulting in more business
The costs associated with most systems fall under the following
broad categories:
· Procurement Costs: This type of cost deals with the purchase
and installation of equipment, cost of setting up site for installing the
equipment, cost of setting up site for installing the equipment, cost
of capital that will be spent, cost of staff dealing with the
procurement activities.
· Start-up Costs: It includes the cost of hiring and setting up
manpower, cost of setting up communication systems (telephone
lines etc.), operating system software etc.
· Project Costs: These are costs that re spent when the project is
underway. Once the project is complete and the system up and
running none of these costs is relevant.
· Ongoing / Recurring costs: It includes rental of the site, cost of
the personnel associated with running of system, cost of
depreciation on hardware, cost of maintenance of hardware, cost of
consumables likes floppies and stationary etc.
 This is a very important aspect to be considered while
developing the project. We decided the technology based on
minimum possible cost factor.
1.3 Operational Feasibility.

It is mainly related to human organizational and political aspects. The

points to be considered are: what changes will be brought with the
system? what organizational structures are disturbed? = what new skills
will be required? Do thk existing staff membcrs have these skills? If not,
can they be trained in due course of time? Generally project will not be
rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the
eventual recommendations. This feasibility study is carried out by a
small group of people who are familiar with information syslem
techniques, who understand the parts of the business that are relevant
to the project and are skilled in system analysis and design process.

No doubt the proposed system is fully GUI based that is very

user friendly and all inputs to be taken all selfexplanatory to a
laymen. Besides, a proper training is taken to let know the
essence of the system to the users so that they feel
comfortable to work with new system.
 CHAPTER:-7

SOFTWARE REQUIREMENT SPECIFICATION.

The structure of the system can be divided into three
main logical components. The first component must
provide some form of menu management allowing the
restaurant to control what can be ordered by customers.
The second component is the web ordering system and
provides the functionality for customers to place their
order and supply all necessary details. The third and final
logical component is the order retrieval system. Used by
the restaurant to keep track of all orders which have been
placed, this component takes care of retrieving and
displaying order information as well as updating orders
which have already been processed.

Customer Web Ordering System Database Order Retrieval

Menu Management

Restaurant Employee
 CHAPTER:-8

DESIGN

8.1 Project Architecture and Navigation.

The project architecture is in a way that when the
Customer opens the Webpage, he/she sees the Home
page at first with various types of Food Items. In the
project, we stated 6 different categories of food items i.e.
Pizza, Burger, Fries, Rice Bowl, Meals and Pasta. If the
Customer chooses Pizza and clicks on Order Now, He/she
gets the sub categories of Pizzas such as Cheese Pizza,
Veggie Pizza, Barbeque Chicken Pizza, Meat Pizza,
Margherita Pizza and Pepperoni Pizza. So whichever Pizza
the Customer wants to order, he/she can click on Add to
Cart option for further Delivery and Payment process.

8.2 USE Case

The USE case model of a system contains the “Used
Cases”. Use cases represents different ways in which the
system can be used by the user. The use cases partition
the system behavior into transactions such that each
 transaction performs some useful action from the users’
point of view.

8.3 Data Flow Diagram

A Data Flow Diagram(DFD) is a graphical representation of

the flow of data through an information system. DFD’s
can also be used for the visualization of data processing. A
DFD is a significant modeling technique for analyzing and
constructing information processes. Data Flow Diagram
uses number of symbols and some are:-

Process

Data Store

Source/Sink

Data Flow

8.4 ER Diagram

ER model is a popular high level conceptual data model.

This model and its variants are frequently used for the
conceptual design of database application and many
database design tools employ its concept.

The ER diagram for the project is as follows:-

 CHAPTER:-9

UI TESTING.

INTRODUCTION
The importance of software testing shouldn’t be
underestimated. This phase is sometimes overlooked, yet
it may have a significant influence on your product and
business. To help you understand the importance of
testing we have implemented various test cases on our
software i.e., Food Ordering System. Functionality, ease
of development, simplicity of installation, quality of
documentation and assistance, performance, and so on
are common testing criteria. White box testing
encompasses a number of ways for evaluating the
usability of an application, a piece of code, or a specific
software package.
When it comes to application testing, unit testing is
typically the initial step. Unit testing is performed on each
unit or block of code as it is produced. Unit testing is
essentially the responsibility of the coder. You write a few
lines of code, a single function, or an object as a software
developer, then test it to confirm it works before going on
to the next phase. Early in the software development
 lifecycle, unit testing aids in the detection of the majority
of issues. Bugs detected early in the development process
are less expensive and easier to fix.

TEST CASE
We have implemented various test cases on our software
i.e., Food Ordering System. A TEST CASE is a sequence of
actions performed to ensure that a certain feature or
operation of your software application is working
properly. A Test Case contains test steps, test data,
precondition, post condition developed for specific test
scenarios to verify any requirement. The test case
contains specified variables or circumstances that a
testing engineer might use to compare expected and
actual outcomes in order to assess whether a software
product meets the customer's needs.

TEST CASE: 01 ADD MENU.

S TEST CASE Expected Result Test Result
No.
1. Enter the images and name of the To show the Successful.
food. view of menu.
2. Enter the rates of the food items. To add the Successful.
rates of food.
3. Click on Order Now. To order the Successful.
food.
 Chapter: -10
FORMS

Forms allow you to collect information and capture work from other
teams or stakeholders in your organization. Create different types of
forms to receive different types of work from your stakeholders.

When you create a form, you can choose the (issue) type for when
people submit the form as a work item to your project. You can choose
the type of work that your form collects, which will change the type of
work item that’s created when that form is submitted to your project.
Each type will have different form fields depending on what kind of
information you want to collect. Your project will only show other types
if you have more than one (issue) type for your project.

You can create as many forms as you need for your business project.

Forms can be used to:

 Help people outside your immediate team send work to your

project team
 Collect the right information from other teams stakeholders in your
organization
 Receive certain requests or information by creating certain types of
forms
When people fill out and submit forms, their responses are submitted to
your business project as work items for your team to begin working on.

Chapter: -11
Glossary.
 SDLC (software development life cycle) – The process used in
software development to build, design, and test high-quality
software. It implies three rules: create high-quality software on
time, stay within budget, and meet customers expectations.
 Agile – A software development approach that implies iterative
software development, flexible planning, and continuous
improvement. The main idea is to deliver software fast to the
market and shape it basing on customers’ real needs.
 SCRUM – A project management methodology for effective team
collaboration based on the Agile software development approach.
 Kanban – An approach for managing software development.
Kanban depicts the planned work and the work that is in progress.
The main idea is to optimize the process and overcome barriers.
 Waterfall – A linear software development approach. Each stage
has to be completed before the next one. This approach doesn’t
imply any overlapping of the development stages.
 Tracker – A tool that helps to monitor the project progress and to
manage the team easily.
 Jira – One of the biggest brands of trackers that works with two
software development approaches: SCRUM and Kanban. It has a
variety of tools for task management, team monitoring, bugs
tracking and provides advanced project analytics.
 Trello – A project management tracker based on the Kanban
software development approach that doesn’t offer any reports.
Best suitable for small teams.
 Redmine – Project management system.
 MVP (minimum viable product) – A product with a basic feature
set that is enough to collect users feedback or even release.
 Sprint – A period of time when the predefined amount of work has
to be completed by the software development team.
 Deadline – A time limit to complete tasks or achieve objectives
before it will have an impact on the project.
 Release – The process of sharing the completed application with
the world, usually implied by adding the app to the app stores.
 Decomposition – A project management technique used to split
the complex problem into parts that are easier to execute.
 Retrospective – A meeting with the customer and development
team after each sprint to present the reports about completed
work, issues that need improvements, and further steps.
 Sprint Review – A meeting when software development team
demonstrates the results of hard work during the sprint to the
customer.
 Velocity – A key metric in the Agile approach that measures the
amount of work that the team resolves during one sprint.
 User Story – The smallest amount of work in the Agile approach. A
user story is a short & detailed description of a goal from a user’s
perspective.
 Story Point – An estimation of task complexity in the Agile
approach.
 WBS (work breakdown structure) – Distribution of a project into
small parts to complete the project successfully.
 Dependencies – Correlations between tasks that establish the
order in which tasks have to be executed.
 Project Plan – A formal document comprising project details that
helps manage the project and its execution.
 Time and Material – A software development pricing model when
the customer agrees to pay the company for the actual time spent
on development & received result and for the cost of materials.
 Risk Management – The process of detecting, assessment, and
priority setting for risks that arise in the software development
process, adjusted by a project manager.
 Risk Register – The tool used to manage risks that looks like a
scatter chart.
 CHAPTER:-12
CONCLUSION.
An online food ordering system is developed where the
customers can make an order for the food and avoid the hassles
of waiting for the order to be taken by the waiter. Using the
application, the end users register online, read the E-menu card
and select the food from the e-menu card to order food online.
Once the customer selects the required food item the chef will be
able to see the results on the screen and start processing the
food. This application nullifies the need of a waiter or reduces the
workload of the waiter. The advantage is that in a crowded
restaurant there will be chances that the waiters are overloaded
with orders and they are unable to meet the requirements of the
customer in a satisfactory manner. Therefore by using this
application, the users can directly place the order for food to the
chef online. In conclusion an online food ordering system is
proposed which is useful in small family run restaurants as well as
in places like college cafeteria, etc. This project can later be
expanded on a larger scale. It is developed for restaurants to
simplify their routine managerial and operational task and to
improve the dining experience of the clients. This also helps the
restaurant owners develop healthy customer relationships by
providing reasonably good services. The system also enables the
restaurant to know the items available in real time and make
changes to their food and beverage inventory based on the orders
placed and the orders completed.

CHAPTER:-13

BIBLIOGRAPHY.
 www.google.com
www.codingninja.c om
 www.wikipedia.com
 www.studocu.com
 www.youtube.com

*********************************************
*********************************************
*********************************************
*********************************************