Software Requirement Specification:

A software requirements specification (SRS) is a comprehensive description of the

intended purpose and environment for software under development. The SRS fully
describes what the software will do and how it will be expected to perform. A
software requirements specification describes the essential behaviour of a software
product from a user's point of view.
An SRS minimizes the time and effort required by developers to achieve desired
goals and also minimizes the development cost. A good SRS defines how an
application will interact with system hardware, other programs and human users in a
wide variety of real-world situations.

Functional Requirement and Non-functional Requirement:

Functional requirements:

All those components necessary in a project either its technical details ,

manipulation of data or anything else which effects the project directly can be
defined as functional requirement.
The practical prerequisites of this ecommerce site are recorded beneath:
 Secure registration process for new customers.
 User Login for purchase.
 When placing the order for purchase, display the price and ask for confirmation.
 Products should be listed depending upon price, categories and popularity.
 Shopping cart should be added so, customers can buy multiple number of products
at once.
 Shopping Cart should display all added items along with price and quantity
 Payment option i.e. PayPal or American Express.

Non-functional requirement
A non-functional requirement is a requirement that specifies criteria that can be used
to judge the operation of a system, rather than specific behaviours. The non-
functional requirements of this system are:
 User-friendly UX/UI design.
 Quickly executable for better performance.
 Capability with browsers. (wesley, 2016)
 24*7 availability
 Better component design to get better performance at peak time.
 Security, Reliability, Maintainability, Portability, Extensibility, Reusability,
Compatibility and Resource utilization.

UML Diagram (Use case):

UML (Use Case diagram) is a graphic representation of the interactions among the
elements of a system. In the picture below, it shows the relationship among the entities
of online shopping system (E Commerce) which includes customer and admin.

UML Diagram (Use case):

UML (Use Case diagram) is a graphic representation of the interactions among the
elements of a system. In the picture below, it shows the relationship among the entities
of online shopping system (E Commerce) which includes customer and admin.

Manage the
products

Update
information
time to time

View PRoducts
Admin of website Customers

Buy products

Rate and give

feed back

Class diagram:
 UML class diagram is a type of static structure diagram which describes the structure of
a system by showing its classes, their attributes and their relationship with objects. In
the picture below, there are five entities namely Customer, Order table, Order details,
Products and Stores which are connected separately on the basis of their relationship
with each other.

ER Diagram:
ERD means Entity Relationship Diagram. It is a data modelling technique that
graphically represents systems entities and relationships with each other.the below
picture describes the entity relationship.

Risk Analysis and Management:

Risk Analysis is the review of the risk associated with a particular event or action.
It is applied in project, information technology, security issues and any action where
risks may be analysed on A quantitates and qualities base risk analysis is a
component of risk management.
In each one project competent are the risk of loss. Likewise within this
project also qualified in the risk of defeated data for the reason that the besiege of
infection and in behalf of the contrasting natural disaster caused to downplay the risk
to do the project in the ranked time we argue around.

Risk Management:
 To stop from such risk we need to sure or keep our files that we have create in that
situation or n the safe drive like in data canter. We need to install antivirus in our PC
to prevent it will clear away the germ of our pc and our files will be safe. We enjoy
involve many ideas I order to avoid form physical damage like fire and so on.

Test Plan

The following information is a summary of the test plan

System Under E-Shopping

Test:
System Function: 1.1 Secure Registration of
Customer (Group A)
1.2 When placing the new
item for purchase,
display the price and ask
for confirmation. (Group
B)
1.3 Sort the items for sell by
price. (Group C)

Prepared by: MNSD Date: 03/03/2017

Approved by: Agha Date: 04/03/2017
Testing Cycle RAD
Type of Test Plan: System Test Plan

Purpose:
The following types of tests will be performed to test the functionality of the
product/version.
 White Box Testing
 Functional testing
System test environments:
System uses following environments:
 ASP.Net(Visual Studio 2012,framework 4.0)
 Microsoft SQL Server 2012
This test plan and test case matrix are designed to test the functionality of the
system in above mentioned environments and also ensuring that existing system
is not affected by the operation of new system.
 Data requirements:
Below are the data requirements for different system requirements
1.1 Secure registration of customers
 Data: User Name Type: Test
 Data: Email ID Type: Email
 Data: Password Type: Password
 Data: Confirm Password Type: Password
 Data: Message 1, Message2 Type: error
1.2 When placing the new item for purchase, display the price and
ask for confirmation.
The GUI based features need to be focused to check the auto-increased
feature of cart, total price of order, changes in available units and feature
to edit before checkout.

1.3 Sort the items for sell by price

The items can be displayed in any order i.e. ascending or descending
order
Selecting the features available in webpages.

Data Values and Combinations

Entrance Criteria
1.1 Secure Registration of Customer: there will not be any prerequisite entrance criteria
unless the outsider have system requirements and the documents. This helps to secure
the customers registration.
1.2 When placing the new item for purchase, display the price and ask for confirmation:
The customers can select items and add in carts without registration unless they have to
buy. For check-out, customer needs to be registered.
1.3 Sort the items for sale.
Test User Email Password Confirm Resul
Cas Name Password t
e