EZ Merchant Online Shopping

7/31/2019 EZ Merchant Online Shopping

1/64

1. INTRODUCTION:

1.1 Project OverviewThis project allows different customers to shop different branded items under

one roof. The customer who is using this system can compare the prices and shop different

items very flexibly. Every user has to read and agree the user license agreement.

Here we have two types of users.

1. Administrator

2. Normal User

1.2 Project Scope:

EzeeMerchant as a true World Wide Internet (Online) is based on marketing

perspective shopping system. The system provides functionality for any customer to interact

with merchants truly online and conduct business. As the name implies, it is shopping

through web with easy to use enriched UI. As getting more clients from various places it is

better to use web for taking orders informing products information to give more facilities to

clients. The following modules have been integrated.

1.3 Screen Design / Graphical User Interface:

The system uses a very user-friendly interface developed using Hyper Text Markup

Language (HTML), which most users are acquainted with and is broadly used on the World

Wide Web (WWW). The controls are placed on the forms in an easily accessible manner so

that user strain is minimized to the maximum extent.

Whenever a user enters any form the system also states the action to be performed

in an easily understandable and pleasant speech. The system also poses a unique format for

each type of employee; this ensures that employee is presented with options he has access

to. This ensures a great deal of security to the system and to the organization as an employee

is not given an option to carryout unauthorized activity.

1


2/64

1.4 General Description:

Admin:

The most remarkable feature is Admin module, which deals with creating giving

access rights to products, Categories, Orders, User Information per Order details etc

(1)Products: It gives the Products Information, Quantity per pack, price

per quantity, price and dummy price etc.

(2)Categories: This module has root category. Root contains several sub

categories. Categories under Root are Id, Name, List of products under

present category and soon.

(3)Orders: Registered client can place orders, can check the status of

order, or Cancel the order if it is not processed.

(4) Email Templates:It allows the administrator to create the some email-

templates for forgot password, order status and pending payment etc.

whenever the administrator wants to send a mail to the customer he will

make use these templates to reduce manual typing.

(5)Preferences:It allows to set the page setups on fly for different pages

like Global Page, Category page and Product List Page etc. it allows us to

change the headers and footers without touching the source code. Simple

we can customize the pages dynamically.

(6)Variables: It allows the administrator to set some parameter values

dynamically. It helps a lot in calculating finally amount based on the current

parameter values.

(7)User Information per Order: It provides a facility to customize the

user information by editing the existing fields, adding the new fields and

setting different types options for the fields.

(8)Countries: It displays Country Names, Country Ids. And it displays

Registered Post cost and Courier cost also. Edit option is edit the ID,

Country Name, Registered Post cost and Courier cost. Delete option is

delete the one row from Country profile.

2


3/64

(9)Shipping Companies:This option gives the shipping companies details. Name

of the company, URL of the company, Tracking details are available under this

option .Edit and Delete options also added to every row.

(10)Users:It gives the total users list under this Administrator. It displays Email

Address (Username), Personal Details, Reference details i.e., who is referred to the

existing user. Edit and Delete options is also available. Edit option is to change the

user profile and Delete option is to delete the user account.

(11) Logout:Come out from the Administrator and Login form will be display to

login.

NORMAL USER:

Normal User can engage in online shopping in any location, and they can

compare the prices and they can buy the product without face-to-face assistance to the

shopper. If any person wants to enter into this, he should be member of this organization.

Register form is available at login page. Just click the link click here. Member can enter

and purchase the goods as his wish. The customer can see the status of goods delivery also

by sitting at home.

(1)Change Password:This option is to change password of user. Whenever

the user clicks this option, Change your Password form will be display.

This form asks the old pass, new password. The old password is correct then

modified (new) password is saved.

(2)Change Profile:If the user clicks this option, User profile form will be

open. If the User wants change his name, address, another details then enter

above information and click the update button.

(3)My Orders:By using this option, the users can Orders under the payment

pending. This option has sub options like OrderID, Date of purchase, Total

Amount, Status of Payment etc.

3


4/64


5/64

2.SYSTEM ANALYSIS:

2.1 Need for the System:

If this system is not there then the customer has to shop the items directly by

manually going to the shop. The user has to go for different shops to buy different branded

items. If the shop is available at different location then we need to contact them though mail

and though phone to shop the items and confirm the order then again the shopper needs to

contact the customers and send the delivery through some communication system. The

shopper has to maintain all the customer details, their orders and the status. It becomes a

tedious process if we maintain it manually. Thats why our client wants to implement a

software application to automate all these tasks very affectively.

2.2 Proposed System:

This system allows the customers to register on their own after reading the license

agreement. After registration each user will receive username and password using which the

customer can shop different products and place it in a cart. The customer can check the

items in the cart at any point of time and he can confirm the order and pay the bill using

credit card. The shopper can manage different categories, products and the cart. He can also

see the customer orders and confirm the order to deliver the good. The customer and the

shopper can track the orders at any point of time. The main features of this system:

1. The user can shop the different branded items under one roof.

2. The shopper can change the any page dynamically without touching the source code.

3. The shopper can change different processing charge values dynamically.

4. The shopper can check the credited amounts and select different options to confirm the

orders or else send the mails to customers using manageable email templates.

2.3 Performing the Feasibility study:

After analyzing the existing system, the organization is in need of automation of

existing manual system. The organization has the capacity to stand the cost of developing

new system and is willing to do that. The product will be of utmost use and the level of ease

has been increased to a great extent.

5


6/64

2.4Software Requirements Specification2.4.1 Introduction:

Purpose:

The purpose of this project is to handle Human Resources of organization.

2.4.1.1 Product Scope

The scope of the project is limited to a single organization.

2.4.1.2 Reference

Java Server Programming J2EE edition wrox.

J2EE Complete reference -McGraw Hill.

My Sql 5.0

Java Servlet Programming Oreilly.

2.4.2 Operating Environment Operating System

Windows 2000server and professional

Hardware platform

Pentium 4 processor

256 MB RAM

Software specifications

J2SDK 1.4J2SDK 1.4 J2EE

MySql 5.0

Microsoft Front Page ExpressInternet Explorer

Tomcat 4.0

3. SYSTEM DEVLOPMENT ENVIRONMENT:

3.1 Java coding standards:Why Coding Standards are Important:

Coding standards for Java are important because they

lead to greater consistency within your code and the code of your teammates.

Greater consistency leads to code that is easier to understand, which in turn means it

is easier to develop and to maintain. This reduces the overall cost of the applications

that you create.

6


7/64

4. AN OVERVIEW TO J2EE:

The following topics describe the J2EE Platform

requirements for each kind of J2EE platform element.

J2EE Application Components

The J2EE runtime environment defines four

application component types that a J2EE product must support:

Application clients are Java programming language

programs that are typically GUI programs that execute on a desktop computer.

Application clients offer a user experience similar to that of native applications, and

have access to all of the facilities of the J2EE middle tier. Applets are GUI

components that typically execute in a web browser, but can execute in a variety of

other applications or devices that support the applet-programming model. Applets can

be used to provide a powerful user interface for J2EE applications. Servlets, JSP pages,

filters, and web event listeners typically execute in a web container and may respond to

HTTP requests from web clients. Servlets, JSP pages, and filters may be used to

generate HTML pages that are an applications user interface. They may also be used to

generate XML or other format data that is consumed by other application components.

A special kind of servlet provides support for web services using the SOAP/HTTP

protocol. Servlets, pages created with the Java Server Pages technology, web filters,

and web event listeners are referred to collectively in this specification as web

components. Web applications are composed of web components and other data such

as HTML pages. Web components execute in a web container. A web server

includes a web container and other protocol support, security support, and so on, as

required by J2EE specifications .Enterprise Java Beans (EJB) components execute in

a managed environment that supports transactions. Enterprise beans typically contain the

business logic for a J2EE application. Enterprise beans may directly provide web

services using the SOAP/HTTP protocol.

7


8/64

J2EE Server Support for Application Components:

The J2EE servers provide deployment, management, and

execution support for conforming application components. Application componentscan be divided into three categories according to their dependence on a J2EE server:

Components that are deployed, managed, and executed on a

J2EE server. These components include web components and Enterprise Java Beans

components. See the separate specifications for these components. Components that are

deployed and managed on a J2EE server, but are loaded to and executed on a client

machine. These components include web resources such as HTML pages and applets

embedded in HTML pages. Components deployment and management is not completely

defined by this specification. Application Clients fall into this category. Future versions

of this specification may more fully define deployment and management of Application

Clients.

J2EE Containers:

Containers provide the runtime support for J2EE application

components. Containers provide a federated view of the underlying.

J2EE APIs to the application components. J2EE application

components never interact directly with other J2EE application components.

J2EE Servers:

Underlying a J2EE container is the server of which it is a

part. A J2EE Product Provider typically implements the J2EE server-side functionality

using an existing transaction processing infrastructure in combination with Java 2 Platform,

Standard Edition (J2SE) technology. The J2EE client functionality is typically built on

J2SE technology.

8


9/64

Resource Adapters:

A resource adapter is a system-level software

component that implements network connectivity to an external resource manager.

A resource adapter can extend the functionality of the J2EE platform either by

implementing one of the J2EE standard service APIs (such as a JDBC driver), or

by defining and implementing a resource adapter for a connector to an external

application system.

Java Transaction API (JTA)

The Java Transaction API consists of two parts:

An application-level demarcation interface is used by the container and

application components to demarcate transaction boundaries. An interface between

the transaction manager and a resource manager used at the J2EE SPI level(in

a future release).

JDBC API:

The JDBC API is the API for connectivity with relational

database systems. The JDBC API has two parts: an application-level interface used

by the application components to access a database, and a service provider

interface to attach a JDBC driver to the J2EE platform. Support for the service

provider interface is not required in J2EE products.

Java Message Service (JMS):

The Java Message Service is a standard API for

messaging that supports reliable point-to-point messaging as well as the publish-

subscribe model. This specification requires a JMS provider that implements both

point-to-point messaging as well as publishes-subscribe messaging.

9


10/64

Java Naming and Directory Interface (JNDI)

The JNDI API is the standard API for naming and directory

access. The JNDI API has two parts: an application-level interface used by the

application components to access naming and directory services and a service

provider interface to attach a provider of a naming and directory service.

Java Connector Architecture:

The Connector architecture is a J2EE SPI that allows

resource adapters that support access to Enterprise Information Systems to be

plugged in to any J2EE product. The Connector architecture defines a standard set

of system-level contracts between a J2EE server and a resource adapter.

Security Service:

The Java Authentication and Authorization Service

(JAAS) enables services to authenticate and enforce access controls upon users. It

implements a Java technology version of the standard Pluggable Authentication

Module (PAM) framework, and extends the access control architecture of the Java 2

Platform in a compatible fashion to support user-based authorization. The Java

Authorization Service Provider Contract for Containers (JACC) defines a contract

between a J2EE application server and an authorization service provider, allowing

custom authorization service providers to be plugged into any J2EE product.

Web Services:

J2EE provides full support for both clients of web services

as well as web service endpoints. Several Java technologies work together to

provide support for web services. The Java API for XML-based RPC (JAX-RPC)

provides support for web service calls using the SOAP/HTTP protocol. JAX-RPC

defines the mapping between Java classes and XML as used in SOAP RPC calls.

The SOAP with Attachments API for Java (SAAJ) provides support for

10


11/64

manipulating low-level SOAP messages. The Web Services for J2EE specification

fully defines the deployment of web service clients and web service endpoints in J2EE,

as well as the implementation of web service endpoints using enterprise beans. The Java

API for XML Registries (JAXR) provides client access to XML registry servers.

Deployment:

The Java 2 Platform, Enterprise Edition Deployment

Specification defines a contract between deployment tools and J2EE products.

The J2EE products provide plug-in components that run in thedeployment tool

and allow the deployment tool to deploy applications into the J2EE product. The

deployment tool provides services used by these plug-in components.

4.1. J2EE Architecture:

11


12/64

4.2. Web Applications and Exploded Directory Format (EDF):

Overview of Web Applications:

A Web application contains an applications resources, such

as servlets., Java Server Pages (JSPs), JSP tag libraries, static resources such as

HTML pages and image files. Web applications deployed on Tomcat Server use a

standard J2EE deployment descriptor file and Tomcat specific employment

descriptor file to define their resources and operating attributes. JSP and HTTP

servlets can access all services and APIs available in Tomcat Server. These services

include database connections via Java Database Connectivity (JDBC), Java

Messaging Service (JMS), XML, and more. A Web archive (WAR file) contains

the files that make up a Web application (WAR file). A WAR file is deployed as a

unit on one or more Tomcat Server instances. A Web archive on Tomcat Server

always includes the following files: One servlet or Java Server Page (JSP), along

with any helper classes. A web.xml deployment descriptor, which is a J2EE

standard XML document that describes the contents of a WAR file.

Tomcat Web Application Manager:

Introduction:In many production environments it is very useful to have the

capability to manage your web applications without having to shut down and restart

Tomcat. This document is for the HTML web interface to the web application

manager. The interface is divided into five sections:

Message - Displays success and failure messages.

Manager - General manager operations like list and help.

Applications - List of web applications and commands.

Install - Installing web applications.

Server Information - Information about the Tomcat server.

12


13/64

Message:

