Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
989 views42 pages

Shopping Cart System Report

The document describes a project report on a shopping cart system. It includes an introduction to the existing system and need for a new system. It then describes the proposed shopping cart system including its modules, objectives and system requirements. It also includes sections on system analysis and design such as use case diagrams, activity diagrams, class diagrams and database design.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
989 views42 pages

Shopping Cart System Report

The document describes a project report on a shopping cart system. It includes an introduction to the existing system and need for a new system. It then describes the proposed shopping cart system including its modules, objectives and system requirements. It also includes sections on system analysis and design such as use case diagrams, activity diagrams, class diagrams and database design.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 42

A

PROJECT REPORT
ON

SHOPPING CART SYSTEM

BY

HIVALE SAKHARAM RAJU


SEM – III, DIV-D
ROLL NO.422
SEAT NO. 20360
2021-2022

SUBMITTED TO
SAVITRIBAI PHULE PUNE UNIVERSITY
PUNE- 411041

IN PARTIAL FULFILLMENT OF
MASTER OF COMPUTER APPLICATION (M. C. A.)

UNDER THE GUIDANCE OF


PROJECT GUIDE NAME
PROF .DR. SUNIL KHILARI SIR

SINHGAD TECHNICAL EDUCATION SOCIETY’S


SINHGAD INSTITUTE OF MANAGEMENT,
VADGAON BK, PUNE
(AFFILIATED TO SAVITRIBAI PHULE PUNE UNIVERSITY, APPROVED BY AICTE
& ACCREDITED BY NATIONAL BOARD OF ACCREDITATION, NEW DELHI)

1
CERTIFICATE

This is to certify that Mr. Hivale Sakharam Raju, has successfully /


partially completed his/her project work entitled “Shopping cart System” in
partial fulfillment of SEM-III Mini Project for the year 2021-2022. He / She have
worked under our guidance and direction.

Prof. Dr. Sunil Khilari Dr. Chandrani Singh


Project Guide Director, SIOM-MCA

Examiner 1 Examiner 2

Date:
Place:

2
DECLARATION

We certify that the work contained in this report is original and has been done by us under
the guidance of my supervisor(s).

 The work has not been submitted to any other Institute for any degree or diploma.

 We have followed the guidelines provided by the Institute in preparing the report.

 We have conformed to the norms and guidelines given in the Ethical Code of Conduct of
the Institute.

 Whenever we have used materials (data, theoretical analysis, figures, and text) from other
sources, we have given due credit to them by citing them in the text of the report and
giving their details in the references.

Name and Signature of Project Team Members:

Sr. No. Seat No. Name of students Signature of students

1 20360 Sakharam Raju Hivale

3
ACKNOWLEDGEMENT

We have immense pleasure in expressing our sincerest and deepest sense of gratitude
towards our guide Mr. Prof. Dr. Sunil Khilari Sir for the assistance, valuable guidance and co-
operation in carrying out this Project successfully. We have developed this project with the help
of Faculty members of our institute and we are extremely grateful to all of them. We also take
this opportunity to thank Director-MCA Dr. Chandrani Singh, for providing the required
facilities in completing this project. We are greatly thankful to our parents, friends and faculty
members for their motivation, guidance and help whenever needed.

Thank You,
Hivale Sakharam Raju

4
INDEX
Contents Page
No
CHAPTER 1 : INTRODUCTION

1.1 Existing System 7

1.2 Need for System 8

1.3 Operating Environment Hardware and Software 9

CHAPTER 2 : PROPOSED SYSTEM

2.1 Proposed System (Introduction of system) 10

2.2 Module specifications (Scope) 11

2.3 Objectives of System 12

CHAPTER 3 : ANALYSIS & DESIGN

3.1 Use Case Diagrams 13

3.1.1 General use case 14

3.1.2 Manage Users’ Information 17

3.1.3 Manage Products Info and Status 19

3.1 3.1.4 Manage Orders and Deliveries


21

3.2 Activity Diagram 23

3.3 Class Diagram 24

3.4 Table specifications (Database design) 25

3.4.1 Admin Login

5
25

3.4.2 User Login 26

3.4.3 Add Product 27

3.5 Realtime Database 28 - 31

CHAPTER 4 : USER MANUAL

4.1 User Interface Screens 32 - 38

4.2 Sample program code 39 - 40

4.3 Limitations 41

4.4 Bibliography 42

6
CHAPTER 1 : INTRODUCTION

1.1Existing System

 In the existing system all transactions, dealings of products, purchasing of


products were done manually which is time consuming.
 Reports are prepared manually as and when needed. Maintaining
