ABSTRACT

Online Food Ordering System is proposed for simplifies the food ordering process. This
System shows an user interface and update the menu with all available options so that it 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 is sent to the customer. The order is
placed in the queue and updated in the Database and returned in real time. The Food Ordering
System described in this document has been designed to fill a specific niche in the market by
providing small restaurants with the ability to offer their customers an online ordering option
without having to invest large amounts of time and money in having custom software designed
specifically for them.
The system, which is highly customizable, allows the restaurant employees to easily manage
the site content, most importantly the menu, themselves through a very intuitive graphical
interface. The website, which is the only component seen by the restaurant customers, is then
built dynamically based on the current state of the system, so any changes made are reflected
in real time. Visitors to the site, once registered, are then able to easily navigate this menu, add
food items to their order, and specify delivery options with only a few clicks, greatly
simplifying the ordering process. Back in the restaurant, placed orders are promptly retrieved
and displayed in an easily readable format for eminent processing.
The purpose of this document is to provide in-depth descriptions of design and implementation
details of the system, as well as descriptions of all available functionality and plans for
evolution.

1|P a g e
 Introduction
1.1. Problem definition: -

1. Some of the major problems reported by the customers surveyed revolved around late
deliveries because of network problem

2. Incorrect orders being delivered due to communication problem.

3. Orders not being delivered at all, rude customer service.

4. Cold food being delivered, and the driver requiring a lot of guidance to find the delivery
location.
5. Sometime payment issue is occurred.

6. Online food ordering system service now days increase your budget.

7.lack of a visual confirmation that the order was placed correctly.

2|P a g e
1.2. Objective:
The main objective of the Online Food Ordering System is to manage the details of Item,
Category, Food, Delivery, Address, Order, Shopping Cart. The purpose of the project is to build
an application program to reduce the manual work for managing the Item Category, Food,
Customer.
1. To allow the customer to make order, view order and make changes before submitting their
order and allow them make payment through prepayment card or credit card or debit card.
2. To provide interface that allows promotion and menu.

3. To prevent interface that shows customers’ orders detail to front-end and admin for
delivering customers’ orders.
4. A tool that allows the management to modify the food information such as price, add a new
menu and many others as well as tools for managing user, system men.
5. This will avoid long queues at the counter due to the speed of execution and number of
optimum screens to accommodate the maximum throughput.

6. To increase eminency and improve services provided to the customers through better
application of technology in daily operations.

7. To be able to stand out from competitors in the food service industry.

8. To enable customers to have a visual confirmation that the order was placed correctly

9. To ensure correct placement of orders through visual confirmation.

10. Improve eminency of restaurant’s staff.

11. Eliminate paper work and increase level of accuracy.

12. Increase speed of service, sales volume and customer satisfaction.

13. To increase eminency by shortening the purchasing time and eliminating paper work like
receipts through online transactions.

14. To reduce time wasting by eliminating long queues.

15. More accuracy and easy order processing.

3|P a g e
1.3. Scope:
1. This system will help to customer and administrator for the ordering process.
2. Easy to make ordering and hopefully can smoothen up the job of administrator and
waiter.
3. This system produces a computerized system in defining the best solution in food delivery
system.
4. Easy access to any stage.

5. Lot of time is saved.

6. Easy back up of data.

4|P a g e
1.4. Technical Details: -

1.4.1. Overview of the Front End:-

❖ Front End: -

React Js. Framework (used to develop single-page, mobile, or server-rendered applications

with frameworks).
Tailwinds (React.js UI library that contains easy-to-use components that are useful for
building interactive user interfaces).
❖ Back End:-

Express JS (Backend application framework for building RESTful APIs with Node.js).

Node JS (Back-end JavaScript runtime environment and executes JavaScript code outside
a web browser).
MongoDB (Cross-platform document-oriented database program).

1.4.2. Existing system

1. The existing system happens to be a non-computerized operating system.

2. All operations are done manually by the waiter carrying paper and to take down the order
of the customer or making an order over the counter.
3. This leads to mistakes because the waiter might not understand what the customer had
ordered therefore serving him/her a different menu.
4. This could be so embarrassing because the customer might not take it lightly with the waiter
which may lead to misunderstanding.

5|P a g e
1.4.3. Limitation of existing system
Due to manual means being employed by the fast food restaurants, it is very difficult to satisfy
the wants and needs of the customers. Most of the problems include:
1. Mistakes are made when taking the orders of the customers .

