Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 35

Cover Page

DESIGN AND IMPLEMENTATION OF FOOD ORDERING MANAGEMENT SYSTEM


A CASE STUDY OF NIHARI FOOD COURT

BY

GROUP 18A

FEBRUARY, 2021
DECLARATION

We, [Names] , hereby declare that this project report entitled “Design and Implementation of

online food ordering Management System" is a record of project work undertaken by us. That it

has not been submitted elsewhere for the award of Diploma or degree. That we have duly

acknowledged all source of materials Consulted and included in this report.

_____________________ __________________
[Names] DATE

_____________________ __________________
[Names] DATE

____________________ __________________
[Names] DATE

____________________ __________________
[Names] DATE

____________________ __________________
[Names] DATE

_______________________ ___________________
[Names] DATE

ii
CERTIFICATION

This project titled "Online food ordering management system meets the regulations governing

the award of Diploma in computer Science and is approved for its contribution to knowledge and

literary presentation.

________________________ _________________ ___________________


Project Supervisor Signature DATE

_______________________ __________________ ____________________


Head ITA Signature DATE

______________________ ___________________ ____________________


Project Chairman Signature DATE

_____________________ ____________________ _____________________


Director ICICT Signature DATE

iii
DEDICATION

We wish to dedicate this entire project report to our beloved parent for their tireless support they

accorded to us ever since we were children. We thank them for the spirit of hard work, courage

and determination they had instilled in us throughout our school days till today. We also honour

and owe our dear sisters and brothers for the happiness and appreciation for the guidance

protection and financial support they offered us. And also, other community members here in

institute (lecturer, staff and course-mates).

iv
ACKNOWLEDGEMENT

We would like to express our thanks to the Almighty God for the gift of life, wisdom and

understanding he had given to us, a reason for our existence. And to our families for the love and

support they had provided throughout our life. We also thank Nihari Food Court Management,

having given their time during our system study and analysis stage, they had been particularly

helpful in providing the necessary data about the existing system. Special thanks go to our

mentors and supervisors, we thank him for the expertise and intelligence that they display while

supervising this project. We believe this good work is result of his good guidance and

cooperation. We would like to convey our gratitude to the lecturers in the institute for the good

job done during the 2 years period of our course. May the good lord bless them and keep them

safe. We love you all.

v
ABSTRACT

This project is about designing and implementing of Food Ordering management system for
Nihari Food Court. To develop the system, the existing manual method was studied using
interview method and Document review, thereby identifying the challenges associated with the
existing system. The activities of the proposed Food ordering management system were defines
using data flow diagram. Then the design of the proposed system was develop using multiple
programming languages such as: HTML, JavaScript, PHP, CSS.

vi
TABLE OF CONTENTS

Cover Page....................................................................................................................................................i
DECLARATION..............................................................................................................................................ii
CERTIFICATION...........................................................................................................................................iii
DEDICATION................................................................................................................................................iv
ACKNOWLEDGEMENT..................................................................................................................................v
ABSTRACT...................................................................................................................................................vi
TABLE OF CONTENTS..................................................................................................................................vii
CHAPTER ONE..............................................................................................................................................1
INTRODUCTION.......................................................................................................................................1
1.1 Background of the Study...................................................................................................................1
1.2 SIGNIFICANCE OF STUDY...................................................................................................................2
1.4 Aims and Objectives..........................................................................................................................3
1.5 METHODOLOGY.................................................................................................................................3
1.6 SCOPE AND LIMITATIONS..................................................................................................................4
1.7 Definition of Terms............................................................................................................................4
CHAPTER TWO.............................................................................................................................................5
LITERATURE REVIEW................................................................................................................................5
2.1 E-commerce System..........................................................................................................................5
1.2 Review of food ordering system........................................................................................................6
2.3 Review of related work......................................................................................................................7
2.4 Existing System..................................................................................................................................8
2.5 proposed System...............................................................................................................................8
CHAPTER THREE..........................................................................................................................................9
ANALYSIS, DESIGN AND IMPLEMENTATION................................................................................................9
3.1 SYSTEM ANALYSIS AND DESIGN.........................................................................................................9
3.2 Analysis Phase...................................................................................................................................9
3.2.1 Requirement Gathering................................................................................................................10
3.2.1.1 Data collected during the Interview Method.............................................................................10
3.2.1.2 Data Collected During the Document Review............................................................................10
3.3 Define the System............................................................................................................................11
3.3.1 Description of the Existing System................................................................................................11

