LIBRARY MANAGEMENT

INTRODUCTION
Library Management System is a windows application written for 32-bit Windows operating systems, designed to help users maintain and organize library. Our software is easy to use for both beginners and advanced users. It features a familiar and well thought-out, an attractive user interface, combined with strong searching Insertion and reporting capabilities. The report generation facility of library system helps to get a good idea of which are the books borrowed by the members, makes users possible to generate reports hard copy. The software Library Management System has four main modules. Insertion to Database Module User friendly input screen Extracting from Database module Attractive Output Screen Report Generation module borrowed book list & Available book list Search Facility system search for books and members

LIBRARY MANAGEMENT

SYSTEM ANALYSIS

EXISTING SYSTEM
System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system. During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are required 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. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs.

System analysis can be categorized into four parts. System planning and initial investigation Information Gathering Applying analysis tools for structured analysis Feasibility study Cost/ Benefit analysis.

In our existing system all the transaction of books are done manually, So taking more time for a transaction like borrowing a book or returning a book and also for searching of members and books. Another major disadvantage is that to preparing the list of books borrowed and the 2

LIBRARY MANAGEMENT available books in the library will take more time, currently it is doing as a one day process for verifying all records. So after conducting the feasibility study we decided to make the manual Library management system to be computerized.

PROPOSED SYSTEM
Proposed system is an automated Library Management System. Through our software user can add members, add books, search members, search books, update information, edit information, borrow and return books in quick time. Our proposed system has the following advantages. User friendly interface Fast access to database Less error More Storage Capacity Search facility Look and Feel Environment Quick transaction

All the manual difficulties in managing the Library have been rectified by implementing computerization. Flexibility: the system should be modifiable depending on the changing needs of the user. Such modifications should entail extensive reconstructing or recreation of software. It should also be portable to different computer systems. Security: This is a very important aspect and I have tried to cover the areas of hardware reliability, fallback procedures, and physical security of data. So the main features of the proposed system are: Fast Member Registration- Through this software the registration process of the individual becomes quite faster and is done at the fast pace. Easy to retrieve the data- By making the proposed system computerized the retrieval of data is very fast and easy. Fast updating- In the proposed system the modifications on the records can be done very easily and at fast pace.. Centralization of the data- All the data would be stored in the database and so keeping and storing of records is easy.

LIBRARY MANAGEMENT Auto Generation-Auto generation of the various certificates and reports on just one click.

FEASIBILITY ANALYSIS
Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility. Technical Feasibility: We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already. Economical Feasibility Development of this application is highly economically feasible .The organization needed not spend much m one for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. I f we are doing so , we can attain the maximum usability of the corresponding resources .Even after the development, the organization will not be in a condition to invest more in t he organization. Therefore, the system is economically feasible.

LIBRARY MANAGEMENT

FUNCTIONAL REQUIREMENTS
Login This allows the user to login to the library management system. Add Book The librarian can add new books to the library management record. Delete Book The librarian can delete those books from the record which are lost, damaged, or not to be issued. Search Books The librarian can search the record of books available in the library. Members also have the capability to search books to see whether a book is available in the library or not. Request Book The member can update a request for a book that he needs on the system. This request shall be completed by the librarian when possible. A student can make only one book request at a time. Next request can be made only when the previous request is completed. Issue Book The librarian can issue a book to the library members. Each time a book is issued to a member, its quantity is reduced by one in the record. Return Book When librarian gives command to return a book to the library, its quantity will be incremented by one in the library record. Update Book Librarian can change the attributes of books stored in the library such as edition, number of available books etc. from time to time. Add Member The librarian will add new member to the library management system by filling his member id, name, d.o.b. etc. and providing a user name and password to the member.

