Software requirement specification for Online Shopping Portal comparison

Software Requirements
Specification
For

Online Shopping Portal

Prepared by-

<Rishabh Chaurasia>
Table of Contents
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Definition 1
1.4 Product Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product perspective
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Principle actors 2
2.5 General constraints 2
2.6 Assumption and Dependencies 2
3. System Features 4
4. Other Nonfunctional Requirements 4
4.1 Performance Requirements 4
4.2 Safety Requirements 5
4.3 Security Requirements 5
4.4 Software Quality Attributes 5

Revision History
Name Date Reason For Changes Version
 1. Introduction
1.1 Purpose

“e-Vaypar” is a website of online shopping serving Indians and others, with a variety of
All Products. These products can be household products, electronic products, clothing
product, and a wide range of IT products.
This project is a business to Consumer, E-Commerce web site. There is
difference between Web site and a portal. My project is a small step toward on line
shopping. Lack of time is the common problem for all job related persons. Online
shopping in India is sure to make the lives of this busy lot much more simpler. I will
like help with a letter introducing to my customers for my new company which provides
on line shopping and shipping services. Selling products and services online can have
major advantages for business .The benefits of shopping online have been endless. Here
some points are given below which explains what it do:-

 Information of the day of fun products from the online shop.

 You get whole information for any product which you want buy without going
here and there.
 It is time saving.
 For the payment the facility of credit card is available.

As we had step into new world where each sphere is colored with the brush
of information and technology. Thus keeping the pace with today need we need
to change each system of our surrounding into new tech & info system with the
repaid life or in business. The computer communication & associated
technologies are developing at a very fast rate and new demands are being made
for providing entertainment and improving productivity of the workforce.
Computer system is a facilitator, catalyst and reforming agent
The e-Vaypar is for consumer item shop web application comparison, in this the
comparison of same product in different websites can be done so that the
consumer can choice best product in low price.

1.2 Document Conventions

This document follows MLA format bold face text has been used to emphasize
section and sub section headings . Highlights is to point out words in the goods
and italicized text is used to lable and recogonize diagram.

1.3 Definition
e-Vaypar: - online shopping System
SRS: - software requirement
Specification GUI:- graphic user
interface
 1.4 Product Scope

This system allows the save money, time and safer delivery.
The purpose of doing this project is to enhance my knowledge in the field of e-
commerce technologies using ASP .NET, C# .NET, HTML, JavaScript, CSS
(Cascading Style Sheet). This website will help in the area of e-business. People will be
able to read and view the information about the products. This website will make a real
impact on electors to choose a better candidate in the real election.

1.5 References
 Software Engineering, Roger S. Pressman, McGraw-Hill
 An integrated approach to software engineering, Pankaj Jalote, Narosa
Publishing House
 System Analysis And Design, Elias M Awad, Galgotia Publication
 Mastering in Asp.Net, Evangelos Petroutsos, BPB Publications
 Introduction to Sql Server, Kevin Loney & George Koch, Tata McGraw Hil

1.6 Product Functions

This website compares the price of product in different websites and saves our time
and money.

1.7 User Classes and Characteristics

User should be familiar with the term like login, register, order, system etc.

1.8 Principle actors

principle actors are Customer and administrator

 User Id and Password Verification

This is the very simple module in which we verify the User id and Password of the
administrator as well as user.
After verification, the administrator has rights to upload the Items, edit the Items, invite
the users to view the website for shopping, and send the Order detail and Invoice to the
users.
 Request Processing

In this module the user will request for the registration. User will fill all the required
information for the registration. After fulfill all the criteria for registration, the system
will assign UserID and Password for the user. By using UserID and Password the user
can login and will be able to purchase items.
1.9 General constrains
A full internet connection is required for OSC.

1.10 Assumption and Dependencies

Working of OSC need internet connection .

2 . System Features
To campare the price of consumer products available in different websites, so that users can
save their time and money .

3. Specific Requirements:
3.1 Functional Requirements:
This section provides requirement overview of the
system.
Various functional modules that can be implemented by
the system will be -

Description:
 3.1.1 Registration
If customer wants to buy the product then he/she must
be
registered, unregistered user can’t go to the shopping
cart.
3.1.2 Login
Customer logins to the system by entering
valid user id and password for the
shopping.
3.1.3 Changes to Cart
Changes to cart means the customer after
login or registration can make order or
cancel order of the product from the
shopping cart.
3.1.4 Payment
In this system we are dealing the mode of payment
by Cash.
We will extend this to credit card, debit card etc., in the future.