vii
3.3.2 Weakness of the Existing system..................................................................................................11
3.3.3 Proposed System..........................................................................................................................11
3.4 System Modeling.............................................................................................................................11
3.4.1 Model of the Existing System........................................................................................................12
3.4.2 Model of the proposed system.....................................................................................................13
3.5 System Requirements......................................................................................................................14
3.5.1 System requirement of the proposed system...............................................................................14
3.6 SYSTEM DESIGN...............................................................................................................................15
3.6.2 Architecture Design......................................................................................................................16
3.7 Database design...............................................................................................................................17
3.7.1 Database Table.............................................................................................................................17
Table 3.1: Items Table Database table design.......................................................................................17
Table 3.2: Orders Database Table Design..............................................................................................18
Table 3.3: Order details Database Table Design...........................................................................18
Table 3.4: Users Database table design.................................................................................................19
Table 3.5: Wallet Database Table Design...............................................................................................19
3.7.2 Entity Relationship Diagram (ERD)................................................................................................20
3.8 Implementation...............................................................................................................................20
CHAPTER FOUR..........................................................................................................................................26
SUMMARY, RECOMMENDATION, AND CONCLUSION...............................................................................26
4.1 SUMMARY.......................................................................................................................................26
4.2 RECOMMENDATION........................................................................................................................26
4.3 CONCLUSION...................................................................................................................................26

viii
CHAPTER ONE

INTRODUCTION

1.0 Background of the Study

The online food ordering system is the latest servicers most fast food restaurants in the western

world are adopting (Purname, 2007). With this method, food is ordered online and delivered to

the customer. This is made possible through the use of electronic payment system. Customers

pay with their credit cards, although credit card customers can be served even before they make

payment either through cash or cheque. So, the system designed in this project will enable

customers go online and place order for their food (Sharma, 2007).

Due to the great increase in the awareness of internet and the technologies associated with it,

several opportunities are coming up on the web. So many businesses and companies now venture

into their business with ease because of the internet. One of such business that the internet

introduced is an online food ordering system. 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 recently, most of this delivery orders were placed

over the phone, but there are many disadvantages to this system.

The main advantage of this system is that it greatly simplifies the ordering process for both the

customer and the restaurant. The system also greatly lightens the load on the restaurants end, as

the entire process of taking orders is automated. Once an order is placed on the webpage that will

be designed, it is placed into the database and then retrieved, in pretty much real-time, by a

desktop application on the restaurants 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

1
read manner. This allows the restaurant employees to quickly go through the orders as they are

placed and produce the necessary items with minimal delay and confusion. The greatest

advantage of this system is its flexibility.

Food Industry has always been a profitable industry not only for manufacturers, suppliers, but

also for the users, distributers. A Real-time online food ordering system is to eliminate the

traditional queuing system drawbacks and disadvantages. Basically, ‘’Online Food Ordering

System” can be defined as a simple and convenient way for the customers to purchase food

online, without having to go to the restaurant (Sunidhi, 2020).

1.1 Statement of the problem

Nihari is a well-known place, people are seeking for more ways to purchase products with much

ease and still maintain cost effectiveness. The manual method of going to their local food sales

outlets to purchase food is becoming obsolete and more tasking.

1.2 SIGNIFICANCE OF STUDY

The food ordering management system will help customers and management to in archiving this

significant as follow:

1. Advertise available foods

2. Reduce the workload in the present system

3. Reduce time wasted in data processing

4. Create a platform for online purchase and delivery

5. Keep accurate record on purchased order and delivery.

