Online shopping ecommerce java project

PROJECT
ON
“Online Shopping Java Project”
Visit:
http://bit.ly/onlineshopping_javaproject
For Complete Project
This is sample report Original
report is of 150 pages

• INTRODUCTION
• DESCRIPTION
• OBJECTIVE

Visit:

INTRODUCTION
The emart is the part of the sample application that
provides customers with online shopping. Through a Web
browser, a customer can browse the catalog, place items
to purchase into a virtual shopping cart, create and
sign in to a user account, and purchase the shopping
cart contents by placing an order with a credit card.
By integrating information and improving processes,
emart will help improve enterprise-wide decision
support and operational efficiency. Improved efficiency
translates into:
• More resources to support the enterprise .
• Improved customer service
• Web-based and more user friendly interfaces to buyers .
An extremely powerful marketing tool, emart’s ability to suggestively
sell alternate and complementary products; e.g. if a customer selects
the "standard" version of a product, you can recommend that they also
consider the "pro" version or if your customer chooses a pair of pants,
you can suggest that they also consider a belt and socks. Simply
specify related product skus and optional text in a product’s definition
in your Merchant Administrator, and PDG Shopping Cart will up-sell
or recommend related products to your customers automatically

DESCRIPTION OF PROJECT
The category screen shows all of the products available for a particular
category.
The product screen shows all of the items in a particular product. Product
screen’s right column of the list shows the price of the item, and includes a
link labelled Add to Cart. This link, which also appears on screen for the
corresponding item, allows the customer to add the item to the cart without
looking at the item details
The item screen shows detailed information about an individual item for
sale .
The Add to Cart link, when clicked, adds an order for the item to the
shopping cart, and then shows the shopping cart contents
The cart screen lists the items currently in the cart, allows the customer to
change the quantity of each item ordered, and shows a title. It also includes
a link to remove the item from the cart, and a link Proceed to Checkout
which, when clicked, shows the order information screen if the user is signed
on. If the user is not signed on, the signon screen is shown instead.
The signon screen allows an existing customer to sign in as an existing user,
and a new customer to create an account. An existing customer enters a
user name and password, and the application displays the Order Information
screen shown in . A new customer enters a user name and password and
clicks the button Create New Account. The application creates a user with
the requested password. If user creation succeeds, the application displays
the Account Information screen.
The account information screen, shown in collects information about a new
customer, including contact information, a credit card, and personal
preferences. This is also the screen displayed whenever the customer clicks
the Account link at the top right corner of the screen (beneath the Search
box). Clicking the Update button directs the browser to a page that
summarizes the information entered.
The Order Information screen allows the user to enter billing and shipping
address. Default values for the addresses come from the contact information
for the currently signed-in customer. This information is transmitted to the
application when the user clicks Submit. The application creates a new

order, sends it to the order processing center, and displays the Order
Complete screen.
The Order Complete screen verifies to the user that the order has been
placed. The screen includes the order number
Key Strengths
A steady stream of innovative features born of a
deep understanding of online shopping as a social
experience. Recent enhancements and additions
include:
g The beginnings of social networking
capabilities, with customers able to connect
with and keep tabs on a network of friends
g The ability for users to “tag” products by
assigning them keywords
g Personal blogs for customers
g Product discussion boards
g The ability to upload images as visual reviews
and product commentary

Visit:
OBJECTIVES
Our Objective
Our objective was to look at online retail from a customer’s point-of-view
and determine which
of the biggest US-based ecommerce sites was providing the best customer
experience.
A secondary aim was to zero in on key trends and identify opportunities for
high-impact

customer experience improvements.
Our Approach
We examined the entire experience. Unlike some studies that focus only
on browsing,
we looked at the entire experience from the first moment on the site through
selection,
purchase, shipping and returns.
We combined objective measurement with expert subjective
analysis. Metrics
have a strong appeal, but in something that involves as many intangibles as
the customer
experience measurement can only take you so far. With this in mind, we
split our analysis
between straightforward objective grading and the expert opinions of our
panelists. (In
poker terms, think of a good objective score as a table stakes and a good
subjective
score as a hand that could win you the game.)
We analyzed a large pool of sites defined by a third party.
Objective evaluation criterion
the interface must use language that is easily understood by target users .
the interface must use graphics or icons that are easily understood by target
users .
the text must be easy to read .
navigation elements must be easily recognized and understood .
product categories must be well thought out, and intuitive .
there must be effective decision support tools to guide you through the
exploration
process .

