SRS on

Zomato

CSE320
Software Engineering

BACHELOR OF
TECHNOLOGY
in
COMPUTER SCIENCE
AND ENGINEERING

By

SOURABH

School of Computer Science and

Engineering
Lovely Professional University Phagwara,
Punjab (India)
 Software Requirement Specification for

ZOMATO
1-Introduction 1.1-Purpose 1.2-Scope
1.3-Definitions
1.3.1-Overview
1.4-Additional Information Description
2- General Description

3- Specific Requirement
3.1-Functional requirement
3.2-Non-functional requirement 4- Test
Cases
5- Data Flow Diagrams (DFDs) 6- Use
Case Diagram
1. Introduction

1.1purpose
This document is meant to
delineate the featuresof
OSS,
As to serve as a guide to
the developers on one
hand and a software
validation document for
the prospective client on
The other. The Online
Shopping System
(OSS)for fashion
Store web application
is intended to provide
complete solutions for
customers through a
single
get way using the
Internet. It will enable
customer to browse
through he shop
And purchase them online
without having
to visit the shop 1.1
Purpose
This document is meant to
delineate the featuresof OSS,
so as to serve as a guide to
the developers on one hand
and a
Software validation
document for the
prospective client on the
other. The Online
Shopping System
(OSS)for fashion
Store web application
is intended to provide
complete solutions for
customers through a
single
get way using the
internet. It will enable
customer to browse
through the shop
And purchase them online
without having
To visit the shop 1.1
Purpose
This document is meant to
delineate the featuresof
OSS, so
As to serve as a
Guide to the dev
elopers on one hand anda
software validation d
ocument for the pro
spective client on the
other. The Online
Shopping System
(OSS)for fashion
Store web application
Is intended to provide
complete solutions for
customers through a
single
 Get way using the
Internet. It will enable
customer to browse
through the shop

And purchase them

online without having
To visit the shop
1.1 Purpose:
This document is meant to demarcate the features of OSS, so as to
serve as a guide to the developers on one hand and a software
validation document for the prospective client on the other. The
Online Shopping System (OSS)for furniture shop web application is
intended to provide complete solutions for vendors as well as
customers through a single gate way using the internet. It will enable
vendors to setup online shops, customer to browse through the shop
and purchase them online without having to visit the shop physically.
The administration module will enable a system administrator to
approve and reject requests for new shops and maintain various lists
of shop category.
2. Scope:
This system allows the customers to maintain their cart for add or
remove the product over the internet.

3. Definitions:
OSS-Online Shopping System
SRS-Software Requirement Specification GUI-Graphical User
Interface

1. Overview
This system provides an easy solution to customer’s to buy food
without going to shop with best deals and offers.

4. Additional Information
This system work on internet server, so it will be operated by any end
user for the buying purpose.

2. General Description
1. ProductPerspective:
The online shopping system (OSS) application enables customers to
browse food items.Also the developer is designing an online food
ordering site to manage the foods and also help the customers
purchase them online without having to visit the shop physically. The
online food ordering system will use the internet as the sole method
for selling foods to its customers.
2.2 Product Functions:
The software should provide a good network. The website and the
application provides a good interface between the user and the server.
It enables users to easily browse any eatables which they require with
ease. They can sort the things according to their needs and compare
with the other food products and select best out of them. It provides
good payment ways like credit card or debit card and cash on
delivery.

3. Specific requirements
1. Functional Requirements
This section provides the requirement overview of the system. Various
functional modules that can be implemented by the system will be:

3.1.1 Functional Requirement 1: Signup

