E Library

Index
1. Overview of the project
2. Existing System
2.1. Existing System
2.2. Limitations
2.3. Need for computerization
3. Proposed System
3.1.1. Proposed system
3.1.2. Objectives
3.1.3. Diagrammatic Representation
3.1.4. Scope
3.1.5. Permission matrix
3.1.6. Features
3.1.7. Advantages
3.1.8. Enhancements
4. Requirement Analysis
4.1. Fact Finding Techniques
4.1.1. Questionnaire
4.1.2. Interview
4.1.3. Observation
4.1.4. Record review
4.2. Feasibility Study
4.2.1. Technical Feasibility
4.2.1.1.
Hardware Software requirement
4.2.2. Economic Feasibility
4.2.3. Operational Feasibility
5. System Analysis Diagrams
5.1. Process Chart
5.2. Data Flow Diagram
5.3. Entity Relationship Diagram
5.4. Data Dictionary
6. Design Specifications
6.1. Input Screen with Interactivity
6.2. Output Screen
7. Technology Used
7.1. JAVA (JDK 1.5)
7.2. JSP TECHNOLOGY
7.3. WEB SERVER TOMCAT
7.4. JDBC
7.5. PRESENTATION BEANS
7.6. POSTGRESQL
Bibliography

E Library

E Library

OVERVIEW
OVERVIEW

An introduction to digital libraries

This is a fascinating period in the history of libraries and
publishing. For the first time, it is possible to build large-scale
services where collections of information are stored in digital
formats and retrieved over networks. The materials are stored
on computers. A network connects the computers to personal
computers on the users' desks. In a completely digital library,
nothing need ever reach paper.
Why digital libraries?
The fundamental reason for building digital libraries is a belief
that they will provide better delivery of information than was
possible in the past. Traditional libraries are a fundamental
part of society, but they are not perfect. Can we do better?
Enthusiasts for digital libraries point out that computers and
networks have already changed the ways in which people
communicate with each other. In some disciplines, they argue,
a professional or scholar is better served by sitting at a
personal computer connected to a communications network

E Library

than by making a visit to a library. Information that was

previously available only to the professional is now directly
available to all. From a personal computer, the user is able to
consult materials that are stored on computers around the
world. Conversely, all but the most diehard enthusiasts
recognize that printed documents are so much part of
civilization that their dominant role cannot change except
gradually. While some important uses of printing may be
replaced by electronic information, not everybody considers a
large-scale movement to electronic information desirable, even
if it is technically, economically, and legally feasible.

E Library

Existing system
If a user wants to borrow some book, his/her library card is a
must. No book will be issued until he/she carries the library
card along with them. The librarian checks if the previous
books borrowed from library has been returned in the fixed
time span. If yes, then only next books can be issued. If not ,
then a fine is to be paid .
We found following limitations or disadvantages related with
manual system
Current system is manual information system, hence the basic
difference between the human and the computer is always
creates limitations on current system which are explained as
following:

Lack of Efficiency
When work load increases human efficiency decreases
rapidly. There are many other factors which affect human
behavior resulting in inconsistency in work efficiency.
Lengthy Procedures & Time Consumption

E Library

This is manual system. Due to lack of accuracy, tedious

procedure and lack of efficiency the procedure becomes
lengthy and time consuming beside this lack of mobility,
documents are scrutinized by, many offices and employees at
different levels manually hence a lot of time is wasted in
moving data from one place to another, making the procedure
lengthy and time consuming

Un-centralized Data
Data is not centralized at all. For example, report
generation becomes time consuming due to lack of efficiency.
All the information regarding geographical components is kept
on paper. This requires lot of manual power and the result is
pilling of paper in different files. Reports also increase the
writing work.

Delay In Decision Making

As the consent and suggestion of every department take
every decision, all scrutinizes the paper and the system being
manual, papers are transposed manually. This requires a lot of
time resulting in delay of decision-making.

Lack of Up-To-Date Information

E Library

If frequent changes are to be done then the frequent

updating of the records manually is not possible. If we tend to
do frequent changes in the Records then it becomes very time
consuming and tedious job, also the possibility of concurrent
of errors during updation of records cannot be ignored.

