ABSTRACT

Library is place where all kind of books are available. Intranet Library
Management system is a web based application. This system contains list of all the
books and can be accessed by remote users concurrently from any where in the
campus. But for that users must be registered user. This system is three tier
architecture.

Client sends requests, on receiving the request the server processes it

and extracts the data from database and sends the result back to the client. This
system provides separate interface and login for librarian, students and faculties.
Librarian can modify database.

Users can search for books and renewal books online. They can
recommend for new books by just sending messages to the librarian from any
where in the college. They can view the issue and return dates of any book and due
they have to pay. This system generates reports that can be used in analyzing the
library performance. Thus the management can take appropriate steps to improve
the facilities.
 INDEX

S. N CONTENTS

1. INTRODUCTION
2. ANALYSIS
2.1 SYSTEM ANALYSIS
2.2 SYSTEM SPECIFICATIONS
3. DESIGN APPROACH
3.1 INTRODUCTION TO DESIGN
3.2 UML DIAGRAMS
3.3 DATA FLOW DIAGRAMS
3.4 E-R DIAGRAMS
4. PROJECT MODULES
5. IMPLEMENTATION
4.1 CONCEPTS AND TECHNIQUES
4.2 TESTING
4.2.1 TEST CASES
6. OUTPUT SCREENS
7. CONCLUSION
8. FUTURE ENHANCEMENTS
9. BIBILIOGRAPHY
INTRODUCTION:

Library Management System consists of list of records about the

management of the details of the students and the issues going on and also about some
books and all. This is a web-based application. The project has three modules namely-
User, Registration, Librarian. According to the Modules the Distributor and Sub
Distributors can manage and do their activities in easy manner.

As the modern organizations are automated and computers are working as per
the instructions, it becomes essential for the coordination of human beings, commodity
and computers in a modern organization. This information helps the distributors to
purchase or sale the products very efficiently.

The administrators and all the others can communicate with the system through
this project, thus facilitating effective implementation and monitoring of various
activities of the distributor of a supermarket.
SYSTEM ANALYSIS:

1. Existing System

. Various problems of physical system are described below :-

 If one is not very careful then there is a possibility of issuing more than one
book to a user.
 There is a possibility of issuing a book to a user, whose membership is not
there.
 When a user requests for the a book, one has to physically check for the
presence of a book in the library
 Answering management query is a time consuming process.
 Daily keeping a manual record of changes taking place in the library such as
book being issued, book being returned etc can become cumbersome if the
Library size is bigger.

2. Proposed System

The LIBRARY MANAGEMENT SYSTEM is a software application which

avoids more manual hours in taking the book, that need to spend in record keeping
and generating reports. Maintaining of user details is complex in manual system in
terms of agreements, royalty and activities. This all have to be maintained in ledgers
or books. Co-coordinators needs to verify each record for small information also.

 Easy search of book in the online library.

 Avoid the manual work.
 User need not go to the library for Issue any kind of book, he can renewal the
book online.
3. Objective of the System

The goal of the system is to bring down the work load with the increased
efficiency and to speed up the activities. With this it is very easy to process course fee
that is collected time to time from students who are registered and studying at
franchisees.

System Specifications

Hardware Requirements:-
 Pentium-IV(Processor).
 256 MB Ram
 512 KB Cache Memory
 Hard disk 10 GB
 Microsoft Compatible 101 or more Key Board

Software Requirements: -
 Operating System : Windows 95/98/XP with MS-office
 Programming language: .NET2.0, VISUAL STUDIO2005
 Web-Technology : ASP.NET
 Back-End : SQL SERVER 2005
 Web Server : IIS.
INTRODUCTION:

Design is the first step in the development phase for any

techniques and principles for the purpose of defining a device, a process or system in
sufficient detail to permit its physical realization.

Once the software requirements have been analyzed and

specified the software design involves three technical activities - design, coding,
implementation and testing that are required to build and verify the software.

The design activities are of main importance in this phase,

because in this activity, decisions ultimately affecting the success of the software
implementation and its ease of maintenance are made. These decisions have the final
bearing upon reliability and maintainability of the system. Design is the only way to
accurately translate the customer’s requirements into finished software or a system.

Design is the place where quality is fostered in

