Software Requirements

Specification
For

IoT-based Smart Shopping Cart

Version 1.0

Prepared by Tanish Rohil Gali

Chaitanya Bharathi Institute of Technology (CBIT)

15-09-2022
Software Requirements Specification for
IoT-based Smart Shopping Cart

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions.................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 2
1.5 References ........................................................................................................................................ 2
2. Overall Description ..................................................................................................................3
2.1 Product Perspective.......................................................................................................................... 3
2.2 Product Functions ............................................................................................................................ 4
2.3 User Classes and Characteristics ..................................................................................................... 4
2.4 Operating Environment.................................................................................................................... 5
2.5 Design and Implementation Constraints .......................................................................................... 6
2.6 User Documentation ....................................................................... Error! Bookmark not defined.
2.7 Assumptions and Dependencies ...................................................................................................... 6
3. External Interface Requirements ...........................................................................................7
3.1 User Interfaces ................................................................................................................................. 7
3.2 Hardware Interfaces ......................................................................................................................... 7
3.3 Software Interfaces .......................................................................................................................... 7
3.4 Communications Interfaces ............................................................................................................. 7
4. System Features .......................................................................................................................8
4.1 System Feature 1 .............................................................................................................................. 8
4.2 System Feature 2 (and so on) ........................................................................................................... 9
5. Other Nonfunctional Requirements .......................................................................................9
5.1 Performance Requirements .............................................................................................................. 9
5.2 Safety Requirements ........................................................................................................................ 9
5.3 Security Requirements ..................................................................................................................... 9
5.4 Software Quality Attributes ............................................................................................................. 9
5.5 Business Rules ................................................................................................................................. 9
6. Other Requirements ..............................................................................................................10
Appendix A: Glossary..................................................................................................................10
Appendix B: Analysis Models .....................................................................................................10
Appendix C: To Be Determined List..........................................................................................10

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for
IoT-based Smart Shopping Cart
1

1. Introduction

1.1 Purpose

This system gives solution to reduce the shopping time at supermarkets. Every supermarket
employs shopping trolley in order to aid customers to select the products which they intend to
purchase. At billing counter customer may face many problems like waiting and don't know even
they have sufficient money for the products they purchase. The billing process at the counter is a
time consuming and also need more human resource in the billing section. To tackle this problem,
we have proposed a solution in which a smart shopping cart is used to overcome these problems. It
has Barcode scanner and touchscreen display, items that are put in the smart shopping cart are read
one by one and the bill is generated and displayed. After the final bill is generated,the customer
pays the bill by either using their Pre charged cards provided by the shopping mall or through any
one of online payment options such as Paytm, UPI, PhonePay etc. This solution will increase the
consumer experience and reduces the shopping time.

1.2 Document Conventions

This Document was created based on the IEEE template for System Requirement Specification
Documents.
This document uses the following conventions.
RFID Radio Frequency Identification
LCD Liquid Crystal Display
IoT Internet of Things
UHF Ultra-High Frequency
RPi Raspberry Pi

1.3 Intended Audience and Reading Suggestions

 Huge crowd in the supermarket at the time of discount offers or weekends.

 Customers travelling with newborn babies or kids can quickly route to the required products
and finish shopping within no time

 Customers who prefer offline shopping to online shopping but are concerned with the time-
consuming process.
Software Requirements Specification for
IoT-based Smart Shopping Cart
2

 Customers who wish to buy very few items but have to stay in the queue till it’s his/her
chance to make the payment.

 Supermarkets where there are limited number of counters available for billing.

1.4 Product Scope

A huge crowd in the supermarket at the time of discount offers or weekends makes trouble to wait
in long queues because of a barcode-based billing process. In this regard, the Internet of Things
(IoT) based Smart Shopping Cart is proposed which consists of Radio Frequency Identification
(RFID) sensors, Arduino microcontroller, Bluetooth module, and Mobile application. RFID sensors
depend on wireless communication. One part is the RFID tag attached to each product and the other
is RFID reader that reads the product information efficiently. This experimental prototype is
designed to eliminate time-consuming shopping process and quality of services issues. The
proposed system can easily be implemented and tested at a commercial scale under the real scenario
in the future. That is why the proposed model is more competitive as compared to others.