2
1.3 Aims and Objectives

This project aimed at developing a new system and also bring to maximum use and to create an

avenue through the web where users can log on to our server and make a selection of whatever

goods or food they like and subsequently pay via the internet.

The following are the objectives this would bring:

1. To design a web based system to preview its contents

2. To design a database to store every items and customers

3. To design a tracking system that will track any new order

4. To reduce the effort take by the manage while services

1.4 SCOPE AND LIMITATIONS

Online Food Ordering System be design to Faster the method of ordering Food in the restaurant.

The system can also be used in any food delivery industry. It will also simplify the process of

food ordering for both the customer and the restaurant managers, as the entire process manual,

this system will to faster the work and to increase the rate of customers in the restaurant.

Due to financial constraints, this could not handle online payment, online tracking progress. We

recommend any student willing to research on similar work should take the weakness of this

system and improve on it.

3
CHAPTER TWO

LITERATURE REVIEW

This chapter provides a better understanding for the need of this project and also help in

describing the concept in this project. It will also describe in detail the selected methodology or

approach that will be used in this project.

2.1 E-commerce System

Electronic commerce or e-commerce according to Garret, (1996) is the exchange of goods and

services by means of the internet or other computer networks. In e commerce, buyers and sellers

transact business over networked computers.

Electronic commerce is also sharing business information, maintaining business relationships

and conducting business transactions by means of communication networks. It includes the

relationship between companies (business-to-business), between customers (customer-to

customer) as well as between companies and customers (business- to-customer). Business to

business segment currently dominates the e-commerce while customer-oriented segment is

significantly lagging behind and current estimate places it at less than 10% of the total volume,

even though they are all experiencing an exponential growth (Vladimir, 1998). E-commerce

offers buyers convenience. They can visit the World Wide Web (www) sites of multiple vendors

24hours a day and seven days a week to compare prices and make purchases, without having to

leave their homes or offices.

For sellers, e-commerce offers a way to cut costs and expand their markets. They do not need to

build staff or maintain a store or print and distribute mail order catalogs. Because they sell over

the global internet, sellers have the potential to market their products or services globally and are

not limited by the physical location of a store.

4
E-commerce also has some disadvantages, however. Customers are reluctant to buy some

products online. Online furniture businesses for example, have failed for the most part because

customers want to test the comfort of an expensive item such as a sofa before they purchase it.

Many people also consider shopping a social experience, for instance, they may enjoy going to a

store or a shopping mall with 10 friends or family, an experience they cannot get online.

Customers also need to be reassured that credit card transactions are secure and that their privacy

is respected. E-commerce is not only widening customer’s choice of product and services, but

also creating new business and compelling established business to develop internet strategies.

An ordering system is referred to as a set of detail methods that is being used in handling the

ordering process. Food ordering can be computerized or done manually. Those helps the

customer to order their food themselves which is known as the customer self-ordering system.

The customer self-ordering system can be defined as a computerized system that is being used by

customers to place their own orders in the restaurant and allow the orders to be tracked, in order

to prepare and deliver the food to the computers.

1.2 Review of food ordering system

Ordering food from restaurants are often viewed as a representation of modern technology, the

concept of “ready cooked food to go” is as old as cities themselves, unique variations are

historical in various cultures. Ancient Roman cities had bread-and-olive stands, East Asian

cultures features noodle shops. Flat bread and falafel are ubiquitous in the Middle East. Popular

Indian fast food delicacies include Vada Pav, Papri Chaat, Bhelpuri, Panipuri and Dahi Vada. In

the French speaking nations of west Africa, meanwhile, roadside stands in and around the larger

cities continue to sell- as they have done for generations-a range of ready-to-eat char grilled meat

5
sticks known locally as “brochettes” (not to be confused with the bread snack of the same name

found in Europe).

The modern history of a fast food in America began on July 7, 1912 with the opening of a fast

food restaurant called the Automat in New York. The Automat was a cafeteria with its prepared

foods behind small glass windows and coin-operated slots. Joseph Horn and Frank Hardart had