development. Software design is a process through which requirements are translated into
a representation of software. Software design is conducted in two steps. Preliminary
design is concerned with the transformation of requirements into data.
DATA FLOW DIAGRAMS:

The DFD takes an input-process-output view of a system i.e. data objects flow
into the software, are transformed by processing elements, and resultant data objects flow
out of the software.

Data objects represented by labeled arrows and transformation are

represented by circles also called as bubbles. DFD is presented in a hierarchical fashion
i.e. the first data flow model represents the system as a whole. Subsequent DFD refine the
context diagram (level 0 DFD), providing increasing details with each subsequent level.

The DFD enables the software engineer to develop models of the

information domain & functional domain at the same time. As the DFD is refined into
greater levels of details, the analyst perform an implicit functional decomposition of the
system. At the same time, the DFD refinement results in a corresponding refinement of
the data as it moves through the process that embody the applications.

A context-level DFD for the system the primary external entities produce
information for use by the system and consume information generated by the system. The
labeled arrow represents data objects or object hierarchy.
RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions
 Reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with Rounded circles.
 A process is required for all the data transformation and Transfers. Therefore,
never connect a data store to a data Source or the destinations or another data
store with just a Data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything the
process is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with Squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
E-R Diagrams:

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a
way to unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic component
of the model is the Entity-Relationship diagram which is used to visually represents data objects.
Since Chen wrote his paper the model has been extended and today it is commonly used for
database design For the database designer, the utility of the ER model is:

 it maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
 it is simple and easy to understand with a minimum of training. Therefore, the model can
be used by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to
implement a data model in a specific database management software.

Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-
many. A one-to-one (1:1) relationship is when at most one instance of a entity A is associated
with one instance of entity B. For example, "employees in the company are each assigned their
own office. For each employee there exists a unique office and for each office there exists a
unique employee.

A one-to-many (1:N) relationships is when for one instance of entity A, there are zero,
one, or many instances of entity B, but for one instance of entity B, there is only one
instance of entity A. An example of a 1:N relationships is a department has many
employees each employee is assigned to one department.

A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance of
entity A, there are zero, one, or many instances of entity B and for one instance of entity B there
are zero, one, or many instances of entity A. The connectivity of a relationship describes the
mapping of associated
ER Notation

There is no standard for representing data objects in ER diagrams. Each modeling

methodology uses its own notation. The original notation used by Chen is widely used in
academics texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, there are a number of notations used, among the more common are Bachman,
crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a
connection. The notation used in this document is from Martin. The symbols used for the basic
ER constructs are:

 entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.
 relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs
 attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
 cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.
 existence is represented by placing a circle or a perpendicular bar on the line. Mandatory
existence is shown by the bar (looks like a 1) next to the entity for an instance is required.
Optional existence is shown by placing a circle next to the entity that is optional
 PROJECT MODULES

MODULES USED:-
The proposed system categories and follows these modules to implement

Login component
1. Administrator(Head office manager)
2. Librarian
3. User

Administrator Component
1. Administrator

Librarian Manager Component

1. Librarian Manager

Student Component
1. Books Details
2. Issue Details

MODULES DESCRIPSTION:-
User: Using login id and password user can the use Library online
where users can search for books and renewal books online. They can recommend
for new books by just sending messages to the librarian from any where in the
college. They can view the issue and return dates of any book and due they have to
pay.
Registration: In the Registration module, user has to register himself by
supplying his personal information which gets store in data base which are using as
 backend. By registering himself user will get his login id and Password so that he
can access Library online. Separate Register form should be designed for separate
user
(Student, Faculty, Librarian) and separate login has to provided for each user. For
example if the users are students then student id should be SH001.

Librarian: Librarian is a person who manages the Library. Librarian

has the permission that he can access the database. There are some tasks which are
performed by the Librarian like:
 Addition of a new book.
 Modification of the book.
 Deletion of the book.
 Searching of the book.
 Managing User

OVERVIEW OF TECHNOLOGIES USED

Front End Technology

FEASIBILITY STUDY:

Feasibility
study is conducted once the problem is clearly understood. Feasibility study is a high
level capsule version of the entire system analysis and design process. The objective is to
determine quickly at a minimum expense how to solve a problem. The purpose of
feasibility is not to solve the problem but to determine if the problem is worth solving.
 The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.

