THE DESIGN AND IMPLEMENTATION OF AN ECOMMERCE

SITE FOR SALES

By

C .PRAVEEN KUMAR
V .LAKSHMIKAR REDDY
K .PURUSHOTTAM NAIDU
L. NARENDRA KUMAR

Project Report Submitted to the faculty of the

Sree Vidyanikethan Institute of management
Department of Master of Computer Applicattions
SVIM

Committee Members:

All Rights Reserved

Abstract
The business-to-consumer aspect of electronic commerce (e-commerce) is the most visible
business use of the World Wide Web. The primary goal of an e-commerce site is to sell
goods and services online.

This project deals with developing an e-commerce website for Online cloths Sale. It
provides the user with a catalog of different customization dress available for purchase in
the online. The system is implemented using a 3-tier approach, with a backend oracle, a
middle tier of HTML and CSS and javascript and a web browser as the front end client.

In order to develop an e-commerce website, a number of Technologies must be studied

and understood. These include multi-tiered architecture, server and client side scripting
techniques, implementation technologies such as Oracle, HTML(CSS,Javascript),
relational databases (such as MYSQL, Access).

This is a project with the objective to develop 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 e-commerce website.
ACKNOWLEDGMENTS

In completing this graduate project I have been fortunate to have help, support and
encouragement from many people. I would like to acknowledge them for their
cooperation.

First, I would like to thank Prof.Naresh Kumar my project advisor, for guiding my
team through each and every step of the process with knowledge and support.
Thank you for your advice, guidance and assistance.

ii
 I would also like to thank MR.Naredra kumar lankanapalli ,Mr.Purushottam Naidu
Kavali and MR.Laksmikar Reddy Varanasi my project committee members, who showed
immense patience and understanding throughout the project and provided suggestions.

TABLE OF CONTENTS

1. INTRODUCTION........................................................................................................... 1
2. LITERATURE REVIEW................................................................................................ 1

iii
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
performing 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 products (such customize dress,branded cloths,all typen of coths) can be bought
from the comfort of home through the Internet.
However, for implementation purposes, this paper will deal with an online shopping store.

An online store is a virtual store on the Internet where customers can browse the catalog
and select for their own designs and branded cloths of interest. The selected items may be
collected in a shopping cart. At checkout time, the items in the shopping cart will be
presented as an order. At that time, more information will be needed to complete the
transaction. Usually, the customer will be asked to fill or select a billing address, a shipping
address, a shipping option, and payment information such as credit card number. An e-mail
and mobile phone notification is sent to the customer as soon as the order is placed.

2. Literature Review

The increasing importance of e-commerce is apparent in the study conducted by

researches at the GVU (Graphics, Visualization, and Usability) Center at the Georgia
Institute of Technology. In their summary of the findings from the eighth survey, the
researchers report that “e-commerce is taking off both in terms of the number of users
shopping as well as the total amount people are spending via Internet based transactions”.
Over three quarters of the 10,000 respondents report having purchased items online. The
most cited reason for using the web for personal shopping was convenience (65%),
followed by availability of vendor information (60%), no pressure form sales person (55%)
and saving time (53%).

1
 Although the issue of security remains the primary reason why more people do not
purchase items online, the GVA survey also indicates that faith in the security of
ecommerce is increasing. As more people gain confidence in current encryption
technologies, more and more users can be expected to frequently purchase items online. A
good e-commerce site should present the following factors to the customers for better
usability.
• Knowing when an item was saved or not saved in the shopping cart.
• Returning to different parts of the site after adding an item to the shopping cart.
• Easy scanning and selecting items in a list.
• Effective categorical organization of products.
• Simple navigation from home page to information and order links for specific
products.

• Obvious shopping links or buttons.

• Minimal and effective security notifications or messages.
• Consistent layout of product information.

Another important factor in the design of an e-commerce site is feedback. The

interactive cycle between a user and a web site is not complete until the web site responds
to a command entered by the user. According to Norman , "feedback--sending back to the
user information about what action has actually been done, what result has been
accomplished--is a well known concept in the science of control and information theory.
Imagine trying to talk to someone when you cannot even hear your own voice, or trying to
draw a picture with a pencil that leaves no mark: there would be no feedback".

Completed orders should be acknowledged quickly. This may be done with an