Applications:
• It Can be utilized in dress showrooms.
• Grocery store
• All wholesale shopping malls
• Industrial application, etc

1.5 References

[1] V. V., P. K. P. and C. R. S., "Smart Shopping Cart," 2018 International Conference on Circuits
and Systems in Digital Enterprise Technology (ICCSDET), 2018, pp. 1-4, doi:
10.1109/ICCSDET.2018.8821103.

[2] Zeeshan Ali,Reena Sonkusare,"RFID based Smart Shopping: An Overview" in International

Conference on Advances in “Communication and Computing ” Technologies ,Issue in 2014.

[3] Prasiddhi K. Khairnar,Dhanashri H. Gawali,"Innovative Shopping Cart For Smart Cities " in
IEEE International Conference On Recent Trends in Electronics Information & Communication
Technology (RTEICT), May 19-20, 2017, India.

[4] Mr.P. Chandrasekar,Ms.T. Sangeetha,"Smart Shopping Cart with Automatic Billing System
through RFID and ZigBee" in IEEE S.A.Engineering College, Chennai, Tamil Nadu, 2014,India.
Software Requirements Specification for
IoT-based Smart Shopping Cart
3

[5] Akshay Kumar, Abhinav Gupta, S. Balamurugan, S. Balaji and Marimuthu R., "Smart Shopping
Cart" in School of Electrical Engineering, VIT University,Vellore IEEE,2017.

[6] Ruinian Li, Tianyi Song, Nicholas Capurso,"IoT Applications on Secure Smart Shopping" in
International Conference on Identification, Information and Knowledge in the Internet of
Things,2017.

[7] T. R. Lekhaa, S. Rajeshwari, J. A. Sequeira, and S. Akshayaa, ‘‘Inte lli  gent shopping cart using
bolt Esp8266 based on Internet of Things,’’ in Proc. 5th Int. Conf. Adv. Comput. Commun. Syst.
(ICACCS), Mar. 2019, pp. 758–761.

[8] A. Kumar, A. Gupta, S. Balamurugan, S. Balaji and R. Marimuthu, "Smart Shopping Cart,"
2017 International conference on Microelectronic Devices, Circuits and Systems (ICMDCS), 2017,
pp. 1-4, doi: 10.1109/ICMDCS.2017.8211723.

2. Overall Description

2.1 Product Perspective

Existing System:
In existing system, customer will not know the amount of total purchase, until he went to the
counter for paying bill. One can remove certain product, once he approaches to the counter, where
he decides which product should be reverted back. To avoid these type of troubles, we develop a
smart trolley, where one can know the total bill of the products purchased and bill amount is also
sent to the billing section wirelessly.

Proposed System:
In the proposed system, we are using the RFID reader at the trolley side and every product in the
supermarket has its unique RFID tag with unique ID. Once the customer drops a certain product in
the trolley, then the tag attached to that product was read by the RFID reader and sent to the
controller. The controller counts the product value and displays its value on the LCD screen of the
trolley. Like that we can add any number of products of our need and check the total bill on the
LCD screen.
Software Requirements Specification for
IoT-based Smart Shopping Cart
4

2.2 Product Functions

 The proposed system makes the billing very simple,stable and as well as reliable

 Customers do not need to wait in long queues for getting billed whereas bill can be
generated automatically by using IoT.

 According to the customer’s convenience, the payment can be made:

o Shopping Wallet provided to the user

o By scanning QR code present in trolley
o Payment using Pre charged cards
Software Requirements Specification for
IoT-based Smart Shopping Cart
5

2.3 User Classes and Characteristics

The application is developed in such a way to to give a real shopping experience to the customers in
no time. Customers have to login to the app and can add the items to the cart that they need to buy
from the respective shop. Once the product list is chosen by the customer, that list is sent to the
admin. Customers can pay either by online or by the use of pre charged cards from the respective
shop. Once the admin receives the list, he allots the customer with a trolley number and an
attender’s ID, which is also displayed in the mobile application . Customers will have access to
customer functions, and the administrator will have access to both customer and administrator
functions.

The customer should be able to:

 To store the shopping list
 To manage the shopping list according to preference.
 To find the location of the given product in the supermarket.
 To view the bill after adding every product
 To view the product info