Lack of Maintenance and Backup

In the current system maintenance and to keep back up
(copy) of every record is not easy. Papers being perishable, the
records cannot be maintained for a very long duration of time.
Also, the records can get destroyed due to calamities such as
fire hence backup of records is required.

Some other problems observed in the system are as follows

If in case many students are already waiting in queue, then it

takes atleast 10 minutes for your number to come. The
required books are checked in the library if the are available at
that particular time. Since vast subject are available it takes
time to search a particular one.

Also as there are limited editions of each book so there are

chances of the book not being issued to the user. If the book

E Library

is been found, then the librarian makes an entry of that book

into your library card and also keeps a copy of it in his
file/documents. This process takes atleast 15-20 minutes.

So, for this purpose it is necessary to plan a computerized

system where this job is done more efficiently and also in less
time.

Need for computerization

1) Decreased workload:
An increase workload can arise from the need to control or
access large number of documents. This may be a result of
overall increase in the number of documents published or may
derived from need to cover the wider subject area. Increased
workload can also stem from desired or necessity to provide a
large number of partons with an adequate service.

E Library

Computerization can be helpful to increase the workload with

constant staff.

2) New services:
Computerization may offer the opportunity the problem of
cost.
But one the main advantage of the computer based system is
the facility for rearranging the records stored in database in
well mannered. This job can be done by administrator
Users can access the e-books they requested for.

3) Greater efficiency:
Computerization may be viewed as means of saving staff time
and money. the records held in computer are accurate and
more accessible than manually. It is more systematic.

4) Other advantages:
Initially constructing the software may require more time, but
afterwards it saves administrators valuable time.
So our goal is to save the time in managing the system.
While managing the system manually there are many chances
of errors. So with the computerization the efficiency, accuracy
increases.

E Library

The main goal of building the software is to provide the

efficiency of user. By having availability of data one can
manage the system very easily.

E Library

Proposed System

The

traditional

library

has

many

disadvantages

of

geographical restrictions, physical presence, limitation of

books, condition of books etc. . .

E-library i.e. electronic library or digital library overcomes all

these disadvantage. Systematic collection of various subject
books is maintained in e-library.

Thus this project consists well mannered collection of

various books.

E Library

Goal of e-library system

Here are some of the potential benefits of digital libraries.

The digital library brings the library to the user

Computer power is used for searching and browsing

Information can be shared

Information is easier to keep current

The information is always available

New forms of information become possible

E Library

Process List
E library processes

1.0

MASTER DB MAINTENANCE
1.1

USER DB
1.1.1 CREATE
1.1.1.1

GENERATE UID

1.1.1.2

VALIDATE USER DETAILS

1.1.2 PASSWORD VALIDATION

1.1.2.1

ACCEPT

1.1.2.2

VALIDATE

1.1.2.3

CONFIRM

1.1.2.4

ASSIGN

1.1.3 ASSIGN PREVILIGES

1.1.4 MODIFY
1.1.4.1

USER SELECTION

1.1.4.2

MODIFY USER

1.1.4.3

CHANGE PASSWORD

1.1.4.4

UPDATE

1.1.5 DELETE
1.1.5.1

USER SELECTION

1.1.5.2

CHECK DEPENDICIES

1.1.5.3

CONFIRM DELETION

1.1.5.4

UPDATION

E Library
1.2

CATEGORY AND SUB CATEGORIES

1.2.1 ADMINISTRATOR LOGIN
1.2.2 CATEGORY CREATION
1.2.2.1

GENERATE CATEGORY ID

1.2.2.2

ASSIGN DESCRIPTION

1.2.2.3

UPDATE DESCRIPTION

1.2.3 CATEGORY MODIFICATION

1.2.3.1

CATEGORY SELECTION

1.2.3.2

DISPLAY DESCRIPTION

1.2.3.3

VALIDATE DESCRIPTION

1.2.3.4

UPDATE CATG DB

1.2.4 DELETE CATG

1.2.4.1

SELECTION

1.2.4.2