Displays information about the success or failure of the last

application manager command you performed. If it succeeded OK is displayed

and may be followed by a success message. If it failed FAIL is displayed

followed by an error message. Common failure messages are documented below

for each command. The complete list of failure messages for each command can

be found in the manager web application documentation.

Manager:

The Manager section has three links:

List Applications - Redisplay a list of web applications. HTML Manager Help - A link to this document.

Manager Help - A link to the comprehensive Manager App HOW TO.

Applications:

The Applications section lists information about all the

installed web applications and provides links for managing them. For each web

application the following is displayed:

Path - The web application context path.

Display Name - The display name for the web application if it has

one configured in its "web.xml" file.

Running - Whether the web application is running and available

(true), or not running and unavailable (false).

Sessions - The number of active sessions for remote users of this web

application. The number of sessions is a link which when submitted displays

more details about session usage by the web application in the Message box.

13


14/64

Commands - Lists all commands which can be performed on the

web application. Only those commands which can be performed will be

listed as a link which can be submitted. No commands can be performed on

the manager web application itself. The following commands can be

performed:

o Start - Start a web application which had been stopped.

o Stop - Stop a web application which is currently running and

make it unavailable.

o Reload - Reload the web application so that new ".jar" files

in /WEB-INF/lib/ or new classes in /WEB-INF/classes/ can be used.

o Remove - Stop and then remove this web application from

the server.

Start:

Signal a stopped application to restart, and make itself available

again. Stopping and starting is useful, for example, if the database required

by your application becomes temporarily unavailable. It is usually better to

stop the web application that relies on this database rather than letting

users continuously encounter database exceptions..If this command

succeeds, you will see a Message like this:

OK - Started application at context path /examples

Otherwise, the Message will start with FAIL and include

an error message. Possible causes for problems include:

Encountered exception

An exception was encountered trying to start the web

application. Check the Tomcat 4 logs for the details.

14


15/64

Invalid context path was specified

The context path must start with a slash character, unless

you are referencing the ROOT web application -- in which case the context path

must be a zero-length string.

No context exists for path /foo

There is no deployed or installed application on the context

path that you specified.

No context path was specified

The path parameter is required.

Stop:

Signal an existing application to make itself unavailable,

but leave it deployed or installed. Any request that comes in while an

application is stopped will see an HTTP error 404, and this application will show

as "stopped" on a list applications command.

If this command succeeds, you will see a Message like

this:

OK - Stopped application at context path /example




An exception was encountered trying to stop the web


15


16/64










Reload:

Signal an existing application to shut itself down and

reload. This can be useful when the web application context is not reloadable

and you have updated classes or property files in the /WEB-INF/classes

directory or when you have added or updated jar files in the /WEB-INF/lib

directory.

NOTE: The /WEB-INF/web.xml web application configuration file is

not checked on a reload; the previous web.xml configuration is used. If you have

made changes to your web.xml file you must stop then start the web application.

If this command succeeds, you will see a Message like this:

OK - Reloaded application at context path /examples




16


17/64

An exception was encountered trying to restart the web.

Remove:

This command will delete the contents of the web

application directory and/or ".war" file if it exists within the app Base directory

(typically "web apps") for this virtual host.The web application temporary work

directory is also deleted. If you simply want to take an application out of service,

you should use the /stop command instead.

Signal an existing application to gracefully shut itself

down, and then remove it from Tomcat (which also makes this context path

available for reuse later). This command is the logical opposite of the /install

command.

If this command succeeds, you will see a Message like this:

OK - Removed application at context path /examples

Otherwise, the Message will start with FAIL and

include an error message. Possible causes for problems include:


An exception was encountered trying to remove the web









17


18/64



Install:

Web applications can be installed using files or

directories located on the Tomcat server or you can upload a web application

archive (WAR) file to the server.

To install an application, fill in the appropriate fields for

the type of install you want to do and then submit it using theInstallbutton.

Install Directory or WAR located on server:

Install and start a new web application, attached to the specified

Context Path: (which must not be in use by any other web application). This

command is the logical opposite of theRemove command.

There are a number of different ways the install

command can be used.

Install a Directory or WAR by URL:

Install a web application directory or ".war" file located

on the Tomcat server. If no Context Path is specified, the directory name or the

war file name without the ".war" extension is used as the path. The WAR or

Directory URL specifies a URL (including the file: scheme) for either a

directory or a web application archive (WAR) file. The supported syntax for a

URL referring to a WAR file is described on the Javadocs page for the

java.net .JarURL Connection class. Use only URLs that refer to the entire WAR

file .In this example the web application located in the directory C:\path\to\foo

on the Tomcat server (running on Windows) is installed as the web application

context named /footoo.

Context Path: /footoo

18


19/64

WAR or Directory URL: file:C:/path/to/foo

In this example the ".war" file /path/to/bar.war on the

Tomcat server (running on Unix) is installed as the web application context

named /bar. Notice that there is no path parameter so the context path defaults

to the name of the web application archive file without the ".war" extension.

Install directory or WAR file located on server:

Install and start a new web application, attached to the

specified Context Path: (which must not be in use by any other web application).

This command is the logical opposite of theRemove command.

There are a number of different ways the install

command can be used Install a Directory or WAR by URL

Install a web application directory or ".war" file located

on the Tomcat server. If no Context Path is specified, the directory name or the

war file name without the ".war" extension is used as the path. The WAR or

Directory URL specifies a URL (including the file: scheme) for either a

directory or a web application archive (WAR) file. The supported syntax for a

URL referring to a WAR file is described on the Javadocs page for the

java.net .JarURL Connection class. Use only URLs that refer to the entire WAR

file.In this example the web application located in the directory C:\path\to\foo

on the Tomcat server (running on Windows) is installed as the web application

context named /footoo.

Context Path: /footoo

WAR or Directory URL: file:C:/path/to/foo

In this example the ".war" file /path/to/bar.war on the

Tomcat server (running on Unix) is installed as the web application context

named /bar. Notice that there is no path parameter so the context path defaults

to the name of the web application archive file without the ".war" extension.

19


20/64

WAR or Directory URL: jar:file:/path/to/bar.war!/

Install a Directory or War from the Host app Base

Install a web application directory or ".war" file located in your

Host appBase directory. If no Context Path is specified the

directory name or the war file name without the ".war" extension is used as

the path. In this example the web application located in a subdirectory named foo in

the Host appBase directory of the Tomcat server is installed as the web application

context named /foo. Notice that there is no path parameter so the context path defaults

to the name of the web application directory.

WAR or Directory URL: foo

In this example the ".war" file bar.war located in your

Host appBase directory on the Tomcat server is installed as the web application

context named /bartoo.

Context Path: /bartoo

WAR or Directory URL: bar.war