The administrator should be able to achieve the following functions:

 To promote a given product and offer special discounts to the consumers.

 To personalize the shelves and products according to consumer preferences.
 To keep a track of available stocks of various products
 To allocate trolley number and attender(if needed) to the customer.

2.4 Operating Environment

Operating environment for the airline management system is as listed below.

 Android Studio
 Tkinter GUI
 Platform :Python IDLE
 Database : MySQL Database
 Display : Liquid Crystal Display(LCD)
 Microcontroller : Raspberry Pi
Software Requirements Specification for
IoT-based Smart Shopping Cart
6

2.5 Design and Implementation Constraints

RFID tags : RFID provide the storage to store data. We use RFID passive tags which do not need
any power supply from any battery(effecient)

Load cell : A lightweight high-resolution strain gauge loadcell wall is used in place of an ordinary
load cell inorder to reduce the weight of the resultant trolley.

LCD Display: A 16x2 LCD display is very basic module and is very commonly used in various
devices and circuits. A 16x2 LCD means it can display 16 characters per line and there are 2 such
lines. In this LCD each character is displayed in 5x7 pixel matrix. The 16 x 2 intelligent
alphanumeric dot matrix display is capable of displaying 224 different characters and symbols

MySQL Database: Implement the database at least using a centralized database management
system.

2.6 Assumptions and Dependencies

 The Customers are expected to carry their own mobile phone with the mobile application
installed in it.

 Though the proposed system aims at minimizing the time required for shopping and
reducing the involvement of man power in the whole process, a minimum amount of man
power is required to ensure that the whole process is going on smoothly.

 It is assumed that the consumer does not rapidly keep and remove items into the cart in a
way that exceeds the speed at which the system can function

 It is assumed that there is no direct contact of liquids with the system as it may affect the
RFID tags.

 The Customer should be able to understand the location of the product inside the
supermarket by looking on the blueprint of supermarket displayed on the mobile
application(although one may also take the help of the employees).

 As the whole process is largely dependent upon the mobile application-there should be no
bugs in the software(or if any should be resolved immediately).

 The buzzer will be on when the actual quantity weight and billed quantity weights are
mismatched and it is assumed that the buzzer is sufficient enough to prevent theft or
customer’s error.
Software Requirements Specification for
IoT-based Smart Shopping Cart
7

3. External Interface Requirements

3.1 User Interfaces

<Describe the logical characteristics of each interface between the software product and the users.
This may include sample screen images, any GUI standards or product family style guides that are
to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will
appear on every screen, keyboard shortcuts, error message display standards, and so on. Define
the software components for which a user interface is needed. Details of the user interface design
should be documented in a separate user interface specification.>

3.2 Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software product
and the hardware components of the system. This may include the supported device types, the
nature of the data and control interactions between the software and the hardware, and
communication protocols to be used.>

3.3 Software Interfaces

<Describe the connections between this product and other specific software components (name
and version), including databases, operating systems, tools, libraries, and integrated commercial
components. Identify the data items or messages coming into the system and going out and
describe the purpose of each. Describe the services needed and the nature of communications.
Refer to documents that describe detailed application programming interface protocols. Identify
data that will be shared across software components. If the data sharing mechanism must be
implemented in a specific way (for example, use of a global data area in a multitasking operating
system), specify this as an implementation constraint.>

3.4 Communications Interfaces

<Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
Software Requirements Specification for
IoT-based Smart Shopping Cart
8

forms, and so on. Define any pertinent message formatting. Identify any communication standards
that will be used, such as FTP or HTTP. Specify any communication security or encryption issues,
data transfer rates, and synchronization mechanisms.>

4. System Features
<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, or combinations of
these, whatever makes the most logical sense for your product.>

4.1 System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High,
Medium, or Low priority. You could also include specific priority component ratings,
such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1
to a high of 9).>
4.1.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the
behavior defined for this feature. These will correspond to the dialog elements
associated with use cases.>
4.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are
the software capabilities that must be present in order for the user to carry out the
services provided by the feature, or to execute the use case. Include how the product
should respond to anticipated error conditions or invalid inputs. Requirements should
be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a
placeholder to indicate when necessary information is not yet available.>
<Each requirement should be uniquely identified with a sequence number or a
meaningful tag of some kind.>

REQ-1:
REQ-2: