Running head: SOFTWARE REQUIREMENTS SPECIFICATION 1

Amazon Software Requirements Specification Documentation

Arlecia Johnson

SWEN 645

06/23/2020
SOFTWARE REQUIREMENTS SPECIFICATION 2

Table of Contents
1. INTRODUCTION....................................................................................................................4
Overview......................................................................................................................................4
Purpose.........................................................................................................................................4
Scope............................................................................................................................................4
Software Requirement Specification (SRS) Outline....................................................................4
Definitions....................................................................................................................................5
References....................................................................................................................................6
2. OVERALL DESCRIPTION....................................................................................................7
Product function...........................................................................................................................7
Product perspective......................................................................................................................7
User classes and characteristics...................................................................................................7
Documentation of the user...........................................................................................................8
Design Implementation................................................................................................................8
Software and hardware requirements...........................................................................................8
Decencies and assumptions..........................................................................................................9
3. SPECIFIC REQUIREMENTS...............................................................................................10
Introduction................................................................................................................................10
Use-Case Reports.......................................................................................................................10
Functional requirements.........................................................................................................10
Search functionality................................................................................................................10
Show similar items.................................................................................................................10
Customized user content........................................................................................................10
Interactive system...................................................................................................................11
Customized profile.................................................................................................................11
Shopping cart, favorite and wish list features........................................................................11
Multiple payment methods.....................................................................................................11
Product tracking.....................................................................................................................12
Non-functional requirements.....................................................................................................12
Maintenance...........................................................................................................................12
Performance............................................................................................................................12
Security...................................................................................................................................12
SOFTWARE REQUIREMENTS SPECIFICATION 3

Reliability...............................................................................................................................12
Constraints.................................................................................................................................12
4. SUPPORTING INFORMATION..........................................................................................13
User interface.............................................................................................................................13
Customer Interface.................................................................................................................13
Customer Login Interface.......................................................................................................14
Use Case Diagram......................................................................................................................14
Sequence Diagrams....................................................................................................................15
User Login..............................................................................................................................15
Search.....................................................................................................................................16
Adding an item to cart............................................................................................................17
SOFTWARE REQUIREMENTS SPECIFICATION 4

Version Control

Version Author Date Changes

1 Arlecia Johnson 06/15/2020 First Draft

2 Arlecia Johnson 06/16/2020 Submitted

3 Arlecia Johnson 07/17/2020 Revised

1. INTRODUCTION
Overview
The primary purpose of this document is to collect and analyze of all ideas that are
considered to define a system and its requirements for consumers. Therefore, this system
requirement specification document aims to provide a detailed outline of our software product,
its goals, and its parameters. To develop an online platform, sound decision making is very vital.
Also, the job requires experts in the field of technology to be undertaken. Excellent programming
of the site by the software engineers make the site highly responsive, and it also experiences few
instances of technical errors. This makes the website the most favorable online shopping store
for most customers around the world. The key features and functions of the system are explained
to enable system developers to meet all the requirements as documented. Also, the system
functionality is explained in a simple language to enable users without prior knowledge of an
online store to use the system without challenges.

Purpose
Amazon.com is an e-commerce site that enables customers to purchase services and
goods electronically without time and distance barriers. A rapid expansion of e-commerce has
been experienced over the past five years and is expected to continue at the same rate. Amazon is
the US’s biggest online store for books, electronics, mobile phones, jewelry, and home
appliances. It offers a wide selection of goods at the lowest prices. Payment options accepted by
Amazon include credit cards, debit cards, and more.
SOFTWARE REQUIREMENTS SPECIFICATION 5

Scope
E-commerce stands for any commercial activity or business type that involves the
internet to transact or transfer information. It covers a wide range of business types from retail
sites through music sites to businesses exchanging services and goods between corporations. E-
commerce is one of the important emerging aspects of the internet.

Software Requirement Specification (SRS) Outline

This document describes the project’s hardware and software, its user interface, and the
target audience. The document defines how our audience, client, and team see the product and
the product’s functionality. Furthermore, the SRS helps the developer and the designer to assist
in the delivery of the software lifecycle.

Abbreviations

DFD Data Flow Diagram

SRS System Requirements Specification
FAQ Frequently Asked Questions
UI User Interface
CRM Customer Relationship Management

Definitions
i. Customer/End user- This is the one who visits the website and purchases services or
goods from the ones added by the sellers.
ii. Product- This is the goods or services offered to customers. The price for a product can
be varied based on the marketing, and targeted segment. Each product offered for
purchase has a useful life after which its replacement is needed.
iii. Seller/vendor- These are the people who add their products to the websites for them to be
purchased by the end-users or customers. Vendors have higher privileges than customers,
for they can manage the goods added to the site.
iv. Administrators- These are the ones who add various categories of the products into the
website. They also administer the sellers or vendors.
SOFTWARE REQUIREMENTS SPECIFICATION 6

