Online Food Delivery System

Management

Software Requirement Specification (SRS)

SOFTWARE PROJECT DOCUMENTATION

Prepared by:
Roll No.
Group MEHWISH SALEEM
21934514
No.3
21934516 NIMRA FATIMA
BS CS 8th sem Session: 2021-23
NIMS College Bahawalpur
The Islamia University of Bahawalpur
 Online Food Delivery System
Management

Roll No. 21934514 MEHWISH SALEEM

Roll No. 21934516 NIMRA FATIMA

A thesis submitted in partial fulfillment of the requirement for the degree of

DEPARTMENT OF COMPUTER SCIENCE & IT

Thesis Supervisor:

External Examiner’s Signature:____________________________________

Thesis Supervisor’s Signature:_________________________________________

DEPARTMENT OF COMPUTER SCIENCE & IT

The Islamia University of Bahawalpur

Session 2021-23
 Project Brief

Project:

Online Food Delivery System Management

Status:

BSCS Project-I

Objective: ‘Food Delivery’ is basically an inventory software that designed specially to meet the
requirements ... invoice management, balance management, view staff sales records, restore by Food
Delivery Powers friendly user interface and functionalities. And Food Delivery Power supports full
customizable company info, logo, tax...

Undertaken By:

Roll No. 21934514 MEHWISH SALEEM

Roll No. 21934516 NIMRA FATIMA

Supervised By:

Operating System:

Microsoft Windows 7 & 8 Ultimate

Project Work Duration:

Duration: Jan 2024 to April 2024

Total months: 4 Months

Tools / Software: Dreamweaver, xAMP, HTML,CSS,PHP

Tools / Software: Dreamweaver, xAMP, HTML,CSS,PHP

 UNDERTAKING

We certify that research work titled “Online Food Delivery System Management” is our own
work. The work has not been presented elsewhere for assessment. Where material has been used
from other sources it has been properly acknowledged / referred.

Roll No. 21934514 MEHWISH SALEEM

Roll No. 21934516 NIMRA FATIMA

DEDICATION:

Endless love of my Parents

Whose Prayers have enabled

Me

To complete my project

&

To our Teachers who always

Encouraged Me

May their love and Prayers

Enlighten

The path of my life.

 FINAL APPROVAL

It is to certify that we have read this Project Documentation in titled online Food Delivery
System Management.. It is our judgment that this project Documentation is of sufficient
standard to warrant its acceptance by the The Islamia University of Bahawalpur, for the
Master degree in Computer Science.

Supervisor:

…………………………

Coordinator of MCS

Department of Computer Science & IT NIMS College Bwp

The Islamia University Bahawalpur

External Examiner: ________________________

 Background of the Study
Online Food Delivery System management is a prime ask foran organization to
achieve its goals of maintaining appropriate level of inventory and minimizing waste . A web-
based system of managing inventory in a company setting is expected to help various
facilities keep an update on the status of their tools and equipment . In this study ,a model is
presented for putting an online supply inventory system in place in different of Punjab ,Buraq
Computers. In designing such a system ,PHP has been employed as a development language
and MySQL as a backend database with CSS implemented for the interface. Two screen-
shots have been illustrated to offer a glimpse of the proposed web-based system and its
applications.

This online supply inventory system would help the person charge of the supply office
find out the capacity of the supplies as well as there information of asset availability, and
replacement of asset documentation holding a key foran organization like company to gaining
competitive advantage through efficient operational performance.

Abstract
The purpose of Online Food Ordering System is to automate the existing manual system
by the help of computerized equipment’s and full-fledged computer software, fulfilling their
requirements, so that their valuable data/information can be stored for a longer period with easy
accessing and manipulation of the same. The required software and hardware are easily available
and easy to work with.

The Online Food Ordering System's main purpose is to maintain track of information
such as Item Category, Food, Delivery Address, Order, and Shopping Cart. It keeps track of
information about the Item Category, the Customer, the Shopping Cart, and the Item Category.
Only the administrator gets access to the project because it is totally built at the administrative
level. The project's purpose is to develop software that will cut down on the time spent manually
managing Item Category, Food, Customer, and Delivery Address. It saves the Delivery Address,
Order, and Shopping Cart information.
Contents
Introduction.................................................................................................................................................9
Justification & Feasibility:............................................................................................................................9
Justification..............................................................................................................................................9
Feasibility...................................................................................................................................................10
Problem Statement:..................................................................................................................................10
Anticipated Benefits:...............................................................................................................................11
Requirements:...........................................................................................................................................11
User Requirements :..................................................................................................................................11
User Interface Requirements:...................................................................................................................11
Goals Scenarios & Use Cases.....................................................................................................................12
Goal 1:...................................................................................................................................................12
Goal 2:...................................................................................................................................................12
Goal 3:...................................................................................................................................................12
Goal 4:...................................................................................................................................................12
Identify Actors:..........................................................................................................................................13
Initial Use Case Diagram:...........................................................................................................................13
System Model:...........................................................................................................................................15
Functional Requirements:.........................................................................................................................15
The Web Ordering System:........................................................................................................................16
Menu Management System:.....................................................................................................................16
Order Retrieval System:.............................................................................................................................17
User Interface Specifications:....................................................................................................................17
Web Ordering System:..............................................................................................................................17
Menu Management System:.....................................................................................................................17
Order Retrieval System:.............................................................................................................................17
Non-functional Requirements:..................................................................................................................18
System Evolution:......................................................................................................................................18
System Design:..........................................................................................................................................19
Level 1: The Database & the 3 Components:.........................................................................................19
Level 2: Web Ordering System Components:........................................................................................19
Level 3: The Login Form:........................................................................................................................20
Level 3: The Main Menu:.......................................................................................................................20
Level 3: The Account Management Form:.............................................................................................21
 Level 3: The Order Form:.......................................................................................................................21
Level 3: The Shopping Cart:...................................................................................................................21
Level 3: The Checkout Form:.................................................................................................................21
Level 2: Menu Management System Components:...................................................................................21
System Design Model................................................................................................................................22
Admin workflow Process...........................................................................................................................23
Customer Workflow Process.....................................................................................................................24
Diagram.....................................................................................................................................................25
Schema Diagram....................................................................................................................................25
E-R Diagram...............................................................................................................................................26
Database Design........................................................................................................................................27
Table..........................................................................................................................................................27
Table Creation...........................................................................................................................................28
System Implementation Plan.................................................................................................................35
Project Planning.........................................................................................................................................35
Facing Problem During Development the Project.....................................................................................36
Final Output...............................................................................................................................................38
Result & Discussion...................................................................................................................................39
Application................................................................................................................................................39
Advantages................................................................................................................................................40
Limitations of the System..........................................................................................................................40
Conclusion & Future Work........................................................................................................................41
Conclusion.................................................................................................................................................41
Future Work..............................................................................................................................................42
REFERENCE................................................................................................................................................43
Introduction:
In this era of revolutions the development of technology has provided seamless luxuries of life
for human being. But if we take a closer look, we realize that at the same time it also has
increased the duration of busy hours for humans. Exhausted of routine’s work at offices,
everyone thinks about some source of refreshment and joy.
Restaurants are on top of the list while thinking about such type of refreshment. Our beautiful
city Bahawalpur is rich of luxurious and Rich-in taste restaurants. There is no shortage of luxury
hotels. Only thing which is short is; Time.
This project is intended to provide one platform; and online platform, for all the citizens. So that
they can enjoy the cuisines and hot deals of popular restaurants at their door steps as well as be
able to book/reserve the tables for them and their loved ones from anywhere in the Pakistan.
Moreover citizens from anywhere in Pakistan will also be able to send beautiful surprises for
their loved ones who are living in Bahawalpur.
User/Customers will sign up for the first time so that to give his/her particulars. And then he/she
will be able to order any item from provided cuisines. The customer from Bahawalpur will pay
on-delivery basis. However one who is outside of Bahawalpur and wants to send a surprise deal
for his/her loved one; he/she have to pay online via his/her credit card.

Justification & Feasibility:

Justification:
In today’s age of fast food and take-out, many restaurants 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 over the phone, but there are many
disadvantages to this system. First, the customer must have a physical copy of the restaurant’s
menu to look at while placing their order and this menu must be up to date. While this
expectation is not unreasonable, it is certainly inconvenient.
Second, the orders are placed using strictly oral communication, which makes it far more
difficult for the customer to receive immediate feedback on the order they have placed. This
often leads to confusion and incorrect orders. The current system is also inconvenient for the
restaurant itself, as they must either have a dedicated staff member to answer the phone and take
orders, or some employees must perform double-duty, distracting them from their regular tasks.
What I propose is an online ordering system, originally designed for use in college
cafeterias, but just as applicable in any food delivery industry. The main advantage of my system
is that it greatly simplifies the ordering process for both the customer and the restaurant. 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.
The system also greatly lightens the load on the restaurant’s end, as the entire process of
taking orders is automated. Once an order is placed on the webpage, it is placed into the database
and then retrieved, in pretty much real-time, by a desktop application on the restaurant’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 restaurant
employees to quickly go through the orders as they are placed and produce the necessary items
with minimal delay and confusion.
While there are already a few systems like this in existence, all those I have encountered
have been designed specifically for one restaurant, and thus cater only to their unique needs.
Perhaps the greatest advantage of my system is its flexibility. The web order forms are built
dynamically from the database, which can be managed using a graphical user interface. This
allows the restaurant employees to not only set up and customize the system on their own, but
also allows them to make changes to the menu in real time. For this reason, the exact same
system can be used by numerous businesses with absolutely no modification to the code itself,
which greatly increases its usefulness.

