SRS OF AMAZON
PREPARED BY:PREPARED
BY:-
Student 2 Name:-Rishi Patel
Roll No: 251
Enrollment Number:22002171310115
Batch/Branch:B9/CST
Student 1 Name:- Tirth Shah
Roll No: 244
Enrollment Number:22002171310129
Batch/Branch:B9/CST
Student 3 Name:-Nency Shah
Roll No: 252
Enrollment Number:22002171310127
Batch/Branch:B9/CST
Student 4 Name:-Chelsi Patel
Roll No: 255
Enrollment Number:22002171210107
Batch/Branch:B9/CSE
Student 5 Name:- Isha Ranpariya
Roll No: 258
Enrollment Number:22002171310113
Batch/Branch:B9/CST
1.INTRODUCTION
INDEX
4.EXTERNAL INTERFACE REQUIREMENTS
1.1 Purpose
1.2 Definitions, Acronyms, Abbreviations
1.3 Scope
1.4 Intended Audience
1.5 Risk Analysis
1.6 Overview
4.1 Software Interface
4.2 Communication Interface
4.3 User Interface
4.4 Hardware Interface
2.OVERALL DESCRIPTION
5.SOFTWARE QUALITY ATTRIBUTES
2.1 Product Perspective
2.2 Product Function
2.3 User Characteristics
2.4 Operating Environment
2.5 Design and implementation constraints
2.6 User Documentation
3.SPECIFIC REQUIREMENTS
3.1 Functional Requirements
3.1.1 Registration
3.1.2 Login
3.1.3 Changes to cart
3.1.4 Payment
3.1.5 Logout
3.2 Supplementary Requirements
5.1 Business Rules
5.2 Performance
5.3 Safety
5.4 Reliability
1.Introduction
Technology giant Amazon.com is considered the largest online retailer in the world mainly measured by revenue and
market capital. With separate retail websites spread across different continents such as; Americas, Europe, Asian and
Australia. The tech giant is looking to simplify its online shopping system to make it user friendly and very easy to use
for everyone.
Amazon.com, Inc. has contracted with Staylor LLC to create a user-friendly online shopping system. Staylor LLC
specializes in front and backend web and UX design, with a proven track record for delivering creative world class
websites, something very important to Amazon.com.
This document is the Software Requirement Specification (SRS) for the online shopping system. It will outline all of the
agreed upon features of the online shopping system.
1.1 Purpose
The purpose of the Software Requirement Specification is to provide a clear, documented model of the requirements
for the online shopping system, that will provide top level use cases for a web customer making purchases online.
The web design will implement several Use Cases which are as follows:1.Login
2.Search item
3.View and Select item
4.Add to cart
5.View cart
6.Buy item now
7.Proceed to checkout
8.Enter method of delivery
9.Make payment
10.View and order item
1.2 Definitions, Acronyms and Abbreviations
There are some key points which define amazon website interface and through which we are able to do online shopping
through amazon.
Website
: A address that is connected to the internet to provide one or more web pages or other content.
Online
: Connected to a computer network or accessible by computer.
Browse
: Reading superficially or at random
Search
: The activity of looking thoroughly in order to find something.
Shopping cart : A handcart that holds items (groceries or other goods) while shopping.
Checkout
: Confirm and pay goods (or services) using a payment facility
.
1.3 Scope
Amazon is often recognized for its success as an online retailer, but another one of the comp
any's core business units is its extensive list of subscription services….Prime, Amazon's main
subscription service, provides shipping and delivery benefits and online shopping discounts.
Web Customer actor uses the Amazon web site to make purchases online. Top level use cases are
View Items, Make Purchase and Client Register. View Items use case could be used by customer as
top-level use case if customer only wants to find and see some products. This use case could also be
used as a part of Make Purchase use case. Client Register use case allows customer to register on
the web site, for example to get some coupons or be invited to private sales. Note, that Checkout use
case is included use case not available by itself - checkout is part of making purchase.
1.4 Intended audience:
Amazon's target market is middle and upper-class consumers (evenly split between
genders) with home computers or smart devices aged between 18-44 as of 2022.
Additionally, 60% of Amazon's target market are from the United States who prefer
shopping online for convenience, fast delivery and competitive prices.
1.5 RISK ANALYSIS:
7 types of risk analysis every energy trader should know:• Value at risk
• Mark to market
• Counterparty credit exposure
• Counterparty Collateral requirements
• Cost to credit
• Hedge effectiveness test
• Stress testing
1.6 Overview
The SRS of amzon.com is divided into two main parts: Overall Description
and Specific Requirements.
The Overall Description describes the requirements at a high level, while
the Specific Requirements describe all of the relevant requirements of the
system.
2.Overall Description:
The online shopping system allows the actor (web customer) to use the Amazon website to make
purchases online. The top-level features are to allow the actor to browse the website as a guest
user or log in as a registered user. The browse and search items can be used by customer as
primary feature use case if the customer only wants to find and see some products. The search and
browse Items use case is extended by several optional use cases - customer may search for items,
browse catalog, view and select these items, add them to shopping cart and view the shopping cart.
All these use cases are extending use cases because they provide some optional functions allowing
customer to find item. The second set of features allows the actor to make purchase. The make
purchase use case requires the customer to either use the buy item now option with one click
payment authentication and verification (available only to registered users) to place the order or go
through the checkout use case. In the checkout use case, customer provide the shipping address,
and then specific the method of payment which can be done either by using credit card or with bank
account. After providing the payment method, customer will review and order item.
2.1 Product Perspective
The online shopping system allows the actor (web customer) to use the Amazon website to make
purchases online. The top-level features are to allow the actor to browse the website as a guest user
or log in as a registered user. The browse and search items can be used by customer as primary
feature use case if the customer only wants to find and see some products. The search and browse
Items use case is extended by several optional use cases -customer may search for items, browse
catalogue, view and select these items, add them to shopping cart and view the shopping cart. All
these use cases are extending use cases because they provide some optional functions allowing
customer to find item. The second set of features allows the actor to make purchase. The make
purchase use case requires the customer to either use the buy item now option with one click
payment authentication and verification (available only to registered users) to place the order or go
through the checkout use case. In the checkout use case, customer provide the shipping address,
and then specific the method of payment which can be done either by using credit card or with bank
account. After providing the payment method, customer will review and order item.
Login
Browse
item
Search item
Registered User
View and
select item
Add to
shopping
cart
Customer
Buy item
now
Payment authentication
Proceed to
checkout
Guest user
View
shopping
cart
Enter
method of
delivery
Credit card
Make
payment
USE CASE DIAGRAM
Review &
order item
Bank account
SEQUENCE Diagram
STATE Diagram
CUSTOMER
AMAZON
PAYMENT SERVICES
COURIER COMPANY
Load website
Go to AMAZON
Order an Item
Add the item to The basket
Enter Checkout
In
stock
?
ACTIVITY Diagram
Display “in stock”
Calculate the total price
Enter the card details
Verified
?
Enough
funds
Charge Customer
Send confirmation to Amazon
Send order confirmation
Receive the item
Packing
Send item to courier
Deliver the item
DFD ZERO DIAGRAM
Customer
Management
Shopping
Management
Payment
Management
AMAZON
Order
Management
System User
Management
Login
Management
LEVEL 1 DFD
DFD LEVEL-2
DIAGRAM
2.2 Product Function
The function of this app is described below:• Login
• Search the product
• Give related product list according to the demand of the user
• Click on the product to view the details
• Show all the specifications and reviews of the product
• Add the product in the cart when “Add to cart” button is pressed
• Show the items in the cart when “cart” icon is clicked
• Go to payment procedure
• Add the details like: address, phone number, full name and email address etc.
• Confirm order through email
• Tracking the order through email
2.3 User characteristics:
This system will be used by the customers for online shopping of everything. The main user is shopkeeper, buyer,
the delivery service. It does not need proper knowledge of the system to use it. It is self-explanatory. And if the user
need help the help guide is available.
2.4 Operating environment:
This system can be used on window XP, window 7, window 10, android operating system and IOS etc.
2.5 Design and implementation constraints:
this system will be made on html.CSS and C++ on back end.Decision regarding which database to use should be
taken considering the fact that data being exchanged or stored is large, and the appropriate data management
system will yield efficient performance.
2.6 User documentation :
User documentation include (online help and user manual).
3.SPECIFIC REQUIREMENTS:
3.1 FUNCTIONAL REQUIREMENTS
Various functional modules that can be implemented by the system. The functional
requirements of Amazon are discussed below:
3.1.1 Registration
If customer wants to buy the product, then he/she must be registered,
unregistered user can’t go to the shopping cart.
3.1.2 Login
Customer logins to the system by entering valid user id and password for the shopping.
3.1.3 Changes to Cart
Changes to cart means the customer after login or registration can make order
or cancel order of the product from the shopping cart.
3.1.4 Payment
In this system we are dealing the mode of payment by Cash. We will extend this to
credit card, debit card etc. in the future.
3.1.5 Logout
After ordering or surfing for the product customer has to logout.
3.2 Use-Case Reports
Use Case Name: Login
Summary: The login feature allows the actor of the software to use the website as a registered user.
Preconditions: create an account.
Triggers: Actor selects the sign in button.
Basic course of events (Scenario):Internal Precondition: The sign in windows is displayed.
ACTOR
SYSTEM
1. The actor select to sign in.
2. The website email(phone for mobile
account) and password.
3. Actor completes fields and select
sign in.
4. The website validates actor as
registered user.
SCREEN
Internal Post Condition:- 1. Actor confirmed by system as registered user.
2. Customer can proceed to use website.
Alternative paths:
Actor search item and browse catalog as guest user.
Internal Precondition: None
ACTOR
SYSTEM
SCREEN
1.Actor search item and browse
catalog as guest user.
2.Online shopping
Version:1.0
3.Software Requirement
Specification
Date:10/01/2018
SLLC-001
Use Case Name: Search items
Summary: The search items allows the actor of the software to find products on the website.
Preconditions: None.
Triggers: Actor clicks on the search box.
Basic course of events (Scenario):Internal Precondition: None
ACTOR
SYSTEM
1.The actor type in keyword of the
item.
2.The website display list of possible
items related to keyword.
3.The actor clicks search icon
4.The website returns selected results
based on the keyword.
SCREEN
Use Case Name: Browse
Items Summary: The search items allows the actor of the software to browse items in the catalog on the website.
Preconditions: None.
Triggers: Actor select the ‘category’ down arrow.
Basic course of events (Scenario):Internal Precondition: A drop down arrow showing product category is shown
ACTOR
SYSTEM
1.The actor clicks the catalog list
icon.
2.The website displays catalog
item by category.
3.Actor selects a catalog from
the list.
4.The website displays items in
the selected category.
SCREEN
Use Case Name: View and Select
Item Summary: The view and select item feature allows the actor to of the software find and select product he/she
wants to purchase.
Preconditions: None.
Triggers: Actor select an item from the selected result.
Basic course of events (Scenario): Internal Precondition: Website shows product details
ACTOR
SYSTEM
1.Actor view result list and select an
item.
2.Website shows item in detail.
SCREEN
Use Case Name: Buy item now
Summary: The buy item now feature allows the actor of the software quickly order item using 1-Clicking ordering.
Preconditions: Actor need to 'Turn on 1-Click ordering for this browser' to use the feature.
Triggers: Actor selects the ‘Buy Now’ button.
Basic course of events (Scenario): Internal Precondition: The system authenticates user and process order.
ACTOR
SYSTEM
1. Actor clicks on the ‘BUY NOW’
button (only available to registered
users).
2. The system authenticates user and
order product.
SCREEN
Use Case Name: Add to shopping cart
Summary: The add to shopping cart feature allows the actor of the software to create a new album inthe album
library.
Preconditions: None.
Triggers: Actor clicks the ‘Add to Cart’ button.
Basic course of events (Scenario): Internal Precondition: None
ACTOR
SYSTEM
1. Actor clicks the ‘ADD TO CART’ button.
2.System adds item to cart.
SCREEN
Use Case Name: View shopping cart
Summary: The view shopping cart feature allows the actor of the software to view list of items in the shopping cart.
Preconditions: None.
Triggers : Actor clicks the ‘edit your cart’ button.
Basic course of events (Scenario): Internal Precondition: None
ACTOR
SYSTEM
1.Actor clicks ‘EDIT YOUR CART’
button after adding item to cart.
2.The system displays list of items in
the shopping cart.
SCREEN
Alternative paths:
Actor click the cart icon on the top right of the screen to view shopping cart.
Internal Precondition: None
ACTOR
SYSTEM
1.Actor clicks the cart icon on the top
right of the screen.
2.The system displays list of items in
the shopping cart.
SCREEN
Use Case Name: Proceed to checkout
Summary : The proceed to checkout feature allows the actor of the software to make payment and complete order.
Preconditions: None.
Triggers: Actor click the proceed to checkout button.
Basic course of events (Scenario):Internal Precondition-None
ACTOR
SYSTEM
1. Actor clicks the proceed to checkout
button.
2.The system displays the checkout
window with summary of the order ,
payment and delivery method.
SCREEN
Use Case Name: Enter method of delivery
Summary: The enter method of delivery feature allows the actor of the software to specify where and how the item will
be delivered.
Preconditions: None.
Triggers: Actor clicks on shipping address or the link ‘change’.
Basic course of events (Scenario):Internal Precondition: None
ACTOR
SYSTEM
1.Actor clicks the shipping address or
the link ‘change’.
2.The system shows list of recently used
address or an option to add new
address.
3.Actor selects desired shipping address
from list, or add a new address
SCREEN
Use Case Name: Make payment
Summary: The make payment feature allows the actor of the software to pay for item in the shopping cart.
Preconditions: None.
Triggers: Actor triggers the create album event.
Basic course of events (Scenario):Internal Precondition: None
ACTOR
SYSTEM
1.Actor clicks the payment method or
the link change.
2.The system shows list of credit/debit
cards or an option to add a credit or a
debit card.
3.The system shows other payment
methods(actors) such as a bank
account,gift card and promotion code.
4.Actor selects desired payment method
from several option.
SCREEN
Use Case Name: Review and order item
Summary: The review and order item feature allow the actor of the software to complete the order.
Preconditions: None.
Triggers: Actor clicks the ‘place your order’ button.
Basic course of events (Scenario): Internal Precondition: None
ACTOR
SYSTEM
1.Actor clicks ‘PLACE YOUR ORDER’
button.
2.The system orders the item.
SCREEN
3.3 Supplementary Requirements:
There are a couple of non-functional requirements that are associated with this software
system. The website shall run on all browsers. The website shall support screen reader
software for disabled people and follow 508 standards.
4.External Interface Requirements
Interface requirements include:
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 send one copy of the bill to the customer’s Email
address.
4.1 Software Interface
AWS (Amazon Web Services) is a comprehensive, evolving cloud computing platform provided by
Amazon that includes a mixture of infrastructure as a service (IaaS), platform as a service (PaaS) and
packaged software as a service (SaaS) offering. AWS services can offer an organization tool such as
compute power, database storage and content delivery services.
AWS launched in 2006 from the internal infrastructure that Amazon.com built to handle its online
retail operations. AWS was one of the first companies to introduce a pay-as-you-go cloud computing
model that scales to provide users with compute, storage or throughput as needed.
4.2 Communication Interface
The Web Real-Time Communication (WebRTC) standard supports sending real-time video, audio,
and arbitrary data between two peers. Amazon supports WebRTC to enable real-time streaming of
audio, video, and (optionally) arbitrary data between Alexa and your smart home device. Alexa
communicates commands over the real-time communication (RTC) data channel to your device, and
then your device responds and reports state back over the data channel.
4.3 User Interface
The user interface for the software shall be compatible to any browser such as Internet Explorer,
Mozilla or Netscape Navigator by which user can access to the system.
The user interface shall be implemented using any tool or software package like Java Applet, MS
Front Page, EJB etc.
4.4 Hardware Interface
Since the application must run over the internet, all the hardware shall require to connect internet
will be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet Cross-Cable.
5.SOFTWARE QUALITY ATTRIBUTES:
Software Quality Attributes are features that facilitate the measurement of performance of a
software product by Software Testing professionals, and include attributes such as availability,
interoperability, correctness, reliability, learnability, robustness, maintainability, readability,
extensibility, testability, efficiency, and portability. High scores in Software Quality Attributes enable
software architects to guarantee that a software application will perform as the specifications
provided by the client.
5.1 Business rules:
A business rule is a constraint of the business itself that may guide system development. It is a rule
that must be followed, no matter what else is happening. It often involves very specific criteria or
conditions for compliance. All users need a valid email address.in amazon we need whole
information of the customer and the shopkeeper their address, cell phone number, email address,
name and CNIC etc. to make the business affective and easy to use.
5.2 Performance:
The system must be interactive and the delays involved must be less .
5.3 Safety:
Information transmission should be securely transmitted to server without any changes in information.
5.4 Reliability:
The system must be interactive and the delays involved must be less. So in every action-response of
the system, there are no immediate delays. In case of opening windows forms, of popping error
messages and saving the settings or sessions there is delay much below 2 seconds, in case of
opening databases, sorting questions and evaluation there are no delays and the operation is
performed in less than 2 seconds for opening, sorting, computing, posting > 95% of the files. Also,
when connecting to the server the delay is based editing on the distance of the 2 systems and the
configuration between them so there is high probability that there will be or not a successful
connection in less than 20 seconds for sake of good communication.
SECURITY REQUIREMENT:
• The system uses SSL (secured socket layer) in all transactions that include
any confidential customer information.
• The system must automatically log out all customers after a period of
inactivity.
• The system should not leave any cookies on the customer’s computer
containing the user’s password.
• The system’s back-end servers shall only be accessible to authenticated
administrators.
• Sensitive data will be encrypted before being sent over insecure
connections like the internet.
MERITS/DEMERITS
REFERENCES
FUTURE SCOPE
THANK YOU….