2. The process of collecting customers’ purchases order is very tedious. This makes it
impossible to deliver goods on time.

3. It leads to lack of understanding between the customers and the employees.

4. The record keeping system is poor. Losses of vital records have been reported in the past
consequently. Besides, protecting the file system from unauthorized access is a problem that
has defiled solution.

1.4.4. Proposed system

The Online Food Order System application is a web-based system. This web site provide
complete product to place review, order and order processing. It can be accessed through
internet browsers on pc, laptop etc.

6|P a g e
 System Planning and Schedule

2.1. Software development model: -

This project is developed on the concept of the Spiral Model. The Spiral Model is a software
development life cycle (SDLC) model that provides a systematic and iterative approach to
software development.

It is based on the idea of a spiral, with each iteration of the spiral representing a complete
Software development cycle, from requirements gathering and analysis to design,
implementation, testing, and maintenance.

7|P a g e
2.2. Gantt chart: -

A Gantt chart is a graphical depiction of a project schedule. The Gantt chart is the most widely
use chart in project management.
These charts are useful in planning a project and defining the sequence of tasks that require
completion. In most instances, the chart is displayed as a horizontal bar chart.

8|P a g e
 Software Requirement Speciflcation(SRS)

3.1. Introduction of SRS: -

SRS is a blueprint or roadmap for the software you're going to build. An SRS not only keeps
your teams aligned and working toward a common vision of the product, it also helps ensure
that each requirement is met. It can ultimately help you make vital decisions on your
product’s lifecycle, such as when to retire an obsolete feature.
It takes time and careful consideration to create a proper SRS. But the effort it takes to write
an SRS is gained back in the development phase. It helps your team better understand your
product, the business needs it serves, its users, and the time it will take to complete.

3.2. Technology Requirements

3.2.1. Hardware to be used: -

1) CPU-Processor – 3.5 Ghz CPU.

2) RAM – 8*2 GB RAM

3) Disk space – 100 GB

3.2.2. Software to be used: -

1) Any browser like Microsoft Edge, Chrome.

2) Windows 11 above.

3) A browser supporting Visual Studio and SQL Cloud Server on system.

3.2.3. Functional requirement: -

These are statements of services the system should provide, how the system should react to
particular inputs, and how the system should behave in particular situations. It specifies the
application functionality that the developers must build into the product to enable users to
accomplish their tasks.
1. Registration: Application provides a link for the Users/Client Registration.

2. Log In: Administrator and Client can log in by entering user name and password and manage
their work on website.
3. Save information: Client enter all its necessary information by filling personal info form
and system save that information.
4. Change requirements: Customer can change any of their information any time.
9|P a g e
 5. Food Menu: Admin can insert, update and delete the food items from the menu list.

6. Show Food Menu: There is a list of all types of food the restaurant is dealing with
the available themes.
7. Record Order Details: Customer can select food items from menu and can add the desired
food items to. The cart. Customer can place the order and gets the confirmation against
That Order in the form of message.
8. Show Order Status: Customer can check the status of his/her placed order.

9. View Orders: Admin can view the placed order and delivered order.

3.2.4. Performance Requirements: -

1. Improve perfect food delivery System.

2. Operations are done within few seconds.

3. User friendly and Mobile-Friendly Website

4. Highly Customizable.

5. Content management system

6. Social media integration

7. Customer Support and Interface

8. Product comparison and user-generated reviews

9. Appropriate operation output will be displayed to within few second.

10. When the selection is made and confirmed by the customer, the receipt shall be produced
within some seconds.

3.2.5. Security Requirements: -

1. Customer Identification

2. Pages of the website must be access in the way they were intended to be accessed.
3. Included files shall not be accessed outside of their parent file.
4. Administrator can only perform administrative task on pages they are privileged to access.

5. Customers will not be allowed to access the administrator pages.

10 | P a g e
Object Oriented Analysis & Design Diagrams

DFD Level 0

11 | P a g e
DFD Level 1

12 | P a g e
13 | P a g e
DFD Level 2

14 | P a g e
Use case Diagram

15 | P a g e
Activity Diagram (Admin)

16 | P a g e
Activity Diagram (User)

17 | P a g e
Class Diagram (Admin)

18 | P a g e
Class Diagram (User)

19 | P a g e
Sequence Diagram (Admin)

20 | P a g e
Sequence Diagram (User)

21 | P a g e
ER diagram

22 | P a g e
 Database

5.Database Table: -

