CSE320

SOFTWARE REQUIREMENT SPECIFICATION

For

Zomato

Name: Aakash Kumar

Reg. no: 11803424
Section: K18JFB51
Submitted to : Sakshi ma’am
 Zomato is an on-demand food delivery
platform having a presence in more than 23
countries and also provides information
about close-by restaurants, their menu card
average cost, rating and reviews.

SOFTWARE
REQUIREMENT
SPECIFICATION
FOR ZOMATO

By: Aakash Kumar

 Content table
1. Introduction

1.1 purpose

1.2 Intended Audience and Document Overview

1.3 Definitions, Acronyms and Abbreviations

1.4 Product of scope

2. Overall Description

2.1 Product Perspective

2.2 Product function

2.3 User Classes and characteristics

2.4 Operating Environment

2.5 Design and implement constraints

2.6 Assumption and Dependencies
2.7 Support

3. Specific Requirement
3.1 functional Requirement by user
3.2 Functional Requirement by Restaurant
3.3 Functional Requirement by Wish-Master
3.4 New functional requirement

4. Non-Functional Requirement

5.External Internal Requirements

5.1 User Interface,
5.2 Software Interface
5.3 Hardware Interface
5.4 Communications Interfaces

6.Software design Description

7. Screenshot of application
8. Test cases (Manual)

Introduction
1.1 purpose
This document presents a detailed explanation of the objectives, features, user interface and
application of Zomato in real life. It will also describe how the system will perform and under
which it must operate. In this document it will be also shown user interface. Both the
stakeholders, user and the developers of the system can benefit from this document.

1.2 Intended Audience and Document Overview

This document is intended for different types of readers such as customers, stakeholder, system
designer, system developer and tester. By reading this document a reader can learn about what
the project is implemented for and how it will present it’s basic ideas. This document has a
sequential overview of the whole project so if a reader reads the document from top to bottom,
he will get a clear idea about the project.

1.3 Definitions, Acronyms and Abbreviations

We will also use bold letter to emphasis main topics and for all the major functions of the
system. We will use some acronyms through this document. Abbreviations and definition of
some useful terms we will use are given below :

TERM Definition, Acronyms &Abbreviation

System Admin System admin is a person who is responsible for managing the
whole system and who has full access to the system.
System User The person who is using or operating the system with a limited
privilege.
Data Base Collection of all the information monitored by this system.
Software Requirements A document that completely describes all of the functions of a
Specification (SRS) proposed system and the constraints under which it must operate.
For example, this document.
Stakeholder Any person who is involved in the development process of the
software.
User name Name provided to the every customer or shop owner
 password Each customer must have to set password to protect the data from
others
payment User pays the amount for the food
location Particular area of user
Human network All the man power who takes the food from restaurant and delivers
to the door.
discount Relaxation on price provided to user on particular bookings.
Advertisement Showing the restaurant’s picture on the home page.
Cashback Returns some amount of amount to the user

1.4 Product of scope

This product will help the user to connect the restaurant , Here user can order the food for their
doorstep, see the rating and review, menu list, price, table reservation and search the restaurant.

2. Overall Description

2.1 Product Perspective

This software will help the user to connect to the restaurant, through this system a shop owner
can reach to other areas, helps to make a order who are unable to go to the restaurant, it keeps
record and payments details so, owner can make good decision, provides a great variety to the
user.

2.2 Product function

2.2.1 Food order via mobile application

2.2.2 Make the payment through various method

2.2.3 Take order by the particular restaurant

2.2.4 Live location of the food

2.2.5 Wish master gets information of food and user

2.2.6 Tip to wish master (online pay)

2.2.7 wish master review

2.2.8 Food review

Restaurant
USER

Server Restaurant1
USER1
ZOMATO

USER2 Restaurant2

2.3 User Classes and characteristics

There are five types of actors and one cooperating system
Characteristics : There are several user of this system
USER : With no any special training to operate the software
RESTAURANT: Will get order from user and prepare food
WISH MASTER: Gets information and takes food from the restaurant and delivers to user door
ADMIN: Who can make changes in interface of application

2.4 Operating Environment

OPERATING SYATEM: It works on Android (version above 4), Windows 10 App , IOS
Display: One display connected to Internet to each restaurant to see the order

2.5 Design and implement constraints

