1.

Introduction
1.1 Objective&scope of the project:
The main objective of the online buying is to enable a customer to buy the
products through the net. Many people choose to conduct shopping online because of
the convenience.The purpose of the document is to describe the requirements for an
online bookshop, also describes the interface for the system. This document is the
only one that describes the requirements of the system.
A web based application for online book shop. The main objective of
thesystem is to guide the users how to get the books from the webby selecting one
from no of books it gives the detail description of book in detail. Performance is quite
excellent and user understandable.

Object oriented software engineering Bernd Bruegge, Allen H. Dutoit

Web technology and design C. Xavier

The present system does not have efficient search operations, low privileges

for administrators and even some book stores are lack in security optionsThe
proposed system provides efficient search operations by author, category, title search,
efficient options as unregister user cannot logged into registered users or
administrators, provide several options for administrators to perform efficient
operations.

1.2 Background Details:

The manual system gives us very less security for saving data and some data
may be lost due to miss-management.The System not providing any on line interface ,so
the paper work is taking a lot of time to maintain and communicate, which is hence very
laborious and expensive.This system is not also providing any report generation facility
for user specific requirements.The system is not also providing any online facility to
reserve their bookings for cargo shipments and also for passenger voyages.This system
has no facilities to store different stock details, maintenance details and bill details which

can be accessed instantly as per requirement.The system is not maintaining an user

hierarchy. The system is giving only less memory usage for the users.
The development of this new system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach.This
system maintains users personal, address, and contact details.User friendliness

is

provided in the application with various controls provided by system rich user
interface.This system makes the overall project management much easier and
flexible.Various classes have been used for maintain the details of all the users

and

catalog. Authentication is provided for this application only registered users can
access.The users information files can be stored in Centralized database which can be
maintained by the system.This system is providing more memory for the users to
maintain data. This system is providing accessibility control to data with respect to
users.This system is providing on line facilities to book both cargo ships and passenger
ships for voyages.This is providing facilities to store different type of administrative data
through online like ship details, ship parts stock, employee details, ship reservation
details, purchase details and different pay bill details etc.

1.3 Definition of the Problem:

To develop an online comprehensive book shop, to engage public to meet their
needs, this project is designed. The purpose of the document is to describe the
requirements for an online bookshop. It also describes the interface for the system.
In contrast, online shopping helps consumers avoid these disadvantages.
With online shopping, a person logs onto the Internet, visits the store's website,
andchooses the items she desires. The items are held in a virtual shopping cart until she is
ready to make her purchase.

2. System Requirements Specification

2.1 Functional Requirements:
Particular requirements mainly used directly in system development. This functional
requirement also explains the interaction between system and its environment.
Functional requirements are divided into two categories.

User requirements

Administrator requirements

User requirements:

To view the books by author, by title or search by categories.

The books viewed can be added to the shopping cart of the user.

Display the contents of the cart when required and manage the cart.

Customer should register at the website to buy books at book buzz.

Users are allowed to change their password

Administrator Requirements:

Managing books and categories.

Managing users.

View feedback provided by the users.

View the history of the orders.

2.2 Non Functional Requirements:

Particular requirements used indirectly in the system development.

1. User interfaces and human factor:

An interface has been provided to client that is compatible with windows
environment and is designed to be friendly

2. Documentation:
Design level Document is used as a guide for developers and is given with the
system to the client. Implementation level document may also be prepared to have better
resolution when any conflict occurs.

3. Performance characteristics:
Request should be processed within 25 seconds.
Providing the 24*7 service availability to the customers

4. Error handling and extreme conditions:

In case of user error, the system should display a meaningful error message to the
user, such that the user can correct his error.
5. Quality issues:
Data provided by the system is reliable as it directly interacts with user.
6. System modification:
The present system can be modified such that extra constraints can be added
toimprove its performance

7. Physical environment:
The present system can be implemented in substitution to all
metrological stations situatedacross the nation.

8. Security issues:
Administrator login details are not visible to second person

9. Resource issues:
4

The database should not become corrupted in case of system crash or power
failure.

