You are on page 1of 64

1. ABSTRACT

Library Management System (LMS) is basically intended at developing solution for providing an Library Management System for the students. LMS is basically intended to providing a library no extra man power requirement.

In such type of system everything starting from searching to issuing of books and maintenance of student profile and other database will be controlled totally by software. Hence here will be no need of extra registers and stationary for maintaining this.

Working of LMS starts from the issuing of books for students. If a student request for any book from library then the administrator can easily check, weather the requested book is available in library or not. He can also maintain the database of book issued to a particular student.

Requirement of student for a particular book can be in any form, for eg. He/She can ask about the book by just the publisher name or can ask about the book by just author name. To remembering about all author and all publisher is about to impossible for any person managing library. For keeping such type of problem in mind we are providing some very friendly search option for LMS. By these search option one can search the required book in just a second of time.

Here are some summarize reasons which increase the requirement of LMS over manual management of library.

Librarian manages all the books, journals etc. which is present in the library.

If anyone issue the books, librarian searched the student or faculty account manually which is time consuming.

Librarian

searched the

available of books in the library manually which is also time

consuming. Librarian faces difficulties for checking the status of books with different category.

If a book already issue and another person wants to that book. He makes a request for this book. Next time this book is issue to that person who is requested.

In library for manual entry for issuing books, checking due books, available books etc. requirement of persons more for managing the manual entries.

Librarian faces difficulties to list out the borrowed books or journals.

If anyone already a request for issuing book and he want to cancel them. So, that person delays to cancel the request.

There is a big issue for deciding the pending request which is first come.

1

There is a big issue for checking the issued books of a particular day or day wise.

Generation of results manually might result in errors.

In such a system for LMS for managing library, more and reliable search options can be provided for search the books that student needed. Some search options are follow ..

 

Searching by Title Searching by Keyword

Searching by Author

Searching by Corporate Source

We can also provide some advance search option to search the book in our library. Which increase the relevancy of user with the system of LMS.

 

Searching by Year of Publication

Searching the Subject Field

Searching for ISSNs, ISBNs, or other document numbers

The Library Management System will be overcoming the following mentioned problems and will be providing the following features:

All the books, journals etc. are divided into the different categories like departments, authors, publishers etc. So they can manage easily.

Searching of available book is comparatively faster then manual searching.

Checking the status of books with different categories made easy.

Showing the list of all the pending request of the books to be issued.

One or two person can manage the whole library very easily. So reduces man power.

See who has borrowed a particular book/ journal and when the due date for the same is.

Cancel the pending request made easy for a particular book/ journal.

As soon as a pending request is made for a particular book, that book is issued to the first come request.

This online system made easy to sort the issued books of a particular day or day wise.

Automatic reports will generate so; there is no probability of occurrence of the error.

2

Using manual working in managing library increases use of stationary and other physical copies for storing data. By developing this software we will be able to reduce this section of problem.

Keywords:

Issuing scheme

Difficulty level

Users

Books/ Journals

2. INTRODUCTION

Library Management System (LMS) will provide a basis for effective fulfillment of conducting online management of books as a replacement for the manual based entries which are used in the colleges. It is generic solution which is not specifically for S.I.T.E. but can be used by any college, school or institute.

LMS provides a very friendly searching, sorting and managing of books in our library system. LMS is developed for a rich user friendly environment. The only necessary condition for the usage of this software is that there should be following users:

Administrator : He is the person who will be responsible for maintaining the whole system. He will have access to the profile of every student, which will give the record of the books issued or pending on corresponding profile. He will be provided with the effective authorities and supervision of whole system. Administrator can be the Head of library, who will have full access to each student profile and also carry the responsibility for security to the same issues.

3

Student : He is the person who is the issuer of books from library. Library management system is totally based on the profile of student. Which books he is having now and for which is requesting in present will be the database for this system. Student profile will be maintained on the basis of a particular ID provided to them.

Requesting of book and processing that request time can be decreases in LMS. It can provide very effective searching and sorting techniques to search the books requested by students. Librarian just needs to put the author name/publisher name/ISBN no. of that book in a text box and books can be searched. Issuing of books can be done to a student by putting the ID of that student in another text box. All this can be done in very time effective manner. So by implementing the LMS service rate of library will be excellent

2.1 PROBLEM DOMAIN

There are certain problems prevailing presently while managing offline library which are as follows:

4