There are some constraints which are reducing the popularity of ZOMATO
2.5.1 Slow speed of internet of user device, restaurant device or wish master in particular area
2.5.2 Different language in the world sometimes create disadvantage to the ZOMATO
2.5.3 Slow speed of the application forces user to switch to another faster platform
2.5.4 Lower version of android sometimes fails to open the software

2.6 Assumption and Dependencies

2.6.1 All the users, restaurants management, wish-master are comfortable with the
operating system.
2.6.2 Not all the restaurant are connected to the services
2.6.3 Not all the restaurants are available at all time
2.6.4 If order cancel automatic refund will make
2.6.5 Software will never crash

2.7 Support
User can read documentation of application or can make a contact to the customer service for
any assistance.

3. Specific Requirements
3.1 Functional Requirement: Functional requirement can be divided for the three case
3.1.1 functional Requirement by user
3.1.2 Functional Requirement by Restaurant
3.1.3 Functional Requirement by Wish-Master
3.1.4 New features can add

3.1.1 functional Requirement by user1

3.1.1.1 Description: If entered username or password is not present in database
3.1.1.2 Input : Enter username and password
3.1.1.3 Processing: Validate Username and password
3.1.1.4 Output : Enter a valid information or forgot password
3.1.2 functional Requirement by user 2
3.1.2.1 Description: If forgot password selected
3.1.2.2 Input : Enter email
3.1.2.3 Processing: Sending a mail on email entered
3.1.2.4 Output : Set pass and enter to app

3.1.3 functional Requirement by user3

3.1.3.1 Description: If valid password and username entered
3.1.3.2 Input : Enter username and password
3.1.3.3 Processing: Validate Username and password
3.1.3.4 Output : home page of application

3.1.4 functional Requirement by user4

3.1.4.1 Description: If not in area where Zomato providing any service
3.1.4.2 Input : Enter address
3.1.4.3 Processing: Check for services
3.1.4.4Output : Sorry, we are not here. Please enter any other address

3.1.5 functional Requirement by user5

3.1.5.1 Description: If where Zomato providing service
3.1.5.2 Input : Enter address
3.1.5.3 Processing: Check for services
3.1.5.4 Output : List of restaurants available with information’s

3.1.6 functional Requirement by user6

3.1.6.1 Description: If searched for not available restaurant or food
3.1.6.2 Input : Search by food name restaurant
3.1.6.3 Processing: Check for services
3.1.6.4 Output : Sorry, we are not available now. Please enter any other option

3.1.7 functional Requirement by user7

3.1.7.1 Description: If Selects from available list
3.1.7.2 Input : Select restaurant
3.1.7.3 Processing: collecting all information price, specific information, picture, review, rating
3.1..7.4 Output : show all information of product and discount if any

3.1.8 functional Requirement by user8

3.1.8.1 Description: Selects add to cart
3.1.8.2 Input : Selects add to cart
3.1.8.3 Processing: Adding to cart
3.1.8.4 Output : Food added to cart

3.1.9 functional Requirement by user9

3.1.1.9 Description: make order
3.1.1.9 Input : selects payment method
3.1.1.9 Processing: selects method selected
3.1.1.9 Output : Prompts the selected payment interface with bill

3.1.10 functional Requirement by user10

3.1.10.1 Description: If online method selected with valid details
3.1.10.2 Input : Enter payments details
3.1.10.3 Processing: validating payment details
3.1.10.4 Output : Your order has been placed

3.1.11 functional Requirement by user11

3.1.11.1 Description: If cash on delivery method selected
3.1.11.2 Input : cash on delivery selected
3.1.11.3 Processing: placing order
3.1.11.4 Output : Your order has been placed

3.1.2 Functional Requirement by Restaurant

3.1.2.1 functional Requirement by restaurant1

3.1.2.1.1 Description: Receive an order
3.1.2.1.2 Input : Selects from the order list
3.1.2.1.3 Processing: Selecting order item from list
3.1.2.1.4 Output: order confirmed

3.1.2.2 functional Requirement by restaurant2

3.1.2.2.1 Description: packs order as requested and selects order ready
3.1.2.2.2 Input : Select order ready
3.1.2.2.3 Processing: sending information to the Zomato delivery personnel
3.1.2.2.4 Output: order completed

3.1.3 Functional Requirement by delivery personnel

