Self checkout application report

Scan&Pay
A
Project Report
Submitted in partial fulfillment of the requirement for the award of degree of
Bachelor of Engineering
In
Computer Science & Engineering
Submitted to
RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA,
BHOPAL (M.P.)
Guided by Submitted By
Mr. Deepak Singh Chouhan Abhishek Patidar (0875CS171008)
Anand Sharma (0875CS171021)
Ashwin Bicholiya (0875CS171030)
Chirag Kumar Mali (0875CS171037)
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
SHIVAJIRAO KADAM INSTITUTE OF TECHNOLOGY & MANAGEMENT-
TECHNICAL CAMPUS, INDORE
INDORE (M.P.) 452001
2020-2021

ii
Declaration
I hereby declared that the work, which is being presented in the project entitled
“Scan&Pay” partial fulfilment of the requirement for the award of the degree of
Bachelor of Engineering, submitted in the Department of Computer Science &
Engineering at Shivajirao kadam Institute Of Technology And Management , Indore
is an authentic record of my own work carried under the supervision of “Mr. Deepak
Singh Chouhan”. I have not submitted the matter embodied in this report for award of
any other degree.
Abhishek Patidar (0875CS171008)

iii
Project Approval Form
I hereby recommend, that the project prepared under my supervision titled by Scan&Pay
be accepted in partial fulfilment of the requirement for the degree of Bachelor of
Engineering in Computer Science & Engineering.
Mr. Deepak Singh Chouhan
Supervisor
Recommendation concurred in
Prof. Nidhi Joshi
Project In-charge
Prof. Brajesh Chaturvedi
Project Coordinator

iv
Acropolis Technical Campus
Deparment of Computer Science & Engineering
Certificate
The project work entitled “Scan&Pay” submitted by Ashwin Bicholiya(0875CS171030),
Anand Sharma (0875CS171021), Chirag Kumar Mali (0875CS171037), Abhishek
Patidar (0875CS171008) is approved as partial fulfillment for the award of the
degree of Bachelor of Engineering in Computer Science & Engineering by Rajiv Gandhi
Proudyogiki Vishwavidyalaya, Bhopal (M.P.).
Internal Examiner External Examiner
Name:………………. Name: ……………..
Date: …./…/……….. Date: …./…/………..

v
Acknowledgement
With boundless love and appreciation, we would like to extend our heartfelt gratitude and
appreciation to the people who helped us to bring this work in reality. We would like to
have some space of acknowledgement for them.
Foremost, our would like to express our sincere gratitude to our supervisor, Mr. Deepak
Singh Chouhan whose expertise, consistent guidance, ample time spent and consistent
advices that helped us/me to bring this study into success.
To the project in-charges Prof. Nidhi Joshi for their constructive comments,
suggestions, and critiquing even in hardship. We also want to thank project coordinator
Prof. Brajesh Chaturvedi for letting my work be an enjoyable moment and for your
brilliant comments and suggestions.
To the Prof. Prashant Lakkadwala, Head, Department of Computer Science &
Engineering for his favourable responses regarding the study and providing necessary
facility.
To the honourable Dr. Sanjay T. Purkar, Principal, ATC, Indore for his unending
support, advises and effort to make possible.
Finally, we would like to pay our thanks to faculty members and staff of Department of
Computer Science & Engineering for their timely help and support.
We also like to pay thanks to our parents for their eternal love, support and prayers.
Without them it is not possible.
Abhishek Patidar (0875CS171008)

vi
Abstract
Mobile applications can be one of the best ways to keep consumers engaged with
a brand as they are on the move. With the increase in demand for smart phones
and efficiency of wireless networks, the demand for mobile applications has
increased incredibly. Android is one of the most popular open source platforms
that offer the developer full access to the framework API's so as to build
innovative applications. Our project “Scan&Pay” is an android application which
helps the user to purchase the item from stores . This projects overall gives the
easier way to purchase the desired items from stores which will save time with its
simple and effectiveness. The main aim of this project is to build an Android
application that helps the users to purchase the items from stroes without face
long queues and have to wait for their turns. This is a major problem facing by
almost every type of stores, in order to solve this one efficient solution is self
checkout system i.e customer will buy the required goods scans them and pay the
bill by the App itself so this will make process more convienient. The users can
register and login to the app by providing their details. The users can purchase the
item as their desire and they can pay through Credit Card/Debit Card or UPI.The
admin will have control over the entire system. He can view everyone's profile
associated with the Stores. The admin can view records of users and as well all
the users associated to the app have to register. Only registered people can have
access to Purchase the item. The user can view theStores and purchase the
available items through the application. They can also view the Stores profiles
only to know their specialization, their records so that they can approach those
specific Stores.

