1

INTRODUCTION
The project titled Library Management System is Library management software for monitoring and controlling the transactions in a library .The project Library Management System is developed in java, which mainly focuses on basic operations in a library li e adding new member, new boo s, and updating new information, searching boo s and members and facility to borrow and return boo s.

Library Management System! is a windows application written for "#$bit %indows operating systems, designed to help users maintain and organi&e library. 'ur software is easy to use for both beginners and advanced users. (t features a familiar and well thought$out, an attractive user interface, combined with strong searching (nsertion and reporting capabilities. The report generation facility of library system helps to get a good idea of which are the boo s borrowed by the members, ma es users possible to generate reports) hard copy. The software Library Management System has four main modules.

(nsertion to *atabase Module + ,ser friendly input screen -.tracting from *atabase module + /ttractive 'utput Screen 0eport 1eneration module + borrowed boo list 2 /vailable boo list Search 3acility system + search for boo s and members

SYSTEM ANALYSIS

EXISTING SYSTEM:
System /nalysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. 4ere the ey 5uestion is$ what all problems e.ist in the present system6 %hat must be done to solve the problem6 /nalysis begins when a user or manager begins a study of the program using e.isting system.

*uring analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are *ata 3low *iagram, interviews, etc. Training, e.perience and common sense are re5uired for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. / good analysis model should provide not only the mechanisms of problem understanding but also the frame wor of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analy&ed thoroughly in accordance with the needs. System analysis can be categori&ed into four parts. System planning and initial investigation (nformation 1athering /pplying analysis tools for structured analysis 3easibility study

"

7ost8 9enefit analysis.

(n our e.isting system all the transaction of boo s are done manually, So ta ing more time for a transaction li e borrowing a boo or returning a boo and also for searching of members and boo s. /nother major disadvantage is that to preparing the list of boo s borrowed and the available boo s in the library will ta e more time, currently it is doing as a one day process for verifying all records. So after conducting the feasibility study we decided to ma e the manual Library management system to be computeri&ed.

PROPOSED SYSTEM
;roposed system is an automated Library Management System. Through our software user can add members, add boo s, search members, search boo s, update information, edit information, borrow and return boo s in 5uic proposed system has the following advantages. ,ser friendly interface 3ast access to database Less error More Storage 7apacity Search facility Loo and 3eel -nvironment <uic transaction /ll the manual difficulties in managing the Library have been rectified by implementing computeri&ation. time. 'ur

FEASI ILITY ANALYSIS

%hatever we thin need not be feasible .(t is wise to thin about the feasibility of any problem we underta e. 3easibility is the study of impact, which happens in the organi&ation by the development of a system. The impact can be either positive or negative. %hen the positives nominate the negatives, then the system is considered feasible. 4ere the feasibility study can be performed in two ways such as technical feasibility and -conomical 3easibility.

Te!"ni!a# Feasibi#ity: %e can strongly says that it is technically feasible, since there will not be much difficulty in getting re5uired resources for the development and maintaining the system as well. /ll the resources needed for the development of the software as well as the maintenance of the same is available in the organi&ation here we are utili&ing the resources which are available already. E!$n$mi!a# Feasibi#ity *evelopment of this application is highly economically feasible .The organi&ation needed not spend much m one for the development of t he system already available. The only thing is to be done is ma ing an environment for the development with an effective supervision. ( f we are doing so , we can attain the ma.imum usability of the corresponding resources .-ven after the development , the organi&ation will not be in a condition to invest more in t he organi&ation .There fore , the system is economically feasible.

>

%ARD&ARE CONFIGURATION

'r$!ess$r RAM %ar0 Dis1 M$nit$r 3ey $ar0 : :

'enti(m III )*+M%, -./ M .+G -2 C$#$r m$nit$r

-.. 3eys

SOFT&ARE CONFIGURATION

'perating System

@ %indows AT, %indows BC, %indows D;.

Language *atabase

@ Eava # 0untime -nvironment @ MS /ccess#FF?.

SYSTEM RE4UIREMENTS

This management system can be used in windows BC, %indows#FFF, %indows D; and %indows AT, supported for other platform such as /pplet, Macintosh and ,A(D. The system must be running %indows BC, %indows BC or %indows AT:.F operating system and must meet the following hardware re5uirements. 3or %indows B= based computers , a :C> 8 >> M4& or higher processor with CM9 3or %indows BC based computers , a =FF8CCM4& or higher processor with "# Mb of 0/M 3or %indows AT based computers , a :CC 8 >> M4& or higher processor with 1> M9 of 0/M 3or %indows #FF based computers , a ?FF8C=F M4& or higher processor with =1# M9 of 0am

DATA FLO& DIAGRAM

1F

11

1#

SOFT&ARE INTERFACE
A00 Ne5 $$1

Listing A## $$1s

1"

A6ai#ab#e $$1s

$rr$5e0

$$1s

Rem$6e $$1

1:

E0it

$$1 Detai#s

A00 a Member

1=

Listing a## Members

E0it a member

1>

Rem$6e a member

Sear!" 7$r Members an0 $$1s

9orrow 9oo s

1?

0eturning a 9oo

List of (ssued 9oo s

1C

0eserve a 9oo

SYSTEM DESIGN

IN'UT DESIGN
(nput design is the process of converting user$oriented input to a computer based format. (nput design is a part of overall system design, which re5uires very careful attention .'ften the collection of input data is the most e.pensive part of the system. The main objectives of the input design are G 1. ;roduce cost effective method of input

1B

#. /chieve highest possible level of accuracy ". -nsure that the input is acceptable to and understood by the staff. (nput *ata The goal of designing input data is to ma e enter easy, logical and free from errors as possible. The entering data entry operators need to now the allocated space for each fieldH field se5uence and which must match with that in the source document. The format in which the data fields are entered should be given in the input form .4ere data entry is onlineH it ma es use of processor that accepts commands and data from the operator through a ey board. The input re5uired is analy&ed by the processor. (t is then accepted or rejected. (nput stages include the following processes *ata 0ecording *ata Transcription *ata 7onversion *ata Ierification *ata 7ontrol *ata Transmission *ata 7orrection 'ne of the aims of the system analyst must be to select data capture method and devices, which reduce the number of stages so as to reduce both the changes of errors and the cost .(nput types, can be characteri&ed as. -.ternal (nternal 'perational 7omputeri&ed

#F

(nteractive (nput files can e.ist in document form before being input to the computer. (nput

design is rather comple. since it involves procedures for capturing data as well as inputting it to the computer.

OUT'UT DESIGN

'utputs from computer systems are re5uired primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .7omputer output is the most important and direct source of information to the users. *esigning computer output should proceed in an organi&ed well through out the manner. The right output must be available for the

#1

people who find the system easy o use. The outputs have been defined during the logical design stage. (f not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc,

Iarious types of outputs are -.ternal outputs (nternal outputs 'perational outputs (nteractive outputs Turn around outputs /ll screens are informative and interactive in such a way that the user can full fill his re5uirements through as ing 5ueries.

DATA ASE DESIGN

##

The general theme behind a database is to handle information as an integrated whole. / database is a collection of interrelated data stored with minimum redundancy to serve many users 5uic ly and effectively. /fter designing input and output, the analyst must concentrate on database design or how data should be organi&ed around user re5uirements. The general objective is to ma e information access, easy 5uic , ine.pensive and fle.ible for other users. *uring database design the following objectives are concerned@$

7ontrolled 0edundancy *ata independence /ccurate and integrating More information at low cost 0ecovery from failure ;rivacy and security ;erformance -ase of learning and use

#"

TA LES USED

Tab#e Name:

$$1s
Data Ty8e /utoAumber Te.t K"FL Te.t K"FL Te.t K#=L Te.t K#=L Aumber Aumber Aumber Te.t Aumber Aumber Aumber Te.tK#=L Mes8Ao Aumber Des!ri8ti$n ;rimary Jey $ $ $ $ $ $ $ $ $ $ $ $ $ $

Fie#0 Name 9oo (d Subject Title /uthor ;ublisher 7opyright -dition ;ages (S9A Aumber'f9oo s Aumber'f/vailble9oo s Aumber'f9orrowed9oo s Library /vailble ShelfAo

Tab#e Name:

$rr$5

#:

Fie#0 Name 9oo (d Member(* *ay'f9orrowed *ay'f0eturn

Data Ty8e Aumber Aumber *ate8Time *ate8Time

Des!ri8ti$n ;rimary Jey $ $ $

Tab#e Name: Members

Fie#0 Name Member(d (* ;assword A/M-M/(L Major Aumber'f9oo s Mony -.pired

Data Ty8e /utoAumber Aumber Te.tK1FL Te.tK#=L Te.tK#=L Te.tK1FL Aumber Aumber *ate8Time

Des!ri8ti$n ;rimary Jey $ $ $ $ $ $ $ $

SYSTEM IM'LEMENTATION
(mplementation is the stage in the project where the theoretical design is turned into a wor ing system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will wor efficiently and effectively. There are several activities involved while implementing a new project they are

#=

-nd user training -nd user -ducation Training on the application software System *esign ;arallel 0un /nd To Aew System ;ost implementation 0eview

En0 (ser Training: The successful implementation of the new system will purely upon the involvement of the officers wor ing in that department. The officers will be imparted the necessary training on the new technology. En0 User E0(!ati$n: The education of the end user start after the implementation and testing is over. %hen the system is found to be more difficult to under stand and comple., more effort is put to educate the end used to ma e them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this.

Training $7 a88#i!ati$n s$7t5are: /fter providing the necessary basic training on the computer awareness, the users will have to be trained upon the new system such as the screen flows and screen design type of help on the screen , type of errors while entering the data , the corresponding validation chec at each entry and the way to correct the data entered. (t should then cover information needed by the specific user or group to use the system.

#>

'$st Im8#ementati$n 9ie5: The department is planning a method to now the states of t he past

implementation process. 3or that regular meeting will be arranged by the concerned officers about the implementation problem and success

SOFT&ARE TESTING

(s the menu bar displayed in the appropriate contested some system related features included either in menus or tools6 *o pull +*own menu operation and Tool$ bars wor properly6 /re all menu function and pull down sub function properly listed 6H

#?

(s it possible to invo e each menu function using a logical assumptions that if all parts of the system are correct, the goal will be successfully achieved .6 (n ade5uate testing or non$testing will leads to errors that may appear few months later. This create two problem 1. Time delay between the cause and appearance of the problem. #. The effect of the system errors on files and records within the system The purpose of the system testing is to consider all the li ely variations to which it will be suggested and push the systems to limits. The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors and ensure that defined input will produce actual results that agree with the re5uired results. ;rogram level testing, modules level testing integrated and carried out. There are two major type of testing they are 1L %hite 9o. Testing. #L 9lac 9o. Testing.

&"ite $: Testing
%hite bo. some times called 1lass bo. testing! is a test case design uses the control structure of the procedural design to drive test case. ,sing white bo. testing methods, the following tests where made on the system

#C

/L /ll independent paths within a module have been e.ercised once. (n our system, ensuring that case was selected and e.ecuted chec ed all case structures. The bugs that were prevailing in some part of the code where fi.ed bL /ll logical decisions were chec ed for the truth and falsity of the values.

#a!1 b$: Testing

9lac bo. testing focuses on the functional re5uirements of the software. This is blac bo. testing enables the software engineering to derive a set of input conditions that will fully e.ercise all functional re5uirements for a program. 9lac bo. testing is not an alternative to white bo. testing rather it is complementary approach that is li ely to uncover a different class of errors that white bo. methods li e.. 1L (nterface errors #L ;erformance in data structure "L ;erformance errors :L (nitiali&ing and termination errors

CONCLUSION

#B

'ur project is only a humble venture to satisfy the needs in a library. Several user friendly coding have also adopted. This pac age shall prove to be a powerful pac age in satisfying all the re5uirements of the organi&ation.

The objective of software planning is to provide a frame wor that enables the manger to ma e reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the wor that played the ways to success but ALMIG%TY

I LIOGRA'%Y
1L http@88www.java#s.com8

"F

#L http@88www.javaworld.com8javaworld8jw$F1$1BBC8jw$F1$boo review.html 3) Database Programming with JDBC and Java by O'Reilly :L 4ead 3irst Eava #nd -dition =L http@88java.sun.com8javase8technologies8des top8