Right from managing books in library; issuing books, maintaining student profile; charging late fee; everything has to be done manually.

The librarian needs to keep record of books, journals, thesis and video-audio CD’s of various levels of different subjects manually.

Counting of books is to done manually.

All the information related to book like publisher name, author name, year of publication is hard to maintain each year. It also increases man work. And managing such a lot of information also hard for the staff of library.

Checking student profile in the various registers take a lot of time and also increase manual work.

If a Student asks for a particular book then there are many manual steps that are taken into account, such as showing library card, matching of library card no., searching of book and a lot more. These all steps are too much time consuming and hence service level of library decreases.

As all the tasks are performed in manual manner so more staff is required for managing library. It increases expenses on library system.

Student does not have any knowledge about the books that library owns.

All the departmental library does not have any connectivity and hence does not know about the matter owns by each other. It increases difficulty for students.

Maintaining the records of students walking through library is very hard to maintain by library staff.

Pending books database is hard to search in manual system. And hence late fee charged on student cannot remain in a proper way.

All departmental libraries does not have any a centralized system.

If a student request for a book that is not present in library, librarian has to maintain a separate database for such type of books.

If two or more student requests for a book that is not present in library then on being availability of these books, books will be distributed on the basis of priority of student who makes the request of book first. This is very hard to maintain in manual style.

5

If limited number of copies are available in library for a particular book and number of student requesting is more then number of book present in library then students have to suffer due to this problem.

2.2 SOLUTION DOMAIN

For the above problems stated in problem domain we can provide following solutions in our LMS.

Everything like management of book, issuing book and charging late fee does not required to be performed in manual manner.

All the record of library can be saved in a database system provided in LMS.

Only one time entry of each book is required in library and after that books can be counted by LMS

Information regarding books like Author name, publisher name is needed to save in database only for one time. And after that there is no need of keeping records in various registers and files. LMS provide self updating of books on various level.

Student will be provided a unique ID in LMS. On the basis of that id each student can be refined in very simple manner. Librarian can check about each and every record of that student associated with library.

Requesting of book and processing that request time can be decreases in LMS. We can provide very effective searching and sorting techniques to search the books requested by students. Librarian just needs to put the author name/publisher name/ISBN no. of that book in a text box and books can be searched. Issuing of books can be done to a student by putting the ID of that student in another text box. All this can be done in very time effective manner. So by implementing the LMS service rate of library will be excellent.

6

We just need to install LMS and there is only one or two person are requires for managing whole library system. And hence extra expenses on library can be utilized.

Every student can easily access the LMS for different types of book that are categories by author, department and publishers.

LMS contains information about all departmental libraries. So a interconnectivity link establishes among them. Student of different department can also access the books info for a different department.

A branch of LMS provides the information saving system for student walking through library. Students have to fill their ID in LMS at the time of entrance in library. By this library can keep record for all of such students.

By putting a student ID in the LMS, librarian can see every record about student. He can also see all info like pending books on that student, applied late fee charges on him.

LMS provides a interconnection link among all departmental library and with central library. By doing this all library in college will be centralized. And can share information with each other.

Books those are not in library and are requested by student can be maintained in LMS.

3.0 Feasible Study

3.1. Technical Feasibility

The technical feasibility of the system counts for the technical acceptance of the system. It refers to the ability of the process to take advantage of the current state of the technology in pursuing further improvement. The technical capability of the personnel as well as the capability of the available technology should be considered.

In technical feasibility the following issues are taken into consideration:

Whether the required technology is available or not?

The work for the project can be done wih the current equipment and existing software

technology that the organisation to use.

possessess.

.Net is used as a main technology which is easy

7

Whether the required resources are available?

The system does not have any rigid hard-ware and software requirements and there is availability of the people who can perform the software engineering activities required for the development of the system.

Hence, the system is technically feasible.

  • 3.2. Behavioral Feasibility

Behavioral feasibility is the measure that how effective the user uses the system. The behavioral efficiency is one of the major factors of feasibility analysis. The new or the proposed system should be easy to operate, convenient in maintenance and effective in its working. Thus behavioral feasibility is very important factor to be considered for effective working of system. Behavioral feasibility is dependent on human resources available for the project and involves projecting whether the system will operate and be used when installed. The system is behaviorally feasible if it fulfills the following:

  • 1. The proposed system is easy to operate.

  • 2. Existing members are not affected in anyway.

  • 3. Retrieval of information is easy, accurate and fast.

  • 3.3. Temporal Feasibility

