Shopping

A Software Engineering Project
On
Shopping With Use of Barcod Scanner
as the partial fulfillment of
Semester –VI study
for the degree of
Bachelor of Science (Computer Science)

(Affiliated to Veer Narmad South Gujarat University)
during the academic year 2019-2020.
Developed By: Guided By:

Jay Kalariya Dr.Charmy Patel
Sarvajanik Education Society

Shree Ramkrishna Institute of Computer Education and Applied Sciences
Behind P.T Science College, M.T.B. College Campus, Athwalines, Surat-395 001.
Sarvajanik Education Society
Shree Ramkrishna Institute of Computer Education and Applied Sciences
Behind P.T. Science College, M.T.B College Campus, Athwalines, Surat-395 001.
CERTIFICATE
DEPARTMENT OF COMPUTER SCIENCE
This is to certify that Exam no :

Student name :
Jay Kalariya
has / have successfully completed his / her / their software engineering project work entitled
Shopping With Use of Barcod Scanner
as the partial fulfillment of

Semester -VI study
for the degree of
Bachelor of Science (Computer Science)
(Affiliated to Veer Narmad South Gujarat University)
during the academic year 2019-2020.
___________________ ___________________
Internal Project Guide HOD
Dept. of Computer Science
Date : ____________ Place : Surat
University Examination:
Examination No. : ____________
Signature of External Examiners : _______________________________
_______________________________
_______________________________
INDEX
SR.NO CONTENTS Page. No

1. Introduction
 Project Profile
2. System Introduction
 System Definition, Objective and scope
 Hardware & Software Requirements
3. Requirement Analysis & Modeling

 Expected working of system
 Data Flow Diagrams (DFD)
 Process Specification
 Data Dictionary
4. Design
 ER Diagram & Database Design
 System Architecture
 System Flowchart
 Form & Report Designs (Screenshots) Layouts
5. Coding
 Coding Approach/style
 Code Snippets
6. Testing
 Testing Data Inputs ( Data Validations)
 Testing Operations (Actions on each screen)
7. New Tools/ Technologies learned/used
8. System Limitations/Restrictions and

Dependencies/Constraints
9. Future Enhancement & Opportunities
10. Bibliography & References
3
SRICEAS Shopping With Use Of Barcode Scanner
1) INTRODUCTION
4

Project Profile : 
Project Title Shopping With Use Of Barcode Scanner
Project Description The System is Proposed to have following

modules:
 Dealer Module
 User Module
Function Of Dealer :
 Login
 Insert Product
 Update Product
 Remove Product
Function Of User :
 Login
 View Product
 Scan Barcode
 Buy Products
Duration 3 Months
Project Guide Dr.Charmy Patel
Front End Tool Android Studio
Back End Tool SQLite And FireBase
Operating System Window 10 (64-Bit)
Submitted By Jay Kalariya
5
2.System introduction
6



System Definition : 
 
o The main purpose of this project is to shop products by the use of barcode
scanner.
o The Dealer will have special privileges to Add/Update/Delete Product with

Details. The Dealer can login to the Mobile Application and make changes
according to his wish .
o Similarly the User will have their own credentials or can register with new id to
enter into the Application and buy Products.
Objective : 

o The main objective of the system is to reduce the queue at shopping malls.
Shopping and maintain system with powerful algorithms which can generate
bill by considering all the constraints and limitations.
o Barcodes are applied to products as a means of quick identification. They are

used in retail stores as part of the purchase process, in warehouses to track
inventory, and on invoices to assist in accounting, among many other uses.
o So with the help of those barcodes this system will do entries for cart as all the
information can be linked with barcodes.
Scope :
o Scope of this system is limited to adding or removing or updating products by

admin or dealer and the same product added can be used by user after scanning
the barcode to add in his/her cart.
o The scope of this project is limited to Android Devices.





7





Hardware Requirement :
o Processor : Any but latest is good for better experience