of reports is very tedious task.
 Reports are prepared manually as and when needed. Maintaining of reports is
very tedious task.
 In the existing system all transactions, dealings of products, purchasing of
products were done manually which is time consuming.
 Reports are prepared manually as and when needed. Maintaining of reports is
very tedious task.
 To buy any product user has to collect information about it either by visiting the
shop or asking people which is the better one.

7
1.2.Need for System

 Online Shopping Portal is a specific requirement of the client that integrates


the buying and selling services specifically to their customers.
 Need for the new system is due to major drawbacks of existing system.
 Reports can be generated at any time within few seconds, so that manual
labor is not required, and also analysis can be performed much more
frequently which helps in taking decision.
 The details regarding all users, products can also be maintained as their
information is very helpful and sometimes becomes a critical requirement.
 Allows user to get registered from their places and transact for the required
product.
 To overcome these problems in existing system we develop “Shopping Cart
System”.

1.3 Operating Environment Hardware and Software


8
 Hardware:

 Processor-intel PENTIUM GOLD


 Hard Disck-1TB
 RAM-8GB

 Software:

 Front End- Java , xml


 Back End - Firebase
 Operating System-Windows 11
 Tool End- Android Studio

CHAPTER 2 : PROPOSED SYSTEM

9
2.1 Proposed System (Introduction of system)

This project is a web based shopping system for


an existing shop. The project objective is to deliver the online shopping application
into android platform. This project is an attempt to provide the advantages of
online shopping to customers of a real shop. It helps buying the products in the
shop anywhere through internet by using an android device. Thus the customer will
get the service of online shopping and home delivery from his favorite shop. This
system can be implemented to any shop in the locality or to multinational branded
shops having retail outlet chains. If shops are providing an online portal where
their customers can enjoy.
Easy shopping from anywhere, the shops won’t be losing any more
Customers to the trending online shops such as flip cart or eBay. Since the
application is available in the Smartphone it is easily accessible and always
available.

2.2 Module specifications

 Admin
10
 Login
 Add Product
 Check Order
 Show User Order
 Check Product Details

 User

 Login
 Check Product Details
 View Item
 Make Payment
 Make Order

2.3 Objectives of System

11
The Online Shopping System will manage the items on the web and provide
products to the customer online without a physically appearance of that customer.
The system will contain all the items in one place, so users need not to go to the
different shop. As the Online Shopping System is web based so the distant user
from the shop can also get the item and the vendor can cover the wide place to sell.
A user can choose from the different products, can make online payments and will
get the products at the doorstep. This will reduce the time consumption in the
purchase of different items, make the system efficient and user-friendly.

12
CHAPTER 3 : ANALYSIS & DESIGN

3.1 Use Case Diagrams

3.1.1 General Use Case Diagram

Now I present to you the general use case of the Shopping Cart System. This
diagram shows the general processes or function that the system could do that is
based on the activities done by the shopping admin and customers in the system.

General Use Case Diagram

13
Shopping Cart System

Login

Add New Product


p

View Item

Check Product Details

Show User Order Details

Check New Order

Admin User
Manage Item

Make Payment

Make Order

Change Password

Section Purpose

14
Name Use Case System

Description The use case describes steps pf the Admin and User. The
Will login , add , edit , delete and view registered uses.
The user will registered , login , interact with system.

Admin , User
Actor

Only the access that system should have account manage by the
Preconditions
administrator and valid p and password.

Admin and registered User only are permitted for accessing the
Post conditions system..

Actor Action
Basic course of
Step1. The Admin enters phone number and Password. Same
action
for User.

System Response
Step2. The system Check the validate of Email ID and
Password.

Alternate action Step1: If the Admin entered the incorrect Email ID and
Password then system gives message to Admin
User Not Exist.
Step2: System will show the error message.

15
If Admin entered the wrong Email ID , Password then he will get error
Error scenario message. Same for User.

3.1.2 Manage Users’ Information

This is where the admin or the main user of the system could control the
users/customers that could access the system.
16
nmbngjghg

Manage Users Check and save new


Information information

<< include >> << include>>

User
Check and save new
New Information
information
< <<
<< extend >>

,,hghjghjvvvjvjhvjvjvjhvh

Use Case Name : Manage Users’ Information


Actor : User

Summary : Manage User Information , Update and Save etc.

17
Pre-condition : For this actions user must have login credential

Description :  It allows user to login.


 It allows selecting product and quantity.
 Add to cart product.
 Fixed order.

Post-conditions : All data saving and fixed order.

Exception :  Login Failure: When phone number and password


combination wrong.
 Order Not Confirm: When user could not confirm order.
 Prize not generated: When user failed to decide prize of