Install using a Context configuration ".xml" file:

If the Host deploy XML flag is set to true, you can install

a web application using a Context configuration ".xml" file and an optional

".war" file or web application directory. The Context Path is not used when

installing a web application using a context ".xml" configuration file.

A Context configuration ".xml" file can contain valid

XML for a web application Context just as if it were configured in your Tomcat

server.xml configuration file. Here is an example for Tomcat running on

Windows:


21/64

type="org.apache.catalina.UserDatabase"/>

Use of the WAR or Directory URL is optional. When used

to select a web application ".war" file or directory it overrides any doc Base

configured in the context configuration ".xml" file.Here is an example of installing

an application using a Context configuration ".xml" file for Tomcat running on

Windows

XML Configuration file URL: file:C:/path/to/context.xml

Here is an example of installing an application using a

Context configuration ".xml" file and a web application ".war" file located on

the server (Tomcat running on Unix).

XML Configuration file URL: file:/path/to/context.xml

Here is an example of installing an application using a

Context configuration ".xml" file and a web application ".war" file locatedon the

server (Tomcat running on Unix).

XML Configuration file URL: file:/path/to/context.xml

WAR or Directory URL: jar:file:/path/to/bar.war!/

Uplosd a WAR file to Install:

Upload a WAR file from your local system and install it

into the appBase for your Host. The name of the WAR file without the ".war"

extension is used as the context path name.Use the Browse button to select a

WAR file to upload to the server from your local desktop system.

Upload of a WAR file could fail for the following reasons:

File uploaded must be a .war

21


22/64

The upload install will only accept files which have the

filename extension of ".war".

War file already exists on server

If a war file of the same name already exists in your Host's

appBase the upload will fail. Either remove the existing war file from your Host's

appBase or upload the new war file using a different name.

File upload failed, no file

The file upload failed, no file was received by the server.

Install Upload Failed, Exception:

The war file upload or install failed with a Java

Exception. The exception message will be listed..

Installation Notes:

If the Host is configured with unpackWARs=true and you

install a war file, the war will be unpacked into a directory in your Host appBase

directory.

If the application war or directory is installed in your

Host appBase directory and either the Host is configured with autoDeploy=true

or liveDeploy=true, the Context path must match the directory name or war file

name without the ".war" extension.

For security when untrusted users can manage web

applications, the Host deployXML flag can be set to false. This preventsuntrusted users from installing web applications using a configuration XML file

and also prevents them from installing application directories or ".war" files ge

located outside of their Host appBase.

22


23/64

Install Message:

If installation and startup is successful, you will receive a

Message like this:

OK - Installed application at context path /foo



Application already exists at path /foo

The context paths for all currently running web

applications must be unique. Therefore, you must either remove or undeploy the

existing web application using this context path, or choose a different context path

for the new one.

Document base does not exist or is not a readable

OK - Installed application at context path /foo



Application already exists at path /foo

The context paths for all currently running web

applications must be unique. Therefore, you must either remove or undeploy the

existing web application using this context path, or choose a different context path

for the new one.

Document base does not exist or is not a readable directory

The URL specified by the WAR or Directory URL: field

must identify a directory on this server that contains the "unpacked" version of a

web application, or the absolute URL of a web application archive (WAR) file

23


24/64

that contains this application. Correct the value entered for the WAR or Directory

URL: field.


An exception was encountered trying to start the new web

application. Check the Tomcat 4 logs for the details, but likely explanations

include problems parsing your /WEB-INF/web.xml file, or missing classes

encountered when initializing application event listeners and filters.

Invalid application URL was specified

The URL for the WAR or Directory URL: field that youspecified was not valid. Such URLs must start with file:, and URLs for a WAR

file must end in ".war".




must be a "/" string.

Context path must match the directory or WAR file name:

If the application war or directory is installed in your Host

app Base directory and either the Host is configured with auto Deploy=true or live

Deploy=true, the Context path must match the directory name or war file name

without the ".war" extension.

Only web applications in the Host web application directory can be

installed

24


25/64

If the Host deploy XML flag is set to false this error will happen if an

attempt is made to install a web application directory or ".war" file outside of

the Host app Base directory.

5. AN OVERVIEW OF JSP:

The Java Server Pages Technology:

Java Server Pages technology is the Java technology in

the J2EE platform for building applications containing dynamic Web content such as

HTML, DHTML, XHTML and XML. The Java Server Pages technology enables the

authoring of Web pages that create dynamic content easily but with maximum power

and flexibility.

The Java Server Pages technology provides a textual

description for the creation of a response from a request. The technology builds on the

following concepts:

Template Data:

Substantial portions of dynamic content are actually fixed.

The JSP technology allow for the natural manipulation of this data.

Addition of Dynamic Data:

The JSP technology allows the addition of dynamic data to

the template data in a way that is simple yet powerful.

Encapsulation of Functionality:

The JSP technology provides two related mechanisms for the

encapsulation of functionality: the standard Java Beans component architecture and the

tag library mechanism.

Good Tool Support:

The JSP technology has features that enable the creation of

good authoring tools. The result is a flexible and powerful server-side technology.

25


26/64

Benefits of the Java Server Pages Technology:

The Java Server Pages technology offers a number of

benefits:

Write Once, Run Anywhereproperties:

The Java Server Pages technology is platform independent,

both in its dynamic Web pages, Web servers, and its underlying server components..

High quality tool support:

The Write Once, Run Anywhere properties of JSP allows the

user to choose best-of-breed tools. Additionally, an explicit goal of the Java Server

Pages design is to enable the creation of high quality portable tools.

Separation of Roles:

JSP supports the separation of roles: developers write

components that interact with server-side objects.

Reuse of components and tag libraries:

The Java Server Pages technology emphasizes the use of

reusable components such as Java Beans components, Enterprise Java Beans

components and tag libraries.

Separation of dynamic and static content:

The Java Server Pages technology enables the separation of

static content from dynamic content that is inserted into the static template.

26


27/64

Support for scripting and actions:

The Java Server Pages technology supports scripting

elements as well as actions. Actions permit the encapsulation of useful

functionality in a convenient form that can also be manipulated by tools; scripts

provide a mechanism toglue togetherthis functionality in a per-page manner.

Web access layer for N-tier enterprise application architecture(s)

The Java Server Pages technology is an integral part of the

Java 2 Platform Enterprise Edition (J2EE), which brings Java technology to

enterprise computing.

5.1. An Overview of Servlets:

What is a Servlet?

A servlet is a web component, managed by a container that

generates dynamic content. Servlets are small, platform independent Java classes

compiled to an architecture neutral byte code that can be loaded dynamically into

and run by a web server. Servlets interact with web clients via a request response

paradigm implemented by the servlet container. This request-response model is

