srs document(61)

SOFTWARE REQUIREMENTS SPECIFICATION

FOR

ONLINE E-SHOPPING PROJECT

Dharmsinh Desai University ISO 9001:2000 Certified

Nadiad-387001.

Guided by: Prepared by:

Ms.Harshita L Patel Parekh Maulik (CE- 61) Assistant Professor Parmar Darshan(CE-64)Faculty of Technology Parmar Gautam(CE-65)DDU,Nadiad Parmar Kaushik(CE-66)

of 11

TABLE OF CONTENTS:-

1.INTRODUCTION

1.1 Purpose………………………………………………………………………..31.2 Scope.………………………………………………………………………….31.3 References………………………………………………………………….....31.4 Overview……………………………………………………………………...4

2. OVERALL DESCRIPTION

2.1 Product Perspective…………………………………………………………...42.2 Operations……………………………………………………………………..42.3 User Characteristics…………………………………………………………...42.4 Constraints…………………………………………………………………….5

3. SPECIFIC REQUIREMENTS

3.1 Functional Requirements……………………………………………………..83.2 Nonfunctional Requirements …………………………………………………93.3 System Requirements ………………………………………………………....9

of 11

INTRODUCTION:-

1.1 PURPOSE

SRS Of E-Shopping Web Application is designed to allow a quick and easy shopping and also business oriented way. This document specifies all customer requirements of E-commerce according to the modern era of software evolution. This SRS describes all the scope, specification, attributes, functionalities, requirements and capabilities of this project.

SCOPE

Manage Accounts

Manage Shopping Carts

Manage Inventory online.

Print Invoice & Report

Searching techniques.

Confirm orders.

Secure Transactions.

Feedback facility.

Regular updates.

24x7 availability.

Advertisement space.

1.3 REFERENCESIEEE SRS Format

of 11

1.4 OVERVIEW

This document gives you overall view of the e-shopping, design constraints, requirements, assumptions and dependencies and system attributes.

2. THE OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

Online Shopping system is aimed towards the vendors who want to reach out to the maximum cross-section of customer and common people who can be potential customer. It should be user-friendly, ‘quick to learn’ and reliable software for the above purpose. It is intended to be a stand-alone product and should not depend on the availability of other software. It should run on any operating system.

2.2 OPERATIONS

User: Mall Administrator

Functions: The Mall Administrator is the super user and has complete control over all the activities that can be performed. The administrator also manages the list of available product categories. The administrator can also view and delete entries in the guestbook.

User: Mall Customer/Guests

Functions: A Mall Customer can browse through the shops and choose products to place in a virtual shopping cart. The shopping cart details can be viewed and items can be removed from the cart. To proceed with the purchase, the customer is prompted to login. The person can also change his login id or password. The customer can also view the status of any previous orders, and cancel any order that has not been shipped yet.

2.3 USER CHARACTERISTICS

The user should be familiar with the Shopping Mall related terminology like Shopping cart/Checking out/Transaction etc.

The user should be familiar with the Internet.

2.4 CONSTRAINTS

of 11

There is no maintainability of back up so availability will get affected.

Limited to HTTP/HTTPS.

No multilingual support

3. SPECIFIC REQUIREMENTS

3.1 FUNCTIONAL REQUIREMENT

R1: REQUIREMENT OF ADMINISTRATOR

R1.1 admin account

Input: login id and passwordOutput: provide functionality to adminDescription: This is for new admin of site. Ask to admin to enter name and password to open the new account.

R1.2 products details

Input: insert product id,name and its featuresOutput: overall description of the productDescription:admin can see all the products by entering product id/name

R1.3 update information

R1.3.1 update details & prize of products.

Input: info of productOutput: product detailsDescription:admin can update products and prize

R1.3.2 updates details of member

of 11

Input: member id and/or nameOutput: member detailsDescription:admin can also update member information

R1.3.3 updates details of admin