product.

3.1.3 Manage Products Info and Status

18
This is the process where the admin will monitor the products for a certain
category to display it as offer to the customers. The monitoring consist of the encoding
the products from the sellers, updates the products’ status and the count of its orders and
deliveries to the user.

Admin

Use Case Name : Manage Products Info and Status

Actor : Admin

19
Summary : Manage Product Information , Update and Save etc.

Pre-condition : For this actions admin must have login credential

Description :  It allows user to login.


 It allows Add product and quantity.
 It allows decide to prize.

Post-conditions : All data saving and fixed order.

Exception :  Login Failure: When phone number and password


combination wrong.
 Order Not Confirm: When user could not confirm order.
 Prize not generated: When user failed to decide prize of
product.

3.1.3 Manage Orders and Deliveries

This process explains that the information from the uses request and orders
up to deliveries were processed. These information were composed of the date of

20
reservation or order, number of products or items purchased, prizes of each items
and total payment and the date of delivery.

Admin

21
Use Case Name : Manage Orders and Deliveries

Actor : Admin

Summary : Manage Order Product Name , Quantity , Update and Save etc.

Pre-condition : For this actions admin must have login credential

Description :  It allows user to login.


 It allows Add product and quantity.
 It allows decide fixed order.

Post-conditions : All data saving and fixed order.

Exception :  Login Failure: When phone number and password


combination wrong.
 Order Not Confirm: When user could not confirm order.
 Prize not generated: When user failed to decide prize of
product.

22
3.2 Activity Diagram

23
3.3 Class Diagram

24
3.4 Table specifications (Database design)

3.4.1. Table Name: Admin Login


Table Description: Must have phone number and password to login.
Primary Key: phone number

Sr. No Field Name Field Type Size Constraints Description


1 Phone number Int 10 Primary Key, Defines a
Not Null unique admin
phone number
2 Password Text 12 Not Null Admin Profile
Password

25
3.4.2. Table Name: User Login
Table Description: Must have phone number and password to login user.
Primary Key: phone number

Sr. No Field Name Field Type Size Constraints Description


1 Phone number Int 10 Primary Key, Defines a
Not Null unique admin
phone number
2 Password Text 12 Not Null Admin Profile
Password

3.4.2. Table Name: Add Product

26
Table Description: Add product details.
Primary Key: Null.

Sr. No Field Name Field Type Size Constraints Description


1 Product Name Text 20 Null Add Product
name , size ect.
2 Color Text 20 Null Multiple colour
are available.
3 Prize Int 20 - Different
Color, Size are
different
prizes.

27
3.5 Realtime Database (Database Design)

28
Users

29
Order

30
31
CHAPTER 4 : USER MANUAL

4.1 User Interface Screens (Input)

 Home Page

32
 Login page

33
 Login Admin

34
35
36
 Add New Product

37
 Product Successfully Add

38
4.2. Sample program code
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.app.shopping">
<uses-permission
android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission
android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:roundIcon="@mipmap/ic_launcher_round"
android:supportsRtl="true"
android:theme="@style/Theme.Ekart"
tools:replace="android:theme">
<activity android:name="com.app.shopping.HomeActivity"
android:theme="@style/Theme.AppCompat.NoActionBar"/>
<activity android:name="com.app.shopping.SettinsActivity" />
<activity android:name="com.app.shopping.SearchProductsActivity" />
<activity android:name="com.app.shopping.RegisterActivity" />
<activity android:name="com.app.shopping.ProductDetailsActivity" />
<activity android:name="com.app.shopping.LoginActivity" />

39
<activity
android:name="com.app.shopping.ConfirmFinalOrderActivity" />
<activity android:name="com.app.shopping.CartActivity" />
<activity
android:name="com.app.shopping.AdminUserProductsActivity" />
<activity
android:name="com.app.shopping.AdminNewOrdersActivity" />
<activity
android:name="com.app.shopping.AdminCategoryActivity" />
<activity
android:name="com.app.shopping.AdminAddNewProductActivity" />
<activity android:name="com.app.shopping.MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />

<category
android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity
android:name="com.theartofdev.edmodo.cropper.CropImageActivity"
android:theme="@style/Base.Theme.AppCompat" />
</application>
</manifest>

40
4.3 Limitations

This application does not have a built in check out process. An external checkout
package has to be integrated in to this application. Also users cannot save the shopping carts so
that they can access later i.e. they cannot create wish lists which they can access later. This
application does not have features by which user can set price ranges for products and receive
alerts once the price reaches the particular range.

4.4 Bibliography

41
 You Tube
 www.google.com
 Java point
 w3school

42

You might also like