3. Requirement Analysis Document

3.1 System Models:
3.1.1 Identifying Actors:
A scenario is an instance of a use case describing a concrete set of
actions. Scenario is an example describing all common cases.
We describe a scenario using a template with three fields
1. Scenario name
2. Participating Actor
3. Flow of Event

Use case name

Participating actor
Entry condition
Flow of events

Administrator
Administrator, database
Administrator should be logged in.
1. He can change his password.
2.He can manage registered users
3. He can search books by author or title or
edition.
4.He can add or delete books
5.He can update price of books
Manage book buzz website

Exit condition

3.2 Use casemodel:

3.2.1 Identifying Use Cases:

5

It is used in requirements engineering and analysis. It is used to specify

The functionality of system is defined in terms of actors and use cases. The actor is an
external entity that interacts with the system.
Use case is a sequence of events. It explains all possibleactions between actor
and system. The actors are outside of the boundary and usecases are inside this
boundary.

3.2.2 Use case Diagrams:

Use case Diagram For Adminstrator:

registrations

login

select

cust

update

admin

pay cash

delivery report

logout

Fig: 3.1: Use Case Diagram for Online Book Shop

Use Case Diagram For Customer:

type of book

select author
cust

place in cart

select book from cart

Fig: Use case Diagram for Customer

3.3Object Model
3.3.1 Data Dictionary:

S No

Table name Attribute

Name

Data type

Visibility

admin

Varchar2(30)

Public

Aname

Syntax

Create table admin(aname

varchar2(30)primary

key,

pass varchar2(20));

customer

Pwd

Varchar2(20)

Private

Fname

Varchar2(30)

Public

Create

table

cust

(fname varchar2(30),lname
varchar2(20),uname
varchar2(20),pswd
lname

Varchar2(20)

Public

varchar2(10),address
varchar2(50),eid

uname

Varchar2(20)

Public

varchar2(20),mob
integer(15),gender

pswd

Varchar2(10)

private

varchar2(20),city
varchar2(20));

address

Varchar2(50)

Public

eid

Varchar2(20)

Public

mob

Integer(15)

Public

gender

Varchar2(5)

Public

books

city

Varchar2(20)

Public

Bname

Varchar2(30)

Public

Create table
Books(bname

aname

Varchar2(30)

Public

varchar2(30),aname
varchar2(30),edition

edition

Varchar2(30)

Public

varchar2(30),price
varchar2(30),summary

price

Varchar2(30)

Public

Summary

Varchar2(30)

Public

varchar2(20));

3.3.2 Class Diagrams:

The class diagram explains the structure of a system in terms ofClass, attributes
and their operations. The class is nothing but the abstract representation of a system. It
explains the system in terms of set of objects the object is nothing but the instance of a
class. There are created dynamically once completion of the task the object is destroyed.

registrations
cid : string()
cpswd : string
cname : string
caddress : string
phone num : int
checks user details()
accepts registration()

user
uid : string
upswd : string
registers into site()
logs into site()
searches books()
selects books()
log outs()

database
db

payments
uid : int
upswd : string
uaddress : string
draws the amount()

admin
books
author : string
type of book : string
selects type of book()
selects author name()

aid : string
apswd : string
controls website()
logs into site()
checks customer pswd()
maintains books details()

Fig: 3.2: Class Diagram for Online Book Shop

10

3.4Dynamic Models
3.4.1 Sequence Diagrams:
The sequence diagrams mainly used to visualize the communication between the
set of the objects.
Sequence Diagram:

11

:
registrations

: books

: payments

: admin

: cust

: database

1: maintains

2: enter details
3: verify
4: enter user name and password
5: check details
6: valid
7: permint access

8: select type of book

9: display results
10: places in cart
11: payment details

12: pays the amount

13: delivers report

Fig
: 3.3: Sequence diagram for customer

Sequence Diagram for admin:

12

:
registrations

: database

: books

: admin
1: enter details
2: check
3: verify
4: valid
5: add/delete/update
6: perform action

7: display form
8: fill form