DISPLAY DETAILS

1.2.4.3

CHECK DEPEDENCIES

1.2.4.4

CONFIRM DELETION

1.2.4.5

UPDATE DB

1.2.5 SUB CATG CREATION

2.0

1.2.5.1

CATG SELECTION

1.2.5.2

GENERATE SUB CATG ID

1.2.5.3

VALIDATE SUBCATG DETAILS

1.2.5.4

UPDATE SUB CATG DB

REFERENE MATERIAL UPDATION

2.1

EXPERT LOGIN

2.2

CATEGORY SELECTION

E Library

3.0

2.3

SUB CATEGORY SELECTION

2.4

SUBJECT SELECTION

2.5

VALIDATE REFERENCE MATERIAL DETAILS

2.6

UPDATE REFERENCE MATERIAL DB

MATERIAL BROWSER
3.1

DISPLAY CATEGORIES

3.2

CATEGORY SELECTION

3.3

DISPLAY SUBCATEGORIES

3.4

SUB CATEGORY SELECTION

3.5

DISPLAY SUBJECTS

3.6

SUBECT SELECTION

3.7

DISPLAY REFERENCE MATERIAL LIST

3.8

REFERENCE MATERIAL SELECTION

3.9

OPEN REFERECE MATERIAL

3.10 DISPLAY MATERIAL

4.0

SEARCH PROCESS
4.1

DISPLAY SEARCH CRITERIA

4.2

VALIDATE SEARCH CRITERIA

4.3

CONSTRUCT QUERY

4.4

EXECUTE QUERY

4.5

DISPLAY RESULT

SCOPE
MASTER DB MAINTENANCE:

E Library

It basically consists of user DB and category and subcategories.

User DB can create

generation of uid and validate user

details.
Password validation accepts, validates, confirms and
assigns.
Assign privileges is possible.
Modifying

user selection, modify user, change password,

update.
modify -user selection, user, change password and update is
possible.

Category and sub-category consists of administrator

login.
As well as category creation has generating category id,
assigning description, updating description.
Category

modification

has

category

selection,

displaying

description, validation description, update catg DB.

Delete catg has selection , and display details, checks
dependencies ,and confirms deletion, updates DB.

E Library

Sub catg creation has catg selection, generate sub- catg id,
and validation of sub catg details and also updates su catg
DB.
REFERENCE MATERIAL UPDATION:
It basically consists of

expert login, category selection,

subject selection, validation of reference material details,

updation of reference material DB.

MATERIAL BROWSER:

Material

browser

performs

events

like

displaying

categories, category selection, displaying sub-categories, sub

category selection, display reference material list, reference
material selection, and then open the the reference material
and lastly displaying the reference material.

SEARCH PROCESS:
It consists of displaying search criteria ,the validation of
search criteria, construct query, execute query, and then
finally displaying the result.

E Library

Features

Transformation of Library system from Manual to Web Based

gives many features some o them are as follows

Easy to understand and operate.

Supports web as well as local area network.
Platform independent
Huge storage capacity
Speedy operations
Automated report Generation

E Library

ADVANTAGES:
The following are the advantage of e-library:

1) It faces no geographical limitations.

2) No space constraint for reference material.

3) No limitation on number of users.

4) Very economic system as no need of staff members, no

infrastructures, availability for 24*7

5) Large diversity of subject covered is possible.

6) This system can run on internet as well as on LAN.

7)

Within

possible.

minimum

resources

,maximum

utilization

is

E Library

Feasibility study

The feasibility study is useful to evaluate cost and

benefits of a system requested. The feasibility study tries to
anticipate future scenarios of software development.
The feasibility study is carried out by a group of people
who are familiar with the information system techniques,
understand a part of the business that will be involved in the
project and are skilled in system analysis and design process.
It is carried out to understand that whether the requested
system is feasible. There are three aspects in the feasibility
study-

1) Technical Feasibility:

It goes into the details like- can the work for the project with
the

current

technology

equipment

and

available

hardware,

manpower.

existing
Following

software
hardware

software requirement is finalized after assessing its Technical

