Software Requirements

Specification
for
FLIPKART

Version 1.0 approved

Prepared by <author>

<section>

<date created>

Copyright ©2019 Apex Institute of Technology – Chandigarh University
Table of Contents
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Project Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Features 2
2.3 User Classes and Characteristics2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
2.7 Assumptions and Dependencies 3
3. System Features 3
3.1 System Feature 1 3
3.2 System Feature 2 (and so on) 4
4. External Interface Requirements 4
4.1 User Interfaces 4
4.2 Hardware Interfaces 4
4.3 Software Interfaces 4
4.4 Communications Interfaces 4
5. Other Nonfunctional Requirements 5
5.1 Performance Requirements 5
5.2 Safety Requirements 5
5.3 Security Requirements 5
5.4 Software Quality Attributes 5
6. Other Requirements 5
Appendix A: Glossary 5
Appendix B: Analysis Models 6
Appendix C: Issues List 6

Copyright ©2019 Apex Institute of Technology – Chandigarh University
Revision History
Name Date Reason For Changes Version

1. Introduction
1.1 Overview:

The purpose of the document is to collect and analyze all assorted ideas that have come up to
define the system, its requirements with respect to consumers. The purpose of this SRS document
is to provide a detailed overview of our software product, its parameters and goals. Developing an
online platform is a job that requires equal share of technological expertise and sound decision
making. Principally built on PHP, this website offers human experience which makes the shopping
experience as satisfying as in a real store. Programming engineers make it sure that the site is
high on responsiveness and low on tech errors, which is the most favorable selling point of this
online store.

1.2 Purpose:

Flipkart.com is an e-commerce website allows consumers to electronically exchange goods and

services with no barriers of time or distance. Electronic commerce has expanded rapidly over
the past five years and is predicted to continue at this rate, or even accelerate. India's biggest
online store for Mobiles, Fashion(Cloths/Shoes), Electronics, Home Appliances, Books, Jewelry,
Home, Furniture, Sporting goods, Beauty & personal care and more! Largest selection from all
brands at lowest price. Payment options - COD, EMI, Credit card, Debit card & more.

1.3 Scope:

E-commerce is a term for any type of business, or commercial transaction that involves the transfer
of information across the Internet. It covers a range of different types of businesses, from
consumer based retail sites, through auction or music sites, to business exchanges trading goods
and services between corporations. It is currently one of the most important aspects of the Internet
to emerge.

1.4 Outline of SRS:

This document describes the project's target audience and its user interface, hardware and
software requirements. It defines how our client, team and audience see the product and its

Copyright ©2019 Apex Institute of Technology – Chandigarh University
functionality. Nonetheless, it helps any designer and developer to assist in software delivery
lifecycle (SDLC) processes.

1.5 References:
Reference for geeky operating environments www.w3techs.com
Reference for user interfaces of e-commerce www.uianduxdesign.com
Reference for Flipkart’s Vision and moto www.wikipedia.com
Reference for functional diagram https://creately.com/diagram/example/hdkb50lr/Flipkart+DFD
Reference for https://programformca.com

Copyright ©2019 Apex Institute of Technology – Chandigarh University
1.6 Abbreviations:

SRS System Requirements Specification

UI User Interface
FAQ Frequently Asked Questions
CRM Customer Relationship Management
DFD Data Flow Diagram

1.7 Definitions:
1.7.1 End user/Customer - The end user will be the one who visits the website and buys
products online from the ones added by the Vendors/Sellers.
1.7.2 Vendor/Seller - Vendors/Sellers will add their products to the database, which will be seen
in the website to the customers who can buy the products by selecting them. Vendors will
have the special privileges than the end users, and have ability to manage the products
added by them.
1.7.3 Product - A product is the item offered for sale. The price that can be charged depends on
the market, the quality, the marketing and the segment that is targeted. Each product has a
useful life after which it needs replacement, and a life cycle after which it has to be re-
invented.
1.7.4 Administrators - Administrators are the ones who adds or administers the categories for
the products, and administers the Vendors.
1.7.5 User ID - At the time of login or signup user is required to enter our complete details which
gets saved at the particular company’s database and our unique ID is generated which
helps in all correspondence in future.
1.7.6 Seller ID - The seller must have a seller ID and password for this which is used to verify and
find the unique profile of the seller. This allows him to list the products that seller have
available to sell.
1.7.7 Order ID – Each purchased and sold item has a unique Identification no. called Order ID
that is used to track and record the details of the purchase done on the platform. It is
generated by the system itself and no two product can ever have same Order ID.
1.7.8 Bank Details - The transaction amount will be transferred back to the saved account. So
the bank details will be synchronized and saved at the backend database securely.
1.7.9 Online Discussion - The data collected through the online discussion will be spread at
various websites for reference purposes and people’s review points will be noted.

Copyright ©2019 Apex Institute of Technology – Chandigarh University
Software Requirements Specification for <Project> Page 6

2. Overall Description
2.1 Product Perspective:

Flipkart’s online website based e-commerce is an outstanding way of bringing Sellers and
customers on an online platform to make purchase in a secured and efficient manner irrespective of
distance between the two. The product is one stop for 30 million products online. Flipkart offers daily
recommendations for discounts and offers on products based on their category.

2.2 Product Function:

 Provide a simple interface and platform to ease the process of buying as well as
selling products online
 Include smooth functionality and efficiency that adds to buyers’ confidence.
 Appropriate space is dedicated to its Offers zone and deal of the day that fetches adequate
attention of users.
 Flipkart keeps a constant focus on new category creation and expansion of products.
 Ads and promotion activities motivate shoppers to buy online.
 Tracking feature of orders and pending deliveries for both sellers and buyers.
 Notifying order and delivery reports to customers and sellers.

2.3 User Classes and Characteristics:

2.3.1 Customer - He or she is a verified user of website who is intended to buy a product from
the seller via the Flipkart platform. The customer must have a username and password to
make a purchase. The person is regularly updated and fed with latest offers and discounts
according their interest.
2.3.2 Seller - He or she is a verified person who is allowed to sell items over the platform. Seller’s
details are stored on database and all the products are listed under him that he is ready to
sell or are available. He is responsible to set products details, price, and quantity.
2.3.3 Administrator - He or she is responsible for monitoring functions and procedures on
platform. Administrator is responsible to provide valid information of a purchase to the
concerned authority in case of any dispute between the customer and seller or in case of
exchange.

2.4 User Documentation:

 Notifications
• Contact Us
• User Agreement
 Select the operator
• Make A Payment
• Submit Account Details
• Payment Security
 Privacy Policy
Software Requirements Specification for <Project> Page 7

2.5 Design Implementation:

The user interface shall be implemented using any tool or software package like Java Applet, MS
Front Page, Enterprise Java-Beans (EJB) etc. on following languages.

Client-side Programming Language

JavaScript JavaScript is a lightweight, object-oriented, cross-platform scripting
language, mainly used within web pages.
HTML5 HTML5 is the fifth revision of the HTML standard.
CSS Cascading Style Sheets define style rules in a separate CSS file.
2.6 Operating Environment:
Recommended browsers are Chrome, Firefox, Safari and Internet Explorer 8 or higher.

Particulars Client System Server System

Operating System Windows/Linux/Android/iOS Linux
Processor Intel or AMD Intel or AMD
Hard Disk 1 GB 1 TB
RAM 256 8 GB

2.7 Analytics
Analytics are required in order to monitor and analyze the requirements details from customers.

Structured Data The Open Graph protocol, originally developed by Facebook, is an

Formats RDF a-based format that enables any web page to become a rich
object in a social graph.
Google Analytics Google Analytics is a free service to get detailed statistics about the
visitors of a website, provided by Google.

2.8 Assumptions and Dependencies

 The customer and seller must have basic knowledge of computers and English language.
 Each User must have a User ID and password.
 Each Seller must have Seller ID and password.
 There must be an Administrator.
 Internet connection is a must.
 Proper browsers should be installed in the user’s system.
Software Requirements Specification for <Project> Page 8

3. System Features 
3.1 Functional requirements:

This subsection contains the requirements for the e-store. These requirements are organized by the
features discussed in the product functions. Features from there, they are then refined into use
case diagrams and to sequence diagram to best capture the functional requirements of the system.

3.1.1 Provide Search facility -

 User to enter the search text on the screen and display matching products based on
the search.
 Enable user to select multiple options on the screen to search.
 Display only 10 matching result on the current screen.
 Enable user to navigate between the search results.
 Notify the user when no matching product is found on the search.

3.1.2 Tailored Content for the User -

 Using the cookies of the user to study the buying pattern of the user.
 Assists him in his purchase and customizes his homepage according to his
previous interactions.
 Including additions to his wish-list, page views, previous searches, reviews about the
product among other things.
 Making good use of data is imperative to designing great customized user experiences.
3.1.3 Displaying Related Items -

 Including results for related items to the items already bought.

 This can incentivize the customer to purchase more.
 By tracking the buying pattern of the user who is logged in, system recommends
similar items for the user
 Display similar products with high ratings newly in-stock or are featured at special
discount prices.
 Displaying all related items that other users purchased in addition to that product.
 This exposes the user to a larger variety of items of his interest.

3.1.4 Create Sellable items on website -

 Provide an interface to all the sellers to add product description and price through
their account.
 List all the sellers for a common product they offer to sell and prioritize them based
on percent of discount.
Software Requirements Specification for <Project> Page 9

3.1.5 Easy Return or Exchange -

 The system allows customers to return the item back to the seller in case he or she
doesn’t like the product and get the feedback of customer
 The system allows customer to exchange the product with seller in case of delivery of
any defective item and get feedback from customer.
 Notify seller about the customer’s reason and feedback about the product.
3.1.6 Provide personalized profile -

 The seller’s and customer’s profile contain all details of seller and customer respectively
like contact, location, address and seller’s license.
 To display both the active and completed order history in the customer profile.
 To allow user to select the order from the order history and detailed information.
 To display the most frequently searched items by the user in the profile.
 To help seller keep list of products and its information in its profile.

3.1.7 Move transaction money and details to Profile -

 Safe transfer of money into seller’s bank account after successful transaction of money.
 Add details of transfer of money to company’s selling and purchasing events logs
and database.
 Send an order confirmation to the user and seller about the purchase through email or SMS.
3.1.8 Detailed invoice for Customer and Seller -

 The system shall display detailed invoice for current order once it is confirmed.
 The system shall allow user to print the invoice.
 The system shall display detailed information of seller’s detail to customer as well
as customer’s detail to seller.

3.1.9 Provide shopping cart facility -

 The system shall provide shopping cart during online purchase.

 The system shall allow user to add/remove products in the shopping cart.
 Later customer can confirm orders for purchase.
3.1.10 Online tracking of shipments -

 The system shall allow user to enter the order information for tracking.
 The system shall display the current tracking information about the order
 The system notifies seller about delivery of product to the consumer.

3.1.11 Allow multiple payment methods -

 The system shall display available payment methods for payment.

 The system shall allow user to select the payment method for order.
Software Requirements Specification for <Project> Page 10

3.1.12 Provide Customer Support. -

 The system shall provide online help, FAQ’s customer support, and sitemap options for
customer support.
 The system shall allow user to select the support type he wants.
 The system shall allow user to enter the customer and product information for the support.
 The system shall display user contact of seller and Flipkart support desk
 The system shall display the online help upon request.
 The system shall display the FAQ’s upon request.

4. External Interface Requirements

4.1 User interface

 Login or Signup Page

 Homepage containing products according to customer’s interest.
 There will be a screen displaying information about all products that user searches.
 If the customers select any product then it will open another tap about the product
information.
 After all transaction the system makes the selling report as portable document file (pdf) and
sent to the customer E-mail address.

4.1.1 Home Page User Interface:

Software Requirements Specification for <Project> Page 11

4.1.2 Login Interface for User:

HOME
USER

Categor Product Offers Register Contact

View NO
Give info and
Register
Yes

Login

4.1.3 Customer Login Interface:

Software Requirements Specification for <Project> Page 12

4.1.4 Login Interface for Seller:

Logout
HOME
Seller

Home Category Product Offers Contact

Proceed to
Checkout
Jeans View Product Retail about product Add or delete offers
Top
T­Shirt Add product to cart
Blazer

Order history

Proceed to checkout

4.1.5 Seller’s Login Interface:

Software Requirements Specification for <Project>
Page 13

4.2 Hardware Interfaces:

Since the application must run over the internet, all the hardware shall require to connect
internet will be hardware interface for the system. As for e.g. Modem, WAN – LAN,
Ethernet Cross-Cable. The system require Database also for the store the any
transaction of the system like MYSQL etc. system also require DNS (domain name
space) for the naming on the internet. At the last user need web browser for interact with
the system.

Web Server Deployment and Technologies

Nginx Nginx (pronounced as "engine X") is a lightweight open
source web server developed by Igor Sysoev.

MySQL MySQL database for storage of Data and user as well as seller
information
RESTful API A RESTful API is an application program interface (API) that uses
HTTP requests to GET, PUT, POST and DELETE data.

4.3 Communications Interfaces:

The e-store system shall use the HTTPS protocol for communication over the internet
and for the intranet communication will be through TCP/IP protocol suite. The user must
have SSL certificate licensing registered web browser.

1. Other Nonfunctional Requirements

1.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements as
specific as possible. You may need to state performance requirements for individual functional
requirements or features.>

1.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well as
actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>
Software Requirements Specification for <Project>
Page 14

1.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect the
product. Define any security or privacy certifications that must be satisfied.>

1.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility,
interoperability, maintainability, portability, reliability, reusability, robustness, testability, and
usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify
the relative preferences for various attributes, such as ease of use over ease of learning.>

2. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List
< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>