v. Order ID- this is a unique identification number found on every purchased and sold
product or item. It is used to track the record of the purchases performed on the site.
Order ID is generated by the system, and each item has a different Order ID from other
items.
vi. Seller ID- this is a unique identifier that is used to verify the seller. This allows the seller
to list the products or items that are available for sale.
vii. User ID- this is a unique ID generated during the time of signing up on the website. At
the time of login, one is prompted to fill in some information that is saved to the
company’s website; this helps the user to be able to login to the company’s website in the
future.
viii. Online discussion is when the data collected online is spread across various websites and
platforms for review by the people and reference purposes.
ix. Bank details- This is when the transaction amount is transferred back to the saved
accounts. This bank details are synchronized and securely saved at the backend
databases.
References
Checkpoints: Software Requirements Specification. (2020). Retrieved 7 June 2020, from
https://sceweb.uhcl.edu/helm/RationalUnifiedProcess/process/activity/chklists/ck_srs.htm

Davis, B. (2013). Mastering Software Project Requirements: A Framework for Successful

Planning, Development & Alignment (1st Ed.). (Ch 5) Plantation FL: J Ross Publishing.

Soares, H. A., & Moura, R. S. (2015, October). A methodology to guide writing Software
Requirements Specification document. In 2015 Latin American Computing Conference
(CLEI) (pp. 1-11). IEEE.
SOFTWARE REQUIREMENTS SPECIFICATION 7

2. OVERALL DESCRIPTION
Product function
1. Amazon always keeps focusing on the expansion of products and creating a new category
of products.

2. Dedication of appropriate offer zone and the deal of the day that attracts sufficient
attention of users.

3. Promotion and Ads activities motivate customers to shop online.

4. Order notification and delivery reports to the vendors and customers.

5. Provide a simple platform and interface that facilitate and makes the process of buying
and selling easy.

6. Tracking of pending deliveries and orders for both buyers and vendors.

7. Inclusion of smooth efficiency and functionality that adds the customer’s confidence.

Product perspective
Amazon’s e-commerce website has provided an excellent way of bringing customers and
vendors together to make business transactions efficiently and securely, irrespective of the
distance between the two parties. The website provides millions of products online. Each day,
Amazon gives offers on products based on the product’s category. Besides, amazon offers
recommendations for discounts on the products.

User classes and characteristics

Administrator- his or her primary responsibility is monitoring procedures and functions
in a platform. Therefore, it is the responsibility of the administrator to provide all information
concerning purchases to the concerned authorities in case of disputes between the vendors and
the buyers.

Customer- this is the user of the website who is intended to buy services or goods from
the seller via Amazon’s platform. To access the website, the user has to be verified and must
have a username and password to log into the website. The customer is regularly fed and updated
with the latest discounts and offers of his or her interest.
SOFTWARE REQUIREMENTS SPECIFICATION 8

Seller- a seller is a verified person who can sell his or her services and goods over the
website. The seller or vendor is responsible for setting the product’s prices, details, and quantity.
All the seller’s details are stored on the company’s database. Also, all the products which are
ready to be sold are listed under the sender.

User Documentation
Includes user related section topics
 Selection of the operator

 Payment making

 Submission of account detail

 Notifications

 Payment security

 Operator selection

 Contacting us

 User agreement

 Privacy policy

Design Implementation
The graphical user interface is implemented using CSS3, HTML5, bootstrap, and
JavaScript. Any other suitable software package such as Enterprise Java-Beans can be used.

Software and hardware requirements

Particulars Client system
Operating system Windows, Linux, Macintosh,
Android, iOS
Browser Internet Explorer, Safari, Opera,
Mozilla Firefox, Lynx

Decencies and assumptions

1. A reliable internet connection is mandatory.
SOFTWARE REQUIREMENTS SPECIFICATION 9

2. Customers must create an account if they do not have one before they make purchases.
3. Secure and updated internet browsers are highly recommended.
4. Customers must use one of the existing payment methods.
5. Buyers and sellers must verify their email address after creating a profile.
6. System users are encouraged to use strong passwords.

3. SPECIFIC REQUIREMENTS
Introduction
This section of Software Requirement Specification encompasses detailed requirements
of the software system that will enable system developers to meet those requirements, as well as
allowing efficient system testing. The application of use-case modeling captures the most crucial
requirements. Besides, the requirements that are not obtained use-case modeling will be outlined
in the Supplementary Specifications section.