3.1.3.1 functional Requirement by restaurant1
3.1.3.1.1 Description: Receive an order by user
3.1.3.1.2 Input :Order confirmed by delivery personnel
3.1.3.1.3 Processing: confirming order
3.1.3.1.4 Output: order confirmed

3.1.3.2 functional Requirement by restaurant2

3.1.3.2.1 Description: Order completed by restaurant
3.1.3.2.2 Input : Order received from restaurant
3.1.3.2.3 Processing: sending information to user that order received delivery personnel
3.1.3.2.4 Output: order received

3.1.3.3 functional Requirement by restaurant3

3.1.3.3.1 Description: order collected by user
3.1.3.3.2 Input : Parcel delivered
3.1.3.3.3 Processing: sending information to user and Zomato server that order completed
3.1.3.3.4 Output: send message for review

3.1.4 New features can be added

3.1.4.1 For customer :- Getting variety of dishes from various restaurants in the same order.
3.1.4.2 For restaurateur: - instant refund in case of any customer does fraudulent practice.

4. Non-Functional Requirement
4.1 All right reserved to Zomato
4.2 Legal, copyright and all other notice reserved by Zomato
4.3 Security of all the data
4.4 Customer care services in emergency case
4.5 In interrupted condition saves the data
4.6 The source code developed for this system shall be maintained in configuration management
tools.
4.7 The whole system is secured, Only Admin can access all the data.
4.8 This system will use HTTPS. Because of this protocol this is more secure
4.9 System must have to be operable even on slow internet connection

5.External Internal Requirements

There are many types of interfaces as such supported by this software system namely;
5.1 User Interface,
5.2 Software Interface
5.3 Hardware Interface
5.4 Communications Interfaces

5.1 User Interface

The user interface will be implemented using any android smartphone having Zomato app. This
interface will be user friendly. So that every kind of customer can place the food order and make
payment in very secure and easily way. Customers can also give feedback through it easily with
some demo comment or if they are keen to write their review by own they can do it.

5.2 Software Interface

The system shall communicate with the Configurator to identify all the available components to
configure the product. The system shall communicate with the content manager to get the
product specifications, and can communicate with Zomato server to fetch or edit data .

5.3 Hardware Interface

There shall be logical address of the system in IPv6 format.

5.4 Communication Interface

Communication function required the Internet protocol version 6 and it will follow HTTPS. It
will use FTP for whole system with local server. And email communication to device to device
of the system.

6. Software Design Description

6.1 Use-case diagram
6.2 E R diagram
6.3 DFD

6.1 Usecase Diagram

This use case diagram is a graphical description of the interaction among the elements of
ZOMATO. It represents the methodology system analysis to identify, clarify and organize the
requirements of ZOMATO. The main factors taken as Admin, Customer , Restaurant, Supplier.
6.1 Entity Relationship Diagram
It shows the Entity relationship diagram of ZOMATO. In which we described the main entity
and how they are related to each other and can be the requirements to shows their relation with
the database.
6.3 Data Flow Diagram
In this DFD we have divided the action in three level
1.level 0
2. level 1
3.level 2
In level 1 we decompose the order food
In level 2 we decomposes the place order
 Level 2

7. Screenshot of application
In the screenshot we have tried the cover the all aspect of the application as login or register,
food list, cart, restaurant acceptance, Location importance, payment method, cashback or another
offers.
8. Testing (manual)
Steps Action Expected Actual Status
1 Enter Username and Enter to Entered to pass
password homepage homepage

1.1 Enter wrong Username and Enter correct Enter correct pass
password password password

2 Set password Enter email Enter email pass

3 Wrong Service area Enter other Enter other add pass
address

4 Service area List of services List of restaurants pass

5 Search food not available select other option Select other pass
option

6 Select from list All information All information pass

about food about food

7 Add to cart Order detail in Order detail in pass

cart cart
8 Make order Ask Payment Ask payment pass
details detail
9 Select Payment by cash Order placed Order placed pass
10 Selected valid online Order placed Order placed pass
payment
11 Selected invalid online Check payment Check payment pass
payment detail detail
12 Receive order Order confirmed Order confirm pass
13 Select Order ready Message to Message to pass
supplier and supplier and
customer customer
14 Receive order by user Select Order Select Order pass
confirm confirm
15 Inform the user, supplier Order received Order received pass
received food
16 Order collected by customer Order delivered to Order delivered to pass
user, ZOMATO user, ZOMATO