A

PROJECT REPORT ON
(E Commerce Website)

SUBMITTED TO

Maharashtra Education Society’s

MES SENIOR COLLEGE, PUNE

(Affiliated to SAVITRIBAI PHULE PUNE UNIVERSITY)

IN PARTIAL FULFILLMENT OF

BACHELOR OF BUSINESS ADMINISTRATION

(COMPUTER APPLICATION)
(Academic Year 2023-24)

SUBMITTED BY
Mr. Hrishikesh Deshmane Roll No. 2151011
Mr. Mauli Kharsade Roll No. 2151028

TYBBA-CA (Semester-VI)

UNDER THE GUIDANCE OF

Prof. Neha Kulkarni

1
 ACKNOWLEDGEMENT
I would like to take this opportunity to express my heartfelt gratitude and appreciation for the completion of the E Commerce Website as a part
of my academic curriculum. Throughout this project, I had the privilege of working independently under the guidance and mentorship of Neha
Kulkarni. I would like to thank MES Senior College, Principal Sir, All Faculty members, peers and friends for their support and encouragement
throughout this project. Their valuable suggestions, brainstorming sessions, and willingness to provide feedback greatly contributed to the
overall success of this project.

Hrishikesh Deshmane 2151011

Mauli Kharsade 2151028

2
 INDEX

Sr. No Topic Page No.

1 Introduction

▪ Need for System

▪ Scope and limitations of existing system
▪ Operating Environment – H/w & S/w
▪ Architecture of system
▪ Detailed Description of Technology Used
2 Proposed System

▪ Proposed System
▪ Objectives of System
3 System Design

▪ ERD
▪ UML Diagrams
▪ Data Dictionary
4 Outputs and Reports Testing

▪ Test Plan
▪ Black Box Testing or Data Validation Test
Cases
▪ White Box Testing or Functional Validation
Test cases and results
5 User Manual

▪ User Interface Design (Screens etc.)

6 Limitations

7 Future Enhancement

8 Conclusion

9 Bibliography

10 Annexure:

▪ Sample program code

3
CHATPER 1: INTRODUCTION
1.1 Need for System:
Limited Access to Products: Consumers were often restricted to products available in local stores, limiting their choices and variety.
Operating Hours and Holidays: Traditional brick-and-mortar stores had fixed operating hours, and customers were restricted by the store's
schedule. Additionally, stores might be closed on holidays.
Limited Price Comparison: Price comparison was more challenging, as consumers had to visit multiple stores physically to compare prices for
the same or similar products.
Inconvenient Payment Methods: Payment options were limited to cash or card transactions in physical stores, and not all consumers had
access to credit or debit cards.
Lack of Information: Consumers had limited access to product information, specifications, and reviews. They often relied on sales associates
for details about products.
Manual Record Keeping: Shopping required manual record-keeping, such as keeping receipts for warranties, returns, and exchanges.
Security Concerns: Consumers may have had concerns about the security of their personal and financial information during transactions.

1.2 Scope and limitations of existing system:

Scope of the Existing System:
 We can buy product physically with surely.
 We can buy product from trustworthy shops.
 While buying product we can bargain with vendors.
 We can check product before buying.
 Frauds will not happen.
Limitations of the Existing System:
 Travel and travel expenses.
 Receipt collection.
 We cannot return product easily.
 We come to know about the offers once we visit any shop.
 Communication barrier.
 Time consuming.
 Variety, choices of product is not available.

1.3 Operating Environment - H/w & S/w:

Hardware:

 RAM: 2-4GB.
 Hard Disk: 16GB.
Software:

 Frontend: HTML, CSS, JAVASCRIPT, BOOSTRAP.

 Backend: JAVA, JDBC, Servlet JSP, HIBERNATE.

4
1.4 Architecture of System:

End
User

Access system through

Web Browser

(Chrome, Safari, Microsoft

Edge, etc.)

Loads

1. Login and Signup page.

HTML, C User interface: frontened CSS, JAVASCRIPT

2. Home Page, Products page.

3. Access saved information

and Details.

Stored in

User A/C details MySQL Database:

1. Email id Blackened
MySQL, Java, etc.
2. Username

3.Password

Saved details containing

processed information.

5
1.5 Detailed Description of Technology Used:
Frontend Technologies:

HTML (Hypertext Markup Language):

We have used HTML to define the structure and content of web pages using tags and elements. Also, we have used it to create the layout and
structure of user interfaces, including forms, tables, and content display. Created an HTML form I the frontend to capture user input.

This includes the arrangement of headers, footers, navigation menus, content areas, and sidebars.HTML tags are used to format and structure
text content in various ways, such as headings (h1, h2, etc.), paragraphs (p), lists (ul, ol, sli).

CSS (Cascading Style Sheet):

We have used CSS to control the presentation and styling of web pages. It separates the content (HTML) from its visual design. For creating a
consistent and visually appealing user interface. It defines fonts, colors, layout, and responsive design for various devices.CSS is used to apply
styles to HTML elements, such as headings, paragraphs, lists, links, buttons, and form elements.

This includes defining font sizes, colors, margins, padding. CSS is used to control the positioning and layout of elements on the page. It defines
properties like width, height, display, positioning (relative, absolute), and floats to structure the content. CSS sets background colors, images,
gradients, and border styles to enhance the visual appearance of elements. It's used to differentiate sections, highlight important information, and
create a visually pleasing interface.

JavaScript:

JavaScript is used to add interactive features to product pages.

JavaScript is essential for creating dynamic and interactive shopping cart functionality. It enables features such as adding/removing items from
the cart without page reloads, updating the cart dynamically, and calculating the total price.

JavaScript is often used in combination with server-side technologies for user authentication and account management. It can provide features
like password strength validation, email verification, and interactive user account interfaces.

Bootstrap:

Bootstrap provides a responsive grid system that helps developers create a fluid and responsive layout for e-commerce websites. This ensures
that the site looks good and functions well on devices of various screen sizes, including desktops, tablets, and smartphones.

Bootstrap includes a responsive navigation bar component that simplifies the creation of navigation menus. It is often used for the header of an
e-commerce site, containing links to product categories, account information, and the shopping cart.

Bootstrap offers styling for form elements, making it easier to create aesthetically pleasing and consistent forms.

Backend Technologies:

JAVA:

Java is used to develop mobile apps, web apps, desktop apps, games and much more. Java is widely used for server-side processing in e-
commerce applications. Servlets and Java Server Pages (JSP) are commonly employed to handle HTTP requests, process form submissions, and
generate dynamic content to be sent to the user's browser.

Java is used to implement the business logic behind shopping cart functionality and the checkout process. This includes managing inventory,
calculating prices, applying discounts, and handling order processing.

JDBC:

It is an application programming interface (API) for the Java programming language which defines how a client may access a database. It is a
Java-based data access technology used for Java database connectivity.

Driver Manager manages the set of Java Database Connectivity (JDBC) drivers that is used for an application to use.

Database (MySQL):

MySQL is a popular open-source relational database management system (RDBMS) that is widely used for managing and manipulating
databases. It is known for its performance, reliability, and ease of use. MySQL is used to store and manage the core data of an e-commerce
application.

MySQL is employed to store and manage product information, including product names, descriptions, prices, images, and availability.

6
CHAPTER 2: PROPOSED SYSTEM

2.1 PROPOSED SYSTEM: -

1. User Registration and Authentication: Users will have the option to create accounts, enabling personalized experiences, order tracking, and
a more streamlined checkout process. Secure authentication measures will be implemented to protect user data.

2. Extensive Product Information: The platform will offer comprehensive product information, including detailed descriptions, specifications,
customer reviews, and ratings. This information will empower users to make informed decisions without relying solely on sales associates.

3.Shopping Cart: Create a robust shopping cart system for users to add and manage their selected items.

4. Secure Payment Methods: The proposed system will support a variety of secure payment methods, including credit/debit cards, digital
wallets, and other online payment options. This ensures convenience and security for users during transactions.

5. Order Management: Develop an order management system for users to track their orders in real-time. Implement order confirmation emails
and notifications.

6. Real-time Offers: Users will receive real-time notifications about ongoing offers, discounts, and promotions. This ensures that customers are
informed about the latest deals without physically visiting stores.

7. User Reviews and Ratings: Allow users to leave reviews and ratings for products. Display reviews on product pages to assist other users in
making informed decisions.

8. Efficient Return and Exchange Process: The proposed system will introduce a streamlined return and exchange process, allowing users to
initiate returns or exchanges online. This feature enhances user satisfaction and trust in online shopping.

9. Proposed System Architecture: The architecture will involve client-server communication. The user interface (frontend) will be developed
using HTML, CSS, JavaScript, and Bootstrap. The backend will be powered by Java, Servlet JSP, and Hibernate. The MySQL database will
store and manage product information, user data, and transaction records.

2.2 OBJECTIVES OF SYSTEM: -

1. Increase Sales: The primary goal is often to drive online sales and generate revenue.

2. Expand Market Reach: Reach a broader audience by making products or services accessible to customers beyond geographical boundaries.

3. Enhance Customer Experience: Provide a seamless and user-friendly shopping experience to enhance customer satisfaction.

4. Build Brand Awareness: Increase brand visibility and recognition through online presence and marketing efforts.

5. Improve Customer Loyalty: Encourage repeat business by implementing loyalty programs, personalized offers, and excellent customer
service.

6. Diversify Product or Service Offering: Introduce new products or services to cater to changing market demands and customer preferences.

7. Optimize Operational Efficiency: Streamline internal processes such as order fulfillment, inventory management, and customer support to
improve overall efficiency.

8. Data-Driven Decision Making: Use analytics and data insights to make informed business decisions and optimize the website based on user
behavior.

9. Security and Trust: Establish trust with customers by implementing robust security measures, secure payment gateways, and transparent
policies.

10. Adaptation to Technological Trends: Stay current with technological advancements to provide a modern and innovative shopping exp

7
 CHAPTER 3: ANALYSIS & DESIGN
3.1 ERD:

number

Tracking Courier name

detail

has

number date id
name number date
Product
quantity id
1 M 1 1 M
Payment make Customer make Order amt

Cart

address Contact number contains 1

amt
size

name Adde name

id
d to

name

M
Product 1 M
Admin manage has Product
Category

pass
id status price id

8
3.2 UML Diagrams:
Use Case Diagram:

System

Login

Add/Update/Delete Add to cart

Category

Admin
User
Update/delete Cart
Add/Update/Delete
Product

Order Placement

Add Country and

State Calculate Shipping
and tax

Add/Update shipping
charge and tax Payment

Logout

9
Class Diagram:

10
Sequence Diagram:

11
Activity Diagram:

12
13
State Machine Diagram:

14
Data Dictionary:
Table: User

User Id Data type Length user id

User address varchar 255 user Description

User email varchar 255 user Discount

Username varchar 255 user Name

User password int 11 user Photo

User phone int 11 user Price

User pic int 11 user Quantity

User type int 16 User type

Table: Category

Category id Data type Length Description

Category description varchar 255 Email of the user

Category title varchar 255 Password of the user

Table: Product

pId Data type Length Product id

pDescription varchar 255 Product Description

pDiscount varchar 255 Product Discount

pName varchar 255 Product Name

pPhoto int 11 Product Photo

pPrice int 11 Product Price

pQuantity int 11 Product Quantity

Category_categoryId int 16 Category id

CHAPTER 4: OUTPUTS AND REPORTS TESTING

4.1 Test Plan:

Introduction: Outline the purpose, scope, and objectives of testing, along with team roles and responsibilities.

Test Strategy: Define the testing approach, types (functional, usability, security), and environment setup.

Test Phases: Include unit, integration, system, and user acceptance testing (UAT) to ensure end-to-end functionality.

Test Cases: Detail positive and negative scenarios for core functionalities like user registration, product browsing, and checkout.

Non-functional Testing: Cover usability, performance, and security aspects to ensure a seamless and secure user experience.

Compatibility Testing: Verify compatibility across different browsers, devices, and operating systems.

Regression Testing: Ensure that new changes do not impact existing functionalities adversely.