1. Technical Feasibility
The project entitles "Courier Service System” is technically feasibility
because of the below mentioned feature. The project was developed in Java which
Graphical User Interface.
It provides the high level of reliability, availability and compatibility. All
these make Java an appropriate language for this project. Thus the existing
software Java is a powerful language.

2. Economical Feasibility

The computerized system will help in automate the selection leading

the profits and details of the organization. With this software, the machine and
manpower utilization are expected to go up by 80-90% approximately. The costs
incurred of not creating the system are set to be great, because precious time can be
wanted by manually.

3. Operational Feasibility

In this project, the management will know the details of

each project where he may be presented and the data will be maintained as decentralized
and if any inquires for that particular contract can be known as per their requirements and
necessaries.
Implementation:

Implementation is the stage where the theoretical design is turned into a working
system. The most crucial stage in achieving a new successful system and in giving
confidence on the new system for the users that it will work efficiently and effectively.

The system can be implemented only after thorough testing is done and if it is found to
work according to the specification.

It involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the change over and an evaluation of
change over methods a part from planning. Two major tasks of preparing the
implementation are education and training of the users and testing of the system.

The more complex the system being implemented, the more involved will be the
systems analysis and design effort required just for implementation.

The implementation phase comprises of several activities. The required hardware

and software acquisition is carried out. The system may require some software to be
developed. For this, programs are written and tested. The user then changes over to his
new fully tested system and the old system is discontinued.

TESTING:

The testing phase is an important part of software development. It is the puterized

system will help in automate process of finding errors and missing operations and also a
complete verification to determine whether the objectives are met and the user
requirements are satisfied.
Software testing is carried out in three steps:

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

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

3. The final step involves validation and testing which determines which the
software functions as the user expected. Here also some modifications were. In the
completion of the project it is satisfied fully by the end user.

Maintenance and environment:

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

Correction
Adaptation
Enhancement
Prevention

Correction:

Even with the best quality assurance activities is lightly that the customer
will uncover defects in the software. Corrective maintenance changes the software
to correct defects.

Maintenance is a set of software Engineering activities that occur after

software has been delivered to the customer and put into operation. Software
configuration management is a set of tracking and control activities that began
when a software project begins and terminates only when the software is taken
out of the operation.

We may define maintenance by describing four activities that are undertaken

after a program is released for use:
Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance or Enhancement
Preventive Maintenance or reengineering

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

ADAPTATION:

Over time, the original environment (E>G., CPU, operating system, business
rules, external product characteristics) for which the software was developed is likely to
change. Adaptive maintenance results in modification to the software to accommodate
change to its external environment.

ENHANCEMENT:

As software is used, the customer/user will recognize additional functions that will
provide benefit. Perceptive maintenance extends the software beyond its original function
requirements.

PREVENTION:

Computer software deteriorates due to change, and because of this,

preventive maintenance, often called software re engineering, must be conducted
to enable the software to serve the needs of its end users. In essence, preventive
maintenance makes changes to computer programs so that they can be more easily
corrected, adapted, and enhanced. Software configuration management (SCM) is
an umbrella activity that is applied throughout the software process. SCM
activities are developed
Java Technology

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 programmer’s language.
 Java is cohesive and consistent.
 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.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands
the Universe of objects that can move about freely in Cyberspace. In a network,
two categories of objects are transmitted between the Server and the Personal
computer. They are: Passive information and Dynamic active programs. The
Dynamic, Self-executing programs cause serious problems in the areas of
Security and probability. But, Java addresses those concerns and by doing so,
has opened the door to an exciting new form of program called the Applet.

Java can be used to create two types of programs

Applications and Applets : 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++. Java’s 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. It can react to the
user input and dynamically change.

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 scan 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.

Features of java

1) Compiled and Interpreter:- has both Compiled and Interpreter Feature

Program of java is First Compiled and Then it is must to Interpret it .First of all
The Program of java is Compiled then after Compilation it creates Bytes Codes
rather than Machine Language.Then After Bytes Codes are Converted into the
Machine Language is Converted into the Machine Language with the help of the
Interpreter So For Executing the java Program First of all it is necessary to
Compile it then it must be Interpreter

2) Platform Independent:- Java Language is Platform Independent means