vii
Table of Content
Chapter 1: Introduction.........................................................................................................
1.1 Rationale .....................................................................................................................
1.2 Goal.............................................................................................................................
1.3 Objective .....................................................................................................................
1.4 Methodology...............................................................................................................
1.5 Role .............................................................................................................................
1.6 Contribution of Project ...............................................................................................
1.6.1 Market Potential...................................................................................................
1.6.2 Innovativeness......................................................................................................
1.6.3 Usefulness ............................................................................................................
1.7 Report Organization....................................................................................................
Chapter 2: Requirement Engineering....................................................................................
2.1 Requirement Collection ..............................................................................................
2.1.1 <Collection Type 1> ............................................................................................
2.1.2 <Collection Type N> ...........................................................................................
2.2 Requirements ..............................................................................................................
Chapter 3: Analsis & Design ................................................................................................
3.1 Use-case Diagrams......................................................................................................
3.2 Activity Diagrams.......................................................................................................
3.3 Sequence Diagrams.....................................................................................................
3.4 Class Diagrams ...........................................................................................................
3.5 Data Design.................................................................................................................
3.5.1 Schema Definitions..............................................................................................

viii
3.5.2 Integrity Constraints.............................................................................................
3.6 System Architecture....................................................................................................
Chapter 4: Construction........................................................................................................
4.1 Implementation ...........................................................................................................
4.1.1 Implementation Details........................................................................................
4.2 Testing.........................................................................................................................
4.2.1 White Box Testing ...............................................................................................
4.2.2 Black Box Testing................................................................................................
Conclusion & Future Works…………
Appendix A

1
Chapter 1
Introduction
 The retail sales industry has undergone some noticeable transition in the array of
payment methods over the years. Local Retail supermarkets like Dmart, BestPrice
are facing a problem of huge crowd at their billing counters at the time of billing,
specially at rushing shopping hours ,festival seasons ,people have to face long
queues and have to wait for their turns .This is a major problem facing by almost
every type of stores, in order to solve this one efficient solution is self checkout
system i.e customer will buy the required goods scans them and pay the bill by
the App itself so this will make process more convienient.
1.1 Rationale
• The top reasons why Scan&Pay. The reason is self-checkout application is mobile
enabled thus makes it cost effective as it doesn’t require any procurement and
installation of heavy and expensive machines or devices.
• Although there exist a cashier checkout system where Barcode scanner devices
scan the barcode of product and peoples have to pay the amount of products and
the long line at the cashier checkout points which can be frustrating at times for
both customers and the cashier. Especially stores that frequently experience a
large number of customers trying to checkout at the same time. So we are
replacing this old fashioned payment(cashier checkout system) with mobile self-
checkout application.
1.2 Goal
Mobile applications can be one of the best ways to keep consumers engaged with a brand
as they are on the move. With the increase in demand for smart phones and efficiency of
wireless networks the demand for mobile applications has increased incredibly. Android

2
is one of the most popular open source platforms that offers the developers full access to
the framework API's so as to build innovative applications
The main aim of this project is to build an Android application that helps the users to
Purchase itms from the specified.The main features provided by the Scan&Pay
application are as follows :
• Users can signup and signin.
• Restaurant can signup and sigin.
• Provides the searching facilities based on various factors. Such as Food item, Cart,
Order, Customer.
• It tracks all the information of Category,Order etc
• Manage the information of Category.
• Shows the information and description of the item, Cart.
• To increase efficiency of managing the item, Category.
• It deals with monitoring the information and transactions of Order.
• Manage the information of item.
• Manage the information of Order.
1.3 Objective
The main objective of the Project on Scan&Pay Application is to manage the details of
item, Category, Cart, Order, Customer. It manages all the information about item,
Customer. The project is totally built at user, Stores and administrator end and thus only
the administrator is guaranteed the access. The purpose of the project is to build an
application program to reduce the manual work for managing the item, Category,Cart. It
tracks all the details about the Cart, Order, Customer.
1.4 Methodology
The Methodology Adopted is “Agile Methodology” .

