High Level Design (HLD)

ZOMATO RESTAURANT ANALYSIS

AND PREDICT THEIR RATINGS

Revision Number -1.2

Last Date of Revision - 07/07/2024

SATYAM SHARMA

1|PAGE ZOMATO RESTAURANTS ANALYSIS

 Document Control

DATE VERSION DESCRIPTION AUTHOR

01/07/2024 1.0 Abstract, Introduction, General Satyam Sharma
Description

03/07/2024 1.1 Design Detail, API Deployment Satyam Sharma

07/07/2024 1.2 Final Revision Satyam Sharma

2|PAGE ZOMATO RESTAURANTS ANALYSIS

High Level SATYAM

Design (HLD)
SHARMA

TABLE OF CONTENTS
Document Version Control .................................................................................. 2

Abstract. .................................................................................................................... 3

1 Introduction .......................................................................................................... 4

1.1 What is High-level Design Document? .................................................. 4

1.2 Scope .............................................................................................................. 4

2 General Description. .......................................................................................... 5

2.1 Product Perspective & Problem Statement ............................................. 5

2.2 Tools Used ........................................................................................................ 5

3 Design Detail. .......................................................................................................5

3.1 Functional Architecture ............................................................................... 5

3.2 Optimization ................................................................................................... 5

4. KPI ........................................................................................................................... 8

4.1 KPI's (Key Performance Indicators) .......................................................... 9

5 Deployment ..........................................................................................................9

3|PAGE ZOMATO RESTAURANTS ANALYSIS

High Level SATYAM

Design (HLD)
SHARMA

Abstract
Zomato is primarily a food ordering app that is slowly
spreading its offerings in multiple segments. Zomato mainly
rakes in revenue using advertisements from restaurants and
brands that want to use its platform to reach their target
customers.

1. Introduction
1.1 Why this High-level Design Document
The purpose of this High-Level Design (HLD) Document is to
add the necessary detail to the current project description to
represent a suitable model for coding. This document is also
intended to help detect contradictions before coding and can
be used as a reference manual for how the modules interact at
a high level.

The HLD will:

Present all of the design aspects and define them in detail.
Describe the user interface being implemented.
Describe the hardware and software interfaces.
Describe the performance requirements.
Include design features and the architecture of the project.
List and describe the non-functional attributes like:
Security
Reliability
Maintainability
Portability
Application compatibility
Resource utilization

4|PAGE ZOMATO RESTAURANTS ANALYSIS

High Level SATYAM

Design (HLD)
SHARMA

1.2 Scope
The HLD documentation presents the structure of the system,
such as the database architecture, application architecture
(layers), application flow (Navigation), and technology
architecture. The HLD uses non-technical to mildly-technical
terms which should be understandable to the administrators of
the system.

2. General Description
2.1 Product Perspective & Problem Statement
The goal of this project is to analyse the restaurants in Bangalore
and predict their ratings. To achieve the goal, we used a data set
that is formed by the information of 70-80 thousand restaurants
.The problem is based on the given Information about each of
individual. we have to calculate the ratings of individual restaurants.

2.1 Tools Used

5|PAGE ZOMATO RESTAURANTS ANALYSIS

High Level SATYAM

Design (HLD)
SHARMA

3. Design Detail
3.2 Optimization

1. Your data strategy drives performance

Minimize the number of fields.
Minimize the number of records.
Optimize extracts to speed up future queries by materializing
calculatio removing columns and the use of accelerated views.

2. Reduce the marks (data points) in your view

Practice guided analytics. There's no need to fit everything you
plan to show in a single view. Compile related views and connect
then with action filters to travel from overview to highly-
granular views at the speed of though.
Remove unneeded dimensions from the detail shelf.
Explore. Try displaying your data in different types of views.

3. Limit your filters by number and type

Reduce the number of filters in use. Excessive filters on a view
will create a more complex query, which takes longer to return
results. Double-check your filters and remove any that aren’t
necessary.
Use an include filter. Exclude filters load the entire domain of a
dimension while including filters do not. An include filter runs
much faster than an exclude filter, especially for dimensions
with many members.

6|PAGE ZOMATO RESTAURANTS ANALYSIS

High Level SATYAM

Design (HLD)
SHARMA

Use a continuous date filter. Continuous date filters (relative

and range-of-date filters) can take advantage of the indexing
properties in your database and are faster than discrete data
filters
Use Boolean or numeric filters. Computers process integers and
Booleans (t/f) much faster than strings.
Use parameters and action filters. These reduce the query load
(and work across data sources).

4. Optimize and materialize your calculations

Perform calculations in the database
Reduce the number of nested calculations.
Reduce the granularity of LOD or table calculations in the view.
The more granular the calculation, the longer it takes.
Where possible, use MIN or MAX instead of AVG. AVG requires
more processing than MIN or MAX. Often rows will be duplicated
and display the same result with MIN, MAX, or AVG.
Make groups with calculations. Like include filters, calculated
groups load only named members of the domain, whereas
Tableau’s group function loads the entire domain.
Use Booleans or numeric calculations instead of string
calculations. Computers can process integers and Booleans (t/f)
much faster than strings.
Boolean>Int>Float>Date>DateTime>String.

4. KPI
API will be implemented to display and indicate certain KPIs and relevant
indicators for the disease.

7|PAGE ZOMATO RESTAURANTS ANALYSIS

High Level SATYAM

Design (HLD)
SHARMA

4.1 KPIs (Key Performance Indicators)

Key indicators displaying a summary of the restaurants
rating and its relationship with different metrics.
1. Percentage of People book table online or offline.
2. Location of restaurants.
3. Neighborhood in which the restaurants is listed.
4. Restaurants accepts online orders or not.
5. Most liked dish of the restaurants.
6. Cuisine of the respective restaurants.

5. Deployment
Prioritizing data and analytics couldn’t come at a better time.
Your company, no matter what size, is already collecting data
and most likely analysing just a portion of it to solve business
problems, gain competitive advantages, and drive enterprise
transformation. With the explosive growth of enterprise data,
database technologies, and the high demand for analytical
skills, FastAPI is a modern, fast (high-performance), web
framework for building APIs with Python 3.7+ based on standard
Python type hints.
Fast: Very high performance, on par with NodeJS and Go (thanks to
Starlette and Pydantic). One of the fastest Python frameworks available.
Fast to code: Increase the speed to develop features by about 200% to
300%. *
Fewer bugs: Reduce about 40% of human (developer) induced errors. *
Intuitive: Great editor support. Completion everywhere. Less time
debugging.
Easy: Designed to be easy to use and learn. Less time reading docs.
Short: Minimize code duplication. Multiple features from each parameter
declaration. Fewer bugs.

8|PAGE ZOMATO RESTAURANTS ANALYSIS