23 | P a g e
5.1. Network Access (IP Address)

5.2. Clusters

24 | P a g e
5.3. List all food Database

5.4. Orders Database

25 | P a g e
5.5. Users Database

26 | P a g e
 Testing

Features to be tested are: 1. Proper redirected login as per the user. 2. Validation of login and
register module. 3. View Shopping Cart and the Catalogue. 4. View information of various
fields. 5. Validation of booking form.
1. Black Box Testing treats the software as a black box without the knowledge of internal
behavior. It aims to test the functionality according to the requirements. Thus, the tester
only inputs data and sees the output from the test object. This kind of testing requires.
through test cases to be provided to the tester who then can simply verify that for a given
input, the output value is the same as the expected value specified in the test cases.

Black box testing or functional validation test cases and results.

Test code Test case Test Step Excepted Actual Status
Result Result (Pass or Fail)

Test 1 Administr Go to Login Successful Login Pass

ator Page.Enter Login. successful.
Login valid username
and password.
Then Click on
“login”.
Test 2 Place Go to order Placed order Placed order Pass
order placing Page. successfully. successfully.
check the
menu details
and select
menu from it.
Then Click on
“place order”.
Test 3 Check . Go to order Order is Order is Pass
and verify Page. Check submitted. submitted.
customer the order
order. details and
verify it. Then
Click on
“verify order”
Display
message to
customer that
“your order is
submitted”.
Test 4 Customer Go to payment order is order is Pass
Payment page. Select processed processed
payment
option then
click on pay
option.
Display
message to
customer that
“your order is
processed”.
27 | P a g e
 2. White box testing is however, is when the tester has access to the internal data structures,
code and the algorithms. These methods include creating tests to satisfy some code
coverage criteria. For example, the test designer can create test to cause all statements in the
program to be executed at least once. Other examples of white box testing are mutation testing
and fault injection method.
White box testing or functional validation test cases and results

Test Test Case Test Step Expected Actual Status

Code Result Result (Pass
or
Fail)

Test Verify Check the Successful Login Pass

1 response when valid Login successful
a valid username
username and and
password is password
used that written
in respective
fields
Test Verify all Check and Verify Verify Pass
2 decisions verify all successfully successfully
making decisions
statements making
statements
used in
coding.
Test Verify all Check and Verify Verify Pass
3 looping verify all successfully successfully
statements looping
statements
used in
coding.
Test Code Verify to Verify code Verify code Pass
4 optimization remove optimization optimization
repeated and
extra code

28 | P a g e
 Modules

Landing Page:

29 | P a g e
Sign Up Page:

30 | P a g e
31 | P a g e
Menu Page:

32 | P a g e
Order Page:

33 | P a g e
Item Deleted:

34 | P a g e
Payment Gateway:

35 | P a g e
Stripe Integration:

36 | P a g e
Payment Processing:

37 | P a g e
My Order:

38 | P a g e
Admin Dashboard:

39 | P a g e
Add Items:

40 | P a g e
List Items:

41 | P a g e
Order Tracking Page:

42 | P a g e
Updating Order:

43 | P a g e
Order Updated on Users End:

44 | P a g e
 Conclusion

Overall, we have created application in focus of future food delivery system.

Our Project is only a humble venture to satisfy the needs to manage their project work.
Several user-friendly coding has also adopted. This package shall also prove to be a powerful
package in satisfying all system requirements. The objective of software planning is to provide
a framework that enables the manager to make reasonable estimates made within a limited time
frame at the beginning of the software project and should be updated regularly as the project
progresses.

45 | P a g e
 Future Scope

The following section describes the work that will be implemented with future releases of the
software.
o Customize orders: Allow customers to customize food orders
o Enhance User Interface by adding more user interactive features. Provide Deals
and promotional Offer details to home page. Provide Recipes of the Week/Day to
Home Page
o Payment Options: Add different payment options such as Pay Pal , razor pay , Gift
Cards etc.

o Allow to process an order as a Guest

o Order Process Estimate: Provide customer a visual graphical order status bar
o Order Status: Show only Active orders to Restaurant Employees.

46 | P a g e
 References

1. Https://www.w3schools.com

2. Https://www.youtube.com

3. https://react.dev/

4. https://nodejs.org/

5. https://expressjs.com/

6. https://stripe.com/docs

7. https://stripe.com/docs/stripe-js/react

8. ttps://github.com/remy/nodemon

9. https://mongoosejs.com/

47 | P a g e