3
The Agile Method and methodology is a particular approach to project management that
is utilized in software development. This method assists teams in responding to the
unpredictability of constructing software. It uses incremental, iterative work sequences
that are commonly known as sprints.
A sprint is a period of time allocated for a particular phase of a project. Sprints are
considered to be complete when the time period expires. There may be disagreements
among the members of the team as to whether or not the development is satisfactory;
however, there will be no more work on that particular phase of the project. The
remaining phases of the project will continue to develop within their respective time
frames.
1.4.1 The General Principles of the Agile Method
• Satisfy the client and continually develop software.
• Changing requirements are embraced for the clients competitive advantage.

4
• Concentrate on delivering working software frequently. Delivery preference will be
placed on the shortest possible time span.
• Developers and business people must work together throughout the entire project.
• Projects must be based on people who are motivated. Give them the proper environment
and the support that they need. They should be trusted to get their jobs done.
• Face-to-face communication is the best way to transfer information to and from a team.
• Working software is the primary measurement of progress.
• Agile processes will promote development that is sustainable. Sponsors. developers,
and users should be able to maintain an indefinite. constant pace.
• Constant attention to technical excellence and good design will enhance agility.
Simplicity is considered to be the art of maximizing the work that is not done. and it is
essential.
• Self-organized teams usually create the best designs.
1.5 Role
Role of individual member may in each phase of software development or anything else.
Team
Members
Requirment
Gatherings
Analysis Design Implementation Testing Documentation
Ashwin
Bicholiya
✓ ✓ ✓ ✓ ✓ ✓
Anand
Sharma
✓ ✓ ✓ ✓ ✓
Chirag
kumar
mali
✓ ✓ ✓ ✓ ✓
Abhishek ✓ ✓ ✓ ✓ ✓

5
Patidar
1.6 Contribution of Project
Refer to Synopsis Format.
1.6.1 Market Potential
• The figure shows that the recent evolutions have all been incremental in their
value proposition.
• We can say that the next big thing after barcodes was the self‐ checkout counter
and Mobile self Checkout System.
Checkout is the last opportunity for the retailer to make an impression on the consumer.
2000-2015
Barcode
Scanners at the
cash counters
2015-2022
Self-
Checkout
Kiosks
2022
Mobile self
Checkout
System

6
1.6.2 Innovativeness
• The mobile self-checkout application is operated via a virtual shopping cart.
• This virtual shopping cart is linked to the customer’s account which consists of
the customer’s personal and payment card information created on the mobile
application. and complete the Payment.
• The payment can be done by credit, debit cards and NetBanking as well as other
payment merchants like Paytm, GooglePay, PhonePay etc. for a seamless
payment system.
1.6.3 Usefulness
By the help of our application one can have their Items without facing a problem of huge
crowd at their billing counters at the time of billing .It can save enomous amount of
people’s time as many a times people who are having 9 to 5 job.
1.7 Report Organization
The remaining section of the report is structured as follows. Chapter 2 provides detailed
business and technical requirements. Different steps taken for information collection are also
discussed in this chapter. Chapter 3 provides details analysis…………….. and so on.

7
Chapter 2
Requirement Engineering
Requirement Engineering is the process of defining, documenting and maintaining the
requirements. It is a process of gathering and defining service provided by the system.
Requirements Engineering Process consists of the following main activities:
 Requirements elicitation
 Requirements specification
 Requirements verification and validation
 Requirements management
Requirements Elicitation:
It is related to the various ways used to gain knowledge about the project domain and
requirements. The various sources of domain knowledge include customers, business
manuals, the existing software of same type, standards and other stakeholders of the
project.
The techniques used for requirements elicitation include interviews, brainstorming, task
analysis, Delphi technique, prototyping, etc. Some of these are discussed here. Elicitation
does not produce formal models of the requirements understood. Instead, it widens the
knowledge domain of the analyst and thus helps in providing input to the next stage.
Requirements Specifications:
This activity is used to produce formal software requirement models. All the
requirements including the functional as well as the non-functional requirements and the
constraints are specified by these models in totality. During specification, more
knowledge about the problem may be required which can again trigger the elicitation
process.
The models used at this stage include ER diagrams, data flow diagrams(DFDs), function
decomposition diagrams(FDDs), data dictionaries, etc.
Requirements verification and validation:
Verification:
It refers to the set of tasks that ensure that software correctly implements a specific
function.
Validation:
It refers to a different set of tasks that ensure that the software that has been built is
traceable to customer requirements.
If requirements are not validated, errors in the requirements definitions would propagate
to the successive stages resulting in a lot of modification and rework.
The main steps for this process include:

8
 The requirements should be consistent with all the other requirements i.e no two
requirements should conflict with each other.
 The requirements should be complete in every sense.
 The requirements should be practically achievable.
Reviews, buddy checks, making test cases, etc. are some of the methods used for this.
Requirements Management:
Requirement management is the process of analyzing, documenting, tracking, prioritizing
and agreeing on the requirement and controlling the communication to relevant
stakeholders. This stage takes care of the changing nature of requirements. It should be
ensured that the SRS is as modifiable as possible so as to incorporate changes in
requirements specified by the end users at later stages too. Being able to modify the
software as per requirements in a systematic and controlled manner in an extremely
important part of the requirements engineering process.
2.1 Requirement Collection
2.1.1 IDE : Integrated Development Environment
An IDE typically contains a code editor, a compiler or interpreter, and a debugger,
accessed through a single graphical user interface (GUI). The user writes and edits source
code in the code editor. The compiler translates the source code into a readable language
that is executable for a computer. And the debugger tests the software to solve any issues
or bugs.
2.1.2 SDK Software Development Kit:
A software development kit (SDK) is a collection of software development tools in one
installable package. They ease creation of applications by having compiler, debugger and
perhaps a software framework. They are normally specific to a hardware platform and
operating systems combination.
2.1.3 Programming Language:
A programming language is a formal language, which comprises a set of instructions that
produce various kinds of output. Programming languages are used in computer

9
programming to implement algorithms. Most programming languages consist of
instructions for computers.
2.1.3 OS (Operating System):
An operating system is system software that manages computer hardware, software
resources, and provides common services for computer programs.
2.2 Requirements
2.2.1 Functional Requirements:
• Application can be run on the wifi or cellular network.
• User can select the models.
• User can allow to open the camera to take real time images.
• Model work on real time images and give the output.
2.2.2 Non-Functional Requirements:
For developing the application the following are the Hardware Requirements.
Processor: Intel core i3 or higher
RAM: 4 GB
Space on disk: minimum 10GB

10
Flutter:
Flutter is Google's UI toolkit for crafting beautiful, natively compiled applications for mobile, web,
and desktop from a single codebase. Flutter works with existing code, is used by developers and
organizations around the world, and is free and open source.
2.2.3 Visual Studio Code:
Visual Studio Code is a code editor redefined and optimized for building and debugging
modern web and cloud applications. Visual Studio Code is free and available on your
favorite platform - Linux, macOS, and Windows.

11
2.2.4 Android Studio:
Android Studio is the official integrated development environment (IDE) for Google's
Android operating system, built on JetBrains' IntelliJ IDEA software and designed
specifically for Android development. It is available for download on Windows, macOS
and Linux based operating systems.
2.2.5 Dart Programming Language:

12
Dart is a client-optimized programming language for apps on multiple platforms. It is
developed by Google and is used to build mobile, desktop, backend and web
applications. Dart is an object-oriented, class defined, garbage-collected language using
a C-style syntax that transcompiles optionally into JavaScript.
2.2.6 Firebase:
Firebase is a Backend-as-a-Service — BaaS — that started as a YC11 startup and grew
up into a next-generation app-development platform on Google Cloud Platform.
... Firebase frees developers to focus crafting fantastic user experiences. You don't need
to manage servers. You don't need to write APIs.
Chapter 3
Analysis & Design
3.1 Use-case Diagrams
A use-case diagram is a graphical depiction of the interaction among the elements of a
system. A use-case is a methodology used in system analysis to identify, clarify, and
organize system requirements. In this context, the term "system" refers to something
being developed or operated, such as a models . Use case diagrams are employed in