15
4.2 Black Box Testing or Data Validation Test Cases:

STEPS TO
BE ACTUAL
DESCRIPTI FOLLOW EXPECTED RESULT
TC ID NAME ON ED DATA RESULT STAT-US

login valid to verify user 1.Enter

email is able to Valid email
address and login address
valid successfully 2. Enter
password with valid valid
email address Password User Should
and password 3.Click on Email address: be able to User is able
Login [email protected] login to login
TC001 Button Password: 12345 Successfully successfully Pass

1.Enter Email address:

Valid email [email protected]
login valid address 2. Password: 000000
email to verify user Enter
address and is not able to invalid
invalid login Password 3.
password successfully Click on
with valid Login User Should User is not
email address Button not be able to able to login
and invalid login Successfull
TC002 password. successfully y Pass

To verify Email address: User is not

user is not [email protected] be able to
able to login 1.Enter Password: login
successfully invalid Yash@2024 Successfull
with invalid email y
login email address address 2.
invalid and valid Enter valid
email password Password 3. User should
address and Click on not be able to
valid Login login
TC003 password Button successfully Pass

1.Enter Email address:

invalid [email protected]
email Password: 999999
address
To verify
2. Enter
user is not
invalid
able to login
Password
login successfully
3.Click
invalid with invalid
login button
email email address User should User is not
address and and invalid not be able to be able to
invalid password login login
TC004 password registration successfully successfully Pass

To verify 1.Enter Email address:

user is valid user yashsharma10@gmail
registered details .com
Successfully 2.Click on Password:
Register Yash@2024
User Button
Register- User is User is
Valid successfully successfully
TC005 Details register Registered Pass

16
 To verify 1.Enter an Email address: User cannot
user is not invalid [email protected] be registered
TC006 registered login format password: 555555 successfully
successfully 2.click on
register
User button User is not Pass
Registration able to
invalid register
format successfully

4.3 White Box Testing or Functional Validation Test cases and results:

Functional Validation Test Cases:

1. Database Connectivity:

 Test the connection to the database to ensure it is established correctly.

 Result: If successful, confirm that data retrieval and storage operations work as expected. If unsuccessful, investigate and fix any
connectivity issues.

2. User Authentication:

 Test the login process with valid credentials.

 Test the login process with invalid credentials.
 Result: If successful, users should be able to log in with valid credentials and receive appropriate error messages for invalid credentials.

3. Product Inventory Management:

 Test adding a new product to the inventory.

 Test updating the quantity of an existing product.
 Result: If successful, the new product should appear in the product listing, and the updated quantity should reflect in the inventory
database.

4. Checkout Process Integration:

 Test integration with payment gateways (e.g., PayPal, Stripe).

 Verify that payment transactions are processed correctly.
 Result: If successful, payments should be processed without errors, and order details should be updated accordingly in the database.

Test Results:
1. Database Connectivity Test Result:

 Successful: The connection to the database is established, and data operations are performed without errors.
 Unsuccessful: The connection fails, or data operations encounter errors, indicating database connectivity issues that need to be addressed.

2. User Authentication Test Result:

 Successful: Users can log in with valid credentials, and appropriate error messages are displayed for invalid credentials.
 Unsuccessful: Users cannot log in even with valid credentials, or incorrect error messages are displayed, indicating authentication issues
that need to be resolved.

Product Inventory Management Test Result:

 Successful: New products are added to the inventory, and quantity updates are reflected accurately.
 Unsuccessful: New products do not appear in the inventory, or quantity updates are not reflected, indicating issues with inventory
management functionality.

Checkout Process Integration Test Result:

 Successful: Integration with payment gateways is successful, and payment transactions are processed without errors.
 Unsuccessful: Payment transactions fail, or order details are not updated correctly, indicating issues with payment gateway integration

17
CHAPTER 5: USER MANUAL

5.1 User Interface Design:

Home Page:

Login Page:

18
Registration Page:

4.2 Limitations:
 We come to know about the offers once we visit any shop.
 Variety, choices of product is not available.