acknowledgment or fulfillment page. The amount of time it takes to generate and download
this page, however, is a source of irritation for many e-commerce users. Users are quick to
attribute meaning to events. A blank page, or what a user perceives to be "a long time" to
receive an acknowledgment, may be interpreted as "there must be something wrong with
Project Design

2
 In order to design a web site, the relational database must be designed first.
Conceptual design can be divided into two parts: The data model and the process model.
The data model focuses on what data should be stored in the database while the process
model deals with how the data is processed. To put this in the context of the relational
database, the data model is used to design the relational tables. The process model is used
to design the queries that will access and perform operations on those tables.

2.1 Data Model

A data model is a conceptual representation of the data structures that are required
by a database. The first step in designing a database is to develop an Entity-Relation
Diagram (ERD). The ERD serves as a blue print from which a relational database maybe
deduced. Figure 1 shows the ERD for the project and later we will show the transformation
from ERD to the Relational model.

Login page
In the ERD, a rectangle is used to represent a table and a diamond
to represent the relationship between the entities. The cardinality is the frequency of a
relationship between two entities. The types of cardinality are one to one (1:1), one to
many (1:M), zero to many (0:M) and many to many (M:M). One to one means that every
record
in
Sign in Sign up

entity A matches exactly one record in entity B and every record in B matches exactly
one record in A. One to many means that every record in A matches zero or more records

3
in B and every record in B matches exactly one record in A. If there is a one to many
relationship between two entities, then these entities are represented as Associative
Entities. In the Relational Database model, each of the entities will be transformed into a
table. The tables are shown below along with the attributes.

4
2.1.1 Database Design

In this section, the basic structure of the tables composing the database for the project are
shown along with information about primary and foreign keys.

Customer

SNO NAME TYPE DESCRIPTION

1 UserID Varchar Primary key for Customer identification
2 Password Varchar Security for Customer
3 First_Name Varchar
4 Last_Name Varchar
5 Address Varchar
6 City Varchar
7 State Varchar
8 Email Address Varchar
9 Phone_Number Varchar

Books

SNO NAME TYPE DESCRIPTION

1 InventoryID Integer Primary key for Inventory
Identification,
ISBN of a book
2 Book_Name Varchar
3 Author Varchar
5 Nr_books Integer
6 Price Double

State_Tax

5
SNO NAME TYPE DESCRIPTION
1 State Name Varchar Primary key for State Identification
2 Sales Tax Rate Double Sales tax for each state

Shopping_Cart_Items

SNO NAME TYPE DESCRIPTION

1 ShoppingCartID Integer Primary key for Shopping Cart
Identification
2 InventoryID Varchar Foreign key to Inventory
3 Price Double
4 Date Date
5 UserID Varchar Foreign key to Customer
6 Quantity Integer

Order_Details

SNO NAME TYPE DESCRIPTION

1 OrderID Integer Primary key for Order identification
1 UserID Char Foreign key to Customer
2 Receiver’s Name Char If order is to be sent to other address rather
than to the customer, we need that address
3 Address Char
4 City Char
5 Zip Integer
6 State Char Foreign key to State Tax
7 Type of Shipping Char Foreign key to Shipping Type
8 Date of Purchase Date

Shipping_Type

6
SNO NAME TYPE DESCRIPTION
1 Type of Shipping Varchar Primary key to define type of shipping
2 Price Double
3 Approximate days Integer
for delivery

Credit_Card_Details

SNO NAME TYPE DESCRIPTION

1 Credit Username Varchar Primary key for Customer Identification
2 Credit Card Varchar
Number
3 Card Type Varchar Master Card, Visa, Discover
4 CVV Number Integer Number present on the back of the card for
extra security
5 Expiry Date Date
6 UserID Varchar Foreign key to Customer

Book_Review

SNO NAME TYPE DESCRIPTION

1 InventoryID Varchar ISBN of the book on which the review is
written
2 Reviews Varchar Review on the book
3 Rating Varchar Rating given to the book in a scale of 5
4 Review Date Date
5 User Name Varchar Name of the user providing the review

Purchase_History

SNO NAME TYPE DESCRIPTION

1 UserID Varchar Primary key for Customer Identification

7
2 InventoryID Varchar Book purchased by the user
3 Date of Purchase Date
4 OrderID Integer Foreign key to Order_details
5 Quantity Integer
6 Price Double