AMAZON CLONE

Name:- Koyal Babar

Class:- T.Y.B.Sc.IT
Div:- A
Roll No:- 14
Project Guide:-Ms Anuja
Patil
 Introduction
An Amazon clone is a web application built using ReactJS for the frontend and
Firebase for the backend services. ReactJS ensures a fast, interactive, and
dynamic user interface, while Firebase offers features like authentication, real-
time database, cloud storage, and hosting. This project replicates core e-
commerce functionalities, including product listings, user authentication,
shopping carts, and payment handling. It provides a hands-on experience in
building full-stack applications, helping developers understand how to integrate
front-end and back-end technologies seamlessly.
 Objective
• To provide an application in website/ android platform to purchase items in an amazon clone.
• To provide a functional online shopping experience Similar to Amazon.
• To provide veers with a personal account to manage their information and order history.
• To provide users to add, remove and modify items in their cart.
• To provide user to efficiently search and and fillter product by various criteria.
• for showcase information a variety of product with detailed.
• for allows user to save items to a wishlist for future reference.
 Modules
 1. User Authentication
 2. Payment Integration
 3. Product Catalog
 4. Order Management
 5. Product Detail
 1. User Authentication

User authentication is the way a system checks if

someone is who they say they are before allowing
access. This usually involves entering a username and
password. If the information matches what the system
has stored, the user can log in; if it doesn't, access is
denied. Sometimes, extra steps are added for security,
like sending a code to the user's phone that they need
to enter. This process helps keep accounts and
information safe from unauthorized access.
 2. Payment Integration

• Payment integration is the process of adding

payment options to a website or app so users can pay
for their purchases securely. This involves
connecting to payment services like UPI or credit
card processors. When a user checks out, they enter
their payment details, which are sent to the payment
service to complete the transaction. Once the
payment is processed, the order status is updated,
and the user is notified. This makes buying products
online easy and safe.
 3. Product Catalog

• A product catalog is a list of items that are available

for sale in an online store. It includes important
details about each product, such as pictures,
descriptions, prices, and features, making it easy for
customers to browse and compare products. The
catalog is often organized into categories, so
shoppers can find what they need quickly. By
providing clear information and sorting options, a
good product catalog helps users have a better
shopping experience.
 4. Order Management

• Order management is the process of handling

customer orders from start to finish. It includes
receiving orders, managing stock, tracking
shipments, and making sure products are delivered
on time. An order management system helps confirm
payments, update customers about their orders, and
keep everything organized. Good order management
is important for keeping customers happy, ensuring
the right products are available, and making the
whole process run smoothly.
 5. Product Detail

• Product details provide essential information about

an item available for purchase in an e-commerce
application. This typically includes the product
name, description, price, images, specifications, and
customer reviews. Additional features may include
availability status, shipping options, and warranty
information. By presenting this information clearly,
customers can make informed purchasing decisions,
enhancing their overall shopping experience.
 Event table
An event table outlines key actions
in an application and tracks
important activities. For admin
login, it records when administrators
access the system. User registration
captures new user sign-ups, while
user login tracks users logging in.
Add to cart logs products added to
the shopping cart, and remove from
cart notes items removed. Order
placement records when an order is
confirmed, while review tracks user
feedback on products. Logout
registers when users or admins exit
the session, and report logs any
complaints or issues submitted by
users or admins.
 ER
An Entity-Relationship
Diagram : (ER) diagram
shows how different entities are
connected within a system. In this
case, the key entities are User, Admin,
Product, Category, Cart, Order,
Payment, and Review. A User can add
Products to the Cart and place an
Order, which is associated with a
Payment Users can also leave a Review
for a product. Each Product belongs to
one or more Categories, helping with
product organization. Admin manages
Users, Products, Categories, and
Reviews. An Order is linked to a User
and contains multiple Products. This
diagram highlights the relationships
between entities and how data flows,
ensuring seamless interactions within
the system.
 Use
A usecase diagram:
case diagram shows how actors
interact with the system to perform
specific tasks. In this case, the main
actors are Customer and Admin. The
Customer can browse Products, add
items to the Cart, place Orders, make
Payments, write Reviews, and manage
their Account. The Admin manages the
system by adding or updating Products,
organizing them into Categories,
managing Orders, viewing Reports, and
moderating Reviews. This diagram
provides a clear overview of the different
roles and the tasks each actor can
perform within the system.
 Class Diagram:
A class diagram outlines the structure
and relationships between key entities
in an application, such as Cart,
Review, Admin, User, Payment,
Product, Order, and Category. Each
entity is represented as a class with
attributes and methods. User
interacts with Cart to manage
products, places an Order, and
submits Reviews for Products. Admin
oversees Products and Categories,
ensuring smooth operations. Payment
handles transactions linked to Orders,
while Categories group products for
easier navigation. This diagram
highlights how these components
connect, offering a clear view of the
system’s design.
 Sequence Diagram:
A sequence diagram tells the
interactions among various
components in a system, focusing on
the order of events over time. In this
diagram, the lifelines include User,
System, Database, and Payment. The
User initiates the process by sending a
request to the System, such as logging
in or placing an order. The System then
interacts with the Database to retrieve
or store information, like user
credentials or product details. After
validating the data, the System may
call the Payment lifeline to process any
transactions.
 State Chart Diagram

A state chart diagram shows the

different states an object can be in
and how it moves from one state to
another. Each state represents a
specific situation, like a User being
Logged In, Browsing Products or
Checking Out. Transitions happen
when events occur, such as clicking a
button or making a payment. For
example, when a user adds an item to
their cart, the state changes from
Browsing Products to Item Added to
Cart. This diagram helps visualize
how an object behaves and reacts to
different actions in the system.
 Activity Diagram
An activity diagram for an online
banking system shows the flow of
actions from start to finish. It begins
with the User Registration then fill
form and submit it. If not valid then
go to home page. If valid then account
is created then we can browse product
if product is our liking then we can
add to card if we want to add it then
payment is proced and order is
confirmation