Software Requirement Specification
On
AMAZON
COMPUTER SCIENCE AND ENGINEERING
By
Name: ROHIT KUMAR
Registration number: 12219614
Roll No: B-54
Section: DOC12
School of Computer Science and Engineering
Lovely Professional University
Phagwara, Punjab (India)
DECLARATION STATEMENT
I hereby declare that the case study entitled "AMAZON” submitted at Lovely
Professional University, Phagwara, Punjab is an authentic work and has not been
submitted elsewhere.
I understand that the work presented herewith is in direct compliance with Lovely
Professional University’s Policy on plagiarism, intellectual property rights, and highest
standards of moral and ethical conduct. Therefore, to the best of my knowledge, the
content of this case study represents authentic and honest effort conducted, in its
entirety, by me. I am fully responsible for the contents of my case study report.
Signature of Candidate
ROHIT KUMAR
R.No: B-54
ACKNOWLEDGEMENT
I have taken efforts in this SRS. However, it would not have been possible without the
kind support and help of many individuals and organizations. I would like to extend my
sincere thanks to all of them.
I am highly indebted to Lovely Professional University for their guidance and constant
supervision as well as for providing necessary information regarding the SRS & also for
their support in completing the Document.
I would like to express my gratitude towards my teachers & friends for their kind cooperation and encouragement which help me in completion of this SRS Document.
I would like to express my special gratitude and thanks to industry persons for giving me
such attention and time.
My thanks and appreciations also go to my colleague in developing the Document and
people who have willingly helped me out with their abilities.
TABLE OF CONTENTS
CONTENTS
PAGE
NO.
The Case, its rational and scope
i
Declaration by the Student
ii
Acknowledgement
iii
Table of Contents
iv
List of Tables
v
List of Figures
vi
CHAPTER 1: SRS DOCUMENT (14 BOLD ALL CAP)
1
INTRODUCTION (12 Bold)
1
SUB-SECTION TITLE (12 BOLD)
2
CHAPTER 2: SOFTWARE DESIGN DESCRIPTION
CHAPTER 3: MANUAL TEST CASES
LIST OF TABLES
TABLE NO.
List Of Tables
1
Functional Requirements
2
Non-Functional Requirements
PAGE NO.
LIST OF FIGURES
FIGURE NO.
FIGURE DESCREPTION
1
Context Level DFD
2
First Level DFD
3
Second Level DFD (Cart)
4
Second Level DFD
(Registration)
Use Case Diagram
5
PAGE NO.
1. INTRODUCTION
PURPOSE 1.1
The Introduction of the Software Requirements Specification (SRS) gives a review
of the whole SRS with reason, scope, definitions, acronyms, shortened forms,
references and outline of the SRS. The point of this record is to accumulate and
investigate and give an inside and out knowledge of the total amazon internet
shopping framework by characterizing the issue explanation in detail. By and by, it
additionally focuses on the capacities required by partners and their needs while
characterizing abnormal state item highlights. The point by point prerequisites of
the Amazon is given in this report.
Type of Site: E-Commerce etc.
Available in: English.
Founder: Jeff Bezos (executive chairman) and Andy Jassy (president and CEO)
Launched: JULY 05, 1994
SCOPE
Native Android, iOS and Responsive Web Page
It can run on a Windows, Macintosh or Linux operating system, and is supported by
iPhone, Android and Blackberry devices.
OVERVIEW
The accompanying SRS contains the detail item viewpoint from various partners. It
gives the detail item elements of E-Store with client qualities allowed imperatives,
suppositions and conditions and necessities subsets.
Brief About Amazon
 It is one of the world's most valuable brands.
 Current Jeff Bezos (Executive Chairman)
 Andy Jassy (President and CEO)
 Amazon is headquartered in Seattle, Washington.
 Bezos finally decided that his new business would sell books online, because of the
large worldwide demand for literature.
 Bezos' parents invested almost $250,000 in the start-up.
 On July 16, 1995, Amazon opened as an online bookseller, selling the world's
largest collection of books to anyone with World Wide Web access.
 The first book sold on Amazon.com was Douglas Hofstadter's Fluid Concepts and