Feasibility.

E Library

Hardware software requirement for better performance

Hardware:

Processor

Any Pentium III or higher processor

RAM

: Minimum 256 MB or higher.

Disk Space : Minimum 20 GB.

Internet connection

Software:

Operating System

: certified distributions of LINUX

Language

: JDK 1.5

Back End

: postgresql

INTERFACE

: JSP

Web server

: Apache Tomcat 4.1 or Higher

2) Economic Feasibility:
This study deals with are there sufficient benefits in
creating the system to make the cost acceptable or is the cost

E Library

of not creating the system so great that the project has to be

undertaken. We have developed this software using open
source and free ware java so after detailed testing this project
will be available as freely downloadable utility.

3) Operational Feasibility:

Will the system be used if it is developed and implemented?

Will there be resistance from the users to the new system.
Our system is easy to understand easy to operate input
designs are similar to typical queries so this project is
operationally very much feasible.

E Library

Fact Finding Technique

Information gathering for a large and complex system can be
an onerow task. Information must be gathered in organized
way to ensure that nothing is overlooked and that all system
detail is eventually captured.
Before beginning search a system study, an analyst or tem of
analyst must establish a search strategy for gathering the
information needed to develop a model of system.
We used four fact finding techniques in our system analysis:
1.Questionnaires
2.Interviews
3.Record Reviews
4.Observation

1 )Questionnaires:
We used this technique in the initial and final phases of
our project. In the initial phases we prepared questionnaires to
get some basic information about the current system.
Questions asked were both open ended and close ended.
Which were related to user's interaction with current system,
updation and rules for record maintenance, reports generated

E Library

by current system, complications in the system as per the

user.

2)Interviews:
We used this technique frequently in the system analysis
after questionnaires. The interviews were unstructured.

Interview with
Mr. Joshi (Librarian)
Library Incharge
Maharashtra Collge

1) How the system functions?

=>

The students pay for joining library. I give the

library card to that student. Then the name of that

student will be registered
into registration book. Then issue of books for that
particular student can be done henceforth.

E Library

2) What is the most tedious task u face?

=>

i)Our library contains many books. So when

anyone comes to borrow the book, then searching for the

particular book is the most tedious job and it is most time
consuming also.
ii)Another most hectic job is maintenance of all
books, because improper handling of books causes wear an
tear of books which ends up in extreme bad condition of
books . So purchasing new books and maintenance of
them is become very costly.
iii) A more time consuming job is to be done of fine
calculating when students does not return the issued
books in the fixed time span or in intact mannar.

3) Do u feel that students have to face the problems

due to this manual system?
=>i) Yes, definitely, because of limited space we
cannot afford the huge amount of reference material. We
have to keep limited editions of books.

E Library

ii) Another thing is that the students have to

return the book within a limited time span weather that
student wants that book for long time or not.
iii) one biggest problem is that the students physical
presence is extremely necessary at the time of issuing or
return the book.

3)Record Review
This was the most beneficial technique for us while making
our database. We studied the existing file structures,
documents used and generated in the organization. For every
individual piece of information in these files or registers we
tried to identify its significance, need, relation with other data
items and any other features.
We collected documents format for
1) Sections and Subjects
2) Book register
3) Issue register and card
4) Return Register and card

E Library

5) Library Card
6) Fine Receipt

4)Observation
While finding the facts we keenly observed all the activities in
the organization. We paid attention to the transactions, usage
of files and documents, the record keeping and the handling of
queries in

the existing system. Observations helped us in

finding out the actual way functioning apart from the ideal or
desired. This helped us mainly in he interface design.

E Library

PROCESS CHART:

E Library

E Library

E Library

E Library

DATA FLOW DIAGRAM

E Library

E Library

E Library
ENTITYRELATIONSHIP-DIAGRAM

DATA DICTIONARY

CATEGORY:

E Library

Sr.no

Attribute

Key status

Data type

Description

1.

name
c_id

Primary key

integer

Unique

text

assigned
Category

2.

name

key

name

SUB-CATEGORY:

Sr.no.

Attribute

Key status

Data type

Description