9: return updates
10: view orders for bboks
11: get orders
12: return orders list
13: display orders

Fig: Sequence Diagram for admin

3.4.2 Statechart Diagrams:

13

Statechart diagram explains each object different state and transitions. State is
nothing but set of values of an object transition is nothing but future state of an object.

Fig: State Chart Diagram for Online Book Shop

3.4.3 Activity Diagrams:

14

Activity diagram explains internal of set of activities. It is similar to flow chart

except that it contains the synchronization. The synchronization specifies completion of
one activity only the next activity will be started.

home

admin

user

enter user aname

and apwd

enter user
name and pwd

not valid

not valid
valid

valid
see books

display books

add books

select books

update books

display payment
details
pay cash

exit

Fig: 3.6: Activity Diagram for Online Book Shop

4. System Design Document:

15

4.1 Subsystem Decomposition:

This describes the decomposition into subsystems and the responsibilities of
each. This is the main product of system design.

Registration Subsystem:
It looks after registration login details and allows profile viewing.

Communication Subsystem:
The entire system can be decomposed into two subsystems. They are:
Admin subsystem: It is responsible for generation of logins, viewing details,
giving responses to the requests posted by users.
User subsystem: It is responsible for registrations, selecting the book and the
type of book.

admin sub
system

user sub
system

update information

provide information to user

main system

Request for book information

Fig. Subsystem decomposition for Online Book Shop

16

4.2Design Goals:
System designs the transformation of analysis model into a system design
model. During the system design developers defines the design goals of project and
decompose the system into smaller into subsystems that can be realized by individual
teams. Strategic for building system such hardware software are selected.

i.

Portability:
For programs to be dynamically downloaded to all the various types of
platforms that are connected to the Internet, some means of generating portable
executable code is needed .As you will see, the same mechanism that helps
ensure security also helps create portability. Indeed, Javas solution to these two
problems is both elegant and efficient.

ii.

Security:
Every time you that you download a normal program; you are risking
a viral infection. Prior to Java, most users did not download executable
programs frequently, and those who scanned them for viruses prior to execution.
Most users still worried about the possibility of infecting their systems with a
virus. In addition, another type of malicious program exists that must be guarded
against. This type of program can gather private information, such as credit card
numbers, bank account balances, and passwords. Java answers both these
concerns by providing a firewall between a network application and your
computer.

iii.

Robustness:
The multi-platform environment of the Web places extraordinary
demands on a program, because the program must execute reliably in a variety
of systems. The ability to create robust programs was given a high priority in the
design of Java. Java is strictly typed language; it checks your code at compile
time and run time.
Java virtually eliminates the problems of memory management and deallocation, which is completely automatic. In a well-written Java program, all
run time errors can and should be managed by your program.
17

iv.

Memory:
This requires large amount of memory inorder to store all registered
member details.

5. Object Design Document:

5.1Object Design Model:

The entire system is projected with a physical diagram which specifics the
actual storage parameters that are physically necessary for any database to be
stored on to the disk. The overall systems existential idea is derived from this
diagram.
18

The relation upon the system is structure through a conceptual ER-Diagram,

which not only specifics the existential entities but also the standard relations
through which the system exists and the cardinalities that are necessary for the
system state to continue.

ER-Diagrams:

The entity Relationship Diagram (ERD) depicts the relationship between the
data objects. The ERD is the notation that is used to conduct the date modeling
activity the attributes of each data object noted is the ERD can be described
resign a data object descriptions.

The set of primary components that are identified by the ERD are

Data object

Relationships

Attributes

Various types of indicators.

The primary purpose of the ERD is to represent data objects and their
relationships.

Unified Modeling Language Diagrams:

The unified modeling language allows the software engineer to express an

analysis model using the modeling notation that is governed by a set of
syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe the
system from distinctly different perspective. Each view is defined by a set of
diagram, which is as follows.

User Model View:

This view represents the system from the users perspective.

The analysis representation describes a usage scenario from the endusers perspective.

Structural model view:

19

In this model the data and functionality are arrived from inside the system.