Creative Analogies.
 In 2011, Amazon had 30,000 full-time employees in the US, and by the end of
2016, it had 180,000 employees
LIST OF FUNCTIONAL REQUIREMENTS
TABLE NO. 1
1-2
Functions
Login
Sign Up
Login with Facebook
Login with Google
Features and Requirements
Descriptions
The login screen
allows registered user
to login to the site to
access all the features
that the account gives
them to access.
The Signup screen is
for new users to
register to their
service.
Display shifts from
login to Facebook
login, get details and
login to system,
shopping page
Display shifts from
login to Google Gmail
login, get details and
login to system,
PAGE NO.
Input
Output
User needs to enter the
correct login details.
Logs into the account.
Enter the Email,
password, a security
question, D.O.B,etc
Creates a new account
if no errors found.
Login info from
user’s Facebook
account
Promoted to shopping
Login info from
User’s gmail account
Promoted to shopping
shopping page
Categories
Categories is the group
of collection of types
The user clicks on the
of items, each
collection further have Categories icon while
in on-line mode.
subcategories of
products.
The list of categories
is displayed
TV, Appliances,
Electronics
Display shifts from the
Home page to list of
Electronics type items
arranged according to
default sorting type
Select TV,Appliances,
Electronics
Promoted to list of
products
Men’s Fashion
Displays a list of
Men’s products
arranged according to
default sorting type.
Select Men’s Fashion
Promoted to list of
products
Search
Searches for Products
based on the keywords
inserted by the user.
Enter list of valid
keywords.
Displays Products
that matches the
keywords entered by
the user.
Sort by
This module consists
of sorting types to
choose the appropriate
sort for better and
consistent results.
Select the type of
sorting
Sorts the Displayed
product in the selected
order
High to low price
Displays the
products in the
descending order of
price
Select High to low
price
Sorts the Displayed
product in the selected
order
Select Low to High
price
Sorts the Displayed
product in the selected
Order
Select add to cart
Item added to cart
Select cart
Displays to list of
items in cart
Select Remove from
cart
Item removed from
cart
Select Buy Now
Promoted to Payment
& delivery details
page.
Enter delivery details
Promoted to payment
methods
Low to High price
Add to Cart
Cart
Remove from cart
Buy Now
Delivery Details
Displays the products
in the ascending order
of price.
Add item to the cart
list and display the
message that item
added to cart
Display shifts from
current page to list of
items in cart
Remove item from the
cart list and display
the message that item
removed from cart
Display shifts from
buy to payment &
delivery details.
Save delivery details
and other info, display
shifts from delivery
details to payment
methods.
Select a payment
method
Debit card
Cash on delivery
Select the details
about payment
Display shifts from
Payment methods to
bank authentication +
do transaction
Display shifts from
payment method to
transaction accepted
Select already saved
payment Details
Proceeds to buy
Select Debit card +
Enter card credentials
Promoted to bank
authentication and
confirmation
Select cash on
delivery
Promoted to Payment
Accepted
Select my orders
Promoted to orders list
My Orders
Display shifts from
current page to orders
list and details
Track order
Display shifts from
orders to order status
Select track order
received from delivery option
men
Promoted to order
status
Cancel order
Used To Cancel
Orders
Promoted to order
cancelled
Select cancel order
option
LIST OF NON-FUNCTIONAL REQUIRMENTS
TABLE NO. 2
2
Non-Functional Requirements
Non-Functional Requirments
Performance Requirements
Graphical User Interface
Accessibility
PAGE NO.
Description
The item might be founded on web and must
be keep running from a web server. The item
might take introductory load time contingent
upon web association quality which likewise
relies on upon the media from which the item
is run. The execution should rely on
equipment segments of the customer/client
The framework should give a uniform look
and feel between all the site pages. The
framework should give an advanced picture to
every item in the item inventory. The
framework should give utilization of symbols
and toolbars.
The framework should give disable get to. The
framework should give multi dialect bolster.
Reliability
The framework should give stockpiling of
all databases on excess PCs with
programmed switchover. The framework
should accommodate replication of
databases to off-site stockpiling areas.
Availability
The average availability over a year shall
exceed 167 hours per week. The framework
might furnish an authoritative concurrence
with a web access supplier for T3 access with
99.9999% accessibility.
2. FIGURES DFDs
Context level DFD (level-0)
Amazon
DFD level-1
DFD (level-2)
Cart
Registration
Use Case Diagram
Test Cases
General Test Cases

