Online Food Order

System
Adnansami madar Aishwarya. M

1BM20CS400 1BM20CS401

Ashwini Bhavana C K
1BM20CS402 1BM20CS403

Dr.Kayarvizhy.N
M.Tech,Ph.D
Department of Computer Science & Engineering
BMS College of Engineering
 OUTLINE
1. Introduction
2. ER Diagram
3. Schema Diagram
4. Normalization
5. Software requirements/ Tools and
technologies used
6. User Interface
7. References

Food Ordering System Department of CSE, BMSCE 2020-21

2
 Introduction
 The aim of developing Online Food Ordering system project
is to replace the traditional way of taking orders with
computerized system.
 Another important reason for developing this project is to
prepare order summary reports quickly and in correct format
at any point of time when required.
 Online Food Ordering System has lot of scope. This project
can be used by any restaurants or fast foods for customers
for keeping their order records.
 This project is easy, fast and accurate. It requires less disk
space.Online Food Ordering System uses MYSQL Server as
backend so there is no chance of data loss or data security.
Food Ordering System Department of CSE, BMSCE 2020-21
3
 ER Diagram

Food Ordering System Department of CSE, BMSCE

4
2020-21
 Schema Diagram

Food Ordering System Department of CSE, BMSCE

5
2020-21
 Normalization
 The tables are in First Normal Form(1NF )
as there no composite or multivalued
attributes in the table.

Food Ordering System Department of CSE, BMSCE

6
2020-21
 Functional Dependencies

Food Ordering System Department of CSE, BMSCE

7
2020-21
 Normalization
 Attribue closures:-
 Customer table
(Cust_id)+=Cust_id,Fname,Lname,
PhoneNo,Address,Email,Password, Pincode

• Since Cust_id uniquely determines all attributes

in Customer table ,it will form the candidate key
or the primary key of Customer table.

Food Ordering System Department of CSE, BMSCE

8
2020-21
 Normalization
 Customer Table
• It is in 1NF.
• It is in 2NF.
• It is not in 3NF because nonprime attribute is
dependent on super key pin code which is
dependent on candidate in cust_id we can split
the table into 3NF i.e.,

Food Ordering System Department of CSE, BMSCE

9
2020-21
 Normalization
 It is in 3NF:

 It is in BCNF because all nonprime attributes are

dependent on only candidate key that is cust_id.

Food Ordering System Department of CSE, BMSCE

10
2020-21
 Normalization
 Attribute closures:-
 Category table
(C_id)+=C_id,C_name

• Since C_id uniquely determines all attributes in

Category table ,it will form the candidate key or
the primary key of Category table

Food Ordering System Department of CSE, BMSCE

11
2020-21
 Normalization
 Category Table
• It is in 1 NF.
• It is in 2NF.
• It is in 3NF.
• It is in BCNF because it has only one non
prime c_name attribute with candidate in
C_id.

12
 Normalization
 Attribute closures:-
 Food table
(Food_id)+=Food_id,F_name,Price,
Category_id,Image

• Since Food_id uniquely determines all attributes

in Food table ,it will form the candidate key or
the primary key of Food table

Food Ordering System Department of CSE, BMSCE

13
2020-21
 Normalization
 Food Table
• It is in 1NF.
• It is in 2NF because no non Prime attribute is
dependent on the proper subset of any candidate key of
a table.
• It is in 3NF because there is no transitive functional
dependency of any non Prime attribute on any super
key in the table food.
• It is in in BCNF because all non Prime attribute are
fully functional dependent on the only candidate key
that is food_id.

14
 Normalization
 Attribute closures:-
 Order_details table
(Order_id)+=Order_id,Fname,Price,Quality,F_id,
Customer_id,Order_date

• Since Order_id uniquely determines all attributes

in Order_details table ,it will form the candidate
key or the primary key of Order_details table

Food Ordering System Department of CSE, BMSCE

15
2020-21
 Normalization
 Order_details Table
• It is in 1NF because every attribute has only
atomic values.
• It is in 2NF because there is only one candidate
key in table hence all nonprime attributes
dependent on only candidate key that is order_id.
• It is not 3NF because nonkey attitude is
dependent on superkey F_id that is dependent on
candidate key order_id we can decompose it into
3NF by breaking table:

16
Normalization

17
 Normalization
• It is in BCNF as it has only one candidate
key to which all nonprime attribute are fully
functional dependent.

18
 Tools Used
1.Hardware Requirements:

 A PC with the following specifications:

• Intel Core i3 or higher
• 2GB RAM or higher

 A stable internet connection.

19
2.Software Requirements:

 Operating system : Windows, Linux, Mac

 Front end technologies are : HTML, CSS,

JAVASCRIPT,BOOTSTRAP

 Text editor: VS code, Sublime text

 Back end requirement : MYSQL

 Server : XAMPP server

20
 User Interface-Home Page
 Cart – The food-items will be stored which customer
wants to order.

 Register – Registration facility for customers.

 Login – Login facility for the customers.

 Search- Customers can search the food.

 Filters- It fetches food information according to the

Category of food.
Food Ordering system Department of CSE, BMSCE
21
2020-21
 User Interface-Home Page

Food Ordering system Department of CSE, BMSCE

22
2020-21
 Customer Signup

Food Ordering system Department of CSE, BMSCE

23
2020-21
 Customer Login

Food Ordering system Department of CSE, BMSCE

24
2020-21
 After Logging-in

Food Ordering system Department of CSE, BMSCE

25
2020-21
 Category

Food Ordering system Department of CSE, BMSCE

26
2020-21
 Added-to-Cart

Food Ordering system Department of CSE, BMSCE

27
2020-21
 References
 https://getbootstrap.com/

 https://www.w3schools.com/php/default
.asp.

 https://skillforge.com/.

 https://stackoverflow.com/.

28
 THANK YOU

Food Ordering System Department of CSE, BMSCE 2020-21

29