E-Commerce Project

Submitted By

Nista Chauhan
College Roll Number : XX

TEXAS COLLEGE OF MANAGEMENT IT

August,2022
Abstract

In today’s fast-changing business environment, it’s extremely important to be able to

respond to client needs in the most effective and timely manner. If your customers
wish to see your business online and have instant access to your products or services.
newline
Devorah Closet is a lifestyle e-commerce web application, which retails various fash-
ion and lifestyle products (Currently Women’s Wear). This project allows viewing
various products available enables registered users to purchase desired products in-
stantly using PayPal payment processor (Instant Pay) and also can place order by
using Cash on Delivery (Pay Later) option. This project provides an easy access to
Administrators and Managers to view orders placed using Pay Later and Instant Pay
options.
In order to develop an e-commerce website, a number of Technologies must be stud-
ied and understood. These include multi-tiered architecture, server and client side
scripting techniques, implementation technologies such as Servlet,JSP, programming
language (such as JAVA) and Hibernate. This is a project with the objective to de-
velop a basic website where a consumer is provided with a shopping cart application
and also to know about the technologies used to develop such an application. This
document will discuss each of the underlying technologies to create and implement
an ecommerce website.

i
Acknowledgment

In completing this project I have been fortunate to have help, support and encourage-
ment from many people. I would like to acknowledge them for their cooperation. First
and foremost deeply thankful to Professor xxxxxx , for her wonderful guidance during
this project work in field of Computer Science, at Texas college. I am also thankful
for her continuous feedback and encouragement throughout this project work. Her
broad knowledge and hardworking attitude has left me with very deep impressions
and they will greatly benefit me throughout my life. I would like to thank my project
Readers xxxxxx and xxxxxxx for their support throughout this project work.

Nista Chauhan
July 2022

ii
Contents

Abstract i

Acknowledgment ii

List of Figures iv

List of Tables vi

List of Abbreviations vii

1 Introduction 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Overall Description 3
2.1 Product perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 User documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . 3

3 External Requirements 5
3.1 Web Pages details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.1 Home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.2 Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.3 Register page . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.4 Admin page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.5 Normal page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

iii
 3.2.6 Cart Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.7 Check Out page . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.8 Payment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.5 Communication Interface . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.6 System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.7 Memory Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.8 Cost Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.9 Time Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

References 15

iv
List of Figures

3.1 Master Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.2 Footer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Register Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5 admin page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.6 add new Category interface . . . . . . . . . . . . . . . . . . . . . . . 8
3.7 add new product interface . . . . . . . . . . . . . . . . . . . . . . . . 9
3.8 User details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.9 Cart Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.10 Check Out page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.11 Payment Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.12 Gantt chart diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.13 Sample Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 17

v
List of Tables

vi
List of Abbreviations

Short Form1 Full Form 1 in Alphabetical Order

Short Form2 Full Form 2 in Alphabetical Order

vii
Chapter 1

Introduction

1.1 Introduction
E-commerce is fast gaining ground as an accepted and used business paradigm. More
and more business houses are implementing web sites providing functionality for per-
forming commercial transactions over the web. It is reasonable to say that the process
of shopping on the web is becoming commonplace.
The objective of this project is to develop a general purpose e-commerce store where
product like clothes can be bought from the comfort of home through the Internet.
However, for implementation purposes, this paper will deal with an online shopping
for clothes.
This project is mainly divided into two main categories: The Administrators and the
Customers/Users.
The store manager and the staff members operate as the administrators. They can
add, edit, update products or, delete products thus they able to change the names of
products, change prices and, add or remove products.
The customer can search for products selection, update the cart, remove products
from the cart and check out from the shop. The customer is also able to update his
information such as names, address and other data.

1.2 Objective
1. Any member can register and view available products.

1
 2. Only registered member can purchase multiple products.

3. ContactUs page is available to contact Admin for queries.

4. There are three roles available: Visitor, User and Admin.

• Visitor can view available products.

• User can view and purchase products.

• An Admin has some extra privilege including all privilege of visitor and
user.

1.3 Overview
This system provides an easy solution for customers to buy the product without going
to the shop and also to shop owner to sale the product. This proposed system can
be used by any naı̈ve users and it does not require any educational level,experience
or technical expertise in computer field but it will be of good use if user has the good
knowledge of how to operate a computer.

2
Chapter 2

Overall Description

The Online Shopping system (OSS) application enables vendors to set up online shops,
customers to browse through the shops, and a system administrator to approve and
reject requests for new shops and maintain lists of shop categories. Also the developer
is designing an online shopping site to manage the items in the shop and also help
customers to purchase them online without visiting the shop physically.The online
shopping system will use the internet as the sole method for selling goods to its
consumers.

2.1 Product perspective

This product aimed toward a person who don’t want to visit the shop as he might
don’t get time for that or might not interested in visiting there and dealing with lot
of formalities.

2.2 User documentation

The product will be compatible with the Internet Explorer 6.0 or higher. The
databases will be created in the Mysql.

2.3 Assumptions and Dependencies

The assumptions are:-

3
 1. The coding should be error free.

2. The system should be user friendly so that it is easy to use for the users.

3. The system should have more capacity and provide fast access to the database.

4. Users may access from any computer that has internet browsing capabilities and
an internet connection.

5. User must have their correct usernames and passwords to enter into their online
accounts and do actions.

The dependencies are:-

1. The specific hardware and software due to which the product will be run.

2. The end users (admin ) should have proper understanding to the product.

3. On the basis of listing requirements and specification the project will be develop
and run.

4. The information of all users must be stored in a database that is accessible by

Devorah store system.

4
Chapter 3

External Requirements

3.1 Web Pages details

1. Home Page

2. Login Page

3. Register page

4. Admin page

5. About Us page

6. Check Out page

5
3.2 User Interfaces
Admin can View, Edit and Delete everything on the product.
user can view the whole information.
Devorah online Shopping Master Page (Similar Master Page for Visitor, User and
Admin)

3.2.1 Home page

The Home Screen will consist of screen were one can browse through the products
which we have on our website.

Figure 3.1: Master Page

Figure 3.2: Footer

6
3.2.2 Login page

Login page for both users and administrators.

Figure 3.3: Login Page

3.2.3 Register page

Register page for registration of new user.

Figure 3.4: Register Page

7
3.2.4 Admin page

Only difference you see in this page is Role: Admin. User and Admin role will be
checked once the page was login and Session [“role”] will be either Admin or User.
If credentials belong to Admin then role will be Admin and if credentials belong to
User then role will be User.

Figure 3.5: admin page

Admin can add new Category.

Figure 3.6: add new Category interface

8
Admin can add new Product.

Figure 3.7: add new product interface

9
3.2.5 Normal page

In normal page user see and also can edit about their personal details.

Figure 3.8: User details

10
3.2.6 Cart Interface

Cart interface where selected items are shown.

Figure 3.9: Cart Interface

3.2.7 Check Out page

Registered users can order desired products from here with their Information.

Figure 3.10: Check Out page

11
3.2.8 Payment

Once user give their information in checkout page and Order.The payment interface
is redirected.

Figure 3.11: Payment Interface

3.3 Hardware Requirements

1. Operating system : windows

2. Hard disk :4 GB RAM: 112 MB.

3. 2.20 GHz Dual-Core CPU Processor.

3.4 Software Requirements

1. JAVA Development Kit.

2. MySql Server

3. A compatible browser, for accessing the online module.

3.5 Communication Interface

The Customer must connect to the Internet to access the Website.

12
3.6 System Features
• The website authority should ensure the customer provide real product

• Customer support is available from the authority

• Customer information security confirm.

• Manage customer information.

• To increase efficiency of managing the authority work

3.7 Memory Constraints

At least 1.5 GB ram and 550 tb space of hard disk will be required to run the software.
The hard disk requirement may be increased based on the number of data using the
system and the system will provide alerts about disk space availability.

3.8 Cost Estimation

COCOMO(Constructive Cost Model) is a regression model based on LOC i.e., Num-
ber of Lines Of Code.It is procedural cost estimate model for software projects and
often used as a process of reliably predicting the various parameters associated with
making a project such as size,effort,cost,time and quality.It was proposed by Barry
Boehm in 1970 and is based on the study of 63 projects,which make it one of the best-
documented models. The key parameters which define the quality of any software
products,which are also an outcome of COCOMO are primarily Effort and Schedule:

• Effort: Amount of labor that will be required to complete a task.It is measured

• Schedule: Simply means the amount of time required for the completion of
the job.

13
 Types of COCOMO Model

1. Basic

2. Intermediate

3. Detailed

3.9 Time Schedule

A Gantt chart, commonly used in project management, is one of the most popular
and useful ways of showing activities (tasks or events) displayed against time. On the
left of the chart is a list of the activities and along the top is a suitable time scale.
Each activity is represented by a bar; the position and length of the bar reflects the
start date, duration and end date of the activity.

Figure 3.12: Gantt chart diagram

14
References

15
Annex

A. Interviews Question
The following questions are asked to client for collecting the requirements.

1. What will be the total number of user?

2. WHat is your budget?

16
B. Class Diagram

Images/Classdiagram.png

Figure 3.13: Sample Class Diagram

17
C. Sequence Diagram
........

18
D. State Diagram
........

19
E. Team Meetings
........

20
F. Team Report Form
........

21