Feasibility:
At the present moment, the system is entirely functional, save the few minor bugs which
are bound to present themselves during more extensive testing. A user is currently able to
register and log in to the website and place an order. That order is then displayed, correctly and
completely, in the order retrieval desktop application. Much of what is left to do focuses not on
improving functionality, but rather on improving user experience by creating richer graphical
interfaces for the user to interact with and modifying the application’s icons and color schemes
to make them more pleasing to look at and use. For this reason, I feel that completing the project
in the required timeframe is very feasible, particularly if I am able to adhere to the dates outlined
in Figure 1, below.
In addition to time, a second factor influencing feasibility is resources, which also should
not be a concern here. The online ordering system is structured like a fairly standard web
application, and as such requires no special hardware and only basic software, namely web and
database servers, to function properly. Therefore, I anticipate finishing all of the required work
on time or, ideally, ahead of schedule, leaving me with time to investigate a few additional
features I would like to add but are not integral to the system.

Problem Statement:
Citizens of Bahawalpur City are mostly government employees and others are doing jobs in
other private fields. These citizens have a very short time for their entertainment activities. Most
of them curb their joy impulse just because of time limitations. The main intention of this
project; that’s why is to grab their happiness in much less time, so that they don’t miss a single
moment of happiness in their life.

As hoteling is the best source of joy and enjoyment. This project will provide them a robust and
user-friendly platform for meeting their requirements in a best way, and thus providing them all
the wonderful facilities at their door step.

Every fast food has counter where you can place your order and then make the payment. So
every fast food needs an employee for taking the order and processing the payment. Labor rates
are increasing every now and then and it is difficult to find employees in the middle of the
highway, hence to solve this problem we plan to design a "Self Served Fast Food System.

This self-service fast food restaurant will be equipped with a user-friendly touch screen, a
credit/debit card reader, and software for completing the process at the backend. For this system
there will be a system administrator who will have the rights to enter the menu with their current
prevailing prices. He/she can enter anytime in the system by a secured system password to
change the menu contents by adding or deleting an item or changing its price.

Now when the customer enters the Web Site, he will place his order with the intuitive graphical
user interface. He will select from the food options according to his choice and the system will
display the payment amount he has to pay
Anticipated Benefits:
• This will minimize the number of employees at the back of the counter.
• The system will help to reduce the cost of labor.
• The system will be less probable to make mistake, since it?s a machine.
• This will avoid long queues at the counter due to the speed of execution and number of
optimum screens to accommodate the maximum throughput.
• The system will be available 24 hours for 365 days, because the machine is not going to
take any sick or vacation leave.

Requirements:

These are requirements for which this system is developed in order to fulfill them

User Requirements :
• User should be able to navigate the system without any difficulty.
• System supports native language of the country and other commonly spoken languages.
• User should be able to place order according to his choices
• User should be able to make payment using cash/credit/debit card.
• User should get a receipt and a token number after making the payment.
Performance Requirements :
• The system should be able to take any type of inputs, once the mouse is clicked on the
respective button.
• The system should be able to take specific amount of order and display it when finished.
• The system should be able to pass on the order in the kitchen for processing.
• The system should be secured to restrict the number of people to enter the system to
make changes in the menu and its items.
• The system should be sturdy for rough usage.
• System should allow Store manager to add/delete/alter system items.

User Interface Requirements:

• The system must be a graphical user interface for easy use and understanding.
• The system must be able to prompt the user for the next step to be performed during the
process of using the system.
Goals Scenarios & Use Cases
Different scenarios with goals are given below. Which shows how the above requirements
can be achieved?

Goal 1:
The system has a user-friendly user interface.

• Scenario 1.1. A particular user of the system has no difficulty in reading the text on the
display.
• Scenario 1.2. The system is navigable through intuition.
• Scenario 1.3. Menu choices are presented in form of buttons, which contain text as well
as little pictures illustrating the choice for better understanding.

Goal 2:
System takes order from the customer as per his/her choice.

• Scenario 3.1. User selects a combo deal (i.e. a combination of main food, drink and side
dish).
• Scenario 3.2. User may want to make up his own order by selecting dishes.

Goal 3:
System offers the choice to change the menu items to the store manager.

• Scenario 6.1. Store manager decides to add / delete an item from the menu.
• Scenario 6.2. Store manager wants to put festive offers on some items because of which
there is a change in the price of some of the items.
• Scenario 6.3. Store manager notices that some dishes are out of stock. Consequently he
updates the menu so that those items are deleted temporarily deleted from the display
presented to the user.

Goal 4:
The system is resistant to active/rigorous handling.

• Scenario 7.1. The customer must be a minor or hacker who might want to get into the
system to change it. It should provide security for these areas.
• Scenario 7.2. The system will be used by different users and might experience some
rough hand every now and then.
Identify Actors:

An actor is anything that interfaces with the system externally and participates in use case
modeling. In our Self Served Fast Food System the actors would be:

• Customer. This actor is the principle customer who will order food and make the
payment.
• Store Manager. This actor will hold the rights to change the menu and enter the system
to make any changes.
• Internal Order System. This actor will read the order given by the customer and pass it
to the food preparation person.
• Bank System. This actor serve as a backbone for doing the credit / debit card transaction.
• Cash Collector. This actor will accept the cash from the customer and gives back the
change.
• Food Preparation Person. This person receives the order placed by the customer
through internal order system.

Initial Use Case Diagram:

A use case describes a single goal and all the things that can happen as the user attempts to reach
that goal. Use cases are textual description of the interaction between external actors and a
system.
As you can see (in the diagram given below) that the Customer places the order, which is read by
the internal order system and the order is then sent to the food preparation person for execution.
In the meantime the customer makes the payment. If the payment is made in cash there is a cash
collector actor or there is a bank system for credit/debit card processing and keeping the balance
cash amount.
System Model:

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.

Functional Requirements:
As can be seen in the system model diagramed above, each of the three system components
essentially provides a layer of isolation between the end user and the database. The motivation
behind this isolation is twofold. Firstly, allowing the end user to interact with the system through
a rich interface provide a much more enjoyable user experience, particularly for the non-
technical users which will account for the majority of the system’s users. In addition, this
isolation layer also protects the integrity of the database by preventing users from taking any
action outside those which the system is designed to handle. Because of this design pattern, it is
essential to enumerate exactly which functions a user will be presented and these functions are
outlined below, grouped by component.
The Web Ordering System:
Users of the web ordering system, namely restaurant customers, must be provided the
following functionality:
• Create an account.
• Manage their account.
• Log in to the system.
• Navigate the restaurant’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.
• Provide delivery and payment details.
• Place an order.
• Receive confirmation in the form of an order number.

As the goal of the system is to make the process of placing an order as simple as possible
for the customer, the functionality provided through the web ordering system is restricted to that
which most pertinent to accomplish the desired task. All of the functions outlined above, with the
exceptions of account creation and management, will be used every time a customer places an
order. By not including extraneous functions, I am moving towards my goal of simplifying the
ordering process.

Menu Management System:

The menu management system will be available only to restaurant employees and will, as the
name suggests, allow them to manage the menu that is displayed to users of the web ordering
system. The functions afforded by the menu management system provide user with the ability to,
using a graphical interface:

• Add a new/update/delete vendor to/from the menu.

• Add a new/update/delete food category to/from the menu.
• Add a new/update/delete food item to/from the menu.
• Add a new/update/delete option for a given food item.
• Update price for a given food item.
• Update default options for a given food item.
• Update additional information (description, photo, etc.) for a given food item.

It is anticipated that the functionality provided by this component will be one of the first
things noted by the restaurant user, as they will have to go through it to configure their menu,
etc. before beginning to actually take orders. Once everything is initially configured, however,
this component will likely be the least used, as menu updates generally do not occur with great
frequency.
Order Retrieval System:
Of the three components, the order retrieval system is functionally the simplest. Like the menu
management system, it is designed to be used only by restaurant employees, and provides the
following functions:
• Retrieve new orders from the database.
• Display the orders in an easily readable, graphical way.
• Mark an order as having been processed and remove it from the list of active orders.

User Interface Specifications:

Each of the system components will have their own unique interface. These are described below.

Web Ordering System:

Users of the web ordering system will interact with the application through a series of simple
forms. Each category of food has its own form associated with it which presents a drop down
menu for choosing which specific item from the category should be added to the order, and a
series of check boxes and radio buttons for selecting which options are to be included. Adding an
item to the order is accomplished by a single button click. Users select which category of food
they would like to order, and therefore which form should be displayed, by navigating a menu
bar, an approach which should be familiar to most users.
Entering delivery and payment deals is done in a similar manner. The user is presented with a
form and must complete the required fields, which include both drop down and text boxes,
before checking out and receiving a confirmation number. One thing worth noting here is that
whenever possible drop down boxes and buttons were used over freeform input in order to both
simplify the ordering process and reduce the possibility of and SQL injection attempt.

Menu Management System:

User interaction with the menu management system is similar to that with the web ordering
system. Users navigate a tree structure to find the vendor, category, or specific food item that
they would like to modify and after making their selection they are presented with a form which
displays all of the current fields and values associated with that item, all of which can be
modified or removed. The form also presents buttons which allow the addition of new fields and
values. Unlike the web ordering system, however, most of the input here will be freeform,
specifically in the form of text boxes, since there is no finite set of fields which could be added.
This does not raise a major concern though, as input sanitation will be performed, and the user,
who is assumed to be a restaurant employee, is less likely to be malicious than a web user.

Order Retrieval System:

User interaction with the order retrieval will be very simple. The application will automatically
fetch new orders from the database at regular intervals and display the order numbers, along with
delivery time, in a panel on the left hand side of the application
To view the details of an order, the user must simply click on that order number, which will
populate the right-hand panel with the details, displayed in an easy to read and navigate tree
structure. This structure can intuitively be expanded and collapsed to display only the desired
information. Finally, once and order is processed, the user clicks a single button, labeled
“Processed”, to remove it from the list of active orders.

Non-functional Requirements:
Because the design patterns of the Online Ordering System are pretty much the standard for a
web application, the non-functional requirements of the system are very straightforward.
Although written using Google Web Toolkit, the application is cross-compiled to HTML and
JavaScript, along with a PHP backend, all of which are supported by any reasonably well
maintained web server, although I would recommend Apache2, and particularly the free XAMPP
distribution.