Temporal feasibility means whether the project is completed in the given time or not. One of the most difficult aspects of project management is the formulation of estimates of the time required to develop a system. Estimates and time scheduling is an approximation of the hours, days, or months of efforts needed to produce the desired system. It depends on factors like programmer’s ability, program complexity etc.

8

4. Requirement Gathering

4.1 Questionnaires

Q-1: What is library?

Ans: A library is a collection of sources, resources, and services, and the structure in which it is housed; it is organized for use and maintained by a public body, an institution, or a private individual. In the more traditional sense, a library is a collection of books. It can mean the collection, the building or room that houses such a collection, or both. The term "library" has itself acquired a secondary meaning: "a collection of useful material for common use," and in this sense is used in fields such as computer science, mathematics, statistics, electronics and biology.

Q-2:Why use the online library?

Ans: The main reason for using the Online Library is that it has a wealth of quality academic material available to you for free. The University Library pays subscriptions to provide these resources - but

9

for you, the access is free. The Online Library will be an excellent source of academic peer-reviewed information for your research. When students search e-journal and e-book collections and other databases provided by the University, they know that the material they find will be scholarly and normally available in full text. This is just the type of material required to help produce a high quality dissertation or module assignment submission.

Q-3: How to login to use the online library?

Ans: We recommend you to login with your Managed Windows Service (MWS) username and password to the University portal for online students and staff .Once logged in you will have access to all Online Library resources. You can also access Library e-resources through the Online Library home page and, if you haven't already logged into the portal, you will find that when you connect to a Library e-resource you will be prompted to login.

Q-4: What is available on online library?

Ans: Collections of e-journals, newspapers and e-books.

Q-5: What to do if you have problems accessing an Online Library resource?

Ans: If you have a problem accessing an e-journal or database from the Online Library resources please NEVER contact the publisher or supplier yourself. Contact the Online Librarian and the Library will do this for you.

Q-6: How to access the resources of library and uses the benefits of online library?

Ans: You create your account first. After creating your account logged in to the online library portal with your username and your password. Then you are authenticated to access the resources of the library and take benefits of the library.

Q-7: What is Sign-In?

Ans: If you already have an account -- for instance, an email account --set up for you, you 'sign in' or 'sign on' using that existing account.

Q-8: What is Sign-up?

Ans: if you don't have an account, you 'sign up' by creating a new account.

Q-9: What features provides this Library Management system?

Ans: There are many features provides by this system.

User can place the request for issuing a specific book.

Librarian can see the list of issue book.

10

Librarian can see the list of request.

Online reading facility are available.

Q-10: How many user are there in the whole system?

Ans: There are five users are there in the whole LMS system.

Admin

Librarian

Student

Faculty

Publisher

4.2 Domain Data Dictionary

This document describes the tables and data elements within domains used within them Library Management System (LMS) database. It provides guidance on how values in each data element are formulated.

Login Detail

userId

Int

userName

Varchar(20)

password

Varchar(20)

11

   

userType

Int

4.2.2 User Detail

userCategoryId

Int

userId

Int

firstName

Varchar(20)

lastName

Varchar(20)

emailId

Varchar(50)

addressLine1

Varchar(50)

addressLine2

Varchar(50)

City

Varchar(20)

State

Varchar(20)

Country

Varchar(20)

telephoneNo

Varchar(20)

mobileNo

Varchar(20)

dateOfBirth

Date

departmentId

Int

gender

Int

4.2.3 Book Transaction

bookId

Int

bookTransactionId

Int

userId

Int

12

issueDate

Date

recieveDate

Date

issueTime

Date and Time

recieveTime

Date and Time

dueDays

Int

4.2.4

Book Detail

bookId

Int

bookCategoryId

Int

bookName

Varchar(20)

departmentId

Int

bookPublisher

Varchar(50)

bookPrice

Double

bookPublishYear

Varchar(20)

dateOfArrival

Date

noOfBook

Double

bookStatus

Int

bookISBN

Varchar(20)

4.2.5

Book Request

bookId

Int

userId

Int

requestId

Int

bookRequestStatusId

Int

bookRequestDate

Date

bookRequestTime

Date And Time

13

  • 4.2.6 Book Request Status

bookRequestStatusId

Int

bookRequestStatus

Varchar(50)

4.2.7

Department

departmentId

Int

 

departmentStatus

Varchar(50)

4.2.8