the product must be clearly displayed with appropriate visualization tools .
If customer I have been to the site before, it must remember me and
personalize customer’s
subsequent experience?
it is easy to keep track of things customer want to buy .
customer need to register in order to make a purchase or access certain
content .
it does have a history of customer’s transactions that he can easily access .

System Development Methodology
System Development Life Cycle
PHASES:
1.2.1 Initiation Phase
The initiation of a system (or project) begins when a business need or
opportunity is identified. A Project Manager should be appointed to manage the
project. This business need is documented in a Concept Proposal. After the Concept
Proposal is approved, the System Concept Development Phase begins.
1.2.2 System Concept Development Phase
Once a business need is approved, the approaches for accomplishing the
concept are reviewed for feasibility and appropriateness. The Systems Boundary
Document identifies the scope of the system and requires Senior Official approval
and funding before beginning the Planning Phase.
1.2.3 Planning Phase
The concept is further developed to describe how the business will operate once the
approved system is implemented, and to assess how the system will impact
employee and customer privacy. To ensure the products and /or services provide
the required capability on-time and within budget, project resources, activities,
schedules, tools, and reviews are defined. Additionally, security certification and
accreditation activities begin with the identification of system security requirements
and the completion of a high level vulnerability assessment.
1.2.4 Requirements Analysis Phase
Functional user requirements are formally defined and delineate the
requirements in terms of data, system performance, security, and
maintainability requirements for the system. All requirements are defined to a
level of detail sufficient for

systems design to proceed. All requirements need to be measurable and testable
and relate to the business need or opportunity identified in the Initiation Phase.
1.2.5 Design Phase
The physical characteristics of the system are designed during this phase. The
operating environment is established, major subsystems and their inputs and
outputs are defined, and processes are allocated to resources. Everything requiring
user input or approval must be documented and reviewed by the user. The physical
characteristics of the system are specified and a detailed design is prepared.
Subsystems identified during design are used to create a detailed structure of the
system. Each subsystem is partitioned into one or more design units or modules.
Detailed logic specifications are prepared for each software module.
1.2.6 Development Phase
The detailed specifications produced during the design phase are translated into
hardware, communications, and executable software. Software shall be unit tested,
integrated, and retested in a systematic manner. Hardware is assembled and
tested.
1.2.7 Integration and Test Phase
The various components of the system are integrated and systematically tested.
The user tests the system to ensure that the functional requirements, as defined in
the functional requirements document, are satisfied by the developed or modified
system. Prior to installing and operating the system in a production environment,
the system must undergo certification and accreditation activities.
1.2.8 Implementation Phase
The system or system modifications are installed and made operational in a
production environment. The phase is initiated after the system has been tested

and accepted by the user. This phase continues until the system is operating in
production in accordance with the defined user requirements.
1.2.9 Operations and Maintenance Phase
The system operation is ongoing. The system is monitored for continued
performance in accordance with user requirements, and needed system
modifications are incorporated. The operational system is periodically assessed
through In-Process Reviews to determine how the system can be made more
efficient and effective. Operations continue as long as the system can be effectively
adapted to respond to an organization’s needs. When modifications or changes are
identified as necessary, the system may reenter the planning phase.
1.2.10 Disposition Phase
The disposition activities ensure the orderly termination of the system and preserve
the vital information about the system so that some or all of the information may
be reactivated in the future if necessary. Particular emphasis is given to proper
preservation of the data processed by the system, so that the data is effectively
migrated to another system or archived in accordance with applicable records
management regulations and policies, for potential future access.
SDLC Objectives
This guide was developed to disseminate proven practices to system developers,
project managers, program/account analysts and system owners/users throughout
the DOJ. The specific objectives expected include the following:
• To reduce the risk of project failure
• To consider system and data requirements throughout the entire life of the
system
• To identify technical and management issues early