based on the behavior of the Hypertext Transfer Protocol (HTTP).

What is a Servlet Container?

The servlet container, in conjunction with a web server or

application server, provides the network services over which requests and

responses are set, decodes MIME based requests, and formats MIME based

responses. A servlet container also contains and manages servlets through their

lifecycle. A servlet container can either be built into a host web server or installed

as an add-on component to a Web Server via that servers native extension API.

Servlet Containers can also be built into or possibly installed into web-enabled

27


28/64

Application Servers. All servlet containers must support HTTP as a protocol for

requests and responses, but may also support other request / response based

protocols such as HTTPS (HTTP over SSL). The minimum required version of

the HTTP specification that a container must implement is HTTP/1.0. It is strongly

suggested that containers implement the HTTP/1.1 specification as well.

A Servlet Container may place security restrictions on the

environment that a servlet can executed In a Java 2 Platform Standard Edition 1.2

(J2SE) or Java 2 Platform Enterprise Edition 1.3 (J2EE) environment, these

restrictions should be placed using the permission architecture defined by Java 2

Platform. For example, high-end application servers may limit certain action, such

as the creation of a Thread object, to insure that other components of the container

are not negatively impacted.

5.3. An Overview of JDBC

What is JDBC?

JDBC is a Java Api for executing SQL , Statements (As apoint of interest JDBC is trademarked name and is not an acronym; nevertheless,

is often thought of as standing for Java Database Connectivity. It Consists of a set

of classes and interfaces written in the Java Programming language .JDBC

provides a standard API for tool/database developers and makes it possible to

write database applications using a pure Java API

Using JDBC, it is easy to send SQL statements to virtually

any relational database. One can write a single program using the JDBC API ,and

the program will be able to send SQL .statements to the appropriate database. The

Combination of Java and JDBC lets a programmer writes it once and run it

anywhere.

28


29/64

What Does JDBC Do?

JDBC makes possible to

o Establish a connection with a database

o Send SQL statements

o Process the results

o JDBC Driver Types

o The JDBC drivers that we are aware of this time fit into one of four categories

o JDBC-ODBC Bridge plus ODBC driver

o Native-API party-java driver

o JDBC-Net pure java driver

o Native-protocol pure Java driver

An individual database system is accessed via a

specific JDBC driver that implements the java. sql. Driver interface. Drivers exist

for nearly all-popular RDBMS systems, through few are available for free. Sun

bundles a free JDBC-ODBC bridge driver with the JDK to allow access to a

standard ODBC ,data sources, such as a Microsoft Access database, Sun advises

against using the bridge driver for anything other than development and very limited

development.

JDBC drivers are available for most database platforms,

from a number of vendors and in a number of different flavors. There are four

driver categories

Type 01-JDBC-ODBC Bridge Driver:

Type 01 drivers use a bridge technology to connect a java

client to an ODBC database service. Suns JDBC-ODBC bridge is the most

common type 01 driver. These drivers implemented using native code.

29


30/64

Type 02-Native-API party-java Driver:

Type 02 drivers wrap a thin layer of java around database-

specific native code libraries for Oracle databases, the native code libraries might be

based on the OCI(Oracle call Interface) libraries, which were originally designed for

c/c++ programmers, Because type-02 drivers are implemented using native code. in

some cases they have better performance than their all-java counter parts. They add

an element of risk, however, because a defect in a drivers native code section can

crash the entire server

Type 03-Net-Protocol All-Java Driver:

Type 03 drivers communicate via a generic network protocol

to a piece of custom middleware. The middleware component might use any type

of driver to provide the actual database access. These drivers are all java, which

makes them useful for applet deployment and safe for servlet deployment.

Type-04-native-protocol All-java Driver:

Type o4 drivers are the most direct of the lot. Written

entirely in java, Type 04 drivers understand database-specific networking.

protocols and can access the database directly without any additional software

What Is The JDBC-ODBC Bridge ?

The JDBC-ODBC Bridge is a JDBC driver, which

implements JDBC operations by translating them into ODBC operations. To

ODBC it appears as a normal application program. The Bridge is implemented as

the sun .JDBC. odbc Java package and contains a native library used to access

ODBC. The Bridge is joint development of Intersolv and Java Soft.

30


31/64

6. SYSTEM DESIGN:

6.1 Data Dictionary:

Categories:

Name Constraint Data Type Description

Nid Auto_Increment,

PRIMARY KEY

int(11) Category

Identification

Number

nParentID NOT NULL int (11) Parent

IdentificationNumber

txtName varchar(100) Category Name

txtDescription text Description

txtTitle text TitletxtMeta text Meta Name

txtHeader text Header Name

txtFooter text Footer Name

txtMetaReplyTo text Meta Reply Name

txtMetaLanguage text Meta Language

Name

txtMetaDistribution text Meta Distribution

Name

txtMetaCopyright text Meta Copy RightName

txtMetaClassification text MetaClassificationName

txtMetaAuthor text Meta Author Name

txtMetaRevisitAfter text Meta RevisitName

txtMetaDescription text Meta Description

Name

txtMetaRobots text Meta Rebots

txtMetaKeywords text Meta Keywords

Category Product`s:


nCategoryID NOT NULL int(11) Category IdentificationNumber

nProductID NOT NULL int(11) Product IdentificationNumber

nOrder NOT NULL int(11) Order Number

31


32/64

Countries:


txtID NOT NULL,

PRIMARY KEY

char(2) Identification Number

txtName NOT NULL varchar(40) Country Name

dblRegisteredPost NOT NULL double Registered Post Cost

dblExpressCourier NOT NULL double Courier Cost

Email Templates:


txtName PRIMARY KEY NOT NULL (50) NametxtSubject NOT NULL text Subject

txtMessage NOT NULL text Message

txtVariables NOT NULL text Variables

Order Shipping Address:


nOrderID PRIMARY KEY Int(11) Order Identification

Number

txtName varchar (20) Name

txtStreetAddress text Street AddresstxtZipCode varchar (20) Zip Code

txtCity varchar (20) City Name

txtState varchar (20) State Name

txtCountry varchar (20) Country Name

txtPhone varchar (25) Phone Number

txtShippingMethod NOT NULL varchar (20) Shipping Method

Order User Info:


nQuestionID NOT NULL int(11) Question Number

nOrderID NOT NULL int(11) Order Identification Number

nType NOT NULL int(11) Type

txtTitle Text Title

txtValue Text Value

32


33/64

Ordered Items:


nOrderID NOT NULL int(50) Order Identification Number

nProductID NOT NULL int(11) Product Identification Number

dblPrice NOT NULL Double Price Value

DblCost NOT NULL Double Cost Value

nQuantity NOT NULL int(11) No of Items

txtReason Text Remarks

Orders:

Preferences:


txtName NOT NULL varchar(100) Preferences Name

txtValue Text Value

33


nID PRIMARY KEY,

auto_increment

int(11) Order

Identification

Number

txtEmailAddress NOT NULL varchar(50) Email Address

tsChangeTime NOT NULL timestamp(14) Change Time

tsDate NOT NULL timestamp(14) Date

nOrderState NOT NULL int(11) Order State

Number

dblTotal NOT NULL double Total Amount

dblProcessingFees NOT NULL double Procession Fees

dblShippingCharges NOT NULL double Shipping

ChargesdblGrandTotal NOT NULL double Grand Total

DblPaid NOT NULL double Paid Amount

txtRemarks text Remarks

txtTracking text Tracking

txtTrackingCompany text TrackingCompany

txtTrackingURL text Tracking URL


34/64

Products:


nID PRIMARY KEY int(11) Product Identification

NumbertxtName NOT NULL varchar(100) Product Name

txtDescription varchar(100) Product Description

txtImgUrl text URL of Image

txtHeader text Header Name

txtFooter text Footer Name

txtBuyNowUrl text URL

txtWeight NOT NULL varchar(50) Weight

dblQtyPerPack NOT NULL double Quantity Per Pack

dblPricePerQty NOT NULL double Price Per Quantity

bActive NOT NULL int(11) Active or Not

dblPrice NOT NULL double PricedblDummyPrice NOT NULL double Dummy Price

dblShippingFactor NOT NULL double Shipping Factor

dblCostPerQty NOT NULL double Cost Per Quantity

dblCost NOT NULL Cost Value

Shipping Charges:


txtCountryID PRIMARY KEY, varchar(40) Country Identification

Number

dblExpressCourier NOT NULL double Courier Amount

dblRegisteredMail NOT NULL double Register Mail Amount

Shipping Companies:


nID PRIMARY KEY,

auto_increment

Int(40) Shipping Company Number

txtName NOT NULL Varchar(100) Shipping Company Name

txtURL Text Company URL

txtTrackingURL text Tracking URL

Use r Info Questions:


nID PRIMARY KEY, int(11) User Information Question ID

34


35/64

auto_increment

txtTitle text Title

nType NOT NULL int(11) Type

txtChoices text Choice

txtAcceptOnly text Acceptance

txtRejectOnly text RejecttxtErrorMsg text Error Message

Users:


txtEmailAddress UNIQUE KEY varchar(50) Email Address

txtPassword NOT NULL varchar(50) Password

nACLBitmap NOT NULL varchar(20) Bit Map

txtFirstname NOT NULL varchar(20) First Name

txtLastname NOT NULL varchar(20) Last Name

txtStreetAddress NOT NULL Text Street AddresstxtZipCode NOT NULL varchar(20) Zip Code

txtCity NOT NULL varchar(15) City Name

txtState NOT NULL varchar(15) State Name

txtCountry NOT NULL varchar(40) Country Name

txtPhone NOT NULL varchar(25) Phone Number

txtReference NOT NULL varchar(100) Reference Name

txtReferredBy NOT NULL varchar(40) Referred By

bSendPromotion NOT NULL tinyint(4) Promotion Option

bNeverSendMail NOT NULL tinyint(4) Never Send Mail Option

dblCredit NOT NULL double Credit Amount

tsLastChange NOT NULL timestamp(14) Last Change Time

tsRegTime NOT NULL timestamp(14) Registration Time

Variables:


txtName PRIMARY KEY, varchar(100) Variable Name

txtValue text Variable Value

7. ER DIAGRAM:

ER Diagram:-

An E-R diagram can express the overall logical structure of a

database graphically. The relative simplicity and pictorial clarity of this diagramming

35


36/64

technique may well account in the large part for the wide spread use of the E-R model. Such

a diagram consists of the following major components:

Rectangles : Which represent entity sets.

Ellipse : Which represents attributes.

Diamond : Which represent relationship sets.

Lines : Which link attributes to entity sets to

relationships sets.

7.1 UNIFIED MODELLING LANGUAGE:

An Overview of UML

The UML is a language for

Visualizing

Specifying

Constructing

Documenting

These are the artifacts of a software-intensive system.

A conceptual model of UML:

The three major elements of UML are

The UMLs basic building blocks

The rules that dictate how those building blocks may be put together.

Some common mechanisms that apply throughout the UML.

Basic building blocks of the UML:

The vocabulary of UML encompasses three kinds of building

blocks:

36


37/64

Things

Relationships

Diagrams

Things are the abstractions that are first-class citizens in amodel Relationships tie these things together. Diagrams group the interesting

collection of things.

There are four kind of things in the UML

1. Structural things

2. Behavioral things.

3. Grouping things

4. An notational things

These things are the basic object oriented building blocks of

the UML. They are used to write well-formed models.

STRUCTURAL THINGS:

Structural things are the nouns of the UML models. These

are mostly static parts of the model, representing elements that are either

conceptual or physical. In all, there are seven kinds of Structural things.

Class:A class is a description of a set of objects that share the same

attributes, operations, relationships, and semantics. A class implements one or more

interfaces. Graphically a class is rendered as a rectangle, usually including its name,

attributes and operations, as shown below.

37


38/64

Window

origin

Size

Open()Close()

Display()

Interface:

An interface is a collection of operations that specify a service

of a class or component. An interface describes the externally visible behavior of that

element. Graphically the interface is rendered as a circle together with its name.

ISpelling

Collaboration:

Collaboration defines an interaction and is a society of roles

and other elements that work together to provide some cooperative behavior thats

bigger than the sum of all the elements. Graphically , a collaboration is rendered as

an ellipse with dashed lines, usually including only its name as shown below.

Use Case:

38

Chain ofResponsibilit

y


39/64

Use case is a description of a set of sequence of actions that

a system performs that yields an observable result of value to a particular things in

a model. Graphically, Use Case is rendered as an ellipse with dashed lines, usually

including only its name as shown below.

Active Class:

An active class is a class whose objects own one or more

processes or threads and therefore can initiate control activity.Graphically, an

active class is rendered just like a class, but with heavy lines usually including its

name, attributes and operations as shown below.

Component:

Component is a physical and replaceable part of a system that

conforms to and provides the realization of a set of interfaces.Graphically, a

component is rendered as a rectangle with tabs, usually including only its name, as

shown below.

39

Place Order

Event

Management

Suspend()Flush()


40/64

orderform.java

Node:

A Node is a physical element that exists at run time

and represents a computational resource, generally having at least some memory

and often, processing capability. Graphically, a node is rendered as a cube, usually

including only its name, as shown below.

server

Behavioral Things:

Behavioral Things are the dynamic parts of UML

models. These are the verbs of a model, representing behavior over time and space.

Interaction:

An interaction is a behavior that comprises a set of

messages exchanged among a set of objects within a particular context to

accomplish a specific purpose. Graphically, a message is rendered as a direct line,

almost always including the name if its operation, as shown below.

Display

40


41/64

State Machine:

A state machine is a behavior that specifies the sequence of

states an object or an interaction goes through during its lifetime on response to

events, together with its responses to those events. Graphically, a state is rendered

as rounded rectangle usually including its name and its sub-states, if any, as shown

below.

Grouping Things:

Grouping things are the organizational parts of the UML

models. These are the boxes into which a model can be decomposed.

Package:

A package is a general-purpose mechanism for organizing

elements into groups.

Business Rules

An notational Things:

An notational things are the explanatory parts of the UML

models.

Note: A note is simply a symbol for rendering constraints

and comments attached to an element or a collection of elements. Graphically a

note is rendered as a rectangle with dog-eared corner together, with a textual or

graphical comment, as shown below.

41

Waiting


42/64

Business Rules

RELATIONSHIPS IN THE UML:

There are four kinds of relationships in the UML:

1. Dependency

2. Association

3. Generalization

4. Realization

CLASS DIAGRAMS:

Class diagrams are the most common diagrams found in

modeling object-oriented systems. A class diagram shows a set of classes, interfaces, and

collaborations and their relationships. Graphically, a class diagram is a collection of vertices

and arcs.Contents:

Class Diagrams commonly contain the following things:

Classes

Interfaces

Collaborations

Dependency, generalization and association relationships.

42


43/64

USE CASES:

Use Case diagrams are one of the five diagrams in the UML

for modeling the dynamic aspects of systems (activity diagrams, sequence

diagrams, state chart diagrams and collaboration diagrams are the four other kinds

of diagrams in the UML for modeling the dynamic aspects of systems). Use Case

diagrams are central to modeling the behavior of the system, a sub-system, or a

class. Each one shows a set of use cases and actors and relationships.

Common Properties:

A Use Case diagram is just a special kind of diagram and

shares the same common properties, as do all other diagrams- a name and

graphical contents that are a projection into the model. What distinguishes a use

case diagram from all other kinds of diagrams is its particular content.

Contents

Use Case diagrams commonly contain:

Use Cases

Actors

Dependency, generalization, and association relationships

Like all other diagrams, use case diagrams may contain

notes and constraints. Use Case diagrams may also contain packages, which are

used to group elements of your model into larger chunks. Occasionally, you will

want to place instances of use cases in your diagrams, as well, especially when you

want to visualize a specific executing system.

43


44/64

INTERACTION DIAGRAMS:

An Interaction diagram shows an interaction, consisting of a

set of objects and their relationships, including the messages that may be

dispatched among them. Interaction diagrams are used for modeling the dynamic

aspects of the system. A sequence diagram is an interaction diagram that

emphasizes the time ordering of the messages. Graphically, a sequence diagram is

a table that shows objects arranged along the X-axis and messages, ordered in

increasing time, along the Y-axis and messages, ordered in increasing time, along

the Y-axis.

Contents:

Interaction diagrams commonly contain:

Objects

Links

Messages

Like all other diagrams, interaction diagrams may contain

notes and constraints.

SEQUENCE DIAGRAMS:

A sequence diagram is an interaction diagram that

emphasizes the time ordering of the messages. Graphically, a sequence diagram is

a table that shows objects arranged along the X-axis and messages, ordered in

increasing time, along the Y-axis.Typically you place the object that initiates the

interaction at the left, and increasingly more sub-routine objects to the right. Next,

you place the messages that these objects send and receive along the Y-axis, in

order of increasing time from top to the bottom. This gives the reader a clear visual

cue to the flow of control over time.

Sequence diagrams have two interesting features:

44


45/64

1. There is the object lifeline. An object lifeline is the vertical dashed line that

represents the existence of an object over a period of time. Most objects

that appear in the interaction diagrams will be in existence for the duration

of the interaction, so these objects are all aligned at the top of the diagram,

with their lifelines drawn from the top of the diagram to the bottom.

2. There is a focus of the control. The focus of control is tall, thin rectangle that

shows the period of time during which an object is performing an action, either

directly or through the subordinate procedure. The top of the rectangle is

aligns with the action; the bottom is aligned with its completion.

ACTIVITY DIAGRAM:

An Activity Diagram is essentially a flow chart showing

flow of control from activity to activity. They are used to model the dynamic

aspects of as system. They can also be used to model the flow of an object as it

moves from state to state at different points in the flow of control.

An activity is an ongoing non-atomic execution with in a

state machine. Activities ultimately result in some action, which is made up of

executable atomic computations that result in a change of state of distinguishes ause case diagram from all other kinds of diagrams is its particular content.

Contents:

Use case diagrams commonly contain:

Use cases

Actors

Dependency, generalizations, and association relationships

45


46/64

Like all other diagrams use case diagrams may

contain notes and constraints Use case diagrams may also contain packages,

which are used to group elements of your model into larger chunks. Occasionally

you will want to place instances of use cases of your diagrams, as well especially

when you want to visualize a specific executing system.

INTERACTION DIAGRAMS:

An interaction diagram shows an interaction,

consisting of a set of objects and their relationships, including the messages

that may be dispatched among them.

A sequence diagram is an interaction diagram that

emphasizes the time ordering of messages. Graphically, a sequence diagram is a

table that shows objects along the X-Axis and messages along the Y-Axis.

Contents:

Interaction diagrams commonly contains:

Objects

Links

Messages

Like all other diagrams, interaction diagrams may

contain notes and constraints.

STATE CHART DIAGRAMS:

A state chart diagram shows a state machine. State

chart diagrams are used to model the dynamic aspects of the system. For the

most part this involves modeling the behavior of the reactive objects. A

reactive object is one whose behavior is best characterized by its response to

events dispatched from outside its context. A reactive object has a clear lifeline

whose current behavior is affected by its past.

46


47/64

8.UML DIAGRAMS:

8.1. Use case Diagrams

47

Category

Management

Product

Management

Order

Management

Email

Templates

Preferences &

Variables

User

Management

Shipping

Companies

Countries

Administrator


48/64

Use Case for Administrator

48

Registration

Change

Passwd

Change

Profile

Product List

Cart

Management

My Orders

Contact

About Us

Normal User


49/64

Use Case for Normal User

49


50/64

Elaborated diagram for: Users

50

Login

Screen

ProductChange

User

My orders

EnterEmail ID

CategoriesAssign the

Task

Select anorder

Enter

password

Update the

changes

Autenticatelog name

Add Items

to cart

Store Buy now

Get thestatus

Display

Authenticate

password

Provide therequired

privileges to

access


51/64

Elaborated diagram for: Administrators

51

Login

ScreenProductsCategory

Managemen User

Management

Enter

Email ID DisplayList

Display list

Add new

user Info

Enter

password

Create New

Category

Autenticatelog name

Create new

Product

StoreStore

Prepareuser info

Authenticate

password

Provide therequired

privileges to

access

Orders

Process the

order

Changethe status

Store

Preference

Select the

page

Edit theproperties

Save


52/64

Class collaboration

Users, User assigned PCs and PC inventory type collaboration

52

Category

-nCategoryID : int

- nProductID : int

- nOrder : int

User Master

- txtEmailAddress:

varchar

- txtPassword : Varchar

- txtName :Varchar

-txtAddr : text

-txtReference : Varchar

-bSendPromotion:tinyint

-bNeverSendMail:tinyint

-dblCredit :double

-tsRegTime :timestamp

Products

Product-ID :

Number

CategoryID :Varchar

Product Name :

Varchar

Product Description :

VarcharOrder

- nID : int

- txtEmailAddress : varchar

- tsChangeTime : timestamp

- tsDate : timestamp

- nOrderState : int- dblTotal : double

- dblProcessingFees : double

- dblShippingCharges: double

- dblGrandTotal : double

- dblPaid : double

- txtRemarks : text

- txtTracking : text

- txtTrackingCompany: text

- txtTrackingURL : text

Shipping Companies

nID :int

txtName : varchar

txtURL : text

txtTrackingURL: text


53/64

Sequence diagram for User Management:

53

Login screen Login Master Login screen Controller

Login

FormEnter the

Email ID

Enter PasswordConnectdb

DB Check

Admin Page

UserAdminPage

Maintenance

Log as

AdminSelect User

Management

option

Delete

Create Logout

User

Edit User

Details

Sign Out


54/64

Sequence diagram for User Orders:

Sequence diagram for Order Management:

54

AdminPageOrders

Login()

Redirect()Display

Ship()

OrderDetails

OrderProces

s()

Shipment

Deliver()

CategoryMaster

ProductMaster Cart

DisplayList()

SelectCatego

ry()

Selectproduct

()

PlaceOrder()

ProductList

AddtoCart()

Order

Complete

TaskCheck()

CreditCard

ShippingCompany


55/64

TEST CASES:

Test Case

No.

Input Expected Behavior Observed

Behavior

Status

P=PASSEDF=FAILED

1 Typed the

http://localhost:8000/E

zeeMerchant

The application

should be launched

and show the initial

Welcome page.

-do-

P

2 Sign in link is clicked This displays the

login page

-do- P

3 The login and

Password for the user

module

Displays the My

Account Page

-do- P

4 The login and

password for the hr is

entered wrongly

Display

authentication

failure page

-do- P

5 Clicked on the change

profile

Change the Old

Password to new

Password

-do- P

6 Clicked on the My

Orders

Displays the status

of Payment

pending, etc.

-do- P

7 Sign in for

administrator

Module

Gives the

information of

List.jsp

-do- P

8 Clicked on Users

Option

Gives the workdays

setup for the

company

-do- P

9 Clicked the Categories Add New Category

or Modify Category

-do- P

10 Clicks on the Products List will display on

existing products.

-do- P

55
http://localhost:8000/EzeeMerchanthttp://localhost:8000/EzeeMerchanthttp://localhost:8000/EzeeMerchanthttp://localhost:8000/EzeeMerchant


56/64


57/64

USER,ADMIN,LOGIN PAGE

57


58/64

REGISTRATION PAGE

58


59/64

USER LOGIN

59


60/64

10. TESTING:Testing is the major quality measure employed during the software

engineering development. Its basic function is to detect error in the software. Testing is necessary for

the proper functioning of the system. Testing has to be done at four levels

10.1 Unit Testing:

Unit testing focuses verification effort on the smallest unit of the software ,

design the module. Here, using the detail design as a guide ,important control paths are tested to

uncover errors within the boundary of the module. Unit testing is always white-box oriented, and the

step can be conducted in parallel for multiple modules.

10.2 Integration Testing:

Integration testing is a systematic technique for constructing the program

structure while at the same time conducting tests to uncover errors , associated with interfacing .The

objective is to take the unit tested modules and build program structure that has been directed by the

design.

10.3 Validation Testing:

Validation testing demonstrates the traces the requirements of the software

This can be achieved through a series of black box tests. System Testing is actually a series of

different tests whose primary purpose is to fully exercise the computer-based system .Although

each test has a different purpose, all works should verify that all system elements have been properly

integrated and perform allocated functions. The various tests include recovery testing , stress testing

and perform testing.

60


61/64

11. MAINTAINACE AND IMPLEMENTATION:

11.1 Corrective maintenance

This acts to correct errors that are uncovered after the software is in use.

11.2 Adaptive Maintenance

This is applied when changes is the external environment

Precipitate modifications to software.

11.3 Preventive maintenance

This improves future maintainability and reliability and provides basis for future

Enhancements.

61


62/64

12. CONCLUSION:

This application helps the customers to shop different items online. The

Shopper can see all the orders and the order details and he can decide whether the order has to be

confirmed or rejected. He can track the order status and he can send the mails to the customers. The

users can flexibly shop the items using user-friendly screens and these screens can be dynamically

changed. Finally this application helps both the customers and the shopper to automate their

activities using a software application and maintain customer data very effectively.

62


63/64

12. GLOSSARY:

API ---- Application Programming Interface.

CGI ---- Common Gateway Interface.

DHTML ---- Dynamic Hyper Text Markup Language.

GUI ---- Graphical User Interface .

HTML ---- Hyper Text Markup Language.

HTTP---- HyperText Transfer Protocol.

J2EE ---- Java 2 Enterprise Edition.

JDBC ---- Java DataBase Connectivity.

JSP ---- Java Server Pages.

SQL ---- Structured Query Language.

URL ---- Uniform Resource Locator.

XML ---- Extensible Markup Language.

63


64/64

13. REFERENCES

1. Deitel and Nieto , Internet and World Wide Web how to program.

2. Ian Somerville, Principles of Software Engineering ,4 Edition .

3. Roger S. Pressman ,Software Engineering A Practitioners Approach .

4. IEEE, IEEE Software Standards , IEEE Press ,1989 .

5. Patrick Naughton and Herbert Schildt , Complete Reference Java 2 , 3 Edition ,Tata McGraw Hill ,1999.

6. Er. V.K.Jain , Programming Java Server Pages & Servlets.

Date post:	05-Apr-2018
Category:	Documents
Upload:	sravanti-phanindra
View:	215 times
Download:	0 times

EZ Merchant Online Shopping

Documents