4.3 Future Enhancement:

 User can change into any language which they are comfortable to use.
 Community engagement, so that they can write reviews, ratings, add photos of product.

4.4 BIBLIOGRAPGY:
o E-commerce: Business, Technology, Society.
o E-commerce Essentials
o https://www.w3schools.com/
o www.flaticon.com

4.5 CONCLUSION:
The development of this e-commerce website represents a significant step forward in enhancing online shopping experiences. The website's
user-friendly interface, streamlined checkout process, and robust security features provide a reliable platform for customers to purchase products
with ease and confidence. Moreover, the website's integration with various payment gateways and shipping providers ensures a seamless
transaction process, while the admin panel's analytics and reporting tools enable efficient monitoring and management of sales and inventory. As
we move forward, it is crucial to continue improving the website based on customer feedback and emerging trends in e-commerce. By doing so,
we can ensure that our platform remains competitive and relevant, providing value to both our customers and the business.

4.6 ANNEXURE:
Sample Program Code:

<%@page import="com.learn.mycart.helper.Helper"%>

<%@page import="com.learn.mycart.entities.Category"%>

<%@page import="com.learn.mycart.dao.CategoryDao"%>

<%@page import="java.util.List"%>

19
<%@page import="com.learn.mycart.entities.Product"%>

<%@page import="com.learn.mycart.dao.ProductDao"%>

<%@page import="com.learn.mycart.helper.FactoryProvider"%>

<%@page contentType="text/html" pageEncoding="UTF-8"%>

<!DOCTYPE html>

<html>

<head>

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

<title>MyCart - Home</title>

<%@include file="components/common_css_js.jsp" %>

</head>

<body>

<%@include file="components/navbar.jsp" %>

<div clas="container-fluid">

<div class="row mt-3 mx-2">

<%

String cat = request.getParameter("category");

// out.println(cat);

ProductDao dao = new ProductDao(FactoryProvider.getFactory());

List<Product> list = null;

if (cat == null || cat.trim().equals("all")) {

list = dao.getAllProducts();

} else {

int cid = Integer.parseInt(cat.trim());

list = dao.getAllProductsById(cid);

CategoryDao cdao = new CategoryDao(FactoryProvider.getFactory());

cdao.getCategories();

List<Category> clist = cdao.getCategories();

%>

<!-- show categories -->

<div class="col-md-2">

<div class="list-group">

<a href="index.jsp?category=all" class="list-group-item list-group-item-action active">

All Products

</a>

<%

for (Category c : clist) {

%>

<a href="index.jsp?category=<%= c.getCategoryId()%>" class="list-group-item list-group-item-action"><%=

c.getCategoryTitle()%></a>

20
 <%

%>

</div>

</div>

<!-- show products -->

<div class="col-md-10">

<!-- row -->

<div class="row mt-4">

<!-- col:12 -->

<div class="col-md-12">

<div class="card-columns">

<!-- Traversing Products -->

<%

for (Product p : list) {

%>

<!-- Product card -->

<div class="card product-card">

<div class="container text-center">

<a href="normal.jsp?id=<%= p.getpId() %>">

<img src="img/products/<%= p.getpPhoto()%>" style="max-height: 200px; max-width: 100%; width: auto;"

class="card-img-top m-2" alt="...">

</a>

</div>

<div class="card-body">

<h5 class="card-title"><%= p.getpName()%></h5>

<p class="card-text">

<%= Helper.get10Words(p.getpDescription())%>

</p>

</div>

<div class="card-footer text-center">

<button class="btn custom-bg text-white" onclick="add_to_cart(<%= p.getpId() %>, '<%= p.getpName() %>', <%=
p.getpPrice() %>)">Add to Cart</button>

<button class="btn btn-outline-primary"> &#8377; <%= p.getpPrice()%>/- <span class="text-secondary discount-

label"> <%= p.getpDiscount() %>% off </span></button>

</div>

</div>

<% }

if (list.size() == 0) {

out.println("<h3>No item in this category</h3>");

%>

21
 </div>

</div>

</div>

</div>

</div>

</div>

<%@include file="components/common_modals.jsp" %>

</body>

</html>

22
23