• To disclose all life cycle costs to guide business decisions
• To foster realistic expectations of what the systems will and will not provide
• To provide information to better balance programmatic, technical,
management, and cost aspects of proposed system development or
modification
• To encourage periodic evaluations to identify systems that are no longer
effective
• To measure progress and status for effective corrective action
• To support effective resource management and budget planning
• To consider meeting current and future business requirements
Key Principles
This guidance document refines traditional information system life cycle
management approaches to reflect the principles outlined in the following
subsections. These are the foundations for life cycle management.
Life Cycle Management Should be used to Ensure a Structured Approach to
Information Systems Development, Maintenance, and Operation
This SDLC describes an overall structured approach to information
management. Primary emphasis is placed on the information and systems decisions
to be made and the proper timing of decisions. The manual provides a flexible
framework for approaching a variety of systems projects. The framework enables
system developers, project managers, program/account analysts, and system
owners/users to combine activities, processes, and products, as appropriate, and to
select the tools and methodologies best suited to the unique needs of each project.
Support the use of an Integrated Product Team
The establishment of an Integrated Product Team (IPT) can aid in the success of
a project. An IPT is a multidisciplinary group of people who support the Project
Manager in the planning, execution, delivery and implementation of life cycle

decisions for the project. The IPT is composed of qualified empowered
individuals
Visit:

from all appropriate functional disciplines that have a stake in the success of the
project. Working together in a proactive, open communication, team oriented
environment can aid in building a successful project and providing decision makers
with the necessary information to make the right decisions at the right time.
Each System Project must have a Program Sponsor
To help ensure effective planning, management, and commitment to information
systems, each project must have a clearly identified program sponsor. The program
sponsor serves in a leadership role, providing guidance to the project team and
securing, from senior management, the required reviews and approvals at specific
points in the life cycle. An approval from senior management is required after the
completion of the first seven of the SDLC phases, annually during Operations and
Maintenance Phase and six-months after the Disposition Phase. Senior management
approval authority may be varied based on dollar value, visibility level,
congressional interests or a combination of these.
The program sponsor is responsible for identifying who will be responsible for
formally accepting the delivered system at the end of the Implementation Phase.
A Single Project Manager must be Selected for Each System Project
The Project Manager has responsibility for the success of the project and
works through a project team and other supporting organization structures, such as
working groups or user groups, to accomplish the objectives of the project.
Regardless of organizational affiliation, the Project Manager is accountable and
responsible for ensuring that project activities and decisions consider the needs of
all organizations that will be affected by the system. The Project Manager develops
a project charter to define and clearly identify the lines of authority between and
within the agency’s executive management, program sponsor, (user/customer),
and developer for purposes of management and oversight.
A Comprehensive Project Management Plan is Required for Each System
Project

The project management plan is a pivotal element in the successful solution
of an information management requirement. The project management plan must
describe how each life cycle phase will be accomplished to suit the specific
characteristics of the project. The project management plan is a vehicle for
documenting the project scope, tasks, schedule, allocated resources, and
interrelationships with other projects. The plan is used to provide direction to the
many activities of the life cycle and must be refined and expanded throughout the
life cycle.
Specific Individuals Must be Assigned to Perform Key Roles Throughout the
Life Cycle
Certain roles are considered vital to a successful system project and at least
one individual must be designated as responsible for each key role. Assignments
may be made on a full- or part-time basis as appropriate. Key roles include
program/functional management, quality assurance, security, telecommunications
management, data administration, database administration, logistics, financial,
systems engineering, test and evaluation, contracts management, and
configuration management. For most projects, more than one individual should
represent the actual or potential users of the system (that is, program staff) and
should be designated by the Program Manager of the program and organization

REQUIRMENTS ANALYSYS
• PROBLEM FORMULATION
• PROJECT CATEGORY
• PLATEFORM SELECTION
• SOFTWARE AND
HARDWARE TOOLS
SYSTEM STUDY AND
PROBLEM
FORMULATION