LIBRARY MANAGEMENT Delete Member This function is used to delete a member from the record if he has to leave the library membership. Search Member The librarian can search the members of the library and see the information related to a member. Update Member The librarian can update the information regarding a member if any change has taken place for example a member may want to change his phone number or his address. Check Member Status The librarian can check how many books have been issued to each member and for how much time till date. Check Book Status The librarian can see the book status that how many copies of each book are available in the library, how many have been issued to members and to which member those books are issued. Impose Late Fine The librarian can impose late fine if a book is not returned to the library up to the due date. Send Email to Member The librarian can send an e-mail to a member if a book issued to that member is required to be returned prior to the due date due to some reason. He can also send some other information regarding the library to the members.

LIBRARY MANAGEMENT

SYSTEM DESIGN
INPUT DESIGN
Input design is the process of converting user-oriented input to a computer based format. Input design is a part of overall system design, which requires very careful attention .Often the collection of input data is the most expensive part of the system. The main objectives of the input design are 1. Produce cost effective method of input 2. Achieve highest possible level of accuracy 3. Ensure that the input is acceptable to and understood by the staff.

Input Data
The goal of designing input data is to make enter easy, logical and free from errors as possible. The entering data entry operators need to know the allocated space for each field; field sequence 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 .Here data entry is online; it makes use of processor that accepts commands and data from the operator through a key board. The input required is analyzed by the processor. It is then accepted or rejected. Input stages include the following processes Data Recording Data Transcription Data Conversion Data Verification Data Control Data Transmission Data Correction

LIBRARY MANAGEMENT One 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.

OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the users. Designing computer output should proceed in an organized well through out the manner. The right output must be available for the people who find the system easy o use. The outputs have been defined during the logical design stage. If not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc, Various types of outputs are External outputs Internal outputs Operational outputs Interactive outputs Turn around outputs

All screens are informative and interactive in such a way that the user can full fill his requirements through asking queries.

LIBRARY MANAGEMENT

DATABASE DESIGN
The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. After designing input and output, the analyst must concentrate on database design or how data should be organized around user requirements. The general objective is to make information access, easy quick, inexpensive and flexible for other users. During database design the following objectives are concerned: Controlled Redundancy Data independence Accurate and integrating More information at low cost Recovery from failure Privacy and security Performance Ease of learning and use

LIBRARY MANAGEMENT

DATA FLOW DIAGRAMS

10

LIBRARY MANAGEMENT

FIG: CONTEXT DIAGRAM

11

LIBRARY MANAGEMENT

12

LIBRARY MANAGEMENT

FIG: 0 LEVEL DFD

FIELDS REQUIRED
The functional requirements of the library management system are stated above. According to these requirements, certain information will be stored in the database and will be accessed from time to time. Information stored in the library management record will be related to the books, members, librarians, borrowed books and librarian according to the system requirements. All these fields are given below:

Information related to Books

Book id Title Publisher Edition ISBN Number of books available Shelf number Subject Author Copyright Pages Number of books Available or not Borrowed by which members

Information related to Members

MemberId User Name Email Address Status Number of Books Books Borrowed Password Name Phone Number Blood Group Member Type Total Fine Date of borrow and return 13

LIBRARY MANAGEMENT Fine imposed if any at return Request made

Information related to Librarian

Librarian ID Password Email Address Shift User Name Name Phone Number Status

ER DIAGRAM

14

LIBRARY MANAGEMENT

15

LIBRARY MANAGEMENT

NORMALIZATION
Book Details Member Details Librarian Details Id, Subject, Title, Shelf, Id, Name, Email, Phone, Id, Name, Email, Phone, Author, Right, Publisher, Edition, Copy Address, Password, Blood Address, Password, User Total, Group, User Name, Type, Name, Blood Group, Shift Total Fine, Request, Book Issued, Issue Date, Return Date

Available, ISBN, Pages

1st NORMAL FORM:

All tables should have atomic values.

Table Name: Book Book Book Id, Subject, Title, Shelf, Author, Publisher, Copy Right, Edition, Total, Available, ISBN, Pages Functional Dependencies: BookID Title, BookID Subject, BookIDAuthor, BookID Publisher BookIDCopy Right, Book ID Edition, BookID Total, BookIDAvailable, BookIDISBN, BookIDPages

Table Name: Member 16