This model view models the static structures.

Behavioral Model View:

It represents the dynamic of behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in the user
model and structural model view.

Implementation Model View:

In this the structural and behavioral as parts of the system are represented as
they are to be built.

Environmental Model View:

In this the structural and behavioral aspects of the environment in which the
system is to be implemented are represented.

20

6. Front End And Back End Tools

6.1 Details about Front End:
6.1.1 Front End or User Design Interface:
The entire user interface is planned to be developed in browser specific
environment with a touch of Intranet-Based Architecture for achieving the Distributed
Concept.
The browser specific components are designed by using the HTML standards,
and the dynamism of the designed by concentrating on the constructs of the Java
Server Pages.

6.1.2 Communication or Database Connectivity Tier:

The Communication architecture is designed by concentrating on the
Standards of Servlets and Enterprise Java Beans. The database connectivity is
established by using the Java Data Base Connectivity.
The standards of three-tire architecture are given major concentration to keep
the standards of higher cohesion and limited coupling for effectiveness of the
operations.

6.1.3 Features of the Language used:

In my project, I have chosen Java language for developing the code.

Java:
Initially the language was called as oak but it was renamed as Java in 1995. The
primary motivation of this language was the need for a platform-independent (i.e.,
architecture neutral) language that could be used to create software to be embedded in
various consumer electronic devices.
Java is a programmers language.
Java is cohesive and consistent.

21

 Except for those constraints imposed by the Internet environment, Java gives
the programmer, full control.
Finally, Java is to Internet programming where C was to system programming.

Applications and Applets:

It can react to the user input and dynamically change. An application is a
program that runs on our Computer under the operating system of that computer. It is
more or less like one creating using C or C++. Javas ability to create Applets makes it
important. An Applet is an application designed to be transmitted over the Internet and
executed by a Java compatible web browser. An applet is actually a tiny Java
program, dynamically downloaded across the network, just like an image. But the
difference is, it is an intelligent program, not just a media file

Features of Java:
Security:
Every time you that you download a normal program, you are risking a viral
infection. Prior to Java, most users did not download executable programs frequently,
and those who did scanned them for viruses prior to execution. Most users still
worried about the possibility of infecting their systems with a virus. In addition,
another type of malicious program exists that must be guarded against. This type of
program can gather private information, such as credit card numbers, bank account
balances, and passwords. Java answers both these
concerns by providing a firewall between a network application and your
computer.
When you use a Java-compatible Web browser, you can safely download Java
applets without fear of virus infection or malicious intent.

Portability:
For programs to be dynamically downloaded to all the various types of
platforms connected to the Internet, some means of generating portable executable
code is needed .As you will see, the same mechanism that helps ensure security also
helps create portability. Indeed, Javas solution to these two problems is both elegant
and efficient.
22

The Byte code:

The key that allows the Java to solve the security and portability problems is that
the output of Java compiler is Byte code. Byte code is a highly optimized set of
instructions designed to be executed by the Java run-time system, which is called the
Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter
for byte code.
Translating a Java program into byte code helps makes it much easier to run a
program in a wide variety of environments. The reason is, once the run-time package
exists for a given system, any Java program can run on it.
Although Java was designed for interpretation, there is technically nothing about Java
that prevents on-the-fly compilation of byte code into native code. Sun has just
completed its Just In Time (JIT) compiler for byte code. When the JIT compiler is a
part of JVM, it compiles byte code into executable code in real time, on a piece-bypiece, demand basis. It is not possible to compile an entire Java program into
executable code all at once, because Java performs various run-time checks that can
be done only at run time. The JIT compiles code, as it is needed, during execution.

Java, Virtual Machine (JVM):

Beyond the language, there is the Java virtual machine. The Java virtual machine is an
important element of the Java technology. The virtual machine can be embedded
within a web browser or an operating system. Once a piece of Java code is loaded
onto a machine, it is verified. As part of the loading process, a class loader is invoked
and does byte code verification makes sure that the code thats has been generated by
the compiler will not corrupt the machine that its loaded on. Byte code verification
takes place at the end of the compilation process to make sure that is all accurate and
correct. So byte code verification is integral to the compiling and executing of Java
code.
Overall Description:

23

Java source
Java

Java byte code

Java VM

.class

Picture showing the development process of JAVA Program

Java source code is located in a. Java file that is processed with a Java compiler called
javac. The Java compiler produces a file called a. class file, which contains the byte
code. The. Class file is then loaded Java programming uses to produce byte codes and
executes them. The first box indicates that the across the network or loaded locally on
your machine into the execution environment is the Java virtual machine, which
interprets and executes the byte code.
Java Architecture:
Java architecture provides a portable, robust, high performing environment for
development. Java provides portability by compiling the byte codes for the Java
Virtual Machine, which is then interpreted on each platform by the run-time
environment. Java is a dynamic system, able to load code when needed from a
machine in the same room or across the planet.
Compilation of code:
When you compile the code, the Java compiler creates machine code (called byte
code) for a hypothetical machine called Java Virtual Machine (JVM). The JVM is
supposed to execute the byte code. The JVM is created for overcoming the issue of
portability. This machine is called Java Virtual Machine.

6.2

Details about Back End:

Role Of Oracle In Database:

24

Oracle 10g is one of the many database services that plug into a client / server
model. It works efficiently to manage resources, a database information, among the
multiple clients requesting & sending.
Structured Query Language (SQL):

SQL is an inter-active language used to query the database and access data in

database. SQL has the following features:

It is a unified language.
It is a common language for relational database
It is a non-procedural language.

Introduction ToOracle:
ORACLE is a comprehensive operating environment that packs the power of a
mainframe system into user microcomputer. It provides a set of functional programs that
user can use as tools to build structures and perform tasks. Because application developed
on oracle are completely portable to environment and then move it into a multi user
platform. Users do not have to be an expert to appreciate ORACLE, but the better user
understands the programmer, the more productivity and creativity you will use the tools it
provides.
What is aRelational Database Management System:
A relational database management system (RDBMS) can perform a wide array of
tasks. It acts as a transparent interface between the physical storage and a logical
presentation of data. It provides a set of more or less flexible and sophisticates tools for
handling information. User can use this tool to:
Define a database
Query the database
Add, edit and delete data
Modify the structure of database
Secure data from public access
Communicate within the networks
Export and Import data
Because it gives so much control over data, a relational DBMS can also save as the
foundation for products that generate application and extract data.
A Database Management system may be called fully relational if it supports:
25

1. Relational Databases and

2. A language that is at least as powerful as the relational algebra
Dr. E.F.Codds Rules.E.F.Codd specified a set of rules that an RDBMS has to do
following 12 rules
1. Information rule: All information in a relational database including table names,
column names, and domain names is represented explicitly by values in tables. With
this design speed and productivity will be improved.
2. Guaranteed access rule: using a combination of table name, a primary key value and
a column name can access Every piece of data in a relational database. With this
productivity is improved since there is no need to resort to using physical pointers of
address and provides data independence.
3. Systematic treatment of null values: The RDBMS distinguishes between blanks
nulls in records and handles such values in consistent manner that produces correct
answers on comparison and calculations. With these users can distinguish results of
queries/operations that involve nulls, zeroes and blanks.
4. Active on-line catalog based on 0the relational model:The description of a database
and its contents are database tables and therefore can be queried on-line via the
database language. With this the DBAs productivity is improved since the changes
are common in catalog to all tables for all queries and reports.
5. Comprehensive data sub-language rule: An RDBMS language supports definitions
of tables/views. Query and update data, integrity constraints, authorizations,
definitions of transactions. With this user productivity is improved since there is a
single approach for all database operations.
6. View updating rule: Any view that is theoretically updateable can be updated using
RDBMS. With this data consistency is ensured since changes in the underlying tables
are transmitted to the view their support.
7. High-level insert, update and delete: The RDBMS supports insertion, updating
deletion at al table level. With this the performance is improved by optimizing the
path for execution.
8. Physical data independence: The execution of adhoc requests and application
programs are not affected by the changes in the physical data access methods. With
this DBA can make changes in application programs or adhoc requests.
26