o Ram : 500 MB (Minimum)
o HDD : 2 GB (Minimum)
Software Requirement :
o Operating System : Any Android Version

o Front-End Tool : Any Android Mobile


8
3. Requirement Analysis & Modeling
9
Expected Working of System :
 Dealer
 Login into Application
 Insert Product
 Update Product
 Remove Product
 User
 Login into Application
 Search Product
 Scan Product
 Buy Product
10
Data Flow Diagram:
 0 Level DFD :
 1 Level DFD (Admin Side) :
11
 1 Level DFD (User Side) :
12
 2 Level DFD :
13
















14
Process Specification :
 Process : 1
Process Name : Login
Input : Email ,Password
Output : Login Success
Entity : User ,Dealer
Database : User ,Dealer
Description : In this Process Dealer and User

Login With use of Their Email
And Password
15
 Process : 2
Process Name : Search Product
Input : Product Name
Output : Product Details And Location
Entity : User
Database : Product
Description : In this Process User Search

Product And View Product
Information and Location In
Perticular Shope.
16
 Process : 3
Process Name : Buy Product
Input : Product Barcode
Output : Product
Entity : User
Database : Product
Description : In this Process User Search

Product And View Product
Information and Location In
Perticular Shope.
17
 Process : 4
Process Name : Manage Order
Input : Product Details
Output : Order Details
Entity : Dealer
Database : Product ,Order
Description : In this Process All Order

managed with product details,
quantity of each product and
price, and Total Amount.
18
 Process : 5
Process Name : Manage Report
Input : Orders
Output : Report
Entity : Dealer
Database : Order
Description : In this Process Dealer Can

Manage Reports with Daily
,Monthly and Yearly Orders.
19
4. Design
20
ER Diagram:




21
Datebase Design:
Table name : Dealer
No Field Name Datatype Constraint Description

1 Dealer ID Number Primary key Contains Id of
Dealer
2 Dealer Name Text Contains Name
of Dealer
3 Dealer Email Text Contains Email
of dealer
4 Password Text Contains
Password of
dealer
5 Dealer Address Text Contains
Address of
Dealer
6 Dealer City Text Contains City
of Dealer
22
Table name : User

1 Cust Id Number Primary Key Contains id of
User
2 Fname Text Contains First
name of User
3 Lname Text Contains Last
name of User
4 Email Text Contains Email
of User
5 Mobile Text Contains
Mobile of User
6 Address Text Contains
Adress of User
7 Pincode Number Only 6Digits Contains
Pincode of
Area
8 City Text Contains City
Name Of User
23
Table name : Products

1 Product Id Number Primary Key Contains
Product Id
2 Product Name Text Contains Name
of Product
3 Product Desc Text Contains
description of
Product
4 Product Price Number Contains Price
of products
5 Product Units Number Contains Units
of Products
6 Brand Id Number Foreign key Contains
with Brands Name
References of of Products
Brands Table
7 Category Id Number Foreign key Contains
with Category name
References of of Products
Category Table
8 Product Text Contains
Barcode Barcode value
of Product
24
Table Name : Category

1 Cat Id Number Primary Key Contains Id of
a Category
2 Category Text Contains
Name Category Name
Table Name : Brands

1 Brand Id Number Primary Key Contains Id of
a Brands
2 Brand Name Text Contains
Brands Name
3 Category Id Text Foreign key Contains
with Category Id
References of
Category Table
25
Table Name : Orders

1 Order_ID Number Contains Id Of
Orders
2 Product ID Number Foreign key Contains Id Of
with Ordered
References of Products
Products Table
3 Product Units Number Contains Units
of Purchased
Products
4 Total Number Contains Total
Payeble
Amount
5 Date of order Date Contains Date
of Orders
6 Customer ID Number Foreign key Contains Id of
with Customers
references of
Customer
Table
26
Flow Chart :
 Dealer Module
27
 User Module