Input:admin idOutput:admin detailsdescription:admin can also change details

R1.3.4 updates invoice & transaction

Input:transaction idDescription:admin updates invoice and also transcation

R1.4 print invoice & report

Input: shopping cart detailsOutput: print billDescription: enter shopping cart details and according to that print bill

R1.5 declare new offers

Input:product id and/or nameOutput:display new offersDescription:admin can also put new product offers for customer

R 1.6 provides safely shopping

R 1.7 transaction facilities and transaction

Input: transaction idOutput:admin manage transaction Description:admin uses transaction facilities

R 1.8 product searching techniques

R 1.8.1 using product name and models

of 11

Input: product nameOutput: required products will be displayedDescription: admin can search products according to product name/models

R 1.8.2 using prize ranges

Input: product prizeOutput: required products will be displayed Description :admin can search products according to prize

R 1.9 change password

Input: enter new passwordOutput: password changedDescription:admin can also change password by entering old password then new password

R 1.10 manages shipping costs.

Description:admin handle all shopping cart functionality

R2: REQUIREMENTS OF CUSTOMERS

R2.1 searching different products.

Input: enter name/id of productOutput: product Description: This is for new user of site. Ask to user to enter name and password to open the new account.

R2.2 searching different products.

Input: enter name/id of productOutput: product

of 11

Description: customer can product by different ways by entering product name/id

R2.3 View shopping history

Input: shopping idOutput: shopping detailsDescription: customer can see history by entering shopping id

R2.4 Receive invoice

Description: customer can also get invoice

R2.5 different techniques for payments.R2.5.1 credit cardR2.5.2 vpp (value paid parcel)

Description: customer can pay by different ways

R2.6 shopping carts.

R2.6.1customer can buy multiple productsDescription: customer can add multiple items in cart

R2.7 cancelling order.

Input: customer id and product idOutput: order cancelDescription: customer can cancel order by entering customer id and product id

3.2 NON FUNCTIONAL REQUIREMENTS

24 X 7 availability

of 11

The system can be viewed by Microsoft Internet Explorer.

Advertisement space where it will effectively catch the customer’s attention and as a source of revenue.

Dynamic price model by which prices can be changed based on demand and supply.

3.3 SOFTWARE SYSTEM REQUIREMENTS

These are software system attributes known as non-functional requirements or quality attributes.These are characteristics the system must possess. These requirements have to be testable just like the functional requirements.

3.3.1 RELIABILITY

It runs in any web browsers.

it runs in all operating system.

3.3.2 AVAILABILITY

Systems have to run 24/7.

The system shall have an availability of 99.99%.

The system shall allow users to restart the application after failure with minimum

loss.

3.3.3 SECURITY of 11

Specify the factors that would protect the software from accidental or malicious

Access, use, modification, destruction, or disclosure.

Utilize certain cryptographic techniques

Keep specific log or history data sets

Restrict communications between some areas of the program

Check data integrity for critical variables

3.3.4 MAINTAINABILITY

The system shall utilize interchangeable plugins.

The system shall be easily updatable for fixes and patches.

The system shall create logs of all changes, updates, or fixes that are done to the

site.

The system shall be easy to upgrade.

3.3.5 EFFICIENCY

The system shall perform searches via shortest path algorithm.

For returning customers, the system shall validate 'existing' credit card in system

after each log in. The system shall automatically compress image files that are too large in size.

The system will employ on demand asynchronous loading for faster execution of

pages. The system shall validate email address existence.

3.3.6 USABILITY of 11

The system shall be easy to use

The system shall be easy to learn

The system shall utilize help bubbles to assist managers, customers, and

administrators

The system shall employ easy to locate buttons

The system shall prompt customer with friend easy to read error messages·

The system shall utilize consistent symbols and colors for clear notifications.

3.3.7 PORTABILITY

It runs anywhere. Anytime and anywhere we can use it.

of 11

srs document(61)

Documents