All of the application data is stored in a Posture SQL database, and therefore a PostgreSQL
server must also be installed on the host computer. As with Apache2, this software is freely
available and can be installed and run under most operating systems.

The server hardware can be any computer capable of running both the web and database servers
and handling the expected traffic. For a restaurant that is not expecting to see much web traffic,
or possibly doing only a limited test run, an average personal computer may be appropriate.
Once the site starts generating more hits, though, it will likely be necessary to upgrade to a
dedicated host to ensure proper performance. The exact cutoffs will need to be determined
through a more thorough stress testing of the system.

System Evolution:
As mentioned in the system model, at the heart of the entire ordering system is the database. In
fact, the system could be completely operational using nothing but the database and an
appropriate shell utility, assuming that all users are well-versed in SQL and enjoy using it to
order food. While this would be a bit extreme, it does illustrate the point that the one part of the
system which will stay relatively constant is the database.

On the other hand, it is very probable that the other components will continue to evolve with
time. For example, with the booming popularity of mobile applications, I would really like to
make the web interface available as a phone application as well. Also it may make sense to at
some point migrate the menu management and order retrieval systems to web, or even mobile,
applications as well, as some users may prefer to use them as such.

I am also certain that if this system goes into actual use, many requests will arise for additional
features which I had not previously considered, but would be useful to have. For this reason, I
feel as though the application can be constantly evolving, which I consider a very good thing.
System Design:

Level 1: The Database & the 3 Components:

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.

Level 2: Web Ordering System Components:

The web ordering system is comprised of 6 major components. These are the login form,
the main menu, the account management form, the order form, the shopping cart, and the
checkout form. When the customer first arrives at the site, they are presented with the login
form. After either signing in or, if they do not yet have an account, first registering and then
signing in, the user is taken to a welcome page with the main menu. From here, they have two
options – they can either change their password and other preferences through the account
management form, or they can select an order form and begin adding items to their order. If they
choose the second path, they can navigate the numerous order forms using the main menu, each
of which corresponds to a specific category of order items, adding items to their shopping cart
along the way. At any time they can view and modify their shopping cart and when they are
finally ready to place their order, they can proceed to the checkout form. The checkout form uses
the contents of the shopping cart to present a summary of the order and to calculate the total cost,
in addition to allowing the user to specify all of the necessary delivery details.
Level 3: The Login Form:

The login form is standard for a form of this type. It provides text fields for username and
password, which the user must enter before signing in. This form also gives the option for a user
to register for the site if they have not yet done so.

Level 3: The Main Menu:

The main menu, found at the top of the screen like in most applications, presents the user
with two levels of selections. They must first choose the vendor they would like to view and then
choose a category of food. Once they make these two selections, the application generates an
order form specifically for that type of food, and displays this form to the user.
Level 3: The Account Management Form:

Currently the account management form only offers the user the option to change their
password.

Level 3: The Order Form:

The order form, which is dynamically generated based on selections from the main menu.

Level 3: The Shopping Cart:

The shopping cart performs much like a shopping cart in any other application. After an
item is added to the order, it is displayed, along with its price, in the shopping cart. The shopping
cart also keeps a running total of the current price of the whole order. By clicking on an item in
the shopping cart, the user can review all of the details for that particular item. Finally, the
shopping cart contains a button for the user to proceed to checkout.

Level 3: The Checkout Form:

The checkout form is the user’s last chance to verify that the contents of their order are
correct before actually placing it. This form also provides fields for the user to supply all of the
necessary checkout and delivery details (payment type, delivery address, etc.).

Level 2: Menu Management System Components:

In order to make use of the menu management system, the user must interact with the
navigation tree, which uses a hierarchical tree structure to display all of the vendors, categories
of foods, and specific food items stored in the system. When the user selects an item from this
tree, they are able to edit the item using the appropriate form – a Vendor Form if a vendor is
selected, a Category Form if a category of foods is selected, and a Food Form if an individual
food item is selected.
System Design Model

Figure : System Model Design

 Admin workflow Process
User goes to home page of the domain. If he/she has an account then he/she can login in
restaurant management system otherwise he/she need to register an account after successful
registration, they can login in home page.

Figure: Admin workflow Process

Customer Workflow Process
Initially to visit the food categories or food menu, users don’t need to login/register an account.
After checking out the categories and menu items, if the user finds his/her desired menu and if
they want to order that particular item they can go to order page. During placing any order the
customer needs to provide his/her required information mentioned the order section.

Figure: Customer Workflow Process

Diagram

Schema Diagram

Figure : Schema Diagram.

E-R Diagram

Figure : E-R Diagram

Database Design
Database design is the management of information using a database paradigm. What data must
be saved and how the various data items interact are determined by the database design that
follows. Developer would start adjusting the data to the database model using this knowledge.
Data classification and relationship discovery are key components of database design.

Table

tbl_admin Table

id full_name username password

tbl_category Table
category_id category_title image_name feature active

tbl_food Table
food_id food_title description price img_name cat_id feature active