Description If customer wants to buy the food product
: then he/she must be registered
Input: The customer should enter his/her details
like contact number, email address, name
and most importantly the location/address
Processing: Anew account is created for the user and a
unique id is given to the user to login
Output: User registers Id and password to login and
start shopping
3.1.2 Functional Requirement 2: Login
Description Customer logins to the system by entering
: the valid user id and password for ordering
food
Input: Customer enters Id and password
Output: Logged in if the authorization module gives
a positive reply
3.1.3 Functional Requirement 3: Authorization of Id
Description The entered Id and password are checked in
: the Database and if it is valid then the user
is allowed to Login
Input: The id and password which are the input of
the login module will be passed to this
module as argument
Processing: The id and password are matched in the
database, if it is Valid one the access is
given otherwise access is Denied
Output: Positive reply to the login module if it is a
valid one
3.1.4 Functional Requirement 4: Add/Remove to cart
Description The customer after login or registration can
: add food items to the cart and remove the
added food items
Input: Item to be added is selected and add to cart
module is called and for removing remove
from cart module is called
Output: The item is added or removed
3.1.5 Functional Requirement 5: Buy Food
Description The customer clicks on the buy now button
: and is taken to the payment option
Input: Number of food items that the user wants to
buy
Output: The order is placed and a copy of it is sent
to the email provided by the customer at the
time of login
3.1.6 Functional Requirement 6: Payment for order
Description There are options for the payment like
: credit or debit cards and cash on delivery
Input: The method of payment chosen by the
customer
Output: The order is finally placed after the
payment is done
3.1.7 Functional Requirement 7: Log Out
Description After the payment or surf is done, the
: customer will be logged out
Input: The user presses the log out option
Output: The user again come back to the login page
3.8.1 Functional Requirement 8: Order Confirmation
 Description System can generate the portable document
: format and then sent the copy to the
customer’s email another to the systems
database to calculate the transactions
Input: The bill generated after the payment is done
Output: The customer gets the invoice of his/her
order
3.1.9 Functional Requirement 9: Order Number Generation
Description An order number is a unique identification
: number given to each order
Input: The order of the customer
Processing: A unique order number is generated for
every order
Output: The customer gets a unique order no for its
order which can be traced
3.1.10 Functional Requirement 10: Food order tracing
Description An order tracing helps customers to view the
: status of their order
Input: The order id of the order to be traced
Processing: The current status of the order is fetched fro
m
the data
Output: The current status of the order is given to the
customer
3.1.11 Functional Requirement 11: Food Filters
Descriptio It filters all the food items according to the
n: customers need
Input: The criteria on which you want to filter the
food items
Processing The items are filtered according to the criteria
: given by the customer
Output: The customer gets a filtered list of items so
that it is easy for him/her to search the item
required
3.1.12 Functional Requirement 12: Search food/restaurants
Descriptio Search the type of food/restaurants which the
n: customer wants
Input: The type of food/ restaurants which the
customer wants
Processing The type of food/ restaurants are searched in
: the database
Output: The items matched with the given type by the
customer and are shown to the customer
3.1.13 Functional Requirement 13: Feedback
Descriptio The experience of the customer after using
n: Zomato is taken in terms of stars
Input: The no. of stars given by the customer as per
his/her experience after using Zomato
 Processing The number of stars given by the user is save
: d
in the database
Output: The average rating is shown to the user
3.1.14 Functional Requirement 14: Food Order Cancellation

Descriptio The customer can cancel or change the order

n: as per his wish and comfort before the
delivery
Input: The customer selects the order to be
cancelled
Output: The order is cancelled and confirmation for
the order cancellation is sent to the customer
3.1.15 Functional Requirement 15: Save to collection

Descriptio The food items can be saved to collection

n: which the user would like to buy in future
Input: The user needs to choose the eatables which
he wants to save to collection
Output: The food item is saved to collection
3.1.16 Functional Requirement 16: Order History
Descriptio The history of ordered food items will be
n: shown
Input: User goes to Order History
Processing System fetches all the orders from the
: database
Output: History of his/her orders is shown
3.1.17 Functional Requirement 17: Restaurant’s Profile
Descriptio The user can himself/herself become a seller
n: if interested
Input: User needs to provide the details of his/her
restaurants
Output: User can sell food online
3.1.18 Functional Requirement 18: Customer Care
Descriptio Customer can ask any queries if he is facing
n: any problem while using the software

Input: Customer needs to choose the method

through which he want to contact the
customer care
3.1.19OutputonaThel Requiremencustomer willt
Functi: 19:getMultiplhis/hereAddqueriresses
resolved
Descriptio Customer can have multiple addresses where
n: he can order food
Input: User gives the address details
Output: The address is added to address database of
that user
3.1.20 Functional Requirement 20: Feedback to Restaurants
Descriptio Customer can give feedbacks to Restaurants
n: in the form stars
Input: User gives stars according to the food
product of the restaurants
Output: Average feedback are shown with every
restaurant profile
3.1.21 Functional Requirement 21: Call to Restaurants
Descriptio Customer can call in the restaurants if they
n: are confused with food details provided in
the profile
Input: User selects the call option from the
restaurant profile
Output: User is able to connect the call to the
restaurants
2. Non Functional Requirements
1. Security
❖The system must automatically log out all the customer after
a certain period of inactivity
❖The system should not leave cookies on the customer’s computer
containing the user’s password
❖Sensitive data will be encrypted before being sent over
insecure connections like the internet