LIBRARY MANAGEMENT Member MemberID, User Name, Book ID, Name, Email, Phone, Address, Password, Blood Group, Type, Total Fine, Request, Book Issued, Issue Date, Return Date Functional Dependencies: MemberIDName, MemberIDUser Name, MemberIDPhone, MemberIDAddress, MemberIDBlood Group, MemberIDEmail, MemberIDTotal Fine, MemberID Type, MemberIDRequest, MemberID, Book IDBook Issued, MemberID, BookIDIssue Date, MemberID, BookIDReturn Date, UserNamePassword Table Name: Librarian Librarian Librarian ID, User Name, Name, Email, Phone, Address, Password, Blood Group, Shift Functional Dependencies: LibrarianIDUser Name LibrarianIDName LibrarianIDEmail LibrarianIDPhone LibrarianIDAddress LibrarianIDBlood Group LibrarianIDShift User NamePassword

2nd NORMAL FORM:

17

LIBRARY MANAGEMENT Tables should be in 1st normal form, All non key attributes should be fully functionally dependent on the primary key

Table Name: Book Book Book Id, Subject, Title, Shelf, Author, Publisher, Copy Right, Edition, Total, Available, ISBN, Pages Full Functional Dependencies: BookID Title, BookID Subject, BookIDAuthor, BookID Publisher BookIDCopy Right, Book ID Edition, BookID Total, BookIDAvailable, BookIDISBN, BookIDPages Table Name: Member Member MemberID, Name, Email, Phone, Address, Blood Group, Type, Total Fine, Request, Book Issued, Issue Date, Return Date Full Functional Dependencies: MemberIDName, MemberID Phone, MemberID Address, MemberID Blood Group, MemberID Email, MemberIDRequest, MemberID Type, MemberIDTotal Fine Table Name: Librarian 18

LIBRARY MANAGEMENT Librarian Librarian ID, Name, Email, Phone, Address, Blood Group, Shift Full Functional Dependencies: LibrarianIDName LibrarianIDEmail LibrarianIDPhone LibrarianIDAddress LibrarianIDBlood Group LibrarianIDShift Table Name: Borrow Borrow TransactionID, Book ID, Member Id, Issue Date, Return Date, Fine Full Functional Dependencies: TransactionID Member Id, TransactionID Book ID, TransactionID Issue Date, TransactionID Return Date, TransactionID Fine

Table Name: Login Login User Name, MemberID/Librarian ID, Password

Full Functional Dependencies: UserName, MemberID/LibrarianIDPassword

3rd NORMAL FORM:

Tables should be in 2NF, 19

LIBRARY MANAGEMENT There should be no transitive dependency

The Borrow table has transitive dependency as shown below: TransactionID Member Id, TransactionID Book ID, MemberId, BookIDIssue Date, MemberId, BookID Return Date, MemberId, BookID Fine It is divided as follows: Table Name: Transaction Transaction MemberID, BookID TransactionID Dependencies: MemberID, BookID TransactionID Table Name: Borrow Borrow TransactionID, IssueDate, ReturnDate, Fine Dependencies: TransactionIDIssueDate, TransactionIDReturnDate, TransactionIDFine

The Login table has transitive dependency as stated below: UserNamePassword, MemberId/LibrarianIDUserName 20

LIBRARY MANAGEMENT Thus we divide this table into two tables: Table Name: User User MemberID/LibrarianID, UserName Dependencies: MemberID/LibrarianIDUserName Table Name: Login Login UserName, Password Dependencies: UserNamePassword

TABLES CREATED
The following tables are created in the database after normalization:

21

LIBRARY MANAGEMENT

Table Name: Bookinfo

create table bookinfo (bookid number primary key, subject varchar(30), title varchar(30), author varchar(30), publisher varchar(30), copyright number, edition number, isbn number, total number, available number, shelf number)

Table Name: Librarian

create table librarian (librarianid number primary key, name varchar(30), email varchar(30), address varchar(30), shift varchar(1))

22

LIBRARY MANAGEMENT

Table Name: Members