User Category

 

userCategoryId

Int

userCategory

Varchar(50)

4.2.9

Book Category

 

bookCategoryId

Int

bookCategory

Varchar(50)

Login detail:-It contains the detail of user-id, password and the type of login for every user.

Book request:-It contains the all request of the books, request date, time and status of the book.

Department:-It contains the department names.

14

Book-detail:-It contains the all detail of the book like book name, book sib, author name, price etc.

User-detail:-It contains user information like his name, address, e-mail id etc.

Book-transaction:-It contains the all information about book issue time, date, due days, receiving time, date etc.

User-category:-It contains the user category like he is admin, student, faculty etc.

Book-request:-It contains the all information about book-request.it contain pending book request.

Book-request Status:-It contains the all existing status for book-requested it contain pending book request

15

5.0 Requirement Analysis

5.1: Identify Entities

In the Library Management System (LMS), it contains following entities.

  • 5.1.1 Library

Library is a main entity which contains books and user entities.

  • 5.1.2 User

Library contains basically three types of users.

I.

Student

II.

Faculty

III.

Publisher

  • 5.1.3 Books

Books contain all types of items like journals, magazines and many more. It contains following attribute book price, book author, ISBN that unique of every book, Author etc.

  • 5.1.4 Status Of Issue

Status of issue tells the status of the issuing books to the available user in the LMS. It has following attributes issue date, issue time, due days, user id that defines this book is issued to which user.

  • 5.1.5 Status Of Return

Status of return tells the return status of issuing books to the available user in the LMS.

16

5.2

:Identify Actors

There are five actors in Library Management System.

 

I.

Admin

II.

Librarian

III.

Student

IV.

Faculty

 

V.

Publisher

5.3

Identify use cases

 

User

 

I.

Log-In:

17

After getting the username and password, end users can log on to their account and can access the website.

II.

Log-out:

After completing his/her work in the portal, he/she can sign out.

III.

Open Profile:

Librarian can open their profile which contains the personal details which he/she provided during sign up.

IV.

View Profile:

Librarian can view their profile which contains the personal details which he/she provided during signup.

V.

Edit Profile:

Librarian can update their profile which contains the personal details which he/she provided during sign up if any updating required.

VI.

Request Book: User may place a request for issuing books that book is already issued to another user.

VII.

Search Book: Student can search the books that are present in the library.

 

Librarian

 

I.

Log-In:

18

After getting the username and password, end users can log on to their account and can access the website.

II.

Log-Out:

After completing his/her work in the portal, he/she can sign out.

III.

Issue Books:

Librarian can issue one or more books to an user.

IV.

View Issued Books:

Librarian can view their issue books which he/she provided to the Student, Faculty or Publisher.

V.

Add Books:

Librarian can add new books in the library.

VI.

Edit Books:

Librarian can edit the books details those books are present in the library.

VII.

Delete Books:

19

Librarian can delete any book which is not present in the library.

Library Management Use-Case Model

5.4.1. Library Management System Use-Case Model Main Diagram:

Librarian can delete any book which is not present in the library. Library Management Use-Case Model

20

5.4.1.1 Use Case Description:

1.1 Admin:

1.1.1 Sign-in:

After getting the username and password, end users can log on to their account

and can access the website.

  • 1.1.2 Approve User:

He/she can approve the user (Student, Faculty, and Publisher) by seeing and

verifying the details of user.

  • 1.1.3 Block User:

He/she can block the user (Librarian, Student, faculty and Publisher) by seeing

and verifying the details of user.

  • 1.1.4 Send Mail:

He/she can send the mail to the user to tell the status of him.

  • 1.1.5 Sign-out:

After completing his/her work in the portal, he/she can sign out.

1.2 Librarian:

1.2.1 Signup:

In order to issue the books the Librarian must sign up by filling the sign

up form and get it approved by admin.

  • 1.2.2 Sign-in:

After getting the username and password, end users can log on to their

account and can access the website.

  • 1.2.3 Open profile:

Librarian can open their profile which contains the personal details

which he/she provided during sign up.

  • 1.2.4 View Profile:

21

Librarian can view their profile which contains the personal details which he/she provided during signup.

  • 1.2.4 Update Profile:

Librarian can update their profile which contains the personal details which he/she provided during sign up if any updating required.

  • 1.2.5 View Issued Books:

Librarian can view their issue books which he/she provided to the Student, Faculty or Publisher.

  • 1.2.6 Send E-mail:

Librarian can send e-mail which gives the information of not return the book in the given the time-period to the faculty, student or publisher.

  • 1.2.7 Sign-out:

After completing his/her work in the portal, he/she can sign out.

1.3 Student:

  • 1.3.1 Signup:

In order to issue the books user must sign up by filling the sign up form and get it approved by admin.

  • 1.3.2 Sign-in:

After getting the username and password, end users can log on to their account and can access the website.

  • 1.3.3 Open profile:

Student can open their profile which contains the personal details which he/she provided during sign up.

22

  • 1.3.4 View profile:

Student can view their profile which contains the personal details which he/she provided during signup.

  • 1.3.4 Update Profile:

Student can update their profile which contains the personal details which he/she provided during sign up if any updating required.

  • 1.3.5 View Books:

Student can view the books in the library.

  • 1.3.6 Issue Books:

Student can issue book from the library.

  • 1.3.7 Return Books:

Student can return the book in giving time period or before time-period.

  • 1.3.8 Search Book:

Student can search the book according his/her requirement.

  • 1.3.9 Reservation of the book:

Student can reserve the book if the book is issued to the other. The student reserves the book.

  • 1.3.10 Cancel the reservation:

Student also cancels reservation after he/she did not need the book.

  • 1.3.11 Sign-out:

After completing his/her work on the portal, he/she can sign out.

23

1.4 Faculty:

  • 1.4.1 Signup:

In order to issue the books user must sign up by filling the sign up form and get it approved by admin.

  • 1.4.2 Sign-in:

After getting the username and password, end users can log on to their account and can access the website.

  • 1.4.3 Open profile:

Faculty can open their profile which contains the personal details which he/she provided during sign up.

  • 1.4.4 View profile:

Faculty can view their profile which contains the personal details which he/she provided during signup.

  • 1.4.5 Update profile:

Faculty can update their profile which contains the personal details which he/she provided during sign up if any updating required.

  • 1.4.6 View Books:

Faculty can view the books in the library.

  • 1.4.7 Issue Book:

Faculty can also issue book from the library.

24

  • 1.4.8 Return Book:

Faculty can return the book in giving time period or before time-period.

  • 1.4.9 Search Book:

Faculty can search the book according his/her requirement.

  • 1.4.10 Reservation of book:

Faculty can reserve the book if the book is issued to the other. The student reserves the book. The faculty reservation has a highest priority.

  • 1.4.11 Cancel the reservation:

Faculty also cancels reservation after he/she did not need the book.

  • 1.4.12 Sign-out:

After completing his/her work on the portal, he/she can sign out.

1.5 Publisher:

  • 1.5.1 Signup:

In order to issue the books user must sign up by filling the sign up form and get it approved by admin.

  • 1.5.2 Sign-in:

After getting the username and password, end users can log on to their account and can access the website.

  • 1.5.3 Open Profile:

Publisher can open their profile which contains the personal details which he/she provided during sign up.

  • 1.5.4 View profile:

Publisher can view their profile which contains the personal details which

25

he/she provided during signup.

  • 1.5.5 Update profile

Publisher can update their profile which contains the personal details which he/she provided during sign up if any updating required.

  • 1.5.6 View Books:

Publisher can view the books in the library.

  • 1.5.7 Issue Book:

Publishers can also Issue Book from library

  • 1.5.8 Return Book:

Publisher can return the book in giving time period or before time-period.

  • 1.5.9 Search Book:

Publisher can search the book according his/her requirement.

  • 1.5.10 Reservation of the book:

Publisher can reserve the book if the book is issued to the other. The student reserve the book. The Publisher reservation has a highest priority.

  • 1.5.11 Cancel the reservation:

Publisher also cancels reservation after he/she did not need the book.

  • 1.5.12 Sign-out:

After completing his/her work in the portal, he/she can sign out.

26

Library Management Sequence Diagram

5.4.1 Library Management Sequence Diagram:

Case 1:

27

Case 2: 28

Case 2:

28

Case 3: Case 4: 29

Case 3:

Case 3: Case 4: 29

Case 4:

29

Case 5: Library Management Class Diagram 30

Case 5:

Case 5: Library Management Class Diagram 30
Case 5: Library Management Class Diagram 30

Library Management Class Diagram

30

5.4.3 Class Diagram

5.4.3 Class Diagram Library Management Collaboration Diagram 31