28
Form & Report Designs :
29
30
31
32
33
34
5. Coding
35
Code Snippest :
36
37
38
6. Testing
39
 Login Page
No. Input Expected Actual Result Result

Result
1 Valid Email and Login Success As Expected Login Success
Password
2 Valid Email and Error Message As Expected Login Fail

Invalid
Password
3 Invalid Email Error Message As Expected Login Fail
and Valid
Password
4 Invalid Email Error Message As Expected Login Fail
and Password
 Product Scan

Result
1 Valid Product Add Item In As Expected Item Add In
Code Cart Cart
2 Invalid Product Error Message As Expected Item Not Add

and Error
MEssage
40
 Quantity Increase/Decrease

Result
1 Increase Quantity and As Expected Quantity and
Quantity Price Increase Price Increase
2 Decrease Quantity and As Expected Quantity And

Quantity Price Decrease Price Decrease
41
7. New Tools /Technologies learned/ used
42
New Tools / Technologies Learned / Used :
 Android Studio
 SQLite Database
 Firebase Database
 Android Using Java
 Android Design Interface
43
8. System Limitations / Constraints
44
System Limitation / Constraints :
 The system is limited to android devices only
 The system is limited to products without sensors
 There is no automation in system
 There will be ambiguity if there are different bar codes for same
products
45
9. Future Enhancement & Opportunities
46
Future Enhancement & Opportunities :
 The future of this project is really vast.
 Automation can be implemented with sensor engineering.
 Data mining can be done for better suggestions of products.
 Product images can be added in No SQL firebase.
47
10. Bibliography & References
48
Bibliography & References :
 Guidelines Of Dr.Charmy Patel & Mr.Jayesh Pushtiwala sir
 www.youtube.com
49

Shopping

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Shopping

Uploaded by

Copyright:

Available Formats

A Software Engineering Project

as the partial fulfillment of

Semester –VI study

for the degree of

Bachelor of Science (Computer Science)

Developed By: Guided By:

Sarvajanik Education Society

This is to certify that Exam no :

Shopping With Use of Barcod Scanner

as the partial fulfillment of

Date : ____________ Place : Surat

Examination No. : ____________

Signature of External Examiners : _______________________________

SR.NO CONTENTS Page. No

 Hardware & Software Requirements

3. Requirement Analysis & Modeling

 Data Flow Diagrams (DFD)

 Form & Report Designs (Screenshots) Layouts

 Testing Operations (Actions on each screen)

7. New Tools/ Technologies learned/used

8. System Limitations/Restrictions and

Project Title Shopping With Use Of Barcode Scanner

Project Description The System is Proposed to have following

Project Guide Dr.Charmy Patel

Front End Tool Android Studio

Back End Tool SQLite And FireBase

Operating System Window 10 (64-Bit)

Submitted By Jay Kalariya

o The Dealer will have special privileges to Add/Update/Delete Product with

o Barcodes are applied to products as a means of quick identification. They are

o Scope of this system is limited to adding or removing or updating products by

o Processor : Any but latest is good for better experience

o Operating System : Any Android Version

 1 Level DFD (Admin Side) :

Process Name : Login

Input : Email ,Password

Output : Login Success

Entity : User ,Dealer

Database : User ,Dealer

Description : In this Process Dealer and User

Process Name : Search Product

Input : Product Name

Output : Product Details And Location

Description : In this Process User Search

Process Name : Buy Product

Input : Product Barcode

Description : In this Process User Search

Process Name : Manage Order

Input : Product Details

Output : Order Details

Database : Product ,Order

Description : In this Process All Order

Process Name : Manage Report

Description : In this Process Dealer Can

Table name : Dealer

No Field Name Datatype Constraint Description

No Field Name Datatype Constraint Description

No Field Name Datatype Constraint Description

No Field Name Datatype Constraint Description

Table Name : Brands

No Field Name Datatype Constraint Description

No Field Name Datatype Constraint Description

No. Input Expected Actual Result Result