create table members (memberid number primary key, name varchar(30), email varchar(30), phone number, address varchar(30), bloodgp varchar(3), type varchar(10), books number, totalfine number) 23

LIBRARY MANAGEMENT

Table Name: Users

create table users (memberid number, librarianid number, username varchar(30), foreign key (memberid) references members(memberid), foreign key (librarianid) references librarian (librarianid))

24

LIBRARY MANAGEMENT

Table Name: Login

create table login (username varchar(30) primary key, password varchar(30))

25

LIBRARY MANAGEMENT

Table Name: Transaction

create table transaction (memberid number, bookid number, transactionid number, foreign key(memberid) references members (memberid), foreign key(bookid) references bookinfo(bookid)) 26

LIBRARY MANAGEMENT

Table Name: Borrow

create table borrow (transactionid number primary key, issuedate date, returndate date, fine number)

27

LIBRARY MANAGEMENT

Book ID

Schema Diagram:
Subject Title Author BookInfo Publisher Copyright Edition ISBN Total Available Shelf Number Transaction TransactionID BookID MemberID

28

LIBRARY MANAGEMENT

Borrow TransactionID IssueDate ReturnDate Fine

Members Member ID Name Email PhoneNo Address BloodGp Type Books TotalFine Librarian Users UserName UserID Login UserName Password

Librarian Librarian ID Name Email Address Shift

OPERATIONS ON EACH TABLE

29

LIBRARY MANAGEMENT

According to different functions of the library management system, following functions will be performed on the database: Add Books: This is done by an insert operation on the books table. Eg. Insert into bookinfo values(1, cse, digital image processing, gonzaleaz, pearson, 465, 4, 1224, 20, 20, 4) Update Books: This is performed by an update operation on the books table. Eg. Update bookinfo set shelf=3 where bookid=1 Search Books: This is performed by a select operation on the books table. Eg. Select * from bookinfo where bookid=1

30

LIBRARY MANAGEMENT Add Member: This is done by an insert operation on the members and login table. Eg. Insert into members values(01, John, John@yahoo.com, 912435467335, 123 L New Dehli, B+, student, 2, 20, null) Insert into login values(john123, acbd123)

Login: This is performed by a select operation on the login table and matching the user name and password. Eg. Select password from login where username=john123

Update Member: 31

LIBRARY MANAGEMENT An update operation on the members table is used to perform this function. Eg. Update members set phone=913456735676 where memberid=1 Make Request: This is done by an update operation on the members table. Eg. Update members set request=software engineering pressman where memberid=1 Search Members: This is done by a select operation on the members table. Eg. Select * from members where memberid=1

Issue books:

32

LIBRARY MANAGEMENT This is performed by an insert operation on the borrow table and an update on the books and members table to decrement the number of available books and increment the number of borrowed books. Eg. Insert into transaction values (1, 1, 1) Insert into borrow values (1, 16-10-2012, 30-10-2012, null) Update bookinfo set available=available-1 where bookid=1 Update members set books=books+1 where memberid=1 Return books: This comprises of the following functions: An update operation on the books table by incrementing the number of books available and decrementing the borrowed books attribute of the member table. Eg. Update borrow set fine=5 where transactionid=1 Update bookinfo set available=available+1 where bookid=1 Update members set books=books-1 where memberid=1 See Book Status: This is performed by a select operation on the borrow table. Eg. Select * from borrow Delete Books: This function is performed by a delete operation on the books table. Eg. Delete from bookinfo where bookid=1 Delete Member: This is done by a delete operation on the members table. Eg. Delete from members where memberid=1

CONCLUSION
33

LIBRARY MANAGEMENT

Our project is only a humble venture to satisfy the needs in a library. This package shall prove to be a powerful package in satisfying all the requirements of the organization. The objective of software planning is to provide a frame work that enables the manager to make 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 work that played the ways to success but Almighty.

REFERENCES
34

LIBRARY MANAGEMENT

1. http://www.freestudentprojects.com/studentprojectreport/system-designdocumentation/system-design-of-library-management-system/

35