MYNTRA.COM:FASHION
1. Introduction
Myntra is a one stop shop for all your fashion and lifestyle needs. Being India's largest ecommerce store for fashion and lifestyle products, Myntra aims at providing a hassle free and
enjoyable shopping experience to shoppers across the country with the widest range of brands
and products on its portal. The brand is making a conscious effort to bring the power of fashion
to shoppers with an array of the latest and trendiest products available in the country.
1.1 Purpose
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. Also, we shall predict and sort out
how we hope this product will be used in order to gain a better understanding of the project,
outline concepts that may be developed later, and document ideas that are being considered, but
may be discarded as the product develops.
In short, the purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. 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 functionality. Nonetheless, it helps any designer and developer to assist in
software delivery lifecycle (SDLC) processes.
1.2 Scope
Myntra value proposition revolves around giving consumers the power and ease of purchasing
fashion and lifestyle products online. Offerings such as the largest in-season product catalogue,
100% authentic products, cash on delivery and 30 day return policy make Myntra, the preferred
shopping destination in the country. To make online shopping easier for you, a dedicated
customer connect team is on standby to answer your queries 24x7.
4|Page
Primarily, the scope pertains to the E-Store product features for making online shopping. It
focuses on the company, the stakeholders and applications, which allow for online sales,
distribution and marketing of electronics.
This SRS is also aimed at specifying requirements of software to be developed but it can also be
applied to assist in the selection of in-house and commercial software products. The standard can
be used to create software requirements specifications directly or can be used as a model for
defining a organization or project specific standard. It does not identify any specific method,
nomenclature or tool for preparing an SRS.
1.3 References
The references are:
 Wikipedia
 Myntra Site(http://Myntra.com/about-us)
 Youtube
1.3 Overview
Myntra is an Indian fashion e-commerce company headquartered
in Bengaluru, Karnataka, India. The company was founded in 2007 to sell personalized gift
items.
In 2011, Myntra began selling fashion and lifestyle products and moved away from
personalisation. By 2012 Myntra offered products from 350 Indian and International brands. The
website launched the brands Fastrack Watches and Being Human. In 2014 Myntra was acquired
by Flipkart in a deal valued at ₹2,000 crore (US$290 million). The purchase was influenced by
two large common shareholders, Tiger Global and Accel Partners.Myntra functions and operates
independently.Myntra continues to operate as a standalone brand under Flipkart ownership,
focusing primarily on "fashion-conscious" consumers.
2. Overall Description
This document contains the problem statement that the current system is facing which is
hampering the growth opportunities of the company. It further contains a list of the stakeholders
and users of the proposed solution. It also illustrates the needs and wants of the stakeholders that
were identified in the brainstorming exercise as part of the requirements workshop. It further lists
and briefly describes the major features and a brief description of each of the proposed system.
5|Page
The following SRS contains the detail product perspective from different stakeholders. It
provides the detail product functions of E-Store with user characteristics permitted constraints,
assumptions and dependencies and requirements subsets.
3. Specific Requirements
The specific requirements are –
3.1 Functionality
3.1.1 Requirements for Customer




Functional Requirement 1
Description:
Create a new account
Input:
Enter the details
Output:
You have Successfully Registered
Functional Requirement 2
Description:
Create a new account using Facebook or Google account
Input:
Enter the Email or password
Output:
You have Successful Registered
Functional Requirement 3
Description:
Product Details
Input:
Select the product
Output:
Information related to product
Functional Requirement 4
Description:
Price management
Input:
Select the product
Output:
6|Page







Showing the cost of the product, discounts applicable for the particular
product of a vendor/seller.
Functional Requirement 5
Description:
Login valid account
Input:
Enter the user name and password
Output:
Displaying your account
Functional Requirement 6
Description:
Login invalid account
Input:
Enter the username and password
Output:
Account are not valid or invalid account
Functional Requirement 7
Description:
Transaction
All transactions undergoing in the website will be controlled and managed
by this module. Transactions in the sense, Shopping Cart management.
Functional Requirement 8
Description:
Reporting:
This module deals with report management of the entire system. This
includes three sub-modules Stock Report, Order Report and Delivery
Report.
Functional Requirement 9
Description:
Order Report
Order Report will have the list of products ordered and the customer details
who have bought that product, which are undelivered.
Functional Requirement 10
Description:
Delivery Report
Input:
Enter all the information like Name, age, mobile number, Address
Output:
Your product will Delivered on 3,4days.
Functional Requirement 11
Description:
Logout
Input:
7|Page
Click the Logout After payment
Output:
You have successfully logout.
Non-Functional Requirements
3.2.1Availability

The system should be available at all times, meaning the user can
access it using a web browser, only restricted by the down time of the
server on which the system runs. In case of a of a hardware failure or
database corruption, a replacement page will be shown. Also in case
of a hardware failure or database corruption, backups of the database
should be retrieved from the server and saved by the administrator.
3.2.2 Security




The system use SSL (secured socket layer) in all transactions that
include any confidential customer information.
The system must automatically log out all customers after a period of
inactivity.
The system should not leave any cookies on the customer’s computer
containing the user’s password.
The system’s back-end servers shall only be accessible to
authenticated administrators.
3.2.3 Reliability


The system provides storage of all databases on redundant computers
with automatic switchover.
The reliability of the overall program depends on the reliability of the
separate components. The main pillar of reliability of the system is the
backup of the database which is continuously maintained and updated to
reflect the most recent changes.
3.2.4 Maintainability

8|Page
A commercial database is used for maintaining the database and the
application server takes care of the site. In case of a failure, a reinitialization of the program will be done.
3.3 Security
3.3.1 Data Transfer.
The system shall automatically log out all customers after a period of inactivity.
The system shall confirm all transactions with the customer’s web browser.
The system shall not leave any cookies on the customer’s computer containing the user’s
password.
The system shall not leave any cookies on the customer’s computer containing any of the user’s
confidential information.
3.3.2 Data Storage
The customer’s web browser shall never display a customer’s password. It shall always be
echoed with special characters representing typed characters.
The customer’s web browser shall never display a customer’s credit card number after retrieving
from the database. It shall always be shown with just the last 4 digits of the credit card number.
The system’s back-end servers shall never display a customer’s password. The customer’s
password may be reset but never shown.
3.4 Interfaces
3.4.1 User Interfaces
The user interface for the software shall be compatible to any browser such as Internet
Explorer, Mozilla or Netscape Navigator by which user can access to the system.
The user interface shall be implemented using any tool or software package like Java
Applet, MS Front Page, EJB etc.
3.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.
3.4.3 Software Interfaces
1.
The Myntra e-store system shall communicate with the Configurator to identify all
the available components to configure the product.
2. The Myntra e-store shall communicate with the content manager to get the product
specifications, offerings and promotions.
3.The Myntra e-store system shall communicate with billPay system to identify available
payment methods , validate the payments and process payment.
9|Page