Use-Case Reports
This section comprises of the functional and non-functional requirements of the Amazon
online store.

Functional requirements
The functional requirements for the online store are structured according to features
discussed in the product section. The features are further modeled into use case diagrams and
sequence diagrams which are included in the supporting information section.

1. Search functionality
A customer can select product category and search for it using the search toolbar, and the
matching products based on the user input will be displayed in the form of a list. When the user
input does not match any of the products, he will be notified that no matching product has been
found. Besides, customers will be able to navigate through many search results.
SOFTWARE REQUIREMENTS SPECIFICATION 10

2. Cart
The system provides an interface where sellers can add, edit, or remove products
using their customized profile.

3. View similar/frequently bought items

Based on the customer input, the system shows related products bought with higher
ratings by other users, thus giving a customer a wide variety of products they may
have an interest in. A customer will be able to view similar items that have been
frequently bought or viewed before and their prices.
SOFTWARE REQUIREMENTS SPECIFICATION 11

4. Product review feature

This feature enables a customer to rate a product and write a description of the bought
item.

5. Shopping cart
The system enables customers to add or remove items to a shopping cart and proceed
with payment.
SOFTWARE REQUIREMENTS SPECIFICATION 12

6. Multiple payment methods

The Amazon online store allows customers to purchase items through the use of
different online payment methods such as Gift card, checking account, credit cards,
and Amazon pay.

7. Customized user content

The system will use cookies to monitor customer search patterns, which are essential in
customizing the buyer homepage according to his or her most viewed or searched product
according to previous activities.
SOFTWARE REQUIREMENTS SPECIFICATION 13

8. Customized profile
The system offers different profiles for different system users: Customers, suppliers, and
the support. The customer profile stores the personal information about the customer, order
history, and transactions. The seller or supplier profile comprises of supplier’s personal
information, items posted, items sold, and transaction history. The support profile is a super user
and has more system privileges, such as making decisions based on disputes and responding to
queries.

Non-functional requirements
1. Maintenance
 The web server application is uptime throughout even when some system updates are
being made.

 Online database servers are redundant in case a failure occurs.

2. Performance
 All business activities are done online.

 The system is web-based, and different servers are used to serve different clients
depending on client requests.
 System performance may vary depending on customer and client hardware system
specifications such as speed and general system performance of personal computer as
well as the internet connection.

3. Security
 Secure sockets are used in all forms of transactions.

 The systems logs out a user after a period of inactivity.

 The system does not store cookies on the customer’s computer without permission.

4. Reliability
The online store system has redundant web servers, file storage, and databases to ensure
that it is uptime in case of failure in or other the servers. Besides, servers are in various locations
to improve reliability in case one region is affected.
SOFTWARE REQUIREMENTS SPECIFICATION 14

5. Constraints
 The system loads data slowly or fails to load data completely under poor internet
connection.
 Some products are overrated to attract and trick buyers.

 Sometimes reviews may not be reliable as they are based on personal experience.

4. SUPPORTING INFORMATION
User interface
Use interface includes default homepage, sign up, and login pages. The homepage comprises a
navigation bar, which as various categories of products, current deals, customer service, and
search input.

Customer Interface
The home page allows a user/customer to navigate the website.
SOFTWARE REQUIREMENTS SPECIFICATION 15

Customer Login Interface

Use Case Diagram

The use case diagrams for the online store illustrates the main actors, seller, and buyer, as well as
their relationships. User case diagrams in this software requirement specification depict the
interaction between users and systems.
SOFTWARE REQUIREMENTS SPECIFICATION 16

Sequence Diagrams
UML Sequence Diagrams in this documentation depict how interactions are carried out within
the system. The main sequence diagrams for this documentation are user login, search, and
adding an item to cart sequence diagrams.

User Login
The below image shows user login interface. The interface allows registered users to
login into the online store and access all features of a customer. The customer/user their enter
email or phone and password and access to the system is given after validation. If a customer
does not remember the password, he/she can rese by clicking forgot password link. If in any case
the user does not have an account, he/she can register by clicking the “Create your own Amazon
account” button.
SOFTWARE REQUIREMENTS SPECIFICATION 17

Search Functionality
A customer is able search for a product using the search toolbar, and the matching products
based on the user input will be displayed in the form of a list. Besides, customers will be able to
navigate through many search results.
SOFTWARE REQUIREMENTS SPECIFICATION 18

Adding an item to cart

Customers can add and remove items to and from their shopping cart, then proceed to
payment.