13
UML, a standard notation of real world objects and systems. System objectives can
include planning overall requirement, validating a hardware design, testing and
debugging a software product under development creating an online help reference, or
performing a consumer-service-oriented task. The main components of use-case are:
• Actor.- something with a behavior or role, e g., a person, another system, organization.
• Scenario.- a specific sequence of actions and interactions between actors and the
system.
• Use case:- a collection of related success and failure scenarios, describing actors using
the system to support a goal.
When the customer creates a new account or logs in successfully, the virtual shopping
cart offers the customer the liberty to scan any product of their choice and add or remove
them.
The store clerk returns products that have been removed from the virtual shopping cart to
their original position on the shelf if they are not returned by the customer.

14
Use case diagram of virtual shopping cart I.
The virtual shopping cart automatically identifies the store outlet and loads up the product
list of the store outlet from where the customer is initiating the mobile self-checkout
application. The store outlet allows several customers to shop and use the mobile
selfcheckout application at the same time.
Moreover, the application also notifies the customer via a prompt when there is an issue
reading the product bar code.

15
Use case diagram of virtual shopping cart II.
 Virtual shopping cart: Removing products
the customers will still be able to view the virtual shopping cart and remove a product of
their choice by selecting the product and clicking on “remove product” option without the
need to rescan since the product has been scanned earlier and already exists in the virtual
shopping cart.

16
Use case diagram showing the removal of products from the cart.
 Verification
The store needs to verify that all transaction and payment by customers are thoroughly
scrutinized and approved before a customer exits the store.

17
Use case diagram for payment operation.
 Checkout.
When the payment is verified, the application generates a payment confirmation receipt
which displays the QR code and transaction number. The customer can exit the store
afterwards.
1. Customer: Adding and removing products
The customer can add any product of their choice at the store through the following
simple steps:
• Customer views existing virtual shopping cart.
• Customer clicks “Add Product” to add product to cart.
• Customer scans barcode of product.
• Customer confirms product to be added to cart.
A Customer can successfully remove any product from their virtual shopping cart as via
the following steps.

18
• Customer views virtual shopping cart.
• Customer clicks “Remove Product” to remove product from cart.
• Customer accepts prompt to remove product.
• Customer returns product to its place in store.
Use case diagram for adding / removing product from the cart.
2. Exception flow
There are instances where the mobile self-check application experiences difficulties in
either adding or removing products in the virtual shopping cart . These exceptions may be
due to various factors.
There are occasions when the scanner is unable to read the product barcode. This may be
because of an improper product scan by the customer. When the customer does not align

19
the product correctly with the scanner. The application in this instance will prompt the
customer to re-scan the product as depicted.
Use case diagram when scanner cannot read barcode.
The customer can also have trouble in viewing the shopping cart. This may arise because
of software error e.g. out-of-date software version or GPS store location error. In this
instance, the application promptly informs both the customer and the store. After a
successful software update, the customer can delete the previous virtual shopping cart
and create a new one afterward if the application crashes while the customer is shopping.
Other reasons are when the customer tries to create a second instance of the application
while shopping at the store. The application checks for an existing session and prompts
the customer to use existing the existing session.

20
Use case diagram when customer cannot view cart.
3.2 Activity Diagrams
Activity diagram is another important diagram in UML to describe dynamic aspects of
the system. Activity diagram is basically a flow chart to represent the flow form one
activity to another activity. The activity can be described as an operation of the s drawn
from one operation to another. This flow can be sequential, system. So the control flow is
branched or concurrent. control by usin Activity diagrams deals with all type of flow g
different elements like fork, join etc.

21
When to use an Activity Diagram:-
• When describing work flow across many use cases.
• When analyzing a use case, and before methods are assigned to symbols.
• When dealing with multi-threaded applications.
 Virtual Shopping Cart
When the application is launched after download and installation, it lists the store
location of the nearest outlets the application is initiated from. When the customer
selects the outlet they intend to shop, an account page appears where customers can
create an account if they are using the application for the first time.
Customers can log in if they already have an account. The application prompts the
customer to re-login using correct account information if an invalid username and
password
Figure 3.1: Activity diagram of login page.

22
 Virtual shopping cart: Adding products
