School of Computer Science Engineering and

Information Systems
Fall Semester (2023-24)

FIRST REVIEW

COURSE : SOFTWARE TESTING (B2+TB2)

COURSE CODE : SWE2005
FACULTY : Prof. Prasanna M

PROJECT : TEXTILE MANAGEMENT (TESTING

LLLLLL ONLINE TEXTILE SHOPPING APP MEESHO)

TEAM MEMBERS:
• SAI VARSHA S - 22MIS0324
• PAWAR POSHITHA BAI - 22MIS0362
• NIDARSHANA R.R - 22MIS0387
SOFTWARE REQUIREMENTS SPECIFICATION (SRS) DOCUMENT:

CONTENTS:

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
2.1 Project Perspective
2.1.1 Hardware Interfaces
2.1.2 Software Interfaces
2.2 Product Functions
2.3 User Characteristics
2.4 Assumptions & Dependencies
3. Major Requirements
3.1 External Interfaces
3.1.1 Communication Interfaces
3.2 Performance Requirements
3.3 Logical Database Requirements
3.4 Functional Requirements
3.5 Software System Attributes
3.6 Use case Description and screens
4. Level zero diagram
 1. INTRODUCTION
In 19th century, amidst the improvement of technology and growth of World Wide
Web, the creators realized a chance of coming into online commerce, which was the
beginning of many online textile shopping apps such as Meesho, Myntra……...etc. Online
textile shopping through app has become very popular these days because people find it
convenient and easy to shop from their home or office. People can save their time and
energy by purchasing products online with some discounts. The offers on the internet can be
easily compared, and the buyer can buy the product according to their favourable conditions
like price, quality and other discounts for their individual needs.
This is a sample SRS (Software Requirement Specification) document for the online
shopping system Meesho.

1.1 Purpose
In Online Textile Shopping app consumers can directly buy goods, services etc from a
seller interactively in real-time without an intermediary service over the Internet. It benefits
both consumers and sellers.
The purpose is to give a clear understanding of the requirements of Meesho online
textile shopping app which would be helpful for the designer to take into consideration for
providing a well-organised or implemented system, that will enable top level use for
customer shopping online. Meesho is an APP which is designed to allow owners and
customers to sell or buy product online without going into the website. The APP can be
download for free from any Android phones with a minimum version of 16.1. The APP gives
the same feeling like buying clothes online by visiting the website. The features that are
included on the website have been incorporated into this APP.
Use Cases :
1. Sign up / Login
2. Search Product
3. Categories
4. Select Product
5. Purchase Product now
6. Add to Cart
7. View Cart
8. Continue
9. Payment method
10. Cancel order
11. Order Product.
1.2 Scope
We are looking forward to a flexible online textile shopping system, which has the
basic operations (Use cases) as mentioned in section 1.1. The main operations listed are Sign
up/Login , Search Product, Order Product.
• The Sign up Use case is used for clients to login into site to purchase clothes or invite via
coupons / private sales.
• The Search product use case could be used by customer to search and find the products.
This use case can be high level implementation if the buyer only needs to view a product or
it can be a part of Order product use case if the buyer wants to checkout the viewed
product.
• Order product Use case will be a part of viewing, checking out and making payment Use
cases.

1.3 Definitions, Acronyms and Abbreviations

There are these wide terms used in this Software Requirement Specification document
relating to the design of online textile shopping system. All the terms are common in use and
are self-explainable.
However, the meanings are listed as :
• Online – Connected to a network
• Browse – Casual looking
• Search – The act of finding something we need
• Cart – A hand cart that holds products while shopping online
• Place order – Confirming and ordering something
• Delivery – The process of transferring product from store to your location

1.4 References
• Google (Search Engine)
https://www.google.co.in/
• Online Shopping - UML Use Case Diagram Example. Retrieved from
https://www.uml-diagrams.org/examples/online-shopping-use-case-diagram-
example.html
1.5 Overview
This Software Requirement Specification document has two broadly classified
sections. The Overall Description and Major Requirements. Overall Description tells the high
level requirements of system where as the Major Requirements hold the particular
Requirements needed to be associated with the online textile shopping system.

2. OVERALL DESCRIPTION
The functionality of this system can be broken into two sets. First set, when the
customer wants to search for the products that he/she requires. The user can browse for the
products independent on the status of having a Meesho account. In brief, the customer will
be allowed to view and search the required textile products as a guest user or can as a
logged in user.
These options can be high level or can be followed by other use cases such as selecting
products, adding to cart, and viewing shopping cart. However, for these options to happen,
the customer must register to the website.

2.1 Project Perspective

This is a software to be designed aiming at people who need an easy way of shopping
of clothes process rather than going out and standing in queues to buy in their busy
schedule. This system is to provide an effective way of shopping and also to ensure that
customer finds all variety of products he/she needs that they are not able to find in local
stores.
In Online Textile Shopping app consumers can directly buy goods, services etc from a
seller interactively in real-time without an intermediary service over the Internet. It benefits
both consumers and sellers.
2.1.1 Hardware Interfaces
Meesho can be accessed by web site using search engine or can be downloaded in
apps for PC / Mobile phones.
• RAM – 8 GB (minimum), 16 GB (recommended)
• Storage type: SSD (Solid State Drive)
• Processor Architecture: x64 or ARM64
 2.1.2 Software Interfaces
This shopping app is accessible through Internet on Mobile phone or PC. (Either
by installing or by using search engine.)
Operating System: Windows XP or higher
Programming Languages: Java, C++

2.2 Product Functions

2.3 User Characteristics

User must be able to understand the basic terms used in the online shopping system.
He must be familiar to register, login and ordering features of the system.

2.4 Assumptions & Dependencies