SYSTEM STUDY AND PROBLEM FORMULATION
THE EXISTING SYSTEM
The existing system work manually. The existing system has got lot of
intricacies within itself and need lot of human effort and paper works. All above the
data need to be maintained on ledgers and maintaining this is a tedious and risky
process. As the transactions increases, so the data too. So the task of maintaining
them increases exponentially. To view a data may need lot of paper to be searched.
Some of the negative aspects of the existing system are as follows:
1) Course of action is time consuming. Wherever a need for search arises, the
process evolves search through paper records.
2) Readability of records is constrained. All the records may not be handled or
written by the same person. So the format and style of records differ and
hence it is difficult to understand.
3) Paper records are easily damaged in course of time. The life time of paper
record is unreliable less that it easily gets spoiled.
4) Expenditure is high. Manual system needs added man power.
5) Prone to corruption by unauthorized users. Securing of manual system is not
fully guaranteed. Inaccuracy can be expected. Data can get easily scratched.
6) Techniques used are more complicated. Proper techniques are not exposed,
so the functioning is intricate.
To overcome these, the proposed system has been suggested.
IDENTIFICATION OF NEED

In the world we are growing for globalization day by day with the development in IT
resources and advancement, by using latest technologies every organization wants
to beat its competitors and want to grow. Enterprise Resourceful Planning is the
need of today’s organization. Survival on manual system is difficult so, that’s why
organization of the corporate world wants to computerize their departments. The
modules should be complete database driven and interactive that should provide
the proper information about the Placement and Training Organization.
Success of any system depends up to a large extent on how accurately a
problem is defined, thoroughly investigated and properly carried out to the choice
of solution. Analysis is the only phase in which the requirements for the new system
are identified. System analysis is a detailed study of the various operations
performed by a system and their relationship within and outside of the system. The
question is: what must be done to solve the problem? One aspect of analysis is
defining the boundaries of the system and determining whether or not a candidate
system should consider other related system. During analysis data are collected on
the available files, decision points and transactions handled by the parent system.
Data flow diagram, interviews, onsite observations, questionnaires are used as a
logical system model and tools to perform the analysis.
An analyst is responsible for performing following tasks:
 Gathered all facts about the present system from the employees.
 Studied strength and weakness of the current system.
 Determined “what” must be done to solve the problem.
 Prepared a functional specifications document.
In order to reduce the time, there is a need for computerized system
that cans retrieve data, insert data, update existing data or delete existing data.
These modules are developed wit the aim of reducing time, reducing manpower,
reducing cost so that the records can be easily maintained. The volume of work and

complexity are increasing year by year. This system reduces complexity and
workload.
PRELIMINARY INVESTIGATION
A request to take assistance from information system can be made for
many reasons, but in each case some one in the organization initiate the request.
When the request is made, the first system activity the preliminary investigation
begins. This activity has three parts:
 Request clarification
 Feasible Study
 Request approval
Many requests from employees and users in the organization are not
clearly defined. Therefore, it becomes necessary that project request must be
examined and clarified properly before considering systems investigation.
The feasibility study is carried out by a small group of people who are familiar
with information system techniques, understand the parts of the business or

Visit:
organization that will be involved or affected by the project, and are skilled in the
system analysis and design process.
• Request Approval:
It is not necessary that all request projects are desirable or feasible. Some
organizations receive so many projects request from employees that only a few of
them can be purchased. However, those projects that are feasible and desirable
should be put into a schedule.
In some cases, development can start immediately, although usually system
staff members are busy on other ongoing projects. When such situation arises,

management decides which projects are more urgent and schedule them
accordingly. After a project request is approved, its cost, priority, completion time
and personal requirements are estimated and used to determine where to add it to
any existing project list. Later on, when the other projects have been completed,
the proposed application development can be initiated.
Analysis is a process of studying a problem and to find the best solution
to that problem. System analysis gives us the target for the design and the
implementation. Analysis is one phase, which is important phase for system
development lie cycle. System development is a problem solving techniques.
Analysis involves interviewing the client and the user. Three people and the existing
documents about the current mode of operation are the basic source of information
for the analyst.
Analysis is the process of studying a problem to find the best solution to that
problem. System analysis gives us the target for the design and the
implementation. Analysis is one phase of the very important phase of the system
development life cycle. System development is a problem solving techniques.
Analyses involve interviewing the client and the user. These people and the existing
document about the current mode of operation are the basic source of information
for the analyst.
Human Resource Department of the organization controls the manpower planning
by recording manpower requirements, grade, job specifications and presently
vacancies and strength. It maintains the candidate’s databank for the respective
post.

Visit:
SOFTWARE ENGINEERING PARADIGM
Computer Aided Software Engineering can be as simple as a single tool that support
a specific software engineering activity or as complex as a complete “environment “
that encompasses tools, a database, people, hardware, a network, operating

system, standards, and myriad other components. Each building block forms a
foundation for the next, with tools sitting as the top of the heap. It is interesting to
note that the foundation for effective CASE environment has relatively little to do
for software engineering tools themselves. Rather, successful environments
appropriate hardware and systems software. In addition, the environment
architecture must consider the human work patterns that are applied during the
software engineering process.
The environment composed of the hardware platform and system support
(including networking software, software management, and object management
services), the groundwork for CASE. But the CASE environment itself demands
other building blocks. A set of portability services provides a bridge between CASE
tools and their integration framework and the environment architecture. The
integration framework is a collection of specialized programs that enables
individual’s CASE tools to communicate one another, to create a project database,
and to exhibit the same look and feel to the end user (the software engineer).
Portability services allow CASE tools and their integration framework to migrate
across different hardware platforms and operating system with out significant
adaptive maintenance.
The building blocks represent a comprehensive foundation for the integration of
CASE tools. However, most CASE tools in use today have been: constructed using
all these building blocks.
In fact some CASE tools remain “point solution:” That is, a tool is used to assist in a
particular software engineering activity (e.g. analysis modeling) but does not
directly communicate with other tools, is not tied into a project database, is not
part of an integrated CASE environment (l-CASE). Although this situation is not
ideal, a CASE tool can be used quite effectively, even if it is a point solution.

At the low end of the integration spectrum is the individual (point solution) tool.
When individual tools can provide tools provide facilities for data exchange, the
integration level is improved slightly. Such tools produce output in a standard
format that should be compatible with other tools that can read the format. In
some cases, the builder of complementary CASE tools work together to form a
bridge between the tools (e.g. an analysis and design tool that is coupled with a
code generator). Using this approach, the team developed, synergy between the
tools separately. Single source integration occurs when a single CASE tools vendor
integrates a number of different tools and sells them as a package.
Although this approach is quite effective, the closed architecture of most single
source environments precludes easy addition from other vendors.

Visit:
PROJECT
CATEGORY

PROJECT CATEGORY
Category of this project is RDBMS based, n-tier architecture, Distributed
environment project with server-side components.
Project can be categorized in two ways:-
• Local Area Network projects.
• Distributed Projects.
Local Area Network projects are those projects where application has to be
incorporated in the Local area network of the client i.e within its premises only. In
case of LAN, server is not remotely located and client accesses the application
through the network. Here the question of platform independence does not arise
and we can use the technologies like: Visual Basic, Fox pro, D2k or C, C++, etc.
Distributed projects are those projects where application
is remotely situated. In these kinds of projects, application is remotely situated on
to the remote server from where client machine accesses the application. WAN and
Internet is a kind of distributed application where client machine connects to the
remote server and application is downloaded on to the client machine. Here the
question of platform independence arises and we use technologies like Java Servlet,
Java Server Pages, Java Beans, RMI, etc.

SOFTWARE
REQUIRMENT
SPECIFICATION

SOFTWARE REQUIREMENT SPECIFICATION
Software requirement specification (SRS) is the starting point of the software
development activity. Little importance was given to this phase in the early days of
software development. The emphasis was first on coding and then shifted to
design.
As systems grew more complex, it became evident that the goals of the
entire system cannot be easily comprehended. Hence the need for the requirement
analysis phase arose. Now, for large software systems, requirements analysis is
perhaps the most difficult activity and also the most error prone.
Some of the difficulty is due to the scope of this phase. The software project
is initiated by the client’s needs. In the beginning these needs are in the minds of
various people in the client organization. The requirement analyst has to identify
the requirements by talking to these people and understanding their needs. In
situations where the software is to automate a currently manual process, most of
the needs can be understood by observing the current practice.
The SRS is a means of translating the ideas in the minds of the clients (the
input), into formal document (the output of the requirements phase). Thus, the
output of the phase is a set of formally specified requirements, which hopefully are
complete and consistent, while the input has none of these properties.
PLATEFORM
(Technologies/Tools)

Visit:
PLATEFORM (Technology/Tool Selection)

Introduction to Java/.net
Java is a high-level, third-generation programming language like C,
FORTRAN, Perl and many others. It is a platform for distributed computing – a
development and run-time environment that contains built-in support for the World
Wide Web.
History of Java
Java development began at Sun Microsystems in 1991, the same year the
World Wide Web was conceived. Java’s creator, James Gosling did not design java
for the Internet. His Objective was to create a common development environment
for consumer electronic devices which was easily portable from one device to
another. This effort evolved into a language, code named Oak and later renamed
Java that retains much of the syntax and power of c++, but is simpler and more
platform-independent.
Java Features
Some of the important features of Java are as follows:
• Simplicity
• Orientation
• Platform Independence
• Security
• High Performance
• Multi Threading
• Dynamic linking.
• Garbage Collection.

One of the most important features of Java is platform independence, which
makes it famous and suitable language for World Wide Web.
Why Java is Platform Independent?
Java is Platform Independent because of Java Virtual Machine (JVM).
Java Virtual Machine (JVM)
The client application or operating system must have a java byte-code
interpreter to execute byte-code instructions. The interpreter is a part of a larger
program called the JVM. The JVM interprets the byte code into native code and is
available on platforms that support Java.
When the user runs a Java program, it is up to the JVM to
load, possibly verify, and then execute it. The JVM can perform this function from
within a browser or any other container program or directly on top of the operating
system.
When a browser invokes the JVM to run a Java program, the JVM does a
number of things:
• It validates the requested byte-code, verifying that they pass various
formatting and security checks.
• It allocates memory for the incoming java class files and guarantees that
the security of JVM is not violated. This is known as the class loader
module.
• It interprets the byte code instructions found in the class files to execute
the program.

that has released a number of development tools including SQL *PLUS,
PL/SQL that enables faster and easier application development and its
management.
Oracle is the robust Database System, it support very large database.
Moreover Oracle is widely used as back end for client / server applications.
Administrative tools of Oracle help in securing the Data / Information.
Process of creating a J2EE application:
Assembled
Deployed
Enterprise
Bean
(.jar
Component
(.jar
J2EE Application
Server
(.jar
J2EE
Server

Visit:
Software and Hardware Tools

Development Environment:
• Operating System: Windows XP
The system will be built on windows compatible environment. The
application will be web based developed using Java technology.
• Web Server:
BEA’s WebLogic 8.1 Application Server to serve as Servlet/JSP
engine.The system requires WebLogic Application Server for serving the
requests for Servlet.
• Server side Application Software: Java Server Pages (JSP)
• Business Logic Software: Java Beans. (JB)
• Client Side Application Software: Java Script, HTML
• Data Base: Oracle 8i
The system requires Oracle as a database; however the system will be
ODBC complaint to work on any standard database.
• Client Browsers:
Internet Explorer 5.0 or Netscape Navigator 4.7
The system requires Internet Explorer or Netscape Navigator browser for
client side.
• Dream Weaver 8.0
The system will be developed with Java Technologies using J2SE (JDK
and JRE). Dream Weaver 8.0/ Front Page 2003 as HTML editor.
Hardware & Software Requirements

Hardware requirement
Main Processor Pentium IV
Hard-disk Capaity 8 G.B
RAM 256 MB
Clock Speed 2.8 Hz
Floppy Drive : 1.44MB
Keyboard 104 Key
Monitor V.G.A
4.2 Software specification
Software Requirement
Operating System Window XP
Backend tool Oracle 8i
Front-end tool Java

Online shopping ecommerce java project

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Online shopping ecommerce java project (20)

More from Tutorial Learners (7)

Recently uploaded (20)

Online shopping ecommerce java project