3.1.5 Logout
After ordering or surfing for the product
customer has to logout.

3.1.6 Report Generation

After ordering for the product,the system
will sent one copy of the bill to the
customer’s Email-address and another one
for the system data base.

3.2 Non-Functional Requirements:

Following Non-Functional Requirements will be there in the
insurance to the internet:
(i) Secure access to consumer’s confidential data.
(ii) 24X7 availability.
(iii) Better component design to get better performance at peak
time.
(iv) Flexible service based architecture will be highly desirable for
future extension.Non-Functional Requirements define system
properties and constraints.
Various other Non-Functional Requirements are:
  Security
 Reliability
 Maintainability
 Portability
 Extensibility
 Reusability
 Compatibility
 Resource Utilization

3.3 Performance Requirements:

In order to maintain an acceptable speed at maximum number of
uploads allowed from a particular customer as any number of users
can access to the system at any time.
Also the connections to the servers will be based on the attributes of the
user like his location and server will be working 24X7 times.

3.4 Technical Issues:

This system will work on client-server
architecture. It will require an internet
 server and which will be able to run PHP
application. The system should support
some commonly used browser such as IE,
mozzila firefox,chrome etc.

4. Interface
Requirement:
Various interfaces for the product could be-
1). Login Page
2). Registration Form
3). There will be a screen displaying
information about product that the shop having.
4). If the customers select the buy button
then another screen of shopping cart will be
opened.
5). After ordering for the product,the system will
sent one copyof the bill to the customer’s Email-
address
Software Interface:
1. Operating System:Windows7
Ultimate which supports networking.
2. Front End : ASP.NET 4.0(C#)
3. Back End: SQL SERVER 2010 or
any latest versions
4. Documentation Tools: MS-WORD,
MS-POWERPOINT
 Hardware Interface:
Hardware requirements for insurance on internet
will be same for both parties which are as follows:
Processor: Dual Core(2.7GHz)
RAM:512MB Recommended
HDD: 80 GB (Min 10 MB Virtual Memory Recommended)

Security Measure:
The security of software is threatened at various points throughout its life cycle, both by
inadvertent and intentional choices and actions taken by “insiders”—individuals closely
affiliated with the organization that is producing, deploying, operating, or maintaining the
software, and thus trusted by that organization—and by “outsiders” who have no affiliation
with the organization. The software’s security can be threatened. “Security is about
preventing adverse consequences from the intentional and unwarranted actions of
others.”

External faults that threaten the software’s dependable operation are seen as a security
issue when the faults result from malicious intent or the faults, regardless of their cause, make
the software vulnerable to threats to its security. To be considered secure, software must
exhibit three properties:

1. Dependability
2. Trustworthiness
3. Survivability

AUTHORIZATION

Authorization is the process of giving someone permission to do or have something. In

multi-user computer systems, a system administrator defines for the system which users are
allowed access to the system and what privileges of use (such as access to which file
directories, hours of access, amount of allocated storage space, and so forth). Assuming that
someone has logged in to a computer operating system or application, the system or
application may want to identify what resources the user can be given during this session.
Thus, authorization is sometimes seen as both the preliminary setting up of permissions by a
system administrator and the actual checking of the permission values that have been set up
when a user is getting access.

AUTHENTICATION
 Authentication is the process of determining whether someone or something is, in fact,
who or what it is declared to be. In private and public computer networks (including the
Internet), authentication is commonly done through the use of logon passwords. Knowledge of
the password is assumed to guarantee that the user is authentic. Each user registers initially (or
is registered by someone else), using an assigned or self-declared password. On each
subsequent use, the user must know and use the previously declared password. The weakness
in this system for transactions that are significant (such as the exchange of money) is that
passwords can often be stolen, accidentally revealed, or forgotten.

For this reason, Internet business and many other transactions require a more stringent
authentication process. The use of digital certificates issued and verified by a Certificate
Authority (CA) as part of a public key infrastructure is considered likely to become the
standard way to perform authentication on the Internet.
2.1 Safety Requirements

Information transmission should be securely transmitted to server without any changes

in information.
2.2 Security Requirements

The main security concern is for uses account hence proper login mechanism should be
used to avoid hacking. The tablet I'd registration is way to spam check for increasing
the security.

2.3 Software Quality Attributes

Availability :
If the internet service gets disrupted while sending you information to the server,
the information can be send for verification.

Usability :
As the system is easy to handle and navigates in the most expected way with no
delays .in that case the system program reacts accordingly and transverses
quickly between it's stales.

DATA INTEGRITY & CONSTRAINT INCLUDING

DATABASE DESIGN