DATABASE

MANAGEMENT
SYSTEM PROJECT

Team Members :

Pranav Prasad - 2021CSC1084

Tarleen Kaur Jagveda - 2021CSC1012
Tanishqa Kaur Chahal - 2021CSC1064
Introduction

Zomato is an Indian multinational restaurant aggregator and food delivery company.It

provides information, menus and user-reviews of restaurants as well as food delivery
options from partner restaurants.
The goal of this project is to build a complete backend database for the app.

The purpose of the database is to create and maintain the data for an online food
ordering application. It includes functionalities such as :

● Customer Log in
● Checking out the restaurants and related menu.
● Filtering based on price, cuisine and ratings and locations.
● To cater the order of customers from booking to cancellation.
● Users of this system : customers

This database will be used by an online food ordering application that acts as an
interface between the customers and the restaurants.

Assumptions

We have assumed in our project:

● That the customers are already logged in with their respective accounts
● One customer can place multiple orders but they have to be from one restaurant
only.
● The employee assigned to the order can have multiple orders to deliver
therefore the cardinality is 1:N.
● Each customer will have their own login credentials therefore the cardinality is
1:1.
● Multiple orders can be prepared from a single restaurant so their cardinality is
N:1.
● Each restaurant can have multiple menus so its cardinality is 1:N.
 ● Every order made by the customer will have one payment invoice and multiple
orders will have overall one order detail so their cardinality is 1:N.
● As the database is from the customer's end the main focus is on the orders from
booking it to the preparation and the delivery.

Exclusions

Following things are not being implemented to make it simpler:

● Order customisations
● Zomato gold membership
● Help center
● Sign up

Entities & Attributes

The following 8 entities have been selected along with its attributes:

● Customer
● Cid - Primary Key
● Name (multivalued attribute)
● Address (Composite attribute)
● Order history
● Favorite restaurants

● Restaurants
● Rid - Primary Key
● Ratings
● Address
● Cuisine
● Reviews
● Offers
● Login Credentials
● Phone number - Primary Key
● Cid - Foreign Key
● Password
● Forget password (multivalued attribute)
● User photo

● Menu (weak entity)

● Dish name
● Rid
● ( both name and rid are taken as Primary Key )

● Zomato Employee
● emp_id - Primary Key
● Phone number
● Rating
● Name

● Payment
● Transaction_id - Primary Key
● Mode
● Amount
● Payment date

● Order
● Order_id - Primary Key
● Cid_id - Foreign Key
● R_id - Foreign Key
● Details_id - Foreign Key
● Emp_id - Foreign Key
 ● Price

● Transaction_id - Foreign Key

● Order status
● Order time
● Quantity
● Name

● Order details
● Details_id - Primary Key
● Taxes
● Subtotal
● Instructions
● Delivery time
● Offer applied
● Tips (to employee)

Relationships

● Places: Customer - Order

● Possess: Customer - Login Credentials
● Prepared by: Order - Restaurant
● Consists-of : Restaurant - Menu
● Has: Order - Order details
● Has: Order - Payment
● Delivered: Order - Zomato Employee
ER DIAGRAM