SRS of Amazon Go
SRS of Amazon Go
AMAZON GO
SOFTWARE
REQUIREMENT
SPECIFICATION
TABLE OF CONTENTS
Sr. # Title Page No.
1. Preface 4
2. Introduction 5
i. Purpose 5
ii. Scope 5
iii. Definitions, Acronyms & Abbreviations 6
iv. Technologies to be used 6
v. Overview 7
3. Overall Description 8
i. Product Perspective 8
ii. Product Functions 8
iii. User Class & Characteristics 9
iv. Operating Environment 9
v. Design & Implementation Constraints 10
vi. Assumption and Dependencies 10
vii. User Documentation 11
5. System Features 16
i. System Feature I 16
ii. System Feature II 16
iii. System Feature III 17
iv. System Feature IV 17
BEE DEVS |3
8. Appendix A: Glossary 23
PREFACE
Any part of this document should not be misused, this is only for educational and research
purpose. You can copy and reproduce from this document as long the researches used to write this
document are properly cited and all credits are given of. Otherwise, it will be against copyright
policy ©.
-Neil Armstrong
Feel free to contact us in case of any query or any problem, E-mail any of us at:
UniversityID@students.au.edu.pk
BEE DEVS |5
2. INTRODUCTION
i. Purpose
The purpose of this document is to describe all the requirements needed
for the development of Just Walk out, cashier less technology for retail
stores named “Amazon Go”. This technology facilitates customers by
enabling them to pay for items by simply walking out.
This includes, all stakeholders which may not be limited to, the following:
Customers, Employees, developers, suppliers.
Developers should consult this document and its modifications as the only
source of requirements for the project. They should not consider any
requirements statements as valid, until they appear in this document or its
future modifications.
The Amazon team members should use this document and its
modifications as the primary mean to communicate confirmed
requirements to the development team. The development team expects
many face-to-face conversations for requirements and ideas. Please note
that only the requirements that appear in this document or a future
modification, however, will be used to define the scope of the system.
ii. Scope
This proposed software product is Amazon Go, just walk out cashier less
system. This will help people at retail store by reducing their time of
shopping. This will automate the retail shopping, which facilitate the
customers and reduce the errors. Current system is a half-automated
system, that require consistent support and monitoring. But Amazon Go
BEE DEVS |6
This software will generate auto bills by monitoring the customers activity
with help of advance AI system (the product they pick will be added in the
bills and the product put back will be removed from the bills).
v. Overview
This software Requirement specification document formally specifics the
requirement for the development of Amazon Go. This document is
prepared after a complete business and system analysis. Different
techniques are used to fulfil customer requirement with an efficient way.
The objective of this document is to formally describe the system’s
requirements including functional requirements, non-functional
requirements and business rules and constraints.
This document is organized in the following order:
Section 3 of this document provides details of the business domain that the
proposed “Amazon Go” software will support. These include a general
description of the product, user characteristics, and general constraints.
3. OVERALL DESCRIPTION
Depicts the overall factors that influence the item and its
prerequisites. This part doesn't state explicit necessities. Rather it
gives a foundation to those necessities, which are characterized in
segment 4 of External Interface Requirements, and makes them more
obvious.
i. Product Perspective
This is a mobile application which will link the user with Amazon
Convenience Store, as it is also involved in the same development process. It
will allow user to enter the store and will take record of shopping. The
databases used are Amazon Aurora, MySQL and Oracle Database. They
include shopping cart, bank details, customer information and other client
information as well.
- Fourth Function
During the shopping, it should add the picked items
by communicating with the databases and AI sensors/cameras. Thus, it
should have a cart.
- Fifth Function
It should make a payment request to the user’s bank
or billing company when it is informed that customer has exited the
convenience store.
• This system has not to work as a store where you can online buy
groceries or items without going into the store.
• It is assumed that customer/user will do not go shopping with an
empty bank account as they will be denied access to the store.
• This application is not a bank app, it only uses the permission of
user and bank to make payments.
• This system does not use bitcoins as method of payments.
• This application will not work despite signing in if the payment
details are not verified.
• It is assumed that the customers will not pick up food for other
people as it will add it into their cart.
B E E D E V S | 11
There will be two type of customers entering the grocery/retail store, one those who
have registered downloading the app. Others who have not; these will be either coming
up with someone having access through the app or alone.
They will just have to scan the QR code on entrance machines for entering the store.
3. Guest/Non-Registered Users:
Guest users can have access by the QR code of their partner with whom they are
coming. Family or partner mode will allow them to enter by QR scanning of registered
user.
Whereas non-registered users will have to download the app and sign up for access to
the store as that app will hold all the information of their shopping.
4. In the store:
Customer just need to search for their desired/wanted product or item throughout the
store and pick them up in shopping bag (either from the store or their own plastic bag).
Through different sensors and cameras at the faculty powered by Artificial Intelligence,
any item/s that will be picked will be added to a virtual cart. The data of virtual cart will
be automatically stored and updated on the amazon go app, any item/s your guest is
picking up will be added to that cart too. (Note: if you pick up any item for any other
individual; that will also be added to your cart).
In order to remove something from the virtual cart, simply put it back from where you
have picked it. This will remove it from your cart.
B E E D E V S | 13
7. For checkout:
For checking out, the customer does not have to wait in long lines for paying the bills.
They just have to walk out simply from the store from selected exits as often used in
different metro stations throughout the world. As soon they will leave the store, they
will get a message by Amazon Go app telling them about their virtual cart and its receipt
with payment option.
8. Payment:
After the virtual cart, payment will be made by either the credit card information or
other payment methods (may vary from country to country), such as through PayPal or
Paytm.
Table of AG-223
ID: AG-223
Description: Goal is to create such a system which can handle different type of
users and can allow system to respond to different actions of users.
Preconditions: System is idle with an empty virtual cart and all items at their initial
state.
Postconditions: After all events, system has a virtual cart ready for payment.
Main Customer will walk in scanning QR code, pick the items they want to
Success Scenario: purchase which will be added to virtual cart. When they will walkout a
receipt of virtual cart will be sent on Amazon Go app. Then a
payment will be made by payment method.
Extensions: Other scenario may include the putting back of an item, which will be
automatically removed from cart OR guest user on your app taking
items; which will be added/removed in your cart. If your credit is
empty then it will wait for credit to deduct, until you will be denied
access to the store.
Frequency of Use: This case will be used every time when a customer will enter and do
the checkout.
4. EXTERNAL INTERFACE
REQUIREMENTS
i. User Interfaces
The user interface for the app shall be compatible for different
Operating systems such as android (any version higher then jelly
bean 4.3). Also, on IOS (any version higher then 8.0).
The user interface shall be implemented using any tool or software
packages android studio (Kotlin including JAVA and JVM), Swift and
CPP compiler.
• The Amazon-go app shall communicate with the Configurator to identify all
the available components to configure the product.
• The Amazon-go app shall comprehend picking and placing back of the
products.
• The Amazon-go app shall communicate with bill Pay system to identify
available payment methods, validate the payments and process payment.
• The Amazon-go app shall communicate with management for the refund.
• The Amazon-go app shall generate the bill after leaving the Amazon-go
store.
• The Amazon-go app shall communicate with CRM system to provide
support.
• The Amazon-go app shall communicate with Sales system for order
management.
• The Amazon-go app shall also use the local network for the calling and
registering the complaint if any.
• The amazon-go app shall communicate through the RFID tags or NFC.
B E E D E V S | 16
5. SYSTEM FEATURES
Amazon store does not have a typical entrance. Instead of entering wide
shopping space, visitors have to enter through automatic gates. To get
access through those gate, visitor have to open Amazon App on their
phone and scan the unique code at the entrance.
The machine learning and computer vision it has developed can tell not
just the item that visitor has picked off the self but also the item that is
being put back.
• The first thing you are greeted with as you enter the store is three
turnstiles (gates). These turnstiles are activated only using the QR code
found in your Amazon Go App. These turnstiles keep those visitors out
of store those not having the App downloaded in their phone. These
turnstiles are responsible to register what users are in the store and
when they leave the store.
B E E D E V S | 18
• Ceiling of stores are covered with cameras that watch every move
while the visitors are in the store. When visitor picks up an item from
shelf, it is automatically added by store to visitor virtual cart. When user
returned that item back to shelf, it is automatically removed from virtual
cart.
6. OTHER NONFUNCTIONAL
REQUIREMENTS
Nonfunctional requirements serve as constraints or restrictions on the design of
the system. They ensure the usability and effectiveness of the entire system.
Failing to meet any one of them can result in systems that fail to satisfy inter
business, user or market needs, or that do not fulfill mandatory requirements
imposed by regulatory or standard agencies.
i. Performance Requirements
This section deals with how a software may perform or the standards it
must achieve within a set of criteria.
• App may take initial load time which may depend upon User’s
Internet Connection Stability.
• The system shall require the customer to enter their unique QR code
provided by the app to enter through turnstile.
- The customer shall not be able to activate turnstile without the app.
• The system shall not accidently lose customer’s app account information.
• The system’s cameras shall accurately identify each customer and their
every move throughout their time spent in store.
• The cameras and embedded sensors shall ensure that the products that the
customer is leaving with is what the customers will be paying for.
• The system shall accurately calculate customer’s receipt.
This section deals with ensuring that the security properties of software are being
satisfied.
QR Code:
Customer shall require unique QR code on app to access the store entrance.
- Shall keep customers not set up with the app outside the store,
letting in only customers with the app linked to their amazon
accounts to enter.
The ceiling of the store shall be covered with cameras viewing each customer’s
every move.
Data Transfer:
• The system shall use secure sockets in all transactions that include any
confidential customer information.
• The cashier less system shall use a combination of ceiling mounted cameras
and shelf-weight sensors to automatically track customers and items as
they move around the store.
• The system shall confirm all transactions with the customer’s account.
• The system shall automatically log out from all user accounts after a period
of inactivity.
Data Storage:
This section deals with the features that facilitate the measurement of
performance of a software product.
Operational Availability:
This subsection deals with the comparison of how long a system has been
available to use compared to how long it should have been available to us.
Usability:
This subsection specifies the requirements associated with which the ease the
system can be used.
v. Business Rules
This section deals with the defining or constraining of some aspect of business.
APPENDIX A: GLOSSARY
JS – Java script
SQL – Structured Query Language
QR – Quick Response
SRS – Software Requirement Specification
AI – Artificial Intelligence
IOS – iPhone Operating System
OS – Operating System
NFC – Near Field Communication
XML – Extensible Markup Language
XSD – Schema Definition Language
CRM – Customer Relationship Management
HTTP – Hypertext Transfer Protocol
RFID – Radio Frequency Identification
No part of the SRS has been copied from the internet, all group
members have done their research and we have discussed the
progress several times on zoom meetings. It is plagiarism free.