Software Requirement Specification

On
AMAZON

BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE AND ENGINEERING

By

Name: GEORGE GILBERT RAJU

Registration number: 11801980
Roll No: 16
Section: K18GA

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

George Gilbert Raju

R.No: 16
 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 co-
operation 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

1.1 INTRODUCTION (12 Bold) 1

1.1.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 PAGE NO.

1 Functional Requirements

2 Non-Functional Requirements

LIST OF FIGURES

FIGURE NO. FIGURE DESCREPTION PAGE NO.

1 Context Level DFD

2 First Level DFD

3 Second Level DFD (Cart)

4 Second Level DFD

(Registration)
5 Use Case Diagram

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.
Owner: Amazon
Launched: 23 April 2006
1.2 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.

1.3 REFERENCES
https://www.techopedia.com/definition/27580/amazon/
www.amazon.in/

1.4 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.

LIST OF FUNCTIONAL REQUIREMENTS

TABLE NO. 1 Features and Requirements PAGE NO.

1-2

Functions Descriptions Input Output

The login screen
allows registered user
to login to the site to User needs to enter the
Login Logs into the account.
access all the features correct login details.
that the account gives
them to access.
The Signup screen is
Enter the Email,
for new users to Creates a new account
Sign Up password, a security
register to their if no errors found.
question, D.O.B,etc
service.
Display shifts from
login to Facebook Login info from
Login with Facebook
login, get details and user’s Facebook Promoted to shopping
login to system, account
shopping page
Display shifts from
login to Google Gmail
Login info from
Login with Google login, get details and Promoted to shopping
User’s gmail account
login to system,
shopping page
 Categories is the group
of collection of types The user clicks on the
Categories of items, each The list of categories
Categories icon while
collection further have is displayed
subcategories of in on-line mode.
products.
Display shifts from
the Home page to list
TV, Appliances, of Electronics type Select TV,Appliances, Promoted to list of
Electronics items arranged Electronics products
according to default
sorting type
Displays a list of
Men’s products Promoted to list of
Men’s Fashion Select Men’s Fashion
arranged according to products
default sorting type.
Displays Products
Searches for Products
Enter list of valid that matches the
Search based on the keywords
keywords. keywords entered by
inserted by the user.
the user.
This module consists
of sorting types to Sorts the Displayed
Select the type of
Sort by choose the appropriate product in the selected
sorting
sort for better and order
consistent results.
Displays the Sorts the Displayed
products in the Select High to low
High to low price product in the selected
descending order of price
order
price
Displays the products Sorts the Displayed
Select Low to High
Low to High price in the ascending order product in the selected
price
of price. order
Add item to the cart
list and display the
Add to Cart Select add to cart Item added to cart
message that item
added to cart
Display shifts from
Displays to list of
Cart current page to list of Select cart
items in cart
items in cart
Remove item from the
cart list and display Select Remove from Item removed from
Remove from cart
the message that item cart cart
removed from cart
Display shifts from Promoted to Payment
Buy Now buy to payment & Select Buy Now & delivery details
delivery details. page.
Save delivery details
and other info, display
Promoted to payment
Delivery Details shifts from delivery Enter delivery details
methods
details to payment
methods.
Select a payment Select the details Select already saved
Proceeds to buy
method about payment payment Details
Display shifts from
Promoted to bank
Payment methods to Select Debit card +
Debit card authentication and
bank authentication + Enter card credentials
confirmation
do transaction
Display shifts from
Select cash on Promoted to Payment
Cash on delivery payment method to
delivery Accepted
transaction accepted
Display shifts from
My Orders current page to orders Select my orders Promoted to orders list
list and details
Display shifts from
orders to order status Select track order Promoted to order
Track order
received from delivery option status
men
Used To Cancel Select cancel order Promoted to order
Cancel order
Orders option cancelled

LIST OF NON-FUNCTIONAL REQUIRMENTS

TABLE NO. 2 Non-Functional Rrequirments PAGE NO.

2

Non-Functional Requirments Description

Performance Requirements
Graphical User Interface
Accessibility
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

1.1 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
1.2 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
1.3 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

-----THE END-----