Software Requirement Specification on Online Purchasing System
5,611 views
29 slides
Apr 12, 2019
Slide 1 of 29
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
About This Presentation
Software Requirement Specification on Online Purchasing System, that define various activities
Slide Content
Software Requirements
Specification
for
Purchase
Munshi Saba Farheen
2018MIT015
Shri Guru Gobind Singhji Institute of Engineering and Technology
Nanded.
12/04/2019
Specification
for
Purchase
Munshi Saba Farheen
2018MIT015
Shri Guru Gobind Singhji Institute of Engineering and Technology
Nanded.
12/04/2019
CONTENTS CONTENTS
Contents
1 Introduction 4
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Abbrevations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5 Denitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.1 End user/Customer - . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.2 Vendor/Seller - . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.3 Product - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.4 Administrators - . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.5 User ID - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.6 Seller ID - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5.7 Order ID – . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5.8 Bank Details - . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5.9 Online Discussion - . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Overall Description 7
2.1 Product Perspective: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Product Function: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 User Classes and Characteristics: . . . . . . . . . . . . . . . . . . . . . . 7
2.3.1 Customer - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.2 Seller - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.3 Administrator - . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 User Documentation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5 Operating Environment: . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6 Assumptions and Dependencies: . . . . . . . . . . . . . . . . . . . . . . 8
3 Specic Requirements 9
3.1 Functional requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 Provide Search facility - . . . . . . . . . . . . . . . . . . . . . . 9
3.1.2 Tailored Content for the User - . . . . . . . . . . . . . . . . . . . 9
3.1.3 Displaying Related Items - . . . . . . . . . . . . . . . . . . . . . 9
3.1.4 Create Sellable items on website - . . . . . . . . . . . . . . . . . 9
3.1.5 Easy Return or Exchange - . . . . . . . . . . . . . . . . . . . . . 9
3.1.6 Provide personalized prole - . . . . . . . . . . . . . . . . . . . 10
3.1.7 Move transaction money and details to Prole - . . . . . . . . . . 10
3.1.8 Detailed invoice for Customer and Seller - . . . . . . . . . . . . . 10
3.1.9 Provide shopping cart facility - . . . . . . . . . . . . . . . . . . . 10
3.1.10 Online tracking of shipments - . . . . . . . . . . . . . . . . . . . 10
3.1.11 Allow multiple payment methods - . . . . . . . . . . . . . . . . . 10
3.1.12 Provide Customer Support. - . . . . . . . . . . . . . . . . . . . . 10
3.2 Non-Functional Requirements: . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.1 Performance: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.2 Security: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.3 Reliability: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.4 Safety: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.5 Maintainability: . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1
Contents
1 Introduction 4
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Abbrevations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5 Denitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.1 End user/Customer - . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.2 Vendor/Seller - . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.3 Product - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.4 Administrators - . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.5 User ID - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.6 Seller ID - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5.7 Order ID – . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5.8 Bank Details - . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5.9 Online Discussion - . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Overall Description 7
2.1 Product Perspective: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Product Function: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 User Classes and Characteristics: . . . . . . . . . . . . . . . . . . . . . . 7
2.3.1 Customer - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.2 Seller - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.3 Administrator - . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 User Documentation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5 Operating Environment: . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6 Assumptions and Dependencies: . . . . . . . . . . . . . . . . . . . . . . 8
3 Specic Requirements 9
3.1 Functional requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 Provide Search facility - . . . . . . . . . . . . . . . . . . . . . . 9
3.1.2 Tailored Content for the User - . . . . . . . . . . . . . . . . . . . 9
3.1.3 Displaying Related Items - . . . . . . . . . . . . . . . . . . . . . 9
3.1.4 Create Sellable items on website - . . . . . . . . . . . . . . . . . 9
3.1.5 Easy Return or Exchange - . . . . . . . . . . . . . . . . . . . . . 9
3.1.6 Provide personalized prole - . . . . . . . . . . . . . . . . . . . 10
3.1.7 Move transaction money and details to Prole - . . . . . . . . . . 10
3.1.8 Detailed invoice for Customer and Seller - . . . . . . . . . . . . . 10
3.1.9 Provide shopping cart facility - . . . . . . . . . . . . . . . . . . . 10
3.1.10 Online tracking of shipments - . . . . . . . . . . . . . . . . . . . 10
3.1.11 Allow multiple payment methods - . . . . . . . . . . . . . . . . . 10
3.1.12 Provide Customer Support. - . . . . . . . . . . . . . . . . . . . . 10
3.2 Non-Functional Requirements: . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.1 Performance: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.2 Security: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.3 Reliability: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.4 Safety: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.5 Maintainability: . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1
CONTENTS CONTENTS
3.3 Constraints: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4 Performance Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.5 Technical Issues: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.6 Interface Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7 External user Requirement: . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7.1 Hardware Interface . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7.2 Software interface . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Design Constraints 13
4.1 Standard Development . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 Web Based Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Payment options in Online Shoppingg . . . . . . . . . . . . . . . . . . . 13
5 Pros, Cons, Challenges & Future 15
5.1 Advantages of online shopping . . . . . . . . . . . . . . . . . . . . . . . 15
5.2 Disadvantages of online shopping . . . . . . . . . . . . . . . . . . . . . 15
5.3 Challenges in Online Shopping . . . . . . . . . . . . . . . . . . . . . . . 16
5.4 Future of Online Shopping . . . . . . . . . . . . . . . . . . . . . . . . . 16
6 System Design Specication 17
6.1 UML Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.1 Use Case Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.2 Activity Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.1.3 Class Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.4 State Chart Diagram: . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.5 Sequence Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1.6 Component Diagram: . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1.7 Deployement Diagram: . . . . . . . . . . . . . . . . . . . . . . . 22
6.1.8 ER Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7 Testing 27
7.1 Unit Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2 Integration Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.3 Validation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.4 Performance Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2
3.3 Constraints: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4 Performance Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.5 Technical Issues: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.6 Interface Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7 External user Requirement: . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7.1 Hardware Interface . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7.2 Software interface . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Design Constraints 13
4.1 Standard Development . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 Web Based Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Payment options in Online Shoppingg . . . . . . . . . . . . . . . . . . . 13
5 Pros, Cons, Challenges & Future 15
5.1 Advantages of online shopping . . . . . . . . . . . . . . . . . . . . . . . 15
5.2 Disadvantages of online shopping . . . . . . . . . . . . . . . . . . . . . 15
5.3 Challenges in Online Shopping . . . . . . . . . . . . . . . . . . . . . . . 16
5.4 Future of Online Shopping . . . . . . . . . . . . . . . . . . . . . . . . . 16
6 System Design Specication 17
6.1 UML Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.1 Use Case Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.2 Activity Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.1.3 Class Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.4 State Chart Diagram: . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.5 Sequence Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1.6 Component Diagram: . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1.7 Deployement Diagram: . . . . . . . . . . . . . . . . . . . . . . . 22
6.1.8 ER Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7 Testing 27
7.1 Unit Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2 Integration Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.3 Validation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.4 Performance Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2
LIST OF FIGURES LIST OF FIGURES
List of Figures
1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Activity Diagram 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Activity Diagram 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 State Chart Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7 Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8 Deployement Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10 Create Vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
11 Create Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
12 Product List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
13 Bill Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
14 Payment Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
15 Purchase Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3
List of Figures
1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Activity Diagram 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Activity Diagram 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 State Chart Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7 Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8 Deployement Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10 Create Vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
11 Create Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
12 Product List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
13 Bill Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
14 Payment Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
15 Purchase Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3
1 INTRODUCTION
Chapter 1
1 Introduction
1.1 Overview
The purpose of the document is to collect and analyze all assorted ideas that have come
up to dene the system, its requirements with respect to consumers. Online shopping is
a form of electronic commerce which allows consumers to directly buy goods or services
from a seller over the Internet using a web browser. Consumers nd a product of interest
by visiting the website of the retailer directly or by searching among alternative vendors
using a shopping search engine, which displays the same product's availability and pricing
at dierent e-retailers. Customers can shop online using a range of dierent computers
and devices, including desktop computers, laptops, tablet computers and smartphones.
Anything that customers purchases aects environment by means of delivery, whether they
have the product shipped at home or drive to a brick and mortar store(supermarket). In
earlier days people used to go to dierent shops before purchasing as they didn't have a
great deal of easy access to information on products. Due to the development of World
Wide Web it has now become easy to access the products available worldwide without
wasting time, money and other resources apart from helping environment.
1.2 Purpose
The main purpose of this online shopping cart is that it provides the customers to calculate
easily what all they purchase whether it is goods or services. Shopping cart contains not
only products but also customer data. Today there are an incredible number of shopping
carts.Consider an Amazon.com is an e-commerce website allows consumers to electron-
ically exchange goods and services with no barriers of time or distance. Electronic com-
merce has expanded rapidly over the past ve years and is predicted to continue at this
rate, or even accelerate. India's biggest online store for Mobiles, Fashion(Cloths/Shoes),
Electronics, Home Appliances, Books, Jewelry, Home, Furniture, Sporting goods, Beauty
& personal care and more! Largest selection from all brands at lowest price. Payment op-
tions - COD, EMI, Credit card, Debit card & more.
1.3 Scope
Purchasing and selling products and services over the internet without the need of going
physically to the market is what online shopping all about. Online shopping is just like
a retail store shopping that we do by going to the market, but it is done through the in-
ternet. Online shopping has made shopping painless and added more fun. Online stores
oer product description, pictures, comparisons, price and much more. Few examples of
these are Amazon.com, ebay.com, framt.com and the benets of online shopping is that
by having direct access to consumer ,the online stores can 4 oer products that cater to
the needs of consumer ,cookies can be used for tracking the customer selection over the
internet or what is of their interest when they visit the site again . Online shopping makes
use of digital technology for managing the ow of information, products, and payment be-
tween consumer, site owners and suppliers. Online shopping can be either B2B (business
to business) or B2C (business to consumer) Shopping cart is one of the important facility
4
Chapter 1
1 Introduction
1.1 Overview
The purpose of the document is to collect and analyze all assorted ideas that have come
up to dene the system, its requirements with respect to consumers. Online shopping is
a form of electronic commerce which allows consumers to directly buy goods or services
from a seller over the Internet using a web browser. Consumers nd a product of interest
by visiting the website of the retailer directly or by searching among alternative vendors
using a shopping search engine, which displays the same product's availability and pricing
at dierent e-retailers. Customers can shop online using a range of dierent computers
and devices, including desktop computers, laptops, tablet computers and smartphones.
Anything that customers purchases aects environment by means of delivery, whether they
have the product shipped at home or drive to a brick and mortar store(supermarket). In
earlier days people used to go to dierent shops before purchasing as they didn't have a
great deal of easy access to information on products. Due to the development of World
Wide Web it has now become easy to access the products available worldwide without
wasting time, money and other resources apart from helping environment.
1.2 Purpose
The main purpose of this online shopping cart is that it provides the customers to calculate
easily what all they purchase whether it is goods or services. Shopping cart contains not
only products but also customer data. Today there are an incredible number of shopping
carts.Consider an Amazon.com is an e-commerce website allows consumers to electron-
ically exchange goods and services with no barriers of time or distance. Electronic com-
merce has expanded rapidly over the past ve years and is predicted to continue at this
rate, or even accelerate. India's biggest online store for Mobiles, Fashion(Cloths/Shoes),
Electronics, Home Appliances, Books, Jewelry, Home, Furniture, Sporting goods, Beauty
& personal care and more! Largest selection from all brands at lowest price. Payment op-
tions - COD, EMI, Credit card, Debit card & more.
1.3 Scope
Purchasing and selling products and services over the internet without the need of going
physically to the market is what online shopping all about. Online shopping is just like
a retail store shopping that we do by going to the market, but it is done through the in-
ternet. Online shopping has made shopping painless and added more fun. Online stores
oer product description, pictures, comparisons, price and much more. Few examples of
these are Amazon.com, ebay.com, framt.com and the benets of online shopping is that
by having direct access to consumer ,the online stores can 4 oer products that cater to
the needs of consumer ,cookies can be used for tracking the customer selection over the
internet or what is of their interest when they visit the site again . Online shopping makes
use of digital technology for managing the ow of information, products, and payment be-
tween consumer, site owners and suppliers. Online shopping can be either B2B (business
to business) or B2C (business to consumer) Shopping cart is one of the important facility
4
1.4 Abbrevations 1 INTRODUCTION
provided in online shopping, this lets customer to browse dierent goods and services and
once they select an item to purchase they can place the item in shopping cart, and continue
browsing till the nal selection. Customers can even remove the items from shopping cart
that were selected earlier before they place the nal order. It reminds us of shopping basket
that we carry in departmental store.
1.4 Abbrevations
SRS System Requirements Specication
UI User Interface
FAQ Frequently Asked Questions
CRM Customer Relationship Management
DFD Data Flow Diagram
1.5 Denitions
1.5.1 End user/Customer -
The end user will be the one who visits the website and buys products online from the
ones added by the Vendors/Sellers.
1.5.2 Vendor/Seller -
Vendors/Sellers will add their products to the database, which will be seen in the website
to the customers who can buy the products by selecting them. Vendors will have the
special privileges than the end users, and have ability to manage the products added by
them.
1.5.3 Product -
A product is the item offered for sale. The price that can be charged depends on the
market, the quality, the marketing and the segment that is targeted. Each product has
a useful life after which it needs replacement, and a life cycle after which it has to be
re-invented.
1.5.4 Administrators -
Administrators are the ones who adds or administers the categories for the products, and
administers the Vendors.
1.5.5 User ID -
At the time of login or signup user is required to enter our complete details which gets
saved at the particular company's database and our unique ID is generated which helps in
all correspondence in future.
5
provided in online shopping, this lets customer to browse dierent goods and services and
once they select an item to purchase they can place the item in shopping cart, and continue
browsing till the nal selection. Customers can even remove the items from shopping cart
that were selected earlier before they place the nal order. It reminds us of shopping basket
that we carry in departmental store.
1.4 Abbrevations
SRS System Requirements Specication
UI User Interface
FAQ Frequently Asked Questions
CRM Customer Relationship Management
DFD Data Flow Diagram
1.5 Denitions
1.5.1 End user/Customer -
The end user will be the one who visits the website and buys products online from the
ones added by the Vendors/Sellers.
1.5.2 Vendor/Seller -
Vendors/Sellers will add their products to the database, which will be seen in the website
to the customers who can buy the products by selecting them. Vendors will have the
special privileges than the end users, and have ability to manage the products added by
them.
1.5.3 Product -
A product is the item offered for sale. The price that can be charged depends on the
market, the quality, the marketing and the segment that is targeted. Each product has
a useful life after which it needs replacement, and a life cycle after which it has to be
re-invented.
1.5.4 Administrators -
Administrators are the ones who adds or administers the categories for the products, and
administers the Vendors.
1.5.5 User ID -
At the time of login or signup user is required to enter our complete details which gets
saved at the particular company's database and our unique ID is generated which helps in
all correspondence in future.
5
1.5 Denitions 1 INTRODUCTION
1.5.6 Seller ID -
The seller must have a seller ID and password for this which is used to verify and nd the
unique prole of the seller. This allows him to list the products that seller have available
to sell.
1.5.7 Order ID –
Each purchased and sold item has a unique Identication no. called Order ID that is used
to track and record the details of the purchase done on the platform. It is generated by the
system itself and no two product can ever have same Order ID.
1.5.8 Bank Details -
The transaction amount will be transferred back to the saved account. So the bank details
will be synchronized and saved at the backend database securely.
1.5.9 Online Discussion -
The data collected through the online discussion will be spread at various websites for
reference purposes and people's review points will be noted.
6
1.5.6 Seller ID -
The seller must have a seller ID and password for this which is used to verify and nd the
unique prole of the seller. This allows him to list the products that seller have available
to sell.
1.5.7 Order ID –
Each purchased and sold item has a unique Identication no. called Order ID that is used
to track and record the details of the purchase done on the platform. It is generated by the
system itself and no two product can ever have same Order ID.
1.5.8 Bank Details -
The transaction amount will be transferred back to the saved account. So the bank details
will be synchronized and saved at the backend database securely.
1.5.9 Online Discussion -
The data collected through the online discussion will be spread at various websites for
reference purposes and people's review points will be noted.
6
2 OVERALL DESCRIPTION
Chapter 2
2 Overall Description
2.1 Product Perspective:
Flipkart's online website based e-commerce is an outstanding way of bringing Sellers
and customers on an online platform to make purchase in a secured and efcient manner
irrespective of distance between the two. The product is one stop for 30 million products
online. Flipkart offers daily recommendations for discounts and offers on products based
on their category.
2.2 Product Function:
Provide a simple interface and platform to ease the process of buying as well as selling
products online Include smooth functionality and efciency that adds to buyers' con-
dence. Appropriate space is dedicated to its Offers zone and deal of the day that fetches
adequate attention of users. Flipkart keeps a constant focus on new category creation and
expansion of products. Ads and promotion activities motivate shoppers to buy online.
Tracking feature of orders and pending deliveries for both sellers and buyers. Notifying
order and delivery reports to customers and sellers.
2.3 User Classes and Characteristics:
2.3.1 Customer -
He or she is a veried user of website who is intended to buy a product from the seller
via the Flipkart platform. The customer must have a username and password to make
a purchase. The person is regularly updated and fed with latest offers and discounts
according their interest.
2.3.2 Seller -
He or she is a veried person who is allowed to sell items over the platform. Seller's
details are stored on database and all the products are listed under him that he is ready to
sell or are available. He is responsible to set products details, price, and quantity.
2.3.3 Administrator -
He or she is responsible for monitoring functions and procedures on platform. Adminis-
trator is responsible to provide valid information of a purchase to the concerned authority
in case of any dispute between the customer and seller or in case of exchange.
2.4 User Documentation:
Notications
Contact Us
User Agreement
7
Chapter 2
2 Overall Description
2.1 Product Perspective:
Flipkart's online website based e-commerce is an outstanding way of bringing Sellers
and customers on an online platform to make purchase in a secured and efcient manner
irrespective of distance between the two. The product is one stop for 30 million products
online. Flipkart offers daily recommendations for discounts and offers on products based
on their category.
2.2 Product Function:
Provide a simple interface and platform to ease the process of buying as well as selling
products online Include smooth functionality and efciency that adds to buyers' con-
dence. Appropriate space is dedicated to its Offers zone and deal of the day that fetches
adequate attention of users. Flipkart keeps a constant focus on new category creation and
expansion of products. Ads and promotion activities motivate shoppers to buy online.
Tracking feature of orders and pending deliveries for both sellers and buyers. Notifying
order and delivery reports to customers and sellers.
2.3 User Classes and Characteristics:
2.3.1 Customer -
He or she is a veried user of website who is intended to buy a product from the seller
via the Flipkart platform. The customer must have a username and password to make
a purchase. The person is regularly updated and fed with latest offers and discounts
according their interest.
2.3.2 Seller -
He or she is a veried person who is allowed to sell items over the platform. Seller's
details are stored on database and all the products are listed under him that he is ready to
sell or are available. He is responsible to set products details, price, and quantity.
2.3.3 Administrator -
He or she is responsible for monitoring functions and procedures on platform. Adminis-
trator is responsible to provide valid information of a purchase to the concerned authority
in case of any dispute between the customer and seller or in case of exchange.
2.4 User Documentation:
Notications
Contact Us
User Agreement
7
2.5 Operating Environment: 2 OVERALL DESCRIPTION
Select the operator
Make A Payment
Submit Account Details
Payment Security
Privacy Policy
2.5 Operating Environment:
This is a web based system and hence will require the operating environment for a client
and server GUI.Recommended browsers are Chrome, Firefox, Safari and Internet Ex-
plorer 8 or higher.
2.6 Assumptions and Dependencies:
This software highly depends on type and version of browser being installed in the system
i.e. browser version should be used which have HTML5 support.
The customer and seller must have basic knowledge of computers and English lan-
guage.
Each User must have a User ID and password. Each Seller must have Seller ID and
password.
There must be an Administrator.
Internet connection is a must.
Proper browsers should be installed in the user's system.
8
Select the operator
Make A Payment
Submit Account Details
Payment Security
Privacy Policy
2.5 Operating Environment:
This is a web based system and hence will require the operating environment for a client
and server GUI.Recommended browsers are Chrome, Firefox, Safari and Internet Ex-
plorer 8 or higher.
2.6 Assumptions and Dependencies:
This software highly depends on type and version of browser being installed in the system
i.e. browser version should be used which have HTML5 support.
The customer and seller must have basic knowledge of computers and English lan-
guage.
Each User must have a User ID and password. Each Seller must have Seller ID and
password.
There must be an Administrator.
Internet connection is a must.
Proper browsers should be installed in the user's system.
8
3 SPECIFIC REQUIREMENTS
Chapter 3
3 Specic Requirements
3.1 Functional requirements:
This subsection contains the requirements for the e-store. These requirements are or-
ganized by the features discussed in the product functions. Features from there, they are
then rened into use case diagrams and to sequence diagram to best capture the functional
requirements of the system.
3.1.1 Provide Search facility -
User to enter the search text on the screen and display matching products based on the
search. Enable user to select multiple options on the screen to search. Display only 10
matching result on the current screen. Enable user to navigate between the search results.
Notify the user when no matching product is found on the search.
3.1.2 Tailored Content for the User -
Using the cookies of the user to study the buying pattern of the user. Assists him in his
purchase and customizes his homepage according to his previous interactions. Including
additions to his wish-list, page views, previous searches, reviews about the product among
other things. Making good use of data is imperative to designing great customized user
experiences.
3.1.3 Displaying Related Items -
Including results for related items to the items already bought. This can incentivize the
customer to purchase more. By tracking the buying pattern of the user who is logged in,
system recommends similar items for the user Display similar products with high ratings
newly in-stock or are featured at special discount prices. Displaying all related items that
other users purchased in addition to that product. This exposes the user to a larger variety
of items of his interest.
3.1.4 Create Sellable items on website -
Provide an interface to all the sellers to add product description and price through their
account. List all the sellers for a common product they offer to sell and prioritize them
based on percent of discount.
3.1.5 Easy Return or Exchange -
The system allows customers to return the item back to the seller in case he or she doesn't
like the product and get the feedback of customer The system allows customer to exchange
the product with seller in case of delivery of any defective item and get feedback from
customer. Notify seller about the customer's reason and feedback about the product.
9
Chapter 3
3 Specic Requirements
3.1 Functional requirements:
This subsection contains the requirements for the e-store. These requirements are or-
ganized by the features discussed in the product functions. Features from there, they are
then rened into use case diagrams and to sequence diagram to best capture the functional
requirements of the system.
3.1.1 Provide Search facility -
User to enter the search text on the screen and display matching products based on the
search. Enable user to select multiple options on the screen to search. Display only 10
matching result on the current screen. Enable user to navigate between the search results.
Notify the user when no matching product is found on the search.
3.1.2 Tailored Content for the User -
Using the cookies of the user to study the buying pattern of the user. Assists him in his
purchase and customizes his homepage according to his previous interactions. Including
additions to his wish-list, page views, previous searches, reviews about the product among
other things. Making good use of data is imperative to designing great customized user
experiences.
3.1.3 Displaying Related Items -
Including results for related items to the items already bought. This can incentivize the
customer to purchase more. By tracking the buying pattern of the user who is logged in,
system recommends similar items for the user Display similar products with high ratings
newly in-stock or are featured at special discount prices. Displaying all related items that
other users purchased in addition to that product. This exposes the user to a larger variety
of items of his interest.
3.1.4 Create Sellable items on website -
Provide an interface to all the sellers to add product description and price through their
account. List all the sellers for a common product they offer to sell and prioritize them
based on percent of discount.
3.1.5 Easy Return or Exchange -
The system allows customers to return the item back to the seller in case he or she doesn't
like the product and get the feedback of customer The system allows customer to exchange
the product with seller in case of delivery of any defective item and get feedback from
customer. Notify seller about the customer's reason and feedback about the product.
9
3.1 Functional requirements: 3 SPECIFIC REQUIREMENTS
3.1.6 Provide personalized prole -
The seller's and customer's prole contain all details of seller and customer respectively
like contact, location, address and seller's license. To display both the active and com-
pleted order history in the customer prole. To allow user to select the order from the
order history and detailed information. To display the most frequently searched items by
the user in the prole. To help seller keep list of products and its information in its prole.
3.1.7 Move transaction money and details to Prole -
Safe transfer of money into seller's bank account after successful transaction of money.
Add details of transfer of money to company's selling and purchasing events logs and
database. Send an order conrmation to the user and seller about the purchase through
email or SMS.
3.1.8 Detailed invoice for Customer and Seller -
The system shall display detailed invoice for current order once it is conrmed. The
system shall allow user to print the invoice. The system shall display detailed information
of seller's detail to customer as well as customer's detail to seller.
3.1.9 Provide shopping cart facility -
The system shall provide shopping cart during online purchase. The system shall allow
user to add/remove products in the shopping cart. Later customer can conrm orders for
purchase.
3.1.10 Online tracking of shipments -
The system shall allow user to enter the order information for tracking. The system shall
display the current tracking information about the order The system noties seller about
delivery of product to the consumer.
3.1.11 Allow multiple payment methods -
The system shall display available payment methods for payment. The system shall allow
user to select the payment method for order.
3.1.12 Provide Customer Support. -
The system shall provide online help, FAQ's customer support, and sitemap options for
customer support. The system shall allow user to select the support type he wants. The
system shall allow user to enter the customer and product information for the support.
The system shall display user contact of seller and Amazon support desk The system shall
display the online help upon request. The system shall display the FAQ's upon request.
10
3.1.6 Provide personalized prole -
The seller's and customer's prole contain all details of seller and customer respectively
like contact, location, address and seller's license. To display both the active and com-
pleted order history in the customer prole. To allow user to select the order from the
order history and detailed information. To display the most frequently searched items by
the user in the prole. To help seller keep list of products and its information in its prole.
3.1.7 Move transaction money and details to Prole -
Safe transfer of money into seller's bank account after successful transaction of money.
Add details of transfer of money to company's selling and purchasing events logs and
database. Send an order conrmation to the user and seller about the purchase through
email or SMS.
3.1.8 Detailed invoice for Customer and Seller -
The system shall display detailed invoice for current order once it is conrmed. The
system shall allow user to print the invoice. The system shall display detailed information
of seller's detail to customer as well as customer's detail to seller.
3.1.9 Provide shopping cart facility -
The system shall provide shopping cart during online purchase. The system shall allow
user to add/remove products in the shopping cart. Later customer can conrm orders for
purchase.
3.1.10 Online tracking of shipments -
The system shall allow user to enter the order information for tracking. The system shall
display the current tracking information about the order The system noties seller about
delivery of product to the consumer.
3.1.11 Allow multiple payment methods -
The system shall display available payment methods for payment. The system shall allow
user to select the payment method for order.
3.1.12 Provide Customer Support. -
The system shall provide online help, FAQ's customer support, and sitemap options for
customer support. The system shall allow user to select the support type he wants. The
system shall allow user to enter the customer and product information for the support.
The system shall display user contact of seller and Amazon support desk The system shall
display the online help upon request. The system shall display the FAQ's upon request.
10
3.2 Non-Functional Requirements: 3 SPECIFIC REQUIREMENTS
3.2 Non-Functional Requirements:
3.2.1 Performance:
The product shall be based on web and has to be run from a web server. The product shall
take initial load time depending on internet connection strength which also depends on
the media from which the product is run. The performance shall depend upon hardware
components of the client/customer.
3.2.2 Security:
Data Transfer:
The system shall use secure sockets in all transactions that include any condential cus-
tomer information. The system shall automatically log out all customers after a period
of inactivity. The system shall conrm all transactions with the customer's web browser.
The system shall not leave any cookies on the customer's computer containing the user's
password or condential information.
Data Storage:
The customer's web browser shall never display a customer's password. It shall always
be echoed with special characters representing typed characters. The customer's web
browser shall never display a customer's credit card number after retrieving from the
database. It shall always be shown with just the last 4 digits of the credit card number.
The system's back-end servers shall never display a customer's password. The customer's
password may be reset but never shown. The system's back-end servers shall only be
accessible to authenticated administrators. The system's back-end databases shall be en-
crypted and within company's perimeter.
3.2.3 Reliability:
The system provides storage of all databases on redundant computers with automatic
switchover. The reliability of the overall program depends on the reliability of the separate
components. The main pillar of reliability of the system is the backup of the database
which is continuously maintained and updated to reect the most recent changes.
3.2.4 Safety:
It is the state of being "safe", the condition of being protected against physical, social,
spiritual, nancial, political, emotional, occupational, psychological, educational or other
types or consequences of failure, damage, error, accidents, harm or any other event which
could be considered non-desirable. This can take the form of being protected from the
event or from exposure to something that causes health or economical losses. It can
include protection of people or of possessions.
3.2.5 Maintainability:
A commercial database is used for maintaining the database and the application server
takes care of the site. In case of a failure, a re-initialization of the program will be done.
Also the software design is being done with modularity in mind so that maintainability
can be done efciently.
11
3.2 Non-Functional Requirements:
3.2.1 Performance:
The product shall be based on web and has to be run from a web server. The product shall
take initial load time depending on internet connection strength which also depends on
the media from which the product is run. The performance shall depend upon hardware
components of the client/customer.
3.2.2 Security:
Data Transfer:
The system shall use secure sockets in all transactions that include any condential cus-
tomer information. The system shall automatically log out all customers after a period
of inactivity. The system shall conrm all transactions with the customer's web browser.
The system shall not leave any cookies on the customer's computer containing the user's
password or condential information.
Data Storage:
The customer's web browser shall never display a customer's password. It shall always
be echoed with special characters representing typed characters. The customer's web
browser shall never display a customer's credit card number after retrieving from the
database. It shall always be shown with just the last 4 digits of the credit card number.
The system's back-end servers shall never display a customer's password. The customer's
password may be reset but never shown. The system's back-end servers shall only be
accessible to authenticated administrators. The system's back-end databases shall be en-
crypted and within company's perimeter.
3.2.3 Reliability:
The system provides storage of all databases on redundant computers with automatic
switchover. The reliability of the overall program depends on the reliability of the separate
components. The main pillar of reliability of the system is the backup of the database
which is continuously maintained and updated to reect the most recent changes.
3.2.4 Safety:
It is the state of being "safe", the condition of being protected against physical, social,
spiritual, nancial, political, emotional, occupational, psychological, educational or other
types or consequences of failure, damage, error, accidents, harm or any other event which
could be considered non-desirable. This can take the form of being protected from the
event or from exposure to something that causes health or economical losses. It can
include protection of people or of possessions.
3.2.5 Maintainability:
A commercial database is used for maintaining the database and the application server
takes care of the site. In case of a failure, a re-initialization of the program will be done.
Also the software design is being done with modularity in mind so that maintainability
can be done efciently.
11
3.3 Constraints: 3 SPECIFIC REQUIREMENTS
3.3 Constraints:
Limited numbers search queries for the users.Servers incapable of handling high
trafc burst.
The actual product might differ from its display image. Uniform quality of service
is not ensured.
It cannot ensure the reliability of the review.
The User and Seller must have conrmed User ID and Seller ID respectively.
3.4 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.5 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, Google Chrome ,Mozilla Firefox etc.
3.6 Interface Requirements:
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 cus-
tomer's Email address
3.7 External user Requirement:
3.7.1 Hardware Interface
Device should be enabled with Internet.
3.7.2 Software interface
The user's browser should be HTML5 compatible for a satisfactory user experience.
12
3.3 Constraints:
Limited numbers search queries for the users.Servers incapable of handling high
trafc burst.
The actual product might differ from its display image. Uniform quality of service
is not ensured.
It cannot ensure the reliability of the review.
The User and Seller must have conrmed User ID and Seller ID respectively.
3.4 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.5 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, Google Chrome ,Mozilla Firefox etc.
3.6 Interface Requirements:
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 cus-
tomer's Email address
3.7 External user Requirement:
3.7.1 Hardware Interface
Device should be enabled with Internet.
3.7.2 Software interface
The user's browser should be HTML5 compatible for a satisfactory user experience.
12
4 DESIGN CONSTRAINTS
Chapter 4
4 Design Constraints
There are few constraints that the system should follow. They are:
1. All the inputs should be checked for validation and messages should be given for
the improper data.The invalid data are to be ignored and error messages should be
given.
2. Details provided by the vendor during his sign up should be stored in database.
3. While adding the products to the system, mandatory elds must be checked for vali-
dation whether the vendor has lled appropriate data in these mandatory elds.If not,
proper error message should be displayed or else the data is to be stored in database
for later retrieval.
4. All mandatory elds should be lled by customer, while buying the items from the
cart.
4.1 Standard Development
Tools The system shall be built using a standard web page development tool that conforms
to either IBM's CUA standards or Microsoft's GUI standards like HTML, XML etc.
4.2 Web Based Product
There are no memory requirements The computers must be equipped with web browsers
such as Internet explorer. The product must be stored in such a way that allows the client
easy access to it. Response time for loading the product should take no longer than ve
minutes. A general knowledge of basic computer skills is required to use the product .
4.3 Payment options in Online Shoppingg
Online shoppers commonly use a credit card to make payments, however some systems
enable users to create accounts and pay by alternative means, such as:
Billing to mobile phones and landlines
Cash on delivery (C.O.D., oered by very few online stores)
Cheque
Debit card Direct debit in some countries
Electronic money of various types
Gift cards
Postal money order
Wire transfer/delivery on payment
13
Chapter 4
4 Design Constraints
There are few constraints that the system should follow. They are:
1. All the inputs should be checked for validation and messages should be given for
the improper data.The invalid data are to be ignored and error messages should be
given.
2. Details provided by the vendor during his sign up should be stored in database.
3. While adding the products to the system, mandatory elds must be checked for vali-
dation whether the vendor has lled appropriate data in these mandatory elds.If not,
proper error message should be displayed or else the data is to be stored in database
for later retrieval.
4. All mandatory elds should be lled by customer, while buying the items from the
cart.
4.1 Standard Development
Tools The system shall be built using a standard web page development tool that conforms
to either IBM's CUA standards or Microsoft's GUI standards like HTML, XML etc.
4.2 Web Based Product
There are no memory requirements The computers must be equipped with web browsers
such as Internet explorer. The product must be stored in such a way that allows the client
easy access to it. Response time for loading the product should take no longer than ve
minutes. A general knowledge of basic computer skills is required to use the product .
4.3 Payment options in Online Shoppingg
Online shoppers commonly use a credit card to make payments, however some systems
enable users to create accounts and pay by alternative means, such as:
Billing to mobile phones and landlines
Cash on delivery (C.O.D., oered by very few online stores)
Cheque
Debit card Direct debit in some countries
Electronic money of various types
Gift cards
Postal money order
Wire transfer/delivery on payment
13
4.3 Payment options in Online Shoppingg 4 DESIGN CONSTRAINTS
Some sites will not accept international credit cards, some require both the purchaser's
billing address and shipping address to be in the same country in 19 which site does its
business, and still other sites allow customers from anywhere to send gifts anywhere. The
nancial part of a transaction might be processed in real time (for example, letting the
consumer know their credit card was declined before they log o), or might be done later
as part of the fulllment process.
14
Some sites will not accept international credit cards, some require both the purchaser's
billing address and shipping address to be in the same country in 19 which site does its
business, and still other sites allow customers from anywhere to send gifts anywhere. The
nancial part of a transaction might be processed in real time (for example, letting the
consumer know their credit card was declined before they log o), or might be done later
as part of the fulllment process.
14
5 PROS, CONS, CHALLENGES & FUTURE
Chapter 5
5 Pros, Cons, Challenges & Future
5.1 Advantages of online shopping
Due to rapid growth of technology, business organizations have switched over from the
traditional method of selling goods to electronic method of selling goods. Business orga-
nizations use internet as a main vehicle to conduct commercial transactions.
1. Convenience of online shopping { Customers can purchase items from the comfort
of their own homes or work place. Shopping is made easier and convenient for the
customer through internet. It is also easy to cancel the transactions.
2. No pressure shopping { Generally, in physical stores, the sales representatives try
to in uence the buyers to buy the product. There can be some kind of pressure,
whereas the customers are not pressurized in any way in online stores.
3. Online shopping saves time { Customers do not have to stand in queues in cash
counters to pay for the products that have been purchased by them. They can shop
from their home or work place and do not have to spend time traveling. The cus-
tomers can also look for the products that are required by them by entering the key
words or using search engines.
4. Online tracking { Online consumers can track the order status and delivery status
tracking of shipping is also available.
5. Online shopping saves money { To attract customers to shop online, e-tailers and
marketers oer discounts to the customers. Due to elimination of maintenance,
real- estate cost, the retailers are able to sell the products with attractive discounts
through online. Sometimes, large online shopping sites oer store comparison.
5.2 Disadvantages of online shopping
The major disadvantages of online shopping are as follows.
1. Delay in delivery { Long duration and lack of proper inventory management result
in delays in shipment. Though the duration of selecting, buying and paying for
an online product may not take more than 15 minutes; the delivery of the product
to customer' s doorstep takes about 1-3 weeks. This frustrates the customer and
prevents them from shopping online.
2. Lack of signicant discounts in online shops { Physical stores oer discounts to cus-
tomers and attract them so this makes it dicult for e-tailers to compete with the oine
platforms.
3. Lack of touch and feel of merchandise in online shopping { Lack of touch-feel-try
creates concerns over the quality of the product on oer. Online shopping is not quite
suitable for clothes as the customers cannot try them on.
4. Lack of interactivity in online shopping { Physical stores allow price negotiations
between buyers and the seller. The show room sales attendant representatives pro-
vide personal attention to customers and help them in purchasing goods.
15
Chapter 5
5 Pros, Cons, Challenges & Future
5.1 Advantages of online shopping
Due to rapid growth of technology, business organizations have switched over from the
traditional method of selling goods to electronic method of selling goods. Business orga-
nizations use internet as a main vehicle to conduct commercial transactions.
1. Convenience of online shopping { Customers can purchase items from the comfort
of their own homes or work place. Shopping is made easier and convenient for the
customer through internet. It is also easy to cancel the transactions.
2. No pressure shopping { Generally, in physical stores, the sales representatives try
to in uence the buyers to buy the product. There can be some kind of pressure,
whereas the customers are not pressurized in any way in online stores.
3. Online shopping saves time { Customers do not have to stand in queues in cash
counters to pay for the products that have been purchased by them. They can shop
from their home or work place and do not have to spend time traveling. The cus-
tomers can also look for the products that are required by them by entering the key
words or using search engines.
4. Online tracking { Online consumers can track the order status and delivery status
tracking of shipping is also available.
5. Online shopping saves money { To attract customers to shop online, e-tailers and
marketers oer discounts to the customers. Due to elimination of maintenance,
real- estate cost, the retailers are able to sell the products with attractive discounts
through online. Sometimes, large online shopping sites oer store comparison.
5.2 Disadvantages of online shopping
The major disadvantages of online shopping are as follows.
1. Delay in delivery { Long duration and lack of proper inventory management result
in delays in shipment. Though the duration of selecting, buying and paying for
an online product may not take more than 15 minutes; the delivery of the product
to customer' s doorstep takes about 1-3 weeks. This frustrates the customer and
prevents them from shopping online.
2. Lack of signicant discounts in online shops { Physical stores oer discounts to cus-
tomers and attract them so this makes it dicult for e-tailers to compete with the oine
platforms.
3. Lack of touch and feel of merchandise in online shopping { Lack of touch-feel-try
creates concerns over the quality of the product on oer. Online shopping is not quite
suitable for clothes as the customers cannot try them on.
4. Lack of interactivity in online shopping { Physical stores allow price negotiations
between buyers and the seller. The show room sales attendant representatives pro-
vide personal attention to customers and help them in purchasing goods.
15
5.3 Challenges in Online Shopping 5 PROS, CONS, CHALLENGES & FUTURE
5.3 Challenges in Online Shopping
Here are the top 10 most common challenges:
1. Finding the right products to sell
2. Attracting the perfect customer
3. Generating targeted trac
4. Capturing quality leads
5. Nurturing the ideal prospects
6. Converting shoppers into paying customers
7. Retaining customers
8. Achieving protable long-term growth
9. Choosing the right technology & partners
10. Attracting and hiring the right people to make it all happen
5.4 Future of Online Shopping
Computing power has increased exponentially in the last decade, to the point where big
data and machine learning have come together to make the customer experience richer
and innitely more simple.
People will be able to buy things online without a card number or authentica- tion.The
boundaries between channels associated with online commerce will begin to blur.Fraud
prevention and detection will be completely automated.Retailers will escape the liabil-
ity for fraud.Payments will be all about what the customer wants.Payments will be per-
sonalized for the customer.Same-day shipping will be everywhere.Merchants will need
automation to ght fraud.
16
5.3 Challenges in Online Shopping
Here are the top 10 most common challenges:
1. Finding the right products to sell
2. Attracting the perfect customer
3. Generating targeted trac
4. Capturing quality leads
5. Nurturing the ideal prospects
6. Converting shoppers into paying customers
7. Retaining customers
8. Achieving protable long-term growth
9. Choosing the right technology & partners
10. Attracting and hiring the right people to make it all happen
5.4 Future of Online Shopping
Computing power has increased exponentially in the last decade, to the point where big
data and machine learning have come together to make the customer experience richer
and innitely more simple.
People will be able to buy things online without a card number or authentica- tion.The
boundaries between channels associated with online commerce will begin to blur.Fraud
prevention and detection will be completely automated.Retailers will escape the liabil-
ity for fraud.Payments will be all about what the customer wants.Payments will be per-
sonalized for the customer.Same-day shipping will be everywhere.Merchants will need
automation to ght fraud.
16
6 SYSTEM DESIGN SPECIFICATION
Chapter 6
6 System Design Specication
6.1 UML Diagrams
UML is a standard language for specifying, visualizing, constructing, and documenting
the artifacts of software systems. UML diagrams are not only made for developers but
also for business users, common people, and anybody interested to understand the system.
The system can be a software or non-software system. Thus it must be clear that UML
is not a development method rather it companies with processes to make it a successful
system. UML is a modeling language used to model software and non-software systems.
Although UML is used for non-software systems, the emphasis is on modeling OO
software applications. Most of the UML diagrams discussed so far are used to model
different aspects such as static, dynamic, etc. Now whatever be the aspect, the artifacts
are nothing but objects. If we look into class diagram, object diagram, collaboration
diagram, activity diagrams all would basically be designed based on the objects.
6.1.1 Use Case Diagram:
A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the dierent use cases in which the
user is involved. A use case diagram can identify the dierent types of users of a system
and the dierent use cases and will often be accompanied by other types of diagrams as
well.
Figure 1: Use Case Diagram
17
Chapter 6
6 System Design Specication
6.1 UML Diagrams
UML is a standard language for specifying, visualizing, constructing, and documenting
the artifacts of software systems. UML diagrams are not only made for developers but
also for business users, common people, and anybody interested to understand the system.
The system can be a software or non-software system. Thus it must be clear that UML
is not a development method rather it companies with processes to make it a successful
system. UML is a modeling language used to model software and non-software systems.
Although UML is used for non-software systems, the emphasis is on modeling OO
software applications. Most of the UML diagrams discussed so far are used to model
different aspects such as static, dynamic, etc. Now whatever be the aspect, the artifacts
are nothing but objects. If we look into class diagram, object diagram, collaboration
diagram, activity diagrams all would basically be designed based on the objects.
6.1.1 Use Case Diagram:
A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the dierent use cases in which the
user is involved. A use case diagram can identify the dierent types of users of a system
and the dierent use cases and will often be accompanied by other types of diagrams as
well.
Figure 1: Use Case Diagram
17
6.1 UML Diagrams 6 SYSTEM DESIGN SPECIFICATION
6.1.2 Activity Diagram:
Activity diagrams are graphical representations of work ows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unied Modeling Lan-
guage, activity diagrams are intended to model both computational and organiza- tional
processes (i.e., work ows), as well as the data ows intersecting with the related activities.
Although activity diagrams primarily show the overall ow of control, they can also include
elements showing the ow of data between activities through one or more data store.
Figure 2: Activity Diagram 1Figure 3: Activity Diagram 2
18
6.1.2 Activity Diagram:
Activity diagrams are graphical representations of work ows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unied Modeling Lan-
guage, activity diagrams are intended to model both computational and organiza- tional
processes (i.e., work ows), as well as the data ows intersecting with the related activities.
Although activity diagrams primarily show the overall ow of control, they can also include
elements showing the ow of data between activities through one or more data store.
Figure 2: Activity Diagram 1Figure 3: Activity Diagram 2
18
6.1 UML Diagrams 6 SYSTEM DESIGN SPECIFICATION
6.1.3 Class Diagram:
In software engineering, a class diagram in the Unied Modeling Language (UML) is a
type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among
objects. The class diagram is the main building block of object-oriented modelling. It
is used for general conceptual modelling of the systematic of the application, and for
detailed modelling translating the models into programming code.
Class diagrams can also be used for data modeling. The classes in a class diagram
represent both the main elements, interactions in the application, and the classes to be
programmed.
Figure 4: Class Diagram
6.1.4 State Chart Diagram:
It illustrates the in-trusting events and state of an object and behaviors of an object is
reaction to an event. Transaction shows as allows labeled with theirs event. It is included
with initial pseudo state and nal end state.
The state chart diagram of Online shopping website has 5 stages: Idle, New sale, Get
specication, Prompt Error and generate receipt. In each state the system interacts with
the user and get desired output based on the given inputs.
19
6.1.3 Class Diagram:
In software engineering, a class diagram in the Unied Modeling Language (UML) is a
type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among
objects. The class diagram is the main building block of object-oriented modelling. It
is used for general conceptual modelling of the systematic of the application, and for
detailed modelling translating the models into programming code.
Class diagrams can also be used for data modeling. The classes in a class diagram
represent both the main elements, interactions in the application, and the classes to be
programmed.
Figure 4: Class Diagram
6.1.4 State Chart Diagram:
It illustrates the in-trusting events and state of an object and behaviors of an object is
reaction to an event. Transaction shows as allows labeled with theirs event. It is included
with initial pseudo state and nal end state.
The state chart diagram of Online shopping website has 5 stages: Idle, New sale, Get
specication, Prompt Error and generate receipt. In each state the system interacts with
the user and get desired output based on the given inputs.
19
6.1 UML Diagrams 6 SYSTEM DESIGN SPECIFICATION
Figure 5: State Chart Diagram
6.1.5 Sequence Diagram:
A sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged be-
tween the objects needed to carry out the functionality of the scenario. Sequence diagrams
are typically associated with use case realizations in the Logical View of the system under
development. Sequence diagrams are sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), dierent processes or
objects that live simultaneously, and, as horizontal arrows, the messages exchanged be-
tween them, in the order in which they occur. This allows the specication of simple
runtime scenarios in a graphical manner.
20
Figure 5: State Chart Diagram
6.1.5 Sequence Diagram:
A sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged be-
tween the objects needed to carry out the functionality of the scenario. Sequence diagrams
are typically associated with use case realizations in the Logical View of the system under
development. Sequence diagrams are sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), dierent processes or
objects that live simultaneously, and, as horizontal arrows, the messages exchanged be-
tween them, in the order in which they occur. This allows the specication of simple
runtime scenarios in a graphical manner.
20
6.1 UML Diagrams 6 SYSTEM DESIGN SPECIFICATION
Figure 6: Sequence Diagram
6.1.6 Component Diagram:
A component represents a modular part of a system, that encapsulates it contents and
whose manifestation is replaced with in its environment. A component denes its behav-
iors in terms of provide and required interfaces. Here the four components are customer,
Product, Order and Account.
Figure 7: Component Diagram
21
Figure 6: Sequence Diagram
6.1.6 Component Diagram:
A component represents a modular part of a system, that encapsulates it contents and
whose manifestation is replaced with in its environment. A component denes its behav-
iors in terms of provide and required interfaces. Here the four components are customer,
Product, Order and Account.
Figure 7: Component Diagram
21
6.1 UML Diagrams 6 SYSTEM DESIGN SPECIFICATION
6.1.7 Deployement Diagram:
A deployment shows the assignment of concrete artifacts to computational nodes. It
shows the deployment of software elements to the physical architecture, and the com-
munication. Deployment diagrams are useful to communicate the physical and deploy-
ment architecture. In the deployment diagram the object reference in component diagram
is also included the deployment diagram. In this authority and system admin, interface
through the people. It is the process of installing the program.
Figure 8: Deployement Diagram
6.1.8 ER Diagram:
The purpose of draw this diagram to show the relationship among the objects and personal
attributes that belong to them. Below is diagram where Customer can places many order
(one to one relationship) as they wish when in Online Shopping Store and vice versa. In
order to have a list of order, we must have at least one customer. There may be situation
in which placement order action is not necessary from the customer. Order can contains
many order items details in the list and vice versa is part of the order. In order to have an
order items details, we must have at least one order taken from the customer.Visitors can
view many categories as they wish in Online Shopping Store. Each category will contains
many product (one to many relationship). The product will have the order items details.
22
6.1.7 Deployement Diagram:
A deployment shows the assignment of concrete artifacts to computational nodes. It
shows the deployment of software elements to the physical architecture, and the com-
munication. Deployment diagrams are useful to communicate the physical and deploy-
ment architecture. In the deployment diagram the object reference in component diagram
is also included the deployment diagram. In this authority and system admin, interface
through the people. It is the process of installing the program.
Figure 8: Deployement Diagram
6.1.8 ER Diagram:
The purpose of draw this diagram to show the relationship among the objects and personal
attributes that belong to them. Below is diagram where Customer can places many order
(one to one relationship) as they wish when in Online Shopping Store and vice versa. In
order to have a list of order, we must have at least one customer. There may be situation
in which placement order action is not necessary from the customer. Order can contains
many order items details in the list and vice versa is part of the order. In order to have an
order items details, we must have at least one order taken from the customer.Visitors can
view many categories as they wish in Online Shopping Store. Each category will contains
many product (one to many relationship). The product will have the order items details.
22
6.2 User Interface 6 SYSTEM DESIGN SPECIFICATION
Figure 9: ER Diagram
6.2 User Interface
1. Create Vendor
23
Figure 9: ER Diagram
6.2 User Interface
1. Create Vendor
23
6.2 User Interface 6 SYSTEM DESIGN SPECIFICATION
Figure 10: Create Vendor
2. Create Product
Figure 11: Create Product
3. Product List
24
Figure 10: Create Vendor
2. Create Product
Figure 11: Create Product
3. Product List
24
6.2 User Interface 6 SYSTEM DESIGN SPECIFICATION
Figure 12: Product List
4. Bill Creation
Figure 13: Bill Creation
5. Payment Mode
Figure 14: Payment Mode
6. Purchase Analysis
25
Figure 12: Product List
4. Bill Creation
Figure 13: Bill Creation
5. Payment Mode
Figure 14: Payment Mode
6. Purchase Analysis
25
6.2 User Interface 6 SYSTEM DESIGN SPECIFICATION
Figure 15: Purchase Analysis
26
Figure 15: Purchase Analysis
26
7 TESTING
Chapter 7
7 Testing
Software Testing is an empirical investigation conducted to provide stakeholders with
information about the quality of the product or service under test, with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the
risks at implementation of the software. Test techniques include, but are not limited to,
the process of executing a program or application with the intent of nding software
bugs. It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided
its design and development, so that it works as expected and can be implemented with the
same characteristics.
Software Testing, depending on the testing method employed, can be implemented at
any time in the development process, however the most test effort is employed after the
requirements have been dened and coding process has been completed.
7.1 Unit Testing
The primary goal of unit testing is to take the smallest piece of testable software in the
application, isolate it from the remainder of the code, and determine whether it behaves
exactly as you expect. Each unit is tested separately before integrating them into modules
to test the interfaces between modules. Unit tests are typically written and run by software
developers to ensure that code meets it design and behaves as intended. Its implementa-
tion can vary from being very manual (pencil and paper) to being formalized as part of
build automation.
7.2 Integration Testing
Integration testing, also known as integration and testing (I&T), is a software develop-
ment process which program units are combined and tested as groups in multiple ways.
Integration testing can expose problems with the interfaces among program components
before trouble occurs in real-world program execution. There are two major ways of
carrying out an integration test, called the bottom-up method and the top-down method.
Bottom-up integration testing begins with unit testing, followed by tests of progressively
higher-level combinations of units called modules or builds. In top-down integration test-
ing, the highest-level modules are tested rst and progressively lower-level modules are
tested after that. In a comprehensive software development environment, bottom-up test-
ing is usually done rst, followed by top-down testing.
7.3 Validation Testing
At the validation level, testing focuses on user visible actions and user recognizable output
from the system. Validations testing is said to be successful when software functions in a
manner that can be reasonably expected by the customer. Two types of validation testing
Alpha testing is simulated or actual operational testing by potential users/customers
or an independent test team at the developers' site. Alpha testing is often employed
27
Chapter 7
7 Testing
Software Testing is an empirical investigation conducted to provide stakeholders with
information about the quality of the product or service under test, with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the
risks at implementation of the software. Test techniques include, but are not limited to,
the process of executing a program or application with the intent of nding software
bugs. It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided
its design and development, so that it works as expected and can be implemented with the
same characteristics.
Software Testing, depending on the testing method employed, can be implemented at
any time in the development process, however the most test effort is employed after the
requirements have been dened and coding process has been completed.
7.1 Unit Testing
The primary goal of unit testing is to take the smallest piece of testable software in the
application, isolate it from the remainder of the code, and determine whether it behaves
exactly as you expect. Each unit is tested separately before integrating them into modules
to test the interfaces between modules. Unit tests are typically written and run by software
developers to ensure that code meets it design and behaves as intended. Its implementa-
tion can vary from being very manual (pencil and paper) to being formalized as part of
build automation.
7.2 Integration Testing
Integration testing, also known as integration and testing (I&T), is a software develop-
ment process which program units are combined and tested as groups in multiple ways.
Integration testing can expose problems with the interfaces among program components
before trouble occurs in real-world program execution. There are two major ways of
carrying out an integration test, called the bottom-up method and the top-down method.
Bottom-up integration testing begins with unit testing, followed by tests of progressively
higher-level combinations of units called modules or builds. In top-down integration test-
ing, the highest-level modules are tested rst and progressively lower-level modules are
tested after that. In a comprehensive software development environment, bottom-up test-
ing is usually done rst, followed by top-down testing.
7.3 Validation Testing
At the validation level, testing focuses on user visible actions and user recognizable output
from the system. Validations testing is said to be successful when software functions in a
manner that can be reasonably expected by the customer. Two types of validation testing
Alpha testing is simulated or actual operational testing by potential users/customers
or an independent test team at the developers' site. Alpha testing is often employed
27
7.4 Performance Testing 7 TESTING
for off-the-shelf software as a form of internal acceptance testing, before the soft-
ware goes to beta testing.
Beta testing comes after alpha testing. Versions of the software, known as beta
version, are released to a limited audience outside of the programming team. The
software is released to groups of people so that further testing can ensure the product
has few faults or bugs. Sometimes, beta versions are made available to the open
public to increase the feedback eld to a maximal number of future users
7.4 Performance Testing
This will be performed to test the entire system to see whether all driving requirements are
satised. Allowing multiple users log into the system and perform the operations at the
same time using the JMeter testing tool will do this. This test veries that the components
of the systems meet the stated requirements for speed.
The following components of the system would be analyzed for performance:
Buying: Includes browsing the catalog, selecting a product, add to shopping cart,
checkout, enter personal details and place order.
Searching for a Product.
Getting Product recommendation
Using JMETER tool, approximately 100 concurrent virtual users with a minimum of 50
requests per user will be inputted to calculate the response times for each of the above
components. The above tests would be done in different environments like:
Local connection of 54Mbps
LAN connection of 100Mbps
Wired connection
28
for off-the-shelf software as a form of internal acceptance testing, before the soft-
ware goes to beta testing.
Beta testing comes after alpha testing. Versions of the software, known as beta
version, are released to a limited audience outside of the programming team. The
software is released to groups of people so that further testing can ensure the product
has few faults or bugs. Sometimes, beta versions are made available to the open
public to increase the feedback eld to a maximal number of future users
7.4 Performance Testing
This will be performed to test the entire system to see whether all driving requirements are
satised. Allowing multiple users log into the system and perform the operations at the
same time using the JMeter testing tool will do this. This test veries that the components
of the systems meet the stated requirements for speed.
The following components of the system would be analyzed for performance:
Buying: Includes browsing the catalog, selecting a product, add to shopping cart,
checkout, enter personal details and place order.
Searching for a Product.
Getting Product recommendation
Using JMETER tool, approximately 100 concurrent virtual users with a minimum of 50
requests per user will be inputted to calculate the response times for each of the above
components. The above tests would be done in different environments like:
Local connection of 54Mbps
LAN connection of 100Mbps
Wired connection
28
Download
Download Slideshow Get the original presentation fileQuick Actions
Statistics
- Views 5,611
- Slides 29
- Favorites 2
- Age 2426 days
Related Slideshows
11
8-top-ai-courses-for-customer-support-representatives-in-2025.pptx
JeroenErne2
46 views
10
7-essential-ai-courses-for-call-center-supervisors-in-2025.pptx
JeroenErne2
46 views
13
25-essential-ai-courses-for-user-support-specialists-in-2025.pptx
JeroenErne2
37 views
11
8-essential-ai-courses-for-insurance-customer-service-representatives-in-2025.pptx
JeroenErne2
34 views
21
Know for Certain
DaveSinNM
21 views
17
PPT OPD LES 3ertt4t4tqqqe23e3e3rq2qq232.pptx
novasedanayoga46
26 views