tbl_order
order food Cat price qty total date status cust_ cust cust cust
_id _title _id name _contact _address _email
 Table Creation

tbl_admin Table

CREATE TABLE `tbl_admin` (

`id` int(10) UNSIGNED NOT NULL,

`full_name` varchar(100) NOT NULL,

`username` varchar(100) NOT NULL,

`password` varchar(255) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

//add value & table type

INSERT INTO `tbl_admin` (`id`, `full_name`, `username`, `password`) VALUES
(1, 'Steeve Moore', 'steeve', 'E10ADC3949BA59ABBE56E057F20F883E'), (9,
'Liam Johnson', 'liam', 'E10ADC3949BA59ABBE56E057F20F883E'),

(10, 'Ramsey', 'ramsey', 'E10ADC3949BA59ABBE56E057F20F883E'),

(12, 'Administrator', 'admin', 'E10ADC3949BA59ABBE56E057F20F883E');

tbl_category Table
CREATE TABLE `tbl_category` (

`id` int(10) UNSIGNED NOT NULL,

`title` varchar(100) NOT NULL,

`image_name` varchar(255) NOT NULL,

`featured` varchar(10) NOT NULL,

`active` varchar(10) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

// add value & table type
INSERT INTO `tbl_category` (`id`, `title`, `image_name`, `featured`, `active`)
VALUES (4, 'Pizza', 'Food_Category_790.jpg', 'Yes', 'Yes'), (5, 'Burger',
'Food_Category_344.jpg', 'Yes', 'Yes'),

(9, 'Wraps', 'Food_Category_374.jpg', 'Yes', 'Yes'),

(10, 'Pasta', 'Food_Category_948.jpg', 'Yes', 'Yes'),

(11, 'Sandwich', 'Food_Category_536.jpg', 'Yes', 'Yes');

tbl_food Table
CREATE TABLE `tbl_food` (

`id` int(10) UNSIGNED NOT NULL,

`title` varchar(100) NOT NULL,

`description` text NOT NULL,

`price` decimal(10,2) NOT NULL,

`image_name` varchar(255) NOT NULL,

`category_id` int(10) UNSIGNED NOT NULL,

`featured` varchar(10) NOT NULL,

`active` varchar(10) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

//add value & table type

INSERT INTO `tbl_food` (`id`, `title`, `description`, `price`, `image_name`, `category_id`,

`featured`, `active`) VALUES

(4, 'Ham Burger', 'Burger with Ham, Pineapple and lots of Cheese.', '4.00', 'Food-Name-
6340.jpg', 5, 'Yes', 'Yes'),

(5, 'Smoky BBQ Pizza', 'Best Firewood Pizza in Town.', '9.00', 'Food-Name-8298.jpg', 4, 'No',
'Yes'),

(9, 'Chicken Wrap', 'Crispy flour tortilla loaded with juicy chicken, bacon, lettuce, avocado and
cheese drizzled with a delicious spicy Ranch dressing.', '5.00', 'Food-Name-3461.jpg', 9, 'Yes',
'Yes'),

(10, 'Cheeseburger', 'A cheeseburger is a hamburger topped with cheese. Traditionally, the slice

of cheese is placed on top of the meat patty.', '4.00', 'Food-Name-433.jpeg', 5, 'Yes', 'Yes'),

(11, 'Grilled Cheese Sandwich', 'Assembled by creating a cheese filling, often cheddar or

American between two slices of bread and is then heated until the bread browns and cheese

melts.', '3.00', 'Food-Name-3631.jpg', 11, 'Yes', 'Yes');

 tbl_order Table

CREATE TABLE `tbl_order` (

`id` int(10) UNSIGNED NOT NULL,

`food` varchar(150) NOT NULL,

`price` decimal(10,2) NOT NULL,

`qty` int(11) NOT NULL,

`total` decimal(10,2) NOT NULL,

`order_date` datetime NOT NULL,

`status` varchar(50) NOT NULL,

`customer_name` varchar(150) NOT NULL,

`customer_contact` varchar(20) NOT NULL,

`customer_email` varchar(150) NOT NULL,

`customer_address` varchar(255) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

//add value & table type

INSERT INTO `tbl_order` (`id`, `food`, `price`, `qty`, `total`, `order_date`, `status`,
`customer_name`, `customer_contact`, `customer_email`, `customer_address`) VALUES

(2, 'Best Burger', '4.00', 4, '16.00', '2020-11-30 03:52:43', 'Delivered', 'Kelly Dillard',
'7896547800', 'kelly@gmail.com', '308 Post Avenue'),

(3, 'Mixed Pizza', '10.00', 2, '20.00', '2020-11-30 04:07:17', 'Delivered', 'Thomas Gilchrist',
'7410001450', 'thom@gmail.com', '1277 Sunburst Drive'),

(4, 'Mixed Pizza', '10.00', 1, '10.00', '2021-05-04 01:35:34', 'Delivered', 'Martha Woods',
'78540001200', 'marthagmail.com', '478 Avenue Street'),

(6, 'Chicken Wrap', '7.00', 1, '7.00', '2021-07-20 06:10:37', 'Delivered', 'Charlie', '7458965550',
'charlie@gmail.com', '3140 Bartlett Avenue'),

(7, 'Cheeseburger', '4.00', 2, '8.00', '2021-07-20 06:40:21', 'On Delivery', 'Claudia Hedley',
'7451114400', 'hedley@gmail.com', '1119 Kinney Street'),
(8, 'Smoky BBQ Pizza', '6.00', 1, '6.00', '2021-07-20 06:40:57', 'Ordered', 'Vernon Vargas',
'7414744440', 'venno@gmail.com', '1234 Hazelwood Avenue'),

(9, 'Chicken Wrap', '5.00', 4, '20.00', '2021-07-20 07:06:06', 'Cancelled', 'Carlos Grayson',
'7401456980', 'carlos@gmail.com', '2969 Hartland Avenue'),

(10, 'Grilled Cheese Sandwich', '3.00', 4, '12.00', '2021-07-20 07:11:06', 'Delivered', 'Jonathan
Caudill', '7410256996', 'jonathan@gmail.com', '1959 Limer Street');
ANALYSIS RESULT & DISCUSSION

System Implementation Plan

A software design pattern called Model View Controller, or MVC as it is more formally
known, is used to build online applications. There are three components to the Model View
Controller pattern:

• Model - The lowest level of the pattern, is in charge of maintaining the data.

• View - This is in charge of showing the user all or part of the data.

• Controller - The computer program that controls how the Model and View interact.
MVC is well-liked because it provides for duty separation by separating the application
logic and user interface layers. The Controller accepts all requests from the application
and collaborates with the Model to prepare any necessary data for the View. The View
then constructs a final presentable response using the data produced by the Controller.
The following is a graphic representation of the MVC abstraction. Model of MVC
(Model View Controller Flow)

Project Planning

Here is an illustration of a software project plan: 1) How will the project be carried out within
the company? What are the time, financial, and human resource limitations? What does having
a market strategy entail? 2) Customer meetings: Weekly or as needed customer meetings that
include a progress report presentation. Additionally taking into account customer input,
adjustments and changes are made as necessary. The client is also shown project deliverables
and milestones.
The steps listed below can be used to create successful software projects:

Select a project. The aims and objectives of project are as follows:

• Understanding specifications and requirements.

• Using analysis, design, and implementation methods.

• Using testing procedures.

• Documenting.

• Budget allocation or exceeding limits under control.

• Understanding project milestones and deliverables

• Project estimates.

• Cost and Time.

Facing Problem During Development the Project

During the construction of the web application "Online Food Order," the developer ran into a
few issues. Here are a few issues in brief:

Requirement Gathering Phase: It is a crucial step. The project will fail if the
requirements are poor. At that time, developer became disappointed when
Developer was collecting information and data then what information and data

will be helpful or appropriate for this project.

During Design Phase: At this moment, the developer struggled to decide which
flowchart would be best for this project when creating it.

Development Phase: It is a very major component of the undertaking. Frequently,

the developer misplaced the semicolon (;) at the conclusion of the statement.
Testing Phase: It is an essential component of the project. This section will aid
with project testing overall. During testing, developer has faced some bugs of the
project.
Final Output
 Result & Discussion
The final output is a complete web based Restaurant Management System, which can be used in
any kind of restaurant. This Restaurant Management System can help to manage the Restaurant
more effectively, efficiently and smoothly. This is more secured and there will be speedy and
well ordered authentication procedure for the maintenance of records. At present time, in this
technology based world, people likes and wants everything to be smooth and efficient through
the use of data and information. In this perspective, our Restaurant Management System can be
an ideal platform for the users. Its user friendly interface can help the customers to find his/her
desired menu item and place order with a few click. Customers can easily place an online order
by browsing the menu options, pick what they want sitting at home. And can also receive their
food in a short period of time.

Application

Restaurants, takeaways, and businesses that sell food to go profit from internet meal ordering software
designed specifically for them. Customers like the ease of online meal ordering, which is why it is
expanding quickly. Expand your sales channels by downloading our online food ordering application.

Through this food ordering website, customers may place orders from their computers, tablets, and
cellphones. They can look through your menu options, choose what they want, and submit an order online.
Internet-based payment will also be accepted. Meals can be picked up in person or delivered to customers.

There are many benefits to using an online food ordering app or a restaurant ordering app, including
reduced labor expenses, fewer walk-away customers, and shorter wait times. This restaurant's online
ordering system is intended for independent and multi-location chains that offer food to go, including
eateries, fast food outlets, take-out, and other catering services.

Putting your company online will enable you to generate a lot more revenue, which will enhance your
marketability. Your online menu will give current clients a terrific new option to

place orders, and new customers will easily find you thanks to well-known search engines.
To complement the style and feel of your present website, the system is tailored. In the
digital age, we help business owners grow their enterprises.
Advantages

• It is quick, simple, and pleasant.

• Managing an online menu is easier.

• Access is only a click away.

• Less work for you.

Limitations of the System

The system has certain other restrictions as well. There are only a few basic functions in the
system's shopping cart, and it cannot be extensively customized. Additionally, practically all of
the functionality of the application, including validation, is handled by server-side programming.
It increases the server's workload, especially when a large number of users access the program.
This issue can be resolved by using client-side languages, such as JavaScript or HTML 5, to
check data. Additionally, the order model has been created.
Conclusion & Future Work

Conclusion

Restaurant Management System is a web-based technology that aids the restaurant industry in
carrying out tasks effectively and efficiently. It aids in managing cash flow for managers.
Managers can view analytics data to assess company growth. The manager can control orders
and employee schedules by using this system. The full complement is a restaurant management
system. It provides access to the Online Order platform, third-party connectors software, and
comprehensive CRM solution, which together cover a sizable portion of your restaurant's
requirements. They are not the outdated hardware and software sets for restaurants that were
previously offered. They are the hottest things around, smooth, manageable, inexpensive, and
quick.

In the "Online Food Ordering Project," we made every effort to meet all the demands of the
restaurant. Because it is straightforward and adaptable, the project is successful. The biggest benefit
of my project is that it draws plenty of users because of its simplicity. A novice user may operate it
with ease. Any type of restaurant can utilize our software. By automating meal ordering, billing, and
inventory control, the restaurant management system assists the restaurant manager in managing the
restaurant more successfully and efficiently. The system handles the transaction and stores the data
produced. These data will be used to create reports that assist the restaurant manager in making wise
business decisions. For example, the manager can decide whether more waiters, delivery men,
delivery carts, and cooks are needed based on how many clients will be present during a specific time
period. When this project is finished, all security concerns will be resolved. Additionally, a quick and
secure authentication process will be used for record maintenance. Because it automatically pulls
information about a consumer from the database on subsequent visits, data entry is quick and easy.
As a result, our program will undoubtedly succeed in replacing the antiquated manual way of storing
secure information. The work plan also specifies the specific

front end and back end characteristics of the technology being used in the project. Future project
goals and its scope have been elaborated.
 Future Work

Each project should pay close attention to future development because it contains the system's
most recent features. It lessens software issues and defects. It develops a close relationship with
customers based on their comments or preferences. Developer will incorporate certain dynamic
elements that are briefly described below into my restaurant management system. Reporting
module with real time mechanism.

• Modern architecture with smooth transitions.

• System for email and mobile confirmation.

• Selling Point
REFERENCE

[1] Kirti Bhandge, Tejas Shinde, Dheeraj Ingale, Neeraj Solanki, Reshma Totare,”A Proposed
System for Touchpad Based Food Ordering System Using Android Application”, International

Journal of Advanced Research in Computer Science Technology (IJARCST 2015).

[2] Varsha Chavan, Priya Jadhav,Snehal Korade,Priyanka Teli, ”Implementing Customizable Online
Food Ordering System Using Web Based Application”, International Journal of Innovative
[3] Resham Shinde, Priyanka Thakare, Neha Dhomne, Sushmita Sarkar, ”Design and
Implementation of Digital dining in Restaurants using Android”, International Journal of Advance
[4] Ashutosh Bhargave, Niranjan Jadhav, Apurva Joshi, Prachi Oke, S. R Lahane,“Digital
Ordering System for Restaurant Using Android”, International Journal of Scientific and Research
[5] Khairunnisa K., Ayob J., Mohd. Helmy A. Wahab, M. Erdi Ayob, M. Izwan Ayob, M. Afif
Ayob, ”The Application of Wireless Food Ordering System” MASAUM Journal of Computing

2009.
[6] Noor Azah Samsudin, Shamsul Kamal Ahmad Khalid, Mohd Fikry Akmal Mohd Kohar,

Zulkifli Senin, Mohd Nor Ihkasan,” A customizable wireless food ordering system with real time
customer feedback”, IEEE Symposium on Wireless Technology and Applications(ISWTA) 2011.

[7] Serhat Murat Alagoza, Haluk Hekimoglub,” A study on tam: analysis of customer attitudes in
online food ordering system”, Elsevier Ltd. 2012.

[8] Patel Krishna, Patel Palak, Raj Nirali, Patel Lalit,” Automated Food Ordering System”,

International Journal of Engineering Research and Development (IJERD) 2015.

[9] Mayur D. Jakhete, Piyush C. Mankar,” Implementation of Smart Restaurant with e-menu
Card,” International Journal of Computer Applications 2015 of Smart Restaurant with e-menu
[10] Abhishek Singh, Adithya R, Vaishnav Kanade, Prof. Salma Pathan“ ONLINE FOOD
ORDERING SYSTEM” International Research Journal of Engineering and Technology (IRJET)
2018.
 [11] Gleditsch, N. P., Pinker, S., Thayer, B. A., Levy, J. S., & Thompson, W. R. (2013). The
forum:

[12] Data Analysis. International Data Analysis Review, 15(3), 396-419.

[13] Google for problem solving.

[14] https://www.slideshare.net/

[15] Database Programming with JDBC and Java by O'Reilly

[16] Head First Java 2nd Edition