program of java is Easily transferable because after Compilation of java program
bytes code will be created then we have to just transfer the Code of Byte Code to
another Computer.This is not necessary for computers having same Operating
System in which the code of the java is Created and Executed After Compilation
of the Java Program We easily Convert the Program of the java top the another
Computer for Execution.

3) Object-Oriented:- We Know that is purely OOP Language that is all the Code
of the java Language is Written into the classes and Objects So For This feature
java is Most Popular Language because it also Supports Code Reusability,
Maintainability etc.

4) Robust and Secure:- The Code of java is Robust andMeans ot first checks the
reliability of the code before Execution When We trying to Convert the Higher
data type into the Lower Then it Checks the Demotion of the Code the It Will
Warns a User to Not to do this So it is called as Robust.
Secure : When We convert the Code from One Machine to Another the First
Check the Code either it is Effected by the Virus or not or it Checks the Safety of
the Code if code contains the Virus then it will never Executed that code on to the
Machine.

5) Distributed:- Java is Distributed Language Means because the program of java

is compiled onto one machine can be easily transferred to machine and Executes
them on another machine because facility of Bytes Codes So java is Specially
designed For Internet Users which uses the Remote Computers For Executing
their Programs on local machine after transferring the Programs from Remote
Computers or either from the internet.

6) Simple Small and Familiar:- is a simple Language Because it contains many

features of other Languages like c and C++ and Java Removes Complexity
because it doesn’t use pointers, Storage Classes and Go to Statements and java
Doesn’t support Multiple Inheritance
7) Multithreaded and Interactive:- Java uses Multithreaded Techniques For
Execution Means Like in other in Structure Languages Code is Divided into the
Small Parts Like These Code of java is divided into the Smaller parts those are
Executed by java in Sequence and Timing Manner this is Called as Multithreaded
In this Program of java is divided into the Small parts those are Executed by
Compiler of java itself Java is Called as Interactive because Code of java
Supports Also CUI and Also GUI Programs

8) Dynamic and Extensible Code:- Java has Dynamic and Extensible Code
Means With the Help of OOPS java Provides Inheritance and With the Help of
Inheritance we Reuse the Code that is Pre-defined and Also uses all the built in
Functions of java and Classes

9) Distributed:- Java is a distributed language which means that the program can
be design to run on computer networks. Java provides an extensive library of
classes for communicating ,using TCP/IP protocols such as HTTP and FTP. This
makes creating network connections much easier than in C/C++. You can read
and write objects on the remote sites via URL with the same ease that
programmers are used to when read and write data from and to a file. This helps
the programmers at remote locations to work together on the same project.

10) Secure: Java was designed with security in mind. As Java is intended to be
used in networked/distributor environments so it implements several security
mechanisms to protect you against malicious code that might try to invade your
file system.
For example: The absence of pointers in Java makes it impossible for
applications to gain access to memory locations without proper authorization as
memory allocation and referencing model is completely opaque to the
programmer and controlled entirely by the underlying run-time platform .
11) Architectural Neutral: One of the key feature of Java that makes it different
from other programming languages is architectural neutral (or platform
independent). This means that the programs written on one platform can run on
any other platform without having to rewrite or recompile them. In other words, it
follows 'Write-once-run-anywhere' approach.Java programs are compiled into
byte-code format which does not depend on any machine architecture but can be
easily translated into a specific machine by a Java Virtual Machine (JVM) for that
machine. This is a significant advantage when developing applets or applications
that are downloaded from the Internet and are needed to run on different
systems.

12) Portable : The portability actually comes from architecture-neutrality. In C/C+

+, source code may run slightly differently on different hardware platforms
because of how these platforms implement arithmetic operations. In Java, it has
been simplified. nlike C/C++, in Java the size of the primitive data types are
machine independent. For example, an int in Java is always a 32-bit integer, and
float is always a 32-bit IEEE 754 floating point number. These consistencies
make Java programs portable among different platforms such as Windows, Unix
and Mac .

13) Interpreted : Unlike most of the programming languages which are either
complied or interpreted, Java is both complied and interpreted The Java compiler
translates a java source file to bytecodes and the Java interpreter executes the
translated byte codes directly on the system that implements the Java Virtual
Machine. These two steps of compilation and interpretation allow extensive code
checking and improved security .