1.

name
sc_id

Primary key

integer

Unique

Text

assigned
Sub-category

Foreign key

integer

name
Category id

2.
3.

name
c_id

key

REF-MATERIAL:

Sr.no

Attribute

Key status

Data type

Description

1.

name
r_id

Primary key

integer

Unique

text
text

assigned
Type
Path

2.
3.

r_type
r_path

key

E Library
4.
5.
6.

r_link
e_id
sc_id

Foreign key
Foreign key

Text
Integer
Integer

Link
Expert id
Sub-cat id

Sr.no

Attribute

Key status

Data type

Description

1.

name
e_id

Primary key

Integer

Unique

Text
Text

assigned
Expert name
Expert

Integer

address
Expert

EXPERT:

2.
3.
4.

e_name
e_add
e_phno

key

c_id

Foreign key

integer

phone no.
Category id

Sr.no

Attribute

Key status

Data type

Description

1.

name
reg_id

Primary key

integer

Unique

Text
text
date
Text
text

assigned
First name
Last name
Date of birth
Gender
City

5.

USER:

2.
3.
4.
5.
6.

first_nm
last_nm
date_of_birth
gender
city

key

E Library
7.
8.
9.

county
email_id
password

SCREEN-INFO:

text
varchar
varchar

Country
Email-id
password

E Library

E Library

E Library

E Library

E Library

E Library

E Library

E Library

E Library

Table Structures

Category:

c_id (*)
name
path

sub-cat:

sc_id (*)
name
path
c_id (foreign key)

expert:

e_id (*)
e_name
e_add
e_pno
c_id (foreign key)

ref_material: r_id (*)

E Library

r_type
r_path
r_link
e_id (foreign key)
sc_id (foreign key)

registration: reg_id (*)

first_nm
last_nm
date_of_birth
gender
city
country
email_id
password

Technology Used
After studying and finalizing the scope, in the
technical feasibility we have analyzed possibility of using

E Library

different JAVA technologies, and we have decided this

architecture to maintain following features from programming
point of view

1) JAVA to facilitate OOP programming style with platform

independence.
2) JSP for web interface which will facilitate dynamic page
generation.
3) Beans to use OOP method in better way.
4) Apache TOMCAT which is freeware and reliable to facilitate
WEB SERVER functions.
5) Freeware Postgresql as a backend DB because of its
scalability and platform indeedence.
6) Freeware XML because of its platform independence,
storage capacity, flexibility and efficiency.

JSP (Java Server Pages)

It is an extension of

servlet

technology. This simplify the

delivery of dynamic web content . We can use java beans and

E Library

create custom tag libraries that encapsulates complex and

dynamic functionality.
There are four components of JSP Directives, Actions,
scriptlets, Tag libraries.
Java Server Pages look like standard

XHTML or XML

document. In most of the cases Servlet and JSP technologies

are interchangeable. As with servlets, JSPs normally execute
as part of the web server.

E Library

JSP is an extension of Java Servlet technology

which combines Java server-side programs and
HTML.
It is a server side scripting language.
Java Server Pages (JSP) is normal HTML with Java
code pieces embedded in them.
A JSP compiler is used to compile JSPs into Java
Servlets.

E Library

A JSP compiler may generate a servlet in Java

code that is then compiled by the Java compiler,
or it may generate byte code for the servlet
directly.
Use of JSP
JSP technology is used to create dynamic web
pages, XML/Html documents.
For accessing database information on a Web
server

To generate and consume XML between n-tier

servers or between servers and clients

E Library

We are using JSP, since our application is Web Based. We

need

technology

which

provides

Intra/Internet

supports & JSP is perfect technology for this.

TOMCAT

The servlet and jsp part of Jakarta project is called tomcat.

This is the official reference implementation of JSP and
servlets standerds .
Tomcat is a web server that supports servlets
and JSPs. The accompanying Tomcat Jasper compiler compiles
JSPs into servlets.The Tomcat servlet engine is often used in
combination with an Apache HTTP Server or other web
servers. Tomcat can also function as an independent web
server. Earlier in its development, the perception existed that
standalone