Library Management Collaboration Diagram

31

5.4.4 Library Management Collaboration Diagram:

Case 1:

5.4.4 Library Management Collaboration Diagram: Case 1: Case 2: 32

Case 2:

32

Case 3: Case 4: 33

Case 3:

Case 3: Case 4: 33

Case 4:

33

Case 5: 34

Case 5:

Case 5: 34

34

5.4.5

Activity diagram of each operation

AddStudent : add a new student

validateStudent

[ exists ]

return error

  • message

[ not exists ]
[ not exists ]

add the student record to Student table

5.4.5 Activity diagram of each operation ∑ AddStudent : add a new student validateStudent [ exists

return success

  • message

DeleteStudent : delete an existing student

validateStudent

[ not exists ]

return error

  • message

[ exists ]

delete the student record to Student table

5.4.5 Activity diagram of each operation ∑ AddStudent : add a new student validateStudent [ exists

return success

  • message

35

UpdateStudent : update information of existing student

Update the student record in

the Student table

the Student table

 
∑ UpdateStudent : update information of existing student Update the student record in the Student table

SearchStudent : search students

Query the student record

in Student table

return Resultset

∑ UpdateStudent : update information of existing student Update the student record in the Student table

36

ValidateStudent : validate student

∑ ValidateStudent : validate student Query the student in Student table according to studentID Return Resultset

Query the student in Student

table according to studentID

Return

Resultset

[ empty ]

Return false

[ not empty ]

∑ ValidateStudent : validate student Query the student in Student table according to studentID Return Resultset

Return true

∑ ValidateStudent : validate student Query the student in Student table according to studentID Return Resultset

addBook: Add a new book in database

37

Check Book record in database exist no Insert book record in database return success message yes
 
Check Book record in database exist no Insert book record in database return success message

Check Book record

 
 

in database

   
 
exist

exist

 
no

no

Insert book record

 
 

in database

 
Check Book record in database exist no Insert book record in database return success message
 

return success

 

message

Check Book record in database exist no Insert book record in database return success message yes

yes

Check Book record in database exist no Insert book record in database return success message yes

Return "Book already

exist" message

Check Book record in database exist no Insert book record in database return success message yes

exist: Check if the book record already exist in database.

38

Search Book record in database return not exist message found record? no yes return exist message

Search Book record in database

Search Book record in database return not exist message found record? no yes return exist message
return not exist message
return not exist
message
Search Book record in database return not exist message found record? no yes return exist message

found record?

no

Search Book record in database return not exist message found record? no yes return exist message
yes return exist message
yes
return exist
message

searchBook: Search books in database

Search Book record in database return not exist message found record? no yes return exist message

search book record in database

 
return resultset
 

return

resultset

 
return resultset
return resultset

39

updateBook: modify book info

∑ updateBook: modify book info update record in database return success message ∑ deleteBook: Delete a
 
∑ updateBook: modify book info update record in database return success message ∑ deleteBook: Delete a
 

update record in

database

 
∑ updateBook: modify book info update record in database return success message ∑ deleteBook: Delete a
 

return success

message

 
∑ updateBook: modify book info update record in database return success message ∑ deleteBook: Delete a
 
∑ updateBook: modify book info update record in database return success message ∑ deleteBook: Delete a
 

deleteBook: Delete a book in database

40

check existence no exist? yes delete the return fail record message return success message
check
existence
no
exist?
yes
delete the
return fail
record
message
return success
message
check existence no exist? yes delete the return fail record message return success message ∑ checkIn()

checkIn() : check in one book

41

SQL Statement (Update ..... ) Exception? Yes Print "error message" No return true return false ∑

SQL Statement

(Update ..... ) Exception? Yes Print "error message" No return true return false
(Update
.....
)
Exception?
Yes
Print "error
message"
No
return true
return false
SQL Statement (Update ..... ) Exception? Yes Print "error message" No return true return false ∑

checkOut() : check out one book

42

SQL Statement (Update ..... ) Exception? Yes Print "error message" No return true return false ∑

SQL Statement

(Update ..... ) Exception? Yes Print "error message" No return true return false
(Update
.....
)
Exception?
Yes
Print "error
message"
No
return true
return false
SQL Statement (Update ..... ) Exception? Yes Print "error message" No return true return false ∑

addTolist() : add one book to mylist

43

SQL Statement (Insert ..... ) Exception? Yes Print "error message" No return true return false ∑

SQL Statement

(Insert ..... ) Exception? Yes Print "error message" No return true return false
(Insert
.....
)
Exception?
Yes
Print "error
message"
No
return true
return false
SQL Statement (Insert ..... ) Exception? Yes Print "error message" No return true return false ∑

deleteFromList() : delete one book from mylist

44

SQL Statement (Delete ..... ) Exception? Yes Print "error message" No return true return false ∑

SQL Statement

(Delete ..... ) Exception? Yes Print "error message" No return true return false
(Delete
.....
)
Exception?
Yes
Print "error
message"
No
return true
return false
SQL Statement (Delete ..... ) Exception? Yes Print "error message" No return true return false ∑

Mylist.viewList() : retrieve books in mylist

45

SQL Statement (Select .... ) Exception? Yes Print "error message" No return true return false 46

SQL Statement

(Select .... ) Exception? Yes Print "error message" No return true return false
(Select
....
)
Exception?
Yes
Print "error
message"
No
return true
return false
SQL Statement (Select .... ) Exception? Yes Print "error message" No return true return false 46

46

6.1 Architecture Diagram

6.0 Design

External Database Int W eb Br ow ra ne t Websphere LMS HTTP/HTTPS Application DB Server
External
Database
Int
W eb Br ow ra
ne
t
Websphere
LMS
HTTP/HTTPS
Application
DB
Server
User Int W eb Br o w ra ne t t Web Browser
User
Int
W eb
Br o w ra
ne
t
t
Web Browser
Int W eb Br o ra ne t Librarian/Admi
Int
W eb Br o ra
ne
t
Librarian/Admi

Register User And Issue Books

47

6.2 Mechanism

The Library Management System is designed & developed for a receipt and issuance of books in the library along with the student’s details. The books received in the library are entered in Books Entry form and the new student is entered in the student entry form. When the student wants to get the desired book the same is issued on the availability basis to the student. The issuance and due date for the returning of the book is also entered into the Book Issue form under third menu Book Issue. The student has to pay the fine if any on the basis of no. of days delayed deposit of the book in the library.

Working of LMS starts from the issuing of books for students. If a student request for any book from library then the administrator can easily check, weather the requested book is available in library or not. He can also maintain the database of book issued to a particular student.

Requirement of student for a particular book can be in any form, for eg. He/She can ask about the book by just the publisher name or can ask about the book by just author name. To remembering about all author and all publisher is about to impossible for any person managing library. For keeping such type of problem in mind we are providing some very friendly search option for LMS. By these search option one can search the required book in just a second of time .

48

Data Modeling

Library Management System E-R Diagram

6.3 Data Model:

6.3.1 E-R Diagram:

49

6.3.2 Data Flow Diagram: 0 Level DFD 50

6.3.2 Data Flow Diagram:

  • 0 th Level DFD

50

1 Level DFD 51
  • 1 st Level DFD

51

2 Level DFD 52
  • 2 nd Level DFD

52

7. Logical and Physical Table Logical ∑ Login Detail loginUserId int 53

7. Logical and Physical Table

Logical

Login Detail

loginUserId

int

53

userName

Varchar(20)

password

Varchar(20)

userType

int

userDetailId

int

54

User Detail

userCategoryId

int

userPersonalId

int

firstName

Varchar(20)

lastName

Varchar(20)

emailId

Varchar(50)

addressLine1

Varchar(50)

addressLine2

Varchar(50)

City

Varchar(20)

State

Varchar(20)

Country

Varchar(20)

telephoneNo

Varchar(20)

mobileNo

Varchar(20)

dateOfBirth

Date

departmentId

int

gender

int

55

Book Transaction

bookId

int

bookTransactionId

int

issueDate

Date

recieveDate

Date

issueTime

Date and Time

recieveTime

Date and Time

dueDays

int

userDetailId

int

Book Detail

bookId

int

bookCategory

Varchar(50)

bookName

Varchar(20)

department

Varchar(50)

bookPublisher

Varchar(50)

bookPrice

Double

bookPublishYear

Varchar(20)

dateOfArrival

Date

noOfBook

Double

bookStatus

int

bookISBN

Varchar(20)

Book Request

56

bookId

int

userLoginId

int

userDetailId

int

requestId

int

bookRequestStatus

Varchar(50)

bookRequestDate

Date

bookRequestTime

Date And Time

Physical

Login Detail

userId

int

userName

Varchar(20)

password

Varchar(20)

userType

int

57

User Detail

 

userCategoryId

int

userId

int

firstName

Varchar(20)

lastName

Varchar(20)

emailId

Varchar(50)

 

addressLine1

Varchar(50)

 

addressLine2

Varchar(50)

City

Varchar(20)

State

Varchar(20)

Country

Varchar(20)

 

telephoneNo

Varchar(20)

mobileNo

Varchar(20)

dateOfBirth

Date

 

departmentId

int

gender

int

58

Book Transaction

bookId

int

bookTransactionId

int

userId

int

issueDate

Date

recieveDate

Date

issueTime

Date and Time

 

recieveTime

Date and Time

dueDays

int

Book Detail

bookId

int

 

bookCategoryId

int

bookName

Varchar(20)

 

departmentId

int

 

bookPublisher

Varchar(50)

bookPrice

Double

 

bookPublishYear

Varchar(20)

 

dateOfArrival

Date

noOfBook

Double

bookStatus

int

bookISBN

Varchar(20)

Book Request

59

bookId

int

userId

int

requestId

int

bookRequestStatusId

int

bookRequestDate

Date

bookRequestTime

Date And Time

Book Request Status

bookRequestStatusId

int

bookRequestStatus

Varchar(50)

Department

 

departmentId

int

departmentStatus

Varchar(50)

User Category

 

userCategoryId

int

 

userCategory

Varchar(50)

60

Book Category

bookCategoryId

int

bookCategory

Varchar(50)

  • 8.1. User Interfaces

  • 8.2. Hardware Interfaces

8.0 Specifications

61

Server Side:

Operating System: Windows 9x/xp ,Windows ME

Processor: Pentium 3.0 GHz or higher\

RAM: 256 Mb or more

Hard Drive: 10 GB or more

Client side:

Operating System: Windows 9x or above, MAC or UNIX.

Processor: Pentium III or 2.0 GHz or higher.

RAM: 256 Mb or more

8.3. Software Interface

Database: SQL Server.

Application: ASP (Active Server Pages)

Web Server: IIS (Internet Information Services (IIS) is a powerful Web server that provides a highly reliable, manageable, and scalable Web application infrastructure)

9. Conclusion

Library Management System has been created keeping in mind the needs of Small and Medium scale libraries. Its an efficient software that includes all the basic functionalities like making data entries for new books, newspapers and magazines, registering a new user, editing and deleting records that are required for smooth functioning of a library. Additionally the user login and book history are also stored and can be accessed by the administrator.

62

It also facilitates the librarian to create new user groups and edit their access levels and functions (like that of the assistants). Apart from this the general users are also given the rights to not only keep track of the books that they have issued and fines due but they too can search for the books/magazines/newspapers that interest them.

10 References and Bibliography

  • 1. http://www.koha.org

  • 2. http://www.ed.gov/databases/ERIC_Digests/ed381179.html

3.CHOWDHURY, GG & CHOWDHURY, Sudatta. Text retrieval and library management software in India. Program, 1994, 28(3), 253-261 and NISSAT Newsletter, 1994, 3, p.13-18.

4.CLAYTON, Marlene. Managing automation, 1987. Gower.

5.GARROGIAN, R. Pre-written software: Identification, evaluation and selection. Software Review, 1(1), 1982. P.1-34.

63

6.HERRING, James.E. & MACKENZIE, John. A. Planning for library automation: Aberdeen City libraries, 1986. Library Association.

7.LAXMAN RAO, N. Software selection for Indian Libraries, Library Science, 30; 1993. Paper T,

p.146-151.

8.LOVECY,

Ian.

Automating

library

procedures:

A

survivor’s

handbook,

1984.

Library

Association.

9.MALWAD, NM. Selection Criteria for library automation software. DESIDOC Bulletin of Information Technology, 15(2), March 1995, p.17-26.

10.MATHEWS, JR. A reader on choosing an automated library system. American Library Association, Chicago, 1983.

12.MISHRA, RK. Library software selection: An analysis, IASLIC Bulletin, 44(3), 1999, p.125-

132

13.NEELAMEGHAN, A. ‘Use of Information in Research Invention and Innovation: DRTC Seminar [9] 1971, Paper BA.

14.PATEL, DR & BHARGAVA, Rachna. Comparative study of software packages available in Indian market for library automation. DESIDOC Bulletin of Information Technology, 1995, 15(3),

p.3-12.15.

64