This document describes a food ordering system that aims to simplify the ordering process for both customers and restaurants. It allows customers to place orders through a mobile app instead of verbally, giving them control over their order and real-time feedback. For restaurants, it provides an organized system to manage menus, place orders, and retrieve orders through a single database. The system was designed with usability and versatility in mind, using common programming languages like Java, jQuery, HTML, and MySQL. Its implementation includes features like login, shopping cart, account management, and a real-time email confirmation system.

1. A FOOD ORDERING
SYSTEM

2. Introduction
 Fast food and takeout have pushed many eateries to prioritize speed above quality in
order to compete in today's marketplace.
 Customers can't get real-time feedback on their orders since orders are
placed solely through verbal means of communication. As a result, there is
often a lot of uncertainty and mistakes made.
 For both customers and restaurants alike, the ordering procedure is
substantially simplified by my system.

3. Introduction
 All of the items in the order, as well as the options and delivery information
that go along with them, are readily available in this application.
 As the orders are placed, the personnel may rapidly go through them and
make the appropriate things without any delays or misunderstanding.
 A single system may be utilized by a variety of companies without any
modification to the code, which considerably enhances its use.

4. System design
 Database
 Application ordering system
 Loginform
 Main menu
 Shopping cart
 Account management form

5. Database
 There are three major logical components to the system's structure. It is
essential that the restaurant have some control over what guests may order
from the menu.
 Customer orders may be placed using an app ordering system, which gives
them complete control over the ordering process. The final logical component
is the order retrieval system.
 To keep track of all orders, the restaurant uses the database to keep the
records.

6. Functional Requirements
 Using the app to Place an Order.
 System for the management of menus
 System for locating and retrieving orders

7. Implementation
 The system application is built using Java, jQuery, HTML, and MySQL, and the
data is saved in the latter.
 Our software requires an Android Smart phone and a computer or laptop with
a web browser and an internet connection to function.
 The implementation of our system includes a real-time feedback system in
which an email will be delivered to the consumer after they place an order.

8. LAYOUTS OF THE APP

9. Conclusion
 The online ordering mechanism went through a number of iterations before it
was finally launched.
 Throughout the design phase, system elements were described in a manner
that best suited the business demands of the organization.
 The first step was to conduct an in-depth investigation into the ordering
problems with Mr foodie app and possible fixes.

10. References
 Bhatnagar, P. (2006). Dinning Trends: self service=Quick-service.
 Brickers, J. (2006). Is Fast Casual Self-Service at the Tripping Ponit?
 De Leon, E. (2008, August 23). Best Online Food Ordering System. Restaurant
Checklist.
 Gan, C.C. (2002). Online Fast-Food Restaurant Ordering Systems.
 Hobbs, N. (2004). Restaurant Customer Ordering.
 Kroc, Ray (1977). Grinding it out: The Making of McDonald’s. Chicago:
Contemporary Books.
 Purname, J., & Wibowo, A.Y. (2007). Wireless Application for Ordering
Management System in a Restaurant.
 Sharma, I. (2007). How Online Food Ordering System helps you run more
efficiently.