14) High performance: Java programs are complied to portable intermediate form
know as bytecodes, rather than to native machine level instructions and JVM
executes Java bytecode on. Any machine on which it is installed. This
architecture means that Java programs are faster than program or scripts written
in purely interpreted languages but slower than C and C++ programs that
compiled to native machine languages.Although in the early releases of Java, the
interpretation of by bytecode resulted in slow performance but the advance
version of JVM uses the adaptive and Just in time (JIT) compilation technique
that improves performance by converting Java bytecodes to native machine
instructions on the fly.

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 that’s has been generated by the compiler will not corrupt the
machine that it’s 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

Java Source Java byte code

JavaVM

Java .Class
Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box
indicates that the 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 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. The code is written and compiled for one machine and
interpreted on all machines. This machine is called Java Virtual Machine.
Compiling and interpreting Java Source Code

Java
PC Compiler Interpreter
Java (PC)
Source
Code Byte code
………..
……….. Macintosh Java
Compiler (Platform Interpreter
Independe (Macintosh)
……….. nt)

………… SPARC
Java
Interpreter
Compiler (Spare)

During run-time the Java interpreter tricks the byte code file into thinking that it is
running on a Java Virtual Machine. In reality this could be a Intel Pentium
Windows 95 or SunSARC station running Solaris or Apple Macintosh running
system and all could receive code from any computer through Internet and run
the Applets.

Simple

Java was designed to be easy for the Professional programmer to learn and to
use effectively. If you are an experienced C++ programmer, learning Java will be
even easier. Because Java inherits the C/C++ syntax and many of the object
oriented features of C++. Most of the confusing concepts from C++ are either left
out of Java or implemented in a cleaner, more approachable manner. In Java
there are a small number of clearly defined ways to accomplish a given task.
Object-Oriented

Java was not designed to be source-code compatible with any other language.
This allowed the Java team the freedom to design with a blank slate. One
outcome of this was a clean usable, pragmatic approach to objects. The object
model in Java is simple and easy to extend, while simple types, such as integers,
are kept as high-performance non-objects.

Robust

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 de-allocation,
which is completely automatic. In a well-written Java program, all run time errors
can –and should –be managed by your program.
Java Database Connectivity