9. Logical data independence: Logical changes in tables and views do not require
changes in the application programs or in the format of adhoc requests. With this
databases can change and grow without changes in applications.
10. Integrity independence: Since constraints are stored in system catalog, they can be
changed without changing application program. With this maintenance costs are
reduced since only system catalog need to be changed.
11. Distribution independence: Application programs and adhoc requests are not
affected by changes in the distribution of physical data. With this system reliability
will be improved since application programs will work even if the programs and dare
are shifted.
12. Non-Subversion rule: If the RDBMS has languages that access a record of a time it
cannot be used to bypass integrity. With this data integrity is achieved since the
system catalog is musts
a. Code defined a relationally complete set of operations taking one or more
relation as their operands. The operators are two groups: the traditional set of
operators union, intersection, difference and Cartesian product and the special
operators selection, projection, join and division.
b. A fully relational DBMS has to support the above operations.

The Oracle Environment

ORACLE is modular system that consists of the ORACLE database and
several functional programs. ORACLE tools had four kinds of works:
Database management
Data access and manipulations
Programming
Connectivity

Database Management Tools:

This is usually (known as RDBMS by ORACLE) includes the core programs of
Oracles database management system, the ORACLE database with its associated tables
and views, which are stored in the Oracles data dictionary and a group of helpful
27

activities. The data dictionary sores information related to every facet of database system.
User names, user access rights, table storage information and auditing data for the disaster
recovery are all stored in the data dictionary.
Data Access and Manipulations :
All of Oracles data access and manipulation tools are firmly based on ANSI
standard SQL. In Oracle, the tools that a user will use to access and manipulate data, has
well as to design or use applications. Each provides separate point of entry and unique
speech to the Oracle system

7. Screens
Home Page:
28

Login Page:

29

Purchase Order Page:

30

Purchase Order List Page:

31

Stock Utilization Page:

32

Stock Transfer Page:

33

Stock Flow Page:

34

Cities Page:
35

Publishers Page:
36

Categories Page:
37

Book Page:
38

Bookshop Login Page:

39

Entering Details Page:

40

Purchase Order Detail Page:

41

42

8. Reports

List of Book Page:

43

Purchase Order Page:

44

Utilization Book Page:

45

City Stock Utilization Page:

46

Book Transfer Page:

47

9. Source Code
Admin page:
<!DOCTYPE html>
<%@page import="java.sql.*" %>
<%@page import="bookshop.*" %>
<%@page import="java.util.*" %>
<html>
<%

String type = (String)session.getAttribute("type");