Confirm that client can explore through every one of the items crosswise over
various classifications

Confirm that every one of the connections and standards are diverting to right
item/classification pages and none of the connections are broken

Confirm that the organization logo is obviously noticeable

Confirm that all the content - item, class name, cost and item portrayal are
unmistakably obvious

Confirm that every one of the pictures - item and pennant are plainly
unmistakable

Check that class pages have applicable item recorded particular to the
classification

Check that right number of aggregate items are recorded on the class pages

Look - Verify that on seeking all the item fulfilling the inquiry criteria are
visible on the query item page

Look - Verify the more applicable item for the inquiry term are shown on the
top for a specific pursuit term

Look - Verify that check of items is effectively shown on the query output page
for a specific inquiry term

Sifting - Verify that separating usefulness effectively channels item in light of
the channel connected

Sifting - Verify that separating works effectively on class pages

Sifting - Verify that separating works effectively on the query output page

Sifting - Verify that right number of aggregate items is shown after a channel is
connected

Sorting - Verify that all the sort choices work accurately - effectively sort the
items in view of the sort alternative picked

Sorting - Verify that sorting works effectively on the class pages

Sorting - Verify that sorting works effectively on the query item page

Sorting - Verify that sorting works effectively on the pages containing separated
come about, subsequent to applying channels

Sorting - Verify that item tally stays in place regardless of sorting choice
connected
Item Buy Flow - Test cases

Confirm that on the item page, client can choose the coveted quality of the item e.g.
estimate, shading and so on

Confirm that client can add to truck at least one item

Confirm that client can add items to list of things to get

Confirm that client can purchase items added to truck subsequent to marking into the
application (or according to the usefulness of the site)

Confirm that client can effectively purchase more than one items that were added to
his/her truck

Confirm that client can't include more than accessible stock of the item

Confirm that the point of confinement to the quantity of items a client can by is
working effectively by showing blunder message and keeping client from
purchasing more than the breaking point

Confirm that the conveyance can be declined of for the spots where transportation is
not accessible

Confirm that Cash on Delivery alternative of installment is working fine

Confirm that the distinctive prepaid strategies for installments are working fine

Check that item return usefulness works fine
User (Buyer) Registration - Test cases

Check that all the predefined fields are available on the enlistment page

Confirm that the required/compulsory fields are set apart with * against the field

Confirm that for better UI dropdowns, radio catches and checkboxes and so forth
fields are shown wherever conceivable rather than just textboxes

Check the page has both submit and cross out/reset catches toward the end

Check that clicking submit catch in the wake of entering all the required fields,
presents the information to the server

Confirm that clicking drop/reset catch in the wake of entering all the required fields,
wipes out the submit demand and resets every one of the fields

Check that at whatever point conceivable approval ought to occur at customer side

Check that not filling the compulsory fields and clicking submit catch will prompt
approval mistake

Check that not filling the discretionary fields and clicking submit catch will even
now send information to server with no approval mistake

Check the furthest reaches of the textboxes

Check approval on date and email fields (just substantial dates and legitimate email
Ids ought to be permitted

Check approval on numeric fields by entering letters in order and uncommon
characters

Check that driving and trailing spaces are trimmed

Confirm that entering clear spaces on obligatory fields prompt approval mistake

Confirm that in the wake of making a demand to the server and after that sending a
similar demand again with a similar extraordinary key will prompt server side
approval mistake.
REFERENCES
 https://en.wikipedia.org/wiki/History_of_Am
azon
 https://www.techopedia.com/definition/2758
0/amazon/www.amazon.in/
Books
 "Amazon Empire: The Rise and Reign of Jeff
Bezos". PBS.
-----THE END-----