CHAPTER 2

Software Requirement Specification (SRS)

1
 Software Requirement Specification
A software requirements specification (SRS) is a detailed description of our software
system to be developed with its functional and non-functional requirements. And it may include
a set of use cases that describe user interactions that the software must provide.

2.1. Introduction

2.1.1. Purpose

The main purpose for getting ready this document is to present a general insight
into the analysis and needs of the present system or scenario and for determinant
the operative characteristics of the system.

Scope: This Document plays an important role within the development life cycle
(SDLC) and it describes the entire demand of the system. It's meant to be used by
the developers and can be the essential throughout testing section. Any
amendments created to the wants within the future can should undergo formal
change approval method.

2.1.2. Document Conventions

When writing the SRS document for AllBrandFashionWear.com the following

terminologies are: To make the document more effective and readable, I used
Calibri (Body) font style and 12 font size and headings are bold and highlighted to
look attractive.

2.1.3. Intended Audience and Reading Suggestions

This document is written for the supervisor and also for admin faculty to see what
is developed in this project. It is also for the developers, documentation writers,
testers, and the users who are going to use this web and mobile application.

2.1.4. Product Scope

The final product will enable the different clothing-company/brands to advertise

their products(clothes) through online which will increase the popularity and the

2
 productivity each brand can sell new products easily and capture market by doing
advertisement through online web application and peoples will be notified
through the mobile application and this give more customer satisfaction. Different
companies (especially new one) will get chance of free advertising. We will also
provide different survey, reports that show different companies performance
details. We will manage customer accounts. We will provide the email facility for
further correspondence. We will maintain database for different users.

2.2. Overall Description

2.2.1. Product Perspective

This product is to get all boutiques at uniform place so that peoples can get all at
one place, to add more features like advertising, more efficient description about
the product that makes easy for the customers to do the purchase, the primary
objective is to gather all the brands/boutiques at one place and make easiness for
the peoples/customers.

2.2.2. Product Functions

The final product will enables the customers to get more detailed idea about the
product and information about new product through advertisement. They can
track the previous purchase and validation easily through their personal account
associated to the website.

2.2.3. User Classes and Characteristics

System

It will be the system administrator class He will maintain the overall web store.

Merchant

It includes the people who upload their products on the web.

3
Login

This class will make login of customers and merchants.

Customer

It includes the people who will purchase the things. It will save the attributes of
product sale.

2.2.5. Operating Environment

First it will operate on Internet explorer and Google Chrome. In next increment it
will browse other browsers like Mozilla, Firefox and for their different version
also. We will use Microsoft access database in our project. It can be open on
windows XP, 98, and 7, 8, or 10. But we recommend at least windows 7.The
processor should be at least Pentium 3 or above. The processor speed should be
greater than 400 MHz’s. The video device should support graphics. For the clear
view of graphics and to see video latest flash player should be installing. Ram
should be or greater than 512 Mb. Php will be used.

2.2.5. Design and Implementation Constraints

There is a true need of our product in the cyber world. So we have to complete it
in minimum time say four months. We only use Microsoft access because it is
simple and good to maintain. We should follow the IEEE standards. Default
Language will be English. Project will follow all the copyright and cyber laws of
PTA (Pakistan Telecommunication Authority).

2.2.6. User Documentation

We will give the complete documentation of the project along with web and
android application. We give advices to peoples before launching it in the market,
all will be done after the completion of project.

2.2.7. Assumptions and Dependencies

All things will be happen according to the plan InshAllah.

4
2.3. Functional Requirements

 Create and maintain account.

 View wish list history.
 Add a product by merchant/brand.
 Delete a product by merchant/brand.
 Update a product by merchant/brand.
 Search the required item.
 View the item.
 Store the product in the category.
 GUI should be same in different browsers.
 Give information about latest products.
 Compare the prizes of different brands.

2.4 Non-Functional Requirements

2.4.1. Performance Requirements

 If anybody make new account then he will receive confirmation email.

 Search results shown within 15 sec.
 Web support 200 customers logged at the same time.

2.4.2. Safety Requirements

 We will try the best to make product safe, and everyone will have a secure
account on the web.

2.4.3. Security Requirements

 Web store keep the information of the customers and merchants/brand

safe.
 Web store obeys all the security laws of Pakistan relating to cyber traffic.

5
2.4.4. Software Quality Attributes

 The web app will be easy to use.

 It will be easy to learn how to operate it.
 The web app will show easy to locate buttons.
 The web app use simple English so that user cannot confuse with terms.
 The web app should be easy to upgrade.

6
 CHAPTER 4

Software Requirement Specification (SRS)