• The customer is adding his valid payment credentials.
• Shipping the order to the specified location is the only delivery method.
• Selected and verified items are only shipped.
 3. MAJOR REQUIREMENTS
The specific requirements of this online shopping system will be defined by producing
the 11 use cases mentioned earlier which make up this system.

3.1 External Interfaces

3.1.1 Communication Interfaces
The website will have security designed like SSL Secure Socket Layers) for the login and
any data between server and user will be encrypted since the personal info and payment
info of the user is sensitive.

3.2 Performance Requirements

As this online textile shopping system will be accessed by many people around the
corner of the world, the website must run on an acceptable speed based on the internet and
network available in the locality of the user. The servers’ connections will be based on
attributes of user like location and server will be working 24/7 time.

3.3 Logical Database Requirements

The online textile shopping system contains following data base tables
•Categories
•Cart
•Customer Information
•Payment Details

3.4 Functional Requirements

The functional requirements needed by the online shopping system are
1. Registration: If user wants to buy a product, then a registered account is necessary.
Otherwise, it is not possible.
2. Login/Sign up: User accesses the shopping system by entering valid user id and password
3. Customer: The information and details of user using the website will be tracked and
stored as a list.
4. Products: The clothes info, price, review and the availability are listed out.
5. Changes to cart: User after login can make order or cancel order from the cart
6. Payment: The mode of payment can be through credit card/debit cart/net banking/COD
7. Logout: After ordering or viewing product user will logout
8. Order details: After successful Ordering of product, the system show when the product
ordered is going to arrive.
3.5 Software System Attributes
These requirements are responsible for positive user experience and optimal website
performance.
1. Usability: well -structured and friendly user interface. Better component design for better
performance at peak time.
2. Security: Secure access to customer’s confidential data
3. 24/7 availability
4. Extensibility: Flexible service-based architecture for future extension
5. Reliability: Not losing saved products on the cart in case of power failure or failure of
Internet connection
6. Compatibility: maximum of on all devices
7. Quality: Quality framework produces robust and bug free software.
8. Maintainability: The system should provide backup of data.

3.6 Use case Description and Screens

1. Login Page

Use: This allows the user to use the website as a registered user
Prerequisite: Create an account
Trigger: User needs to select Continue button
Internal Precondition:
• The user selects to Continue after entering the phone number
• User enters the OTP received to his phone number
• User selects Verify
• The website validates user
Internal Post condition:
• User is confirmed as registered user and can proceed to use website

2. Search Product

Use: This allows the user to find products on the website

Prerequisite: None
Trigger: User clicks on search box
Internal Precondition:
• The user types in the keyword
• The website displays all the items related to the keyword
• User clicks search icon
• The website shows selected products related to the keyword searched
Internal Post condition:
• User can view the results and find the product
 3. Categories

Use: This allows the user to browse products in the catalogue of website
Prerequisite: None
Trigger: User clicks on categories
Internal Precondition:
• User clicks on categories icon at the bottom or at the top in the app
• The website shows catalogue item by categories
• User selects a preferred category from the list
Internal Post condition:
• User can view the results and find the product he/she requires
4. Select Product

Use: This allows the user to find and select product they wants
Prerequisite: None
Trigger: User selects an item from the results
Internal Precondition:
• Website shows product details
• User view list and selects an item
• The website shows item in detail
Internal Post condition:
• User can buy the item or can add it to the cart

5. Purchase Product now

Use: This allows the user to quickly order item using buy now
Prerequisite: User needs to click buy now to order
Trigger: User needs to select buy now button
Internal Precondition:
• The system authenticates user and processes order
• User clicks on buy now button (registered users only)
• The system authenticates and order product
Internal Post condition:
• The system confirms that the order has been placed

6. Add to Cart

Use: This allows the user to save the product before the purchase
Prerequisite: registered user only can add and view the cart
Trigger: User needs to select add to cart button
Internal Precondition:
• User needs to click add to cart button
• The system adds the item to the cart
Internal Post condition:
• Item becomes available for buy

7. View Cart
Use: This allows the user to view list of products in the shopping cart
Prerequisite: add the items to the cart
Trigger: User needs to select go to cart button
Internal Precondition:
• User needs to click edit your cart button after adding item to cart
• The system displays the list of items in the cart
Internal Post condition:
• User reviews item in shopping cart
Alternate path icon beside the search button

8. Continue

Use: This allows the user to make payment and order

Prerequisite: None
Trigger: User needs to select proceed to Continue button
Internal Precondition:
• User needs to click proceed to Continue button
• The system displays the Order window with summary of order,
payment and delivery method
Internal Post condition:
• User is ready to Order
 9. Payment method

Use: This allows the user to pay for item in the cart
Prerequisite: None
Trigger: User adds the products to buy
Internal Precondition:
• User clicks on payment method
• The system shows list of credit / debit cards (or) an option to add
cards
• User selects desired payment method from several options
Internal Post condition:
None
10. Cancel Order

Use: This allows the user to cancel the order

Prerequisite: None
Trigger: User displays the order details
Internal Precondition:
• User clicks on the cancel order button in the end
• The system asks for the reason
• User gives the reason and clicks on cancel button
Internal Post condition:
The order will be cancelled

11. Delivery
Use: This allows the user to specify where and how the item should be
delivered
Prerequisite: None
Trigger: User needs to click on shipping address and continue
Internal Precondition:
• User clicks on shipping address and continue
• The system shows list of used addresses or an option to add new
address
• User selects an address or add a new address
Internal Post condition:
• User successfully specified the delivery address
 4. LEVEL ZERO DIAGRAM

Product
Management

Design
Payment
Management
Management

Online textile
shopping
app
(Meesho)

Quality Stock
Management Management

Sales
Management