if(type.equals("Administrator") || type.equals("Store Manager"))
{

%>
<head>
<link rel="stylesheet" type="text/css" href="css/style.css">
<scriptsrc="js/jquery-1.10.2.min.js"></script>
<scriptsrc="js/jquery.form.js"></script>
<scriptsrc="js/validations.js"></script>
<script type="text/javascript" language="javascript">
$(document).ready(function()
{
window.history.forward(1);
});
</script>

48

</head>
<body>
<table class='main'>

<jsp:include

page="/Header.jsp" flush="true" />

<tr height="450">
<td

class='center' width='15%' valign='top' >

<br/>
<jsp:include

page="/Options.jsp" flush="true" />

</td>

<td

class='center' width='67%' valign='top' >

<br/>
<table class='large-list' >
<tr>

<td>

<div id='center'>
<h2> Welcome </h2>

</div>

</td></tr>
</table>

49

<br/>
</td>

<jsp:include

page="/Footer.jsp" flush="true" />

</table>

</body>
<%

%>

50

Customer Page:
<!DOCTYPE html>
<%@page import="java.sql.*" %>
<%@page import="bookshop.*" %>
<%@page import="java.util.*" %>
<html>
<%

String type = (String)session.getAttribute("type");

if(type.equals("Customer"))
{

%>
<head>
<link rel="stylesheet" type="text/css" href="css/style.css">
<scriptsrc="js/jquery-1.10.2.min.js"></script>
<scriptsrc="js/jquery.form.js"></script>
<scriptsrc="js/validations.js"></script>
<script type="text/javascript" language="javascript">
$(document).ready(function()
{
window.history.forward(1);
$(".wise").change(function()
{
$("#center").load(

"ViewBookss.jsp?wise="+

(this).val() );
});

51

});
function load( code )
{
$( "#center" ).load( 'BookDetails.jsp?code='+code );
}
function get( url )
{
$( "#center" ).load( url );
}
function set( url )
{
$('#templete').attr('action', url );
$('#templete').attr('method', 'post' );
$('#templete').ajaxForm(
{
target: '#center'
}).submit();
}
</script>
</head>
<body>

<table class='main'>

<jsp:include

page="/Header.jsp" flush="true" />

<tr height="520">

52

<td

class='center' width='15%' valign='top' >

<br/>

<jsp:include

page="/Options.jsp" flush="true" />

</td>

<td

class='center' width='67%' valign='top' >

<br/>
<table class='large-list' >
<tr>

<td>

<div id='center'>
<h4><span><%= request.getParameter("message") %></span></h4>
<jsp:include

page="/ViewBookss.jsp?wise=All"

flush="true" />

</div>

</td></tr>
</table>
<br/>
</td>
<td

class='center' width='18%' valign='top'>

<br/>
<table class='large-list' >
<tr class='alt' > <td align='center'>

53

Categories</td>

</tr>

<tr><td><input type='radio' name='wise' class='wise' value='All' checked/>

All </td></tr>
<%

try
{
Connection con = ConnectionPool.openConnection();
Statement st = con.createStatement();
ResultSetrs = st.executeQuery( "select category_id , name from

categories order by name" );

while(rs.next() )
{
String code = rs.getString("category id");
String name = rs.getString("name");
out.println(

"<tr><td><input

type='radio'

class='wise' value='"+ code +"' />"+ name + "</td></tr>" );

}
ConnectionPool.closeConnection( con );
}catch( Exception e )
{
System.out.println( " States : " + e );
}
%>
</table>

</td></tr>
<jsp:include

page="/Footer.jsp" flush="true" />

</table>
</body>

54

name='wise'

<%

%>

<html>

10.Testing
Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of software. The results of testing are used
later on during maintenance also.

Testing Objectives:
The main objective of testing is to uncover a host of errors, systematically and with
minimum effort and time. Stating formally, we can say,
Testing is a process of executing a program with the intent of finding an error.
A successful test is one that uncovers an as yet undiscovered error.
A good test case is one that has a high probability of finding error, if it exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable standards.

10.1 Unit Testing:

Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications testing is done to
uncover errors within the boundary of the module. All modules must be successful in the
unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many
modules like Login, HWAdmin, MasterAdmin, Normal User, and PManager. Giving
different sets of inputs has tested each module. When developing the module as well as
finishing the development so that each module works without any error. The inputs are
validated when accepting from the user.
In this application developer tests the programs up as system. Software units in a
system are the modules and routines that are assembled and integrated to form a specific
function. Unit testing is first done on modules, independent of one another to locate
errors. This enables to detect errors. Through this errors resulting from interaction
betweenmodules initially avoided.

55

11. Conclusion
In this project we explained how an ONLINE BOOK SHOP can be designed to
provide an easy interface for the customers to know about various books and they can easily
find them through our site and they can easily buy them through online.
This reduces the burden for customer by going to book stores and searching for books
and it saves time also by visiting online.
Our project also met all the requirements specified in Software Requirement
Specifications and can also handle various runtime errors caused by irrelevant inputs
given by both student and the administrator. Possible future extensions can also be made to
this system.

56

12.Bibliography

Object oriented software engineering Bernd Bruegge, Allen H. Dutoit

Web technology and design C. Xavier
Head first Servest and JSP-OReilly, Bryan Basham, Kathy Sierra and Bert Bates

Websites:
1. www.w3schools.com
2.www.projects-forum.com
3. www.uml-diagrams.org

57