What Is JDBC?
JDBC is a Java API for executing SQL statements. (As a point of interest,
JDBC is a trademarked name and is not an acronym; nevertheless, JDBC 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 combinations of Java and JDBC lets a programmer write it once and run
it anywhere.
What Does JDBC Do?

Simply put, JDBC makes it possible to do three things:

 Establish a connection with a database
 Send SQL statements
 Process the results.

JDBC versus ODBC and other APIs

At this point, Microsoft's ODBC (Open Database Connectivity) API is that

probably the most widely used programming interface for accessing relational
databases. It offers the ability to connect to almost all databases on almost
all platforms.
So why not just use ODBC from Java? The answer is that you can use ODBC
from Java, but this is best done with the help of JDBC in the form of the
JDBC-ODBC Bridge, which we will cover shortly. The question now becomes
"Why do you need JDBC?" There are several answers to this question:

1. ODBC is not appropriate for direct use from Java because it uses a C
interface. Calls from Java to native C code have a number of
 drawbacks in the security, implementation, robustness, and automatic
portability of applications.
2. A literal translation of the ODBC C API into a Java API would not be
desirable. For example, Java has no pointers, and ODBC makes
copious use of them, including the notoriously error-prone generic
pointer "void *". You can think of JDBC as ODBC translated into an
object-oriented interface that is natural for Java programmers.
3. ODBC is hard to learn. It mixes simple and advanced features
together, and it has complex options even for simple queries. JDBC, on
the other hand, was designed to keep simple things simple while
allowing more advanced capabilities where required.
4. A Java API like JDBC is needed in order to enable a "pure Java"
solution. When ODBC is used, the ODBC driver manager and drivers
must be manually installed on every client machine. When the JDBC
driver is written completely in Java, however, JDBC code is
automatically installable, portable, and secure on all Java platforms
from network computers to mainframes.
Two-tier and Three-tier Models

The JDBC API supports both two-tier and three-tier models for database
access.

In the two-tier model, a Java applet or application talks directly to the database.
This requires a JDBC driver that can communicate with the particular database
management system being accessed. A user's SQL statements are delivered to
the database, and the results of those statements are sent back to the user. The
database may be located on another machine to which the user is connected via
a network. This is referred to as a client/server configuration, with the user's
machine as the client, and the machine housing the database as the server. The
network can be an Intranet, which, for example, connects employees within a
corporation, or it can be the Internet.
 JAVA
Application Client machine

JDBC
DBMS-proprietary protocol

DBMS
Database server

Java applet or
Html browser
Client machine (GUI)

HTTP, RMI, or CORBA

Application
Server (Java)
calls
JDBC
Server machine (business
DBMS-proprietary protocol
Logic)

Database server

DBMS

In the three-tier model, commands are sent to a "middle tier" of services,

which then send SQL statements to the database. The database processes
the SQL statements and sends the results back to the middle tier, which then
sends them to the user. MIS directors find the three-tier model very
attractive because the middle tier makes it possible to maintain control over
access and the kinds of updates that can be made to corporate data. Another
advantage is that when there is a middle tier, the user can employ an easy-
to-use higher-level API which is translated by the middle tier into the
appropriate low-level calls. Finally, in many cases the three-tier architecture
can provide performance advantages.

Until now the middle tier has typically been written in languages such as C or
C++, which offer fast performance. However, with the introduction of
optimizing compilers that translate Java byte code into efficient machine-
specific code, it is becoming practical to implement the middle tier in Java.
This is a big plus, making it possible to take advantage of Java's robustness,
multithreading, and security features. JDBC is important to allow database
access from a Java middle tier.
JDBC Driver Types

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

 JDBC-ODBC bridge plus ODBC driver

 Native-API partly-Java driver
 JDBC-Net pure Java driver
 Native-protocol pure Java driver

JDBC-ODBC Bridge

If possible, use a Pure Java JDBC driver instead of the Bridge and an ODBC
driver. This completely eliminates the client configuration required by ODBC.
It also eliminates the potential that the Java VM could be corrupted by an
error in the native code brought in by the Bridge (that is, the Bridge native
library, the ODBC driver manager library, the ODBC driver library, and the
database client library).

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 implements JDBC for any
database for which an ODBC driver is available. The Bridge is
implemented as the

Sun.jdbc.odbc Java package and contains a native library used to access

ODBC. The Bridge is a joint development of Innersole and Java Soft.
JDBC connectivity

The JDBC provides database-independent connectivity between the J2EE

platform and a wide range of tabular data sources. JDBC technology allows
an Application Component Provider to:

 Perform connection and authentication to a database server

 Manager transactions
 Move SQL statements to a database engine for preprocessing and
execution
 Execute stored procedures
 Inspect and modify the results from Select statements
Database:
A database management system (DBMS) is computer software designed for
the purpose of managing databases, a large set of structured data, and run
operations on the data requested by numerous users. Typical examples of
DBMSs include Oracle, DB2, Microsoft Access, Microsoft SQL Server, Firebird,
PostgreSQL, MySQL, SQLite, FileMaker and Sybase Adaptive Server
Enterprise. DBMSs are typically used by Database administrators in the
creation of Database systems. Typical examples of DBMS use include
accounting, human resources and customer support systems.

Originally found only in large companies with the computer hardware

needed to support large data sets, DBMSs have more recently
emerged as a fairly standard part of any company back
Home Page
 Testing is a process of executing a program with the indent of
finding an error. Testing is a crucial element of software quality assurance and presents
ultimate review of specification, design and coding.

System Testing is an important phase. Testing represents an interesting anomaly for the
software. Thus a series of testing are performed for the proposed system before the
system is ready for user acceptance testing.

A good test case is one that has a high probability of finding an as undiscovered
error. A successful test is one that uncovers an as undiscovered error.

Testing Objectives:

1. Testing is a process of executing a program with the intent of finding an error

2. A good test case is one that has a probability of finding an as yet undiscovered
error
3. A successful test is one that uncovers an undiscovered error

Testing Principles:

 All tests should be traceable to end user requirements

 Tests should be planned long before testing begins
 Testing should begin on a small scale and progress towards testing in large
 Exhaustive testing is not possible
 To be most effective testing should be conducted by a independent third party

The primary objective for test case design is to derive a set of tests that has the
highest livelihood for uncovering defects in software. To accomplish this objective two
different categories of test case design techniques are used. They are

 White box testing.

 Black box testing.

White-box testing:

White box testing focus on the program control structure. Test cases are derived
to ensure that all statements in the program have been executed at least once during
testing and that all logical conditions have been executed.

Block-box testing:

Black box testing is designed to validate functional requirements without regard to the
internal workings of a program. Black box testing mainly focuses on the information
domain of the software, deriving test cases by partitioning input and output in a manner
that provides through test coverage. Incorrect and missing functions, interface errors,
errors in data structures, error in functional logic are the errors falling in this category.

Testing strategies:

A strategy for software testing must accommodate low-level tests that are
necessary to verify that all small source code segment has been correctly implemented as
well as high-level tests that validate major system functions against customer
requirements.
Testing fundamentals:

Testing is a process of executing program with the intent of finding error. A good
test case is one that has high probability of finding an undiscovered error. If testing is
conducted successfully it uncovers the errors in the software. Testing cannot show the
absence of defects, it can only show that software defects present.

Testing Information flow:

Information flow for testing flows the pattern. Two class of input provided to test
the process. The software configuration includes a software requirements specification, a
design specification and source code.

Test configuration includes test plan and test cases and test tools. Tests are
conducted and all the results are evaluated. That is test results are compared with
expected results. When erroneous data are uncovered, an error is implied and debugging
commences.

Unit testing:

Unit testing is essential for the verification of the code produced during the
coding phase and hence the goal is to test the internal logic of the modules. Using the
detailed design description as a guide, important paths are tested to uncover errors with in
the boundary of the modules. These tests were carried out during the programming stage
itself. All units of ViennaSQL were successfully tested.

Integration testing :

Integration testing focuses on unit tested modules and build the program structure
that is dictated by the design phase.

System testing:

System testing tests the integration of each module in the system. It also tests to
find discrepancies between the system and it’s original objective, current specification
 and system documentation. The primary concern is the compatibility of individual
modules. Entire system is working properly or not will be tested here, and specified path
ODBC connection will correct or not, and giving output or not are tested here these
verifications and validations are done by giving input values to the system and by
comparing with expected output. Top-down testing implementing here.

Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation.
Acceptance testing begins when the system is complete. Its purpose is to provide the end
user with the confidence that the system is ready for use. It involves planning and
execution of functional tests, performance tests and stress tests in order to demonstrate
that the implemented system satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

Timing Analyzer – also called a profiler, reports the time spent in various regions of the
code are areas to concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect code for
deviations from standards and guidelines.

Test Cases:

Test cases are derived to ensure that all statements in the program have been
executed at least once during testing and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can drive test cases that
 Guarantee that logical decisions on their true and false sides.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and with in their operational bounds.
 Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review before
system testing commences.
CONCLUSION:

The package was designed in such a way that future modifications can be
done easily. The following conclusions can be deduced from the
development of the project.

 Library Management System of the entire system improves the efficiency.

 It provides a friendly graphical user interface which proves to be better
when compared to the existing system.
 It gives appropriate access to the authorized users depending on their
permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is
necessary.
FUTURE ENHANCEMENTS:

This application avoids the manual work and the problems concern with it.
It is an easy way to obtain the information regarding the various products information
that are present in the Library of a particular college.
Well I and my team members have worked hard in order to
present an improved website better than the existing one’s regarding the information
about the various activities. Still ,we found out that the project can be done in a better
way. Primarily, when we request information about a particular product it just shows the
company, product id, product name and no. of quantities available. So, after getting the
information we can get access to the product company website just by a click on the
product name .
The next enhancement that we can add the searching option.
We can directly search to the particular product company from this site .These are the
two enhancements that we could think of at present.
BIBLIOGRAPHY

The following books were referred during the analysis and execution phase of the
project

MICROSOFT .NET WITH C#

Microsoft .net series

ASP .NET 2.0 PROFESSIONAL

Wrox Publishers

ASP .NET WITH C# 2005

Apress Publications

C# COOK BOOK
O reilly Publications

PROGRAMMING MICROSOFT ASP .NET 2.0 APPLICATION

Wrox Professional Guide

BEGINNING ASP .NET 2.0 E-COMMERCE IN C# 2005

Novice to Professional.

WEBSITES:
www.google.com
www.microsoft.com