3.2.2 Reliability
❖The system provides storage of all databases on redundant
computers with automatic switch over
❖Reliability of entire program depends on the reliability of the
separate components
❖The system shall provide for replication of databases to off-site
storage locations

3.2.3Availability
❖The system should be available at all the times, meaning the
user can access it using a web browser, only restricted for
the downtime of the server on which the system runs
❖In case of hardware failure or database corruption, backup
of the database should be retrieved from the server and
saved by the administrator then the service will be
restarted
3. Maintainability
❖A commercial database is used for maintaining the database
and the application server takes care of the site
❖In case of failure the re-initialization of the program will be
done
❖Software design is being done with modularity in mind so that
maintainability can be done efficiently
4. Portability
❖The end user part should be fully portable and any system
using any web browser should be able to use the features
of the system including any hardware platform.
❖The system shall run on pc, laptops, mobile phones and
tablets etc.

5. Performance
❖The product shall be based on web and has to be run from
a web server
❖The product shall take initial load time depending on
internet connection strength which also depends on the
media from which the product is run

6. Supportability
❖Supportability (also known as serviceability) is the ability
to install, configure and monitor the software
❖It is also used to identify the faults and debug the faults
❖It helps in the maintenance of the software by solving the
problems and restoring it

7. Usability
❖Usability which means that how easy the software
performs the specific task.in other words, it shows the
ability of the software to perform tasks
❖In usability, the software is used by specific consumers to
achieve the specific objective with effectiveness,
efficiency, and satisfaction

8. Scalability
❖The software should have the feature of performing best
with best resources
❖It is just about how the software is performing when the
resources are increased than earlier
3.2.9 Recoverability
❖The software should be very easily able to recover from
crashes, hardware failures and other similar problems
❖It is a test by forced failure of the software in a variety of
ways to verify that recovery is properly performed

3.2.10 Manageability
❖The software should be easy to easy to monitor and handle
❖It should be efficient and could be easily maintained so that
the system keeps on performing smoothly
❖It should remain secure
3.2.11 Serviceability
❖The software and its component should have the ability to
get easily maintained and repaired
❖Early detection of problems in this case is critical in this
respect
❖Ideally maintenance and repair operation should cause as
little downtime or disruption as possible
4. Test Cases

Test Case: 1 Test Case Name: Login

System: Zomato Subsystem: Login

Designed by: Sourabh Sharma Designed Date: 15-10-22

Execution by: Execution Date:

Short Description: To Login into Account

Pre-Conditions:
System asks user to enter the user id and password for secure login.

Actions Expected Actual Pass / Fail Comment

Response Output

Login Login Invalid Fail Incorrect

Successfully Username Username
Login Login Invalid Fail Incorrect
Successfully Password Password

Login Login Successfully Pass Welcome

Successfully
Post Conditions: Logged In
Login Successfully.

*****

Test Case: 2 Test Case Name: Add to Cart

System: Zomato Subsystem: Add
Designed by: Sourabh Sharma Designed Date: 15-10-22
Execution by: Execution Date:
Short Description: To Add food item to cart

Pre-Conditions:
System asks user to select the item to be added.

Actions Expected Actual Pass / Fail Comment

Response Output

Add to Added Not added to Fail Already added

Cart Successfully the cart
Add to Added Added Pass Added
Cart Successfully Successfully
Post Conditions:
Added Successfully.

*****

Test Case: 3 Test Case Name: Buy Food

System: Zomato Subsystem: Buy Designed

Designed by: Sourabh Sharma Date: 15-10-22 Execution

Execution by: Date:

Short Description: To Buy food

Pre-Conditions:
System asks user to place order.

Actions Expected Actual Output Pass / Fail Comment

Response

Buy Food Order Placed Not logged in Fail Log in to

Successfully place
order
Buy Food Order Placed Order Placed Pass Order has
Post Conditions: Successfully Successfully been
placed
Order Placed Successfully.

*****
5. Data Flow Diagrams (DFD)

Order Food Details for Payment

Online

Food

Customer Ordering
Payment Gateway
(Zomato)

Payment Confirmation
Delivery of Food

Level 0
Level 1
Level 2
6. Use Case Diagram

Use Case Diagram 1

Use Case Diagram 2