Tomcat

environments

and

was
other

only

suitable

environments

for

development

with

minimal

E Library

requirements for speed and transaction handling. However,

that perception no longer exists; Tomcat is increasingly used
as a standalone web server in high-traffic, high-availability
environments.
Tomcat is cross-platform, running on any operating system
that has a Java Runtime Environment

JDBC
The JDBC API is the industry standard for databaseindependent connectivity between the Java programming
language and a wide range of databases. The JDBC API
provides a call-level API for SQL-based database access.
JDBC technology allows you to use the Java programming
language to exploit "Write Once, Run Anywhere" capabilities
for applications that require access to enterprise data.

JDBC API Overview

E Library

The JDBC API makes it possible to do three things:

Establish a connection with a database or access any

tabular data source

Send SQL statements

Process the results

JDBC Architecture
The JDBC API contains two major sets of interfaces: the first
is the JDBC API for application writers, and the second is the
lower-level

JDBC

technology

drivers

driver
fit

API
into

for
one

driver
of

writers.

four

JDBC

categories.

Applications and applets can access databases via the JDBC

API using pure Java JDBC technology-based drivers, as
shown

in

this

figure:

E Library

Left

side,

Type

4:

Direct-to-Database

Pure

Java

Driver

This style of driver converts JDBC calls into the network

protocol used directly by DBMSs, allowing a direct call from
the client machine to the DBMS server and providing a
practical

solution

for

intranet

access.

Right side, Type 3: Pure Java Driver for Database Middleware

This style of driver translates JDBC calls into the middleware
vendor's protocol, which is then translated to a DBMS
protocol by a middleware server. The middleware provides
connectivity

to

many

different

databases.

The graphic below illustrates JDBC connectivity using ODBC

drivers

and

existing

database

client

libraries.

E Library

Left

side,

Type

1:

JDBC-ODBC

Bridge

plus

ODBC

Driver

This combination provides JDBC access via ODBC drivers.

ODBC binary code -- and in many cases, database client
code -- must be loaded on each client machine that uses a
JDBC-ODBC Bridge. Sun provides a JDBC-ODBC Bridge
driver, which is appropriate for experimental use and for
situations

in

which

no

other

driver

is

available.

Right side, Type 2: A native API partly Java technology-enabled driver

This type of driver converts JDBC calls into calls on the client
API for Oracle, Sybase, Informix, DB2, or other DBMS. Note
that, like the bridge driver, this style of driver requires that
some binary code be loaded on each client machine.

E Library

POSTGRESQL
We commonly get a question about why we use PostgreSQL
or what the difficulty is to move to another database. While I
do not know the original design reasons to use PostgreSQL,
I do know the reasons we continue to use it, which are listed
below. We do plan to eventually convert to Hibernate, which
will provide database independence, but there is not yet a
solid plan for doing so.
Why?
1. It's a mature, fast, enterprise-quality open-source
database.
2. It's what we've always used (i.e.: inertia). There are a
number

of

PostgreSQL-specific

ties

which

make

migration to another database a non-trivial process.

Here is a (possibly incomplete) list of such ties:
o

"IPLIKE" comparison function: this is written in C

and loaded in the database to provide LIKE-like
functionality for IP addresses, e.g.: "192.168.*.*".

PL/PgSQL

stored

procedures

for

performing

database-intensive operations involving availability

calculations.
o

Installer database-related code

E Library

General Advantages
There are several key advantages of using PostgreSQL:
1. PostgreSQL is free, Open Source software
2. PostgreSQL has excellent commercial and community
support options
3. PostgreSQL has legendary reliability and stability
4. PostgreSQL is very scalable and extensible
5. PostgreSQL is cross platform
6. PostgreSQL is designed for high volume environments
7. PostgreSQL is easy to administer

BIBLIOGRAPHY

1. Comlpete Reference Java 2.

By Nauguto Schilt.
2. Java 2 (Black Book).

E Library

By Steven Holzner.
3. Comlpete Reference SQL.
By Groff Weinburg.
4. JDBC & Java.
By George Reese
Web Sites