On successful account creation, the customer will be able to view the virtual shopping
cart and product list of the store outlet
3.3 Sequence Diagrams
A Sequence diagram is an interaction diagram that shows how objects operate with one
another and in what order It is a construct of a message sequence chart it shows object
interaction arranged in time sequence It depicts the objects and classes involved in the
scenario and the sequence of messages exchanged between the objects needed to carry
Oct the functionality of the scenano Sequence diagrams are typically associated with use
case realizations in the Logical View of the system under develoPment. Sequence

23
diagrams are sometimes called event diagrams or event scenarios. A sequence diagram
shows as parallel vertical lines (lifelines).
3.4 Product life management
At regular intervals, the store needs to fashion out a system to undergo a product
routine check. During this routine check, products due for replacement either because
of they have been expired or need to be discontinued can be effectively resolved and
subsequently removed from the shelves.
Identifying and removing expired products is mandatory especially with consumables
and cosmetics products. It not only prevents instances of customers being exposed to
the dangers of consuming them, but the reputation of the store is maintained by
making sure all safety standards are complied with.
A store can discontinue a product for various motives. One is when the demand of
such product decreases. When a product remains on the shelf for a long period
without being sold, it does not augur well for the store. The decision by the store to

24
discontinue such a product is indeed in order. The store can also decide to
discontinue a product that is out of current trend e.g. clothing items [6].
Moreover, a store is obligated to discontinue a product if the manufacturer ceases
producing the product due to reasons like product defects posing harmful threats,
manufacturing company folding up etc. [6].
A class diagram can be derived from these events as depicted in figure 11.
Figure 11. Class diagram for product life management.

25
3.7 Data Design
3.7.1 Schema Definitions
We have used NoSQL database so the Schema is in the format of JSON.
User {
User id:”value”[
“value”,
“value”
]
Email id: “value”
Password: “value”
Name: “value”
}
Stores {
Restaurant id: “value” [
“value”,
“value”
]
Email id: “value”
Password: “value”
Name: “value”
}
StorestData {
StoresData: “value” [
“value”

26
“value”
]
Amount: “value”
ProductName: “value”
ImageUrl: “value”
StoresName: “value”
Barcode:”Value”
}
3.7.2 Integrity Constraints
● We are using Firebase hence the data that is requested or updated are stored in
device offline then if there is an internet connection the data is synchronized with
the cloud.
● It also has auto re-attempt functionality that retries automatically if there is some
issue with the internet or server.
Domain Diagram

28
Chapter 4
Construction
4.1 Implementation
We have implemented our application by Dart programming language with the help of
Flutter SDK and for the source code editor and automation tool we used VS Code.
4.1.1 Implementation Details
4.1.1.1 Software Details
For delevoping application following are the Software Requirements:-
Operating System: Windows 10
Language: Flutter SDK, Dart
Technologies used Flutter SDK, Dart, Android Studio, Vs Code
Debugger: Android Dalvik Debug Monitor service
For running the application the following are the Software Requirements:
Operating System. Android 7.0 or higher versions
Network: Wi-Fi Internet or cellular Network 3
4.1.1.2 Hardware Details
Processor: Minimum 2 GHz
Memory (RAM): Minimum 4GB
Hard Drive: 50 GB
4.2 Testing
Testing is vital for the success of any software. no system design is ever perfect. Testing
is also carried in two phases. first phase is during the software engineering that is during

29
the module creation. second phase is after the completion of software. this is system
testing which verifies that the whole set of programs hanged together.
Testing Scope :
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and code generation Once source code has been
generated, software must be tested to uncover and correct as many errors as possible
before delivery to the customer. Our goal is to design a series of test cases that have a
high likelihood of finding errors. That's where software-testing techniques come in to the
picture. These techniques provide systematic guidance for designing tests that
1. Exercise the internal logic of software components and
2. Exercise the input and output domains of the program to uncover errors in program
function, behavior and performance.
Testing of the software leads to the uncovering of errors in the software functional and
performance requirements are met. Testing also provides a good indication of software
reliability as software quality as a whole. The result of the different phases of testing are
evaluated and then compared with the expected results. If the errors are uncovered they
are debugged and corrected. A strategy approach to software testing has the generic
characteristics:
1. Testing begins at the module level and works "outwards° towards the integration
of the entire computer based system.
2. Different testing techniques are appropriate Testing and Debu at different points
of time.
3. Testing and Debugging are different activities, but debugging must be
accommodated in the testin, strategy A strategy for the software testing must
aCcon.m.dated low level tests that are necessary to verify that a small source code
segment is Pertbrining correctly according to the customer's requirements and that
of developer's expectations.
Testing Principle:

30
Testing is the process used to measure the quality of developed computer software
software is a Process designed to make computer code does that it was designed
to do and that does not do anything unintended. One of the primary causes of poor
program testing is the tact that most programmer begin with a false definition of
the term They might say testing Is the processed demonstrating that error are not
present.
1. The purpose of testing is to show that a program performs its intended
function correctly.
2. "Testing is a process of establish confidence that program does what it is
supposed to do ". this last statement are all based on false primes At the start
of testing, a program should not be merely tested to show that it work Rather
the test should start with the assumption that the program contains error and
the goal is to find as many error as possible.
4.2.1 White Box Testing
White box testing approach focus on the program control structure .Knowing the internal
working of program. test can be conducted to ensure that internal operations are
performed According to specification and all internal components have been exactly
exercised It examines the logic of the program by testing every path of the program.
White box testing improves its quality through condition testing winch attempts to find
errors in the following categories:
1. Boolean operator error
2. Boolean variable error
3. Relational operator error
Complexity of test and uncovered error is limited by the constrained scope establish for
unit testing The unit test is white box oriented, and the step can be conducted in parallel
for multiple components.

31
4.2.2 Black Box Testing
Black box testing This approach locus on the functional requirements of the software
Knowing the specified function that a product has been designed to perform, tests can be
conducted that demonstrate each function is fully operational while at the same time
searching for errors in each function. Black box testing attempts to find errors in the
following categories
1. Incorrect or missing unction
2. Interface errors
3. Errors in database and external data base access.
Testing involves the various text and invalid entries in the name text box, trying to filling
of invalid entries in the flex grid, etc.
Test Case: N+1
Test Case: M
4.3:TestCases
4.3.1 Unit Testing
In unit testing, various modules have been tested individually. This has been done
manually to test if the expected result is actually seen on the screen. The following are
the test cases with the help of which the application has been tested.
Sr. No Test-case Description Expected Result Actual Result
1. On Load of Home Screen Take Minimum 5 sec Pass
2. On clicking Sign in as user Display the screen of User
login
Pass
3. On clicking the Product item cart
icon
Item Added in the cart Pass

32
4. On clicking the Next Button Display the Payment Option
Screen
Pass
5. On clicking Debit and Credit card or
UPI option
Display the Payment Screen Pass
6. On Clicking the Logout Button Profile get Logout Pass
Conclusion & Future Works
The aim was to propose a functional model for a mobile self-checkout application
that will be developed for a client's retail store. The features of the application were
clearly expounded by highlighting the probable chain of actions that may occur
between the key actors of the application i.e. virtual shopping cart, store, employee
and the customer and the mobile self-checkout application.
The sequence of events owing to the interaction of an actor or collection of actors
with the application were distinctly illustrated with UML diagrams. In some rare case
where events did not happen as premeditated, reasons were given as well as helpful
tips on how to remedy such occurrence.
This study also developed a user interface prototype to show the possible appearance
of the mobile self-checkout application. A recommendation for the frontend, backend
technology and implementation best suitable for the development of the application
is given later in this section.
It is clear the application is going to be an immense asset to the client's business
venture. Congestion currently experienced during peak period of sales at the cashier
checkout point will be a thing of the past. The shopping process will be much faster,
efficient and less strenuous for all parties involved. Moreover, from the store
perspective, documentation and tasks e.g. store inventory, sales reports, product
restock orders will be effortlessly implemented.

33
Future Work:
The application can be improved in many ways and can be extended to support more
devices like the tablets and iOS devices. In the upcoming days we can improve our
application by adding Dashboard for Stores Owner where the Store owner can track the
order of users. Also we will add offer page where users can get the best deals on
Products.
References:
 https://scet.berkeley.edu/wp-content/uploads/UCB-ELPP-Future-of-Self-
Checkout-Report.pdf
Github Link of our project:
 https://github.com/Ashwinbicholiya/scanpay

Self checkout application report

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Self checkout application report

Ähnlich wie Self checkout application report (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Self checkout application report