already opened an Automat in Philadelphia but their Automat at Broadway and 13th street, in

New York City, created a sensation and numerous Automat restaurants were quickly built around

the country to deal with the demand. Automats remained extremely popular throughout the

1920’s and 1930’s. The company also popularized the notion of “take-out” food, with their

slogan “less work for mother”. The American company White Castle is generally credited with

opening the second fast food outlet in Topeka, Kansas in 1921, selling hamburgers for five cents

apiece. White Castle later added five holes to each beef patty to increase its surface area and

speed cooking times. White Castle was successful from its inception and spawned numerous

competitors.

2.3 Review of related work

Gan (Gan, 2002) Develop an online fast food restaurant ordering system that allows customers

to place orders anytime at any place. The system helps to manage order from customer as well as

advertise promotion. It allows kitchen staff to view ordering information, management to

manage fast food raw materials and staff to search customer delivery and profile information.

This system helps to reduce queue issues during peak hours, speed up food preparation and

increase customer volumes. The system was developed using PHP, HTML, JavaScript.

Similarly, Vaishnavi et al. (2017) designed Food Ordering and Payment System using GPS and

Android, the system allows customers to use a mobile application to place an order, the mobile

6
app uses a GPS for locator in order for the waiter to deliver the order to the exact location. It also

helps the managements to manage their inventory and daily income. The project was developed

with the help of Java, XML, Laravel.

Also, Trupthi et al. (2019), designed a system Online Food Ordering System, the success of this

project was the use of PHP, HTML, CSS, AJAX, SQL and Jquery. The customers uses this

system to order food online, while ordering, a customer had to place his name, ID, password and

address before ordering. This system is wee because a customers had to be filling form every

time he/she have to order food online.

Abhishek et al. (2018), designed an online food ordering system. The system was designed to

avoid users doing fatal errors where users can change their own profile also where users can

track their food items through GPS and where users can provide feedback and recommendations

to Restaurants / Mess service providers. This system was archive using JAVA, XML.

2.4 Existing System

The existing system coming to the restaurant and making of orders, the customer have to pay in

cash to the cashier, also the use of paper in record receipt and inventory.

2.5 proposed System

This proposed system will have a friendly user interface that will eases the customer work.

Customer can choose more than one item to make an order and can view order details before

logging off. The order confirmation will be sent to the customer. If an order is placed in the

queue, it will be updated in the database and returned in real time. This system will assist the

staff to go through the orders in real time and process it efficiently with minimal errors. With the

7
help of this system, people can easily order the food. It can also ensure that the people do not

waste their precious time and use their time productively in the other works.

CHAPTER THREE

ANALYSIS, DESIGN AND IMPLEMENTATION

3.1 SYSTEM ANALYSIS AND DESIGN

System analysis and design is a problem-solving technique that decomposes a system into its

component pieces for the purpose of studying how well the component works and interact to

accomplish their purpose (John, 2011). The development of a new information system involves

several different activities. These activities, or phases, usually include planning phase, design

phase, analysis phase, implementation phase and maintenance/support phase. (Unhelkar.

2016).

3.2 Analysis Phase

The analysis phase answers all the questions of who will use the system, what the system will

do and where and when it will be used. During this phase, the project investigates any current

system in order to identify how to improve the new system. The steps involved in Analysis

phase are:

i. Requirement gathering

ii. Define the system

iii. Build protocols for the new system

iv. Prioritize requirements

v. Evaluate alternatives

vi. Meets with the management to discuss the new options.

8
3.2.1 Requirement Gathering

Requirement gathering is an essential part of any project and project management. Understanding fully

what a project will deliver is critical to its success. Requirement gathering is the practice of researching

and discovering the requirement of a system from users (Satzinger, 2007). During the

requirement gathering of this proposed system, an Interview and Document review were used to

gather these requirements.

3.2.1.1 Data collected during the Interview Method

During the interview session, the cashier was interviewed about the current manual process of

ordering food, based on the interview, it was clear that a customer must have to come to the

restaurant and order. During the ordering system, the customer had to fill a receipt form to

choose the type of food he/she want to be served. The receipt contains food list with prices.

If a food is been ordered, the cashier will have to record it on a loge book, after the day, they

calculate the total money earned and lost in a day.

3.2.1.2 Data Collected During the Document Review

Below is diagram that shows the application form for the existing system.
Item Name Qnt Price
Item 1 ₦ 320
Item 2 ₦ 500
Item 3 ₦ 250
Item 4 ₦ 300
Item 5 ₦ 150
Item 6 ₦ 50
9
Item 7 ₦ 100
Item 8 ₦ 300
Total
Figure 3.1: Receipt ordering of the existing system

3.3 Define the System

3.3.1 Description of the Existing System

A customer has to go to the restaurant in other to make an order, hence, the customer also make a

phone call to know whether a specific food item is the menu or not. After making enquiries, the

customer has to fill a choice slip by picking his/her desirable food and give to the waiter. The

customer waits until for the ordering to be done before going out.

3.3.2 Weakness of the Existing system

The existing system is weak because every process is done manually. With this manual method,

there is highly possibility of human error. Similarly, it consumed a lot of time, and lead to over

crowding of people in the restaurant. When ordering, the cost of money is calculated manually

with this can prompt error in figures. The cashier and the admin has to do manual calculation for

daily and weekly incomes.

3.3.3 Proposed System

This proposed system will provide an efficient system that will computerize the manual process

through the use of online. A customer can see the available food menu through online and order

without coming to the restaurant. With this system, all calculations will be done systematically,

the admin and the cashier call see daily income and it will reduce overcrowding the restaurant.

10
3.4 System Modeling

According to Alain, (2006), System modeling is the interdisciplinary study of the use of

models to conceptualize and construct systems in business and IT development. There are

different types of system modeling which are:

i. Functional modeling.

ii. Systems architecture modeling.

iii. Business process modeling

iv. Enterprise modeling

3.4.1 Model of the Existing System

A functional model is a diagrammatic format of describing an existing system based on the

data collected. It is also a functional model that is graphically represent an enterprise's that

functioned within a defined scope. The purposes of the functional model are to describe the

functions and processes of a design. (Alain. 2006). Below is a functional model of the existing

system.

Goes to Restaurant To collect Menu List

Fill and Return from

Customer collect from


FOOD
Waiter

Pays to gives
Cashier

Figure 3.2: A Functional Model of Process in the Existing System

11
In the diagram above, it illustrated that the customer has to go to the restaurant and collect a

menu list from the waiter, the customer fills the menu list and return it back to the waiter, then,

the customer collects the ordered food from the waiter and pay to the cashier.

3.4.2 Model of the proposed system

Based on the requirement, an architecture modeling technique is used to describe a proposed

system. System architecture is a conceptual model that defines the structure, behavior, and

more views of a new system. An architecture model is a formal description and representation

of a system, organized in a way that supports reasoning about the structures and behaviors of a

new system (Pdrez-Martinez, 2004). Below is an architectural model of the new proposed

system.

Start

Admin Voter

Admin Interface Details Customer Interface

Login

Database

12

Interface
Food Menu
Order food
Orders
Orders
All Orders

Not deliver Edit Details


Cecile order

User

Figure 3.3: Architecture Diagram of the proposed system Interface Structure

3.5 System Requirements

System requirements are the configuration that a system must have in order for a hardware or

software application to run smoothly and efficiently. Failure to meet these requirements can

result in installation problems or performance problems. However Functional requirement, Non-

functional requirements, User requirements, Interface requirements, Operational requirements,

hardware requirements and software requirements are very important for any design system.

After analyzing the data collected, user requirement, system hardware and software requirement,

(Jeffrey, 2013).

3.5.1 System requirement of the proposed system

User Requirement

Based on the data collection, the user requirements should be based on the following:

i. Authenticated details to access the system

ii. Understand the system

iii. Knowing the controls

Functional Requirements

13
The functional requirements that the system must do before accessing it are as follows:

i. It should verify the user input details for allowing to access

ii. Allow the Admin to view all orders

iii. Allow the Admin to add new food menu

iv. Allow the Admin to view menu food list and reset

v. The customer to order food

vi. Allow customer to view ordered list

Software Requirement

Software is a set of instruction that tells computer what to do. The various software required for

proper functional of the proposed system are listed below:

i. Operating system such as Windows: 7, 8.1,10 or Android Phone.

ii. Notepad++ or Subline text

iii. Localhost server ( Xamp x 3.2.2)

iv. Browser like Google chrome, opera mini, UCbrowser, Firefox.

v. Adobe Photoshop or CorelDraw for editing image.

Hardware Requirements

Computer hardware is the physical and touchable components of a computer system that work

with the software to achieve proper functionalities of the computer system. The hardware

requirements for the proposed system are:

i. HP Laptop, Dell

ii. Memory capacity of 32giga bytes

14
iii. Hard Disk 500gb

iv. Processor Speed 2.23GHz

3.6 SYSTEM DESIGN

System design is the process of defining architecture, modules, interface and data for a system to

satisfy specified requirements. System design could be seen as the application of system theory

to product development, (Bentley et, al., 1986). There are different types of system design:

Logical Design, Architectural Design, and Physical Design. Base on the requirements, the

system used Architectural Design, and Physical Design.

3.6.2 Architecture Design

The Architecture design specified the overall architecture and the piecemeal of software and

hardware that will be used. System architecture shows the key components of a system (Alan.

2012). The architecture design of the proposed system application is a user interface design with

visual basic QUI, which communicate with web server and database using MySQL connector.

The following diagram shows the architecture design of the proposed system.

Interface Client Computer


(Customer/admin
(HTML, CSS, integration)
JavaScript, php)

Database
15
(MySQL)
Figure 3.5: Architecture Design of the proposed system.

3.7 Database design

Database Design is a collection of processes that facilitate the designing, development,

implementation and maintenance of enterprise data management systems. It helps produce

database systems that meet the requirements of the users and have high performance. The Steps

involve in Database design are: Define the Purpose of the Database (Requirement Analysis),

Gather Data, Organize in tables and specify the Primary Keys. Create Relationships among

Tables, and Refine & Normalize the Design. (Code. 1970).

3.7.1 Database Table

Tables are the two-dimensional structures including rows (tuples or records) and columns (fields)

in which the data for entities are placed. The tables are designed to contain the same kind of

information linked by foreign keys and ids (TechTarget, 2013). The following tables show the

database tables for the proposed system and the attributes for each table.

Column Type Null

16
id (Primary) int(11) No

Name varchar(20) No

Price int(11) No

Deleted tinyint(4) No

Table 3.1: Items Table Database table design

Column Type Null Default Links to


id (Primary) int(11) No
customer_id int(11) No users -> id
Address varchar(300) No
Description varchar(300) No
Date datetime No current_timestamp()
payment_type varchar(16) No Wallet
Total int(11) No
Status varchar(25) No Yet to be delivered
Deleted tinyint(4) No 0

Table 3.2: Orders Database Table Design

Column Type Null Default Links to


id (Primary) int(11) No
order_id int(11) No orders -> id
item_id int(11) No items -> id
quantity int(11) No

17
price int(11) No
Table 3.3: Order details Database Table Design

Column Type Null Default Links to


id (Primary) int(11) No
role varchar(15) No Customer
name varchar(15) No
username varchar(10) No
password varchar(16) No
email varchar(35) Yes NULL
address varchar(300) Yes NULL
contact bigint(11) No
verified tinyint(1) No 0
deleted tinyint(4) No 0

Table 3.4: Users Database table design

Column Type Null Default Links to


id (Primary) int(11) No
customer_id int(11) No users -> id

Table 3.5: Wallet Database Table Design

Column Type Null Default Links to


id (Primary) int(11) No
wallet_id int(11) No wallet -> id

18
number varchar(16) No
cvv int(3) No
balance int(11) No 2000
Table 3.6: Wallet Details Database design

3.7.2 Entity Relationship Diagram (ERD)

A database consisting of independent and unrelated tables serves little purpose. The power of

relational database lies in the relationship that can be defined between tables. The most crucial

aspect in designing a relational database is to identify the relationships among tables. The types

of relationship include: one-to-many, many-to-many, and one-to-one.

19
Figure 3.6: Entity-relation Diagram

3.8 Implementation

The system implementation defines the construction, installation, testing and delivery of the

proposed system. After thorough analysis and design of the system, the system implementation

incorporates all other development phases to produce a functional system (Satzinger et al., 2007).

The proposed Electronic Voting management system was developed using HTML, CSS for

graphical user interface, while php, and javaScript language was used for the back-end, while

SQL code for connecting to the database server. The following figures show the screenshots of

the interfaces of the developed system and the developed system codes is reflected in the

20
Appendix.

Figure 3.7: User Login page designed interface

Figure 3.8: User registration designed interface

21
Figure 3.9: Menu list designed interface

Figure 3.10 Add to cart designed interface

22
Figure 3.11: Check out designed interface

Figure 3.12: Admin Login designed interface

23
Figure 3.13: Oders List designed interface

Figure 3.14: Menu/Adding List designed interface

24
Figure 3.15: Food Category designed interface

25
CHAPTER FOUR

SUMMARY, RECOMMENDATION, AND CONCLUSION

4.1 SUMMARY

This project work aimed at designing and implementing an online food ordering system that

will make an efficient way for ordering food at Nihari Food Ristorante, Zaria. The current

system is tedious and time wasting, the new design will help the ristorante in managing the

ordering system in a computerized way. The new design was achieved using multiple

programming languages which are: HTML, CSS, JavaScript, PHP and SQL.

4.2 RECOMMENDATION

In the fastest world of today, the majority of people are frequently online, many customers of

now days are mostly attracted to online ordering, so introducing food ordering system will be

convenient for people to get food at their door step. The most of restaurant have to show on food

items and offered, lowest price and extremely simplified navigation for the order.

4.3 CONCLUSION

Online Food Ordering system is developed to help and solve one of the important problems of

customer in nihari. Because Large number of customers uses the internet and phone. Various

issues related to Mess/Tiffin Service will be solved by these systems. Thus, implementation of

Online Food Ordering system is done to help and solve one of the important problems of

customer. It helps customer in making order easily and gives information needed in making

order to customer place.

26
REFERENCE

Musei clinton, 2018. Design and implementation of online food ordering system

Hannu Jaakkola and Bernhard Thalheim. (2011) "Architecture-driven modelling methodologies." In:
Proceedings of the 2011 conference on Information Modelling and Knowledge Bases
XXII. Anneli Heimbürger et al. (eds). IOS Press. p. 98

John Wiley & Sons, Inc, (2011) System Analysis And design, Fifth Edition

Levin, M. S. (2015). Modular system design and evaluation.


Samson, Alain & Voyer, Benjamin. (2012). Two minds, three ways: Dual system and process models in
consumer psychology. AMS Review. 2. 10.1007/s13162-012-0030-9.

Satzinger, John & Batra, Dinesh & Topi, Heikki. (2007). Analysis and Design in the IS Curriculum: Taking it
to the Next Level. Communications of the Association For Information Systems. 20. 483-
496. 10.17705/1CAIS.02031.

Teorey T.J., Lightstone S.S., Nadeau T., Jagadish H.V. (2009). Database Design: Know it all.1st ed.
Burlington, MA.: Morgan Kaufmann Publishers.
Unhelkar, B. (2016). The art of agile practice: A composite approach for projects and organizations:
Auerbach Publications

Whitten, Jeffrey L.;  Bentley, Lonnie D.;  Dittman, Kevin C.  (2004).  Fundamentals of system analysis and
design methods.
William, G. (1962). The design of engineering system. New YORK:: wILLEY.

27

You might also like