TRIBHUVAN UNIVERSITY

INSTITUTE OF ENGINEERING

HIMALAYA COLLEGE OF ENGINEERING

A THIRD YEAR CASE STUDY REPORT ON

“LIBRARY MANAGEMENT SYSTEM”
SOFTWARE ENGINEERING
Sagar Acharya (072/BCT/48)

Sandesh Sharan Poudel (072/BCT/54)

Sanjeev Panta(072/BCT/57)

Saroj Poudel (072/BCT/58)

A CASE STUDY REPORT SUBMITTED TO THE DEPARTMENT OF

ELECTRONICS AND COMPUTER ENGINEERING FOR THE PARTIAL
FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF
BACHELOR'S IN COMPUTER ENGINEERING:
9th Magh,2074

1
 “LIBRARY MANAGEMENT SYSTEM”
A THIRD YEAR CASE STUDY
SOFTWARE ENGINEERING
Sagar Acharya (072/BCT/48)

Sandesh Sharan Poudel (072/BCT/54)

Sanjeev Panta(072/BCT/57)

Saroj Poudel (072/BCT/58)

SUPERVISOR :
Er. Jivraj Upadhyay

Er. Nurendra Shakya

“A THIRD YEAR CASE STUDY REPORT SUBMITTED FOR THE

PARTIAL FULFILLMENT OF THE DEGREE OF BACHELOR’S IN
COMPUTER ENGINEERING”:

Department of Electronics and Computer Engineering

HIMALAYA COLLEGE OF ENGINEERING

Chyasal, Lalitpur

2
ACKNOWLEDGEMENT
We extend our sincere thanks to Nobel College for providing us the opportunity to fulfill our
project goals.

We would like to express our deep debt to Er. Jivraj Upadhyay and Er. Nurendra Shakya for
their vital suggestions, meticulous guidance and constant motivation which went a long way in
the successful completion of this project.

We would also like to express gratitude to our HOD Er. Ashok GM and DHOD Er. Devendra
Kathayat for their great heart as well as his kind support.

We would also like to thank to our class mates for supporting to completing this project directly
as well as indirectly.

3
ABSTRACT
Library management system is a project which aims in developing a computerized system to
maintain all the daily work of library. This project has many features which are generally not
available in normal library management systems like facility of user login and a facility of
teacher’s login. It also has a facility of admin login through which the admin can monitor the
whole system. It also has facility of an online notice board where teachers can student can put up
information about workshops or seminars being held in our colleges or nearby colleges and
librarian after proper verification from the concerned institution organizing the seminar can add
it to the notice board. It has also a facility where student after logging in their accounts can see
list of books issued and its issue date and return date and also the students can request the
librarian to add new books by filling the book request form. The librarian after logging into his
account ie. admin account can generate various reports such as student report, issue report,
teacher report and book report.

Overall this project of ours is being developed to help the students as well as staff of library to
maintain the library in the best way possible and also reduce the human efforts.

4
CONTENT
ACKNOWLEDGEMENT ...........................................................................................................3
ABSTRACT ...............................................................................................................................4
1. INTRODUCTION ...............................................................................................................7
2. OBJECTIVES ......................................................................................................................8
3. SOFTWARE REQUIREMENT SPECIFICATION ..............................................................9
3.1. GENERAL DESCRIPTION .........................................................................................9
3.1.1. PRODUCT DESCRIPTION: .................................................................................9
3.1.2. PROBLEM STATEMENT: ...................................................................................9
3.1.3. SYSTEM OBJECTIVES........................................................................................9
4. SYSTEM REQUIREMENTS............................................................................................. 11
4.1. NON-FUNCTIONAL REQUIREMENTS................................................................... 11
4.2. FUNCTIONAL REQUIREMENTS ............................................................................ 11
4.2.1. NORMAL USER ........................................................................................................ 11
4.3. SOFTWARE AND HARDWARE REQUIREMENTS................................................ 13
4.3.1. SOFTWARE REQUIREMENTS ......................................................................... 13
4.3.2. HARDWARE REQUIREMENTS ....................................................................... 13
5. EXISTING VS PROPOSED SYSTEM .............................................................................. 14
6. Feasibility Study ................................................................................................................ 15
6.1. Economic feasibility ................................................................................................... 15
6.2. Technical feasibility .................................................................................................... 15
6.3. Operational Feasibility ................................................................................................ 15
7. SYSTEM TESTING .......................................................................................................... 16
7.1. UNIT TESTING ......................................................................................................... 16
7.2. INTEGRATION TESTING ........................................................................................ 17
7.3. BLACKBOX TESTING ............................................................................................. 17
7.4. WHITEBOX TESTING .............................................................................................. 18
8. TABLE DESIGN ............................................................................................................... 19
9. GANTT CHART ............................................................................................................... 21
10. SYSTEM DIAGRAM .................................................................................................... 22
10.1. USECASE DIAGRAM ........................................................................................... 22

5
 10.2. SEQUENCE DIAGRAM ........................................................................................ 23
10.3. ER DIAGRAM ........................................................................................................ 24
10.4. CLASS DIAGRAM................................................................................................. 25
10.5. DFD DIAGRAM ..................................................................................................... 26
10.5.1. LEVEL 0 .......................................................................................................... 26
10.5.2. LEVEL 1 .......................................................................................................... 27
10.5.3. LEVEL 2 .......................................................................................................... 28
11. CONCLUSION AND FUTURE SCOPE ........................................................................ 29
12. REFERENCES ............................................................................................................... 30

6
1. INTRODUCTION
Library management system (LMS) is an enterprise resource planning system for a library,
used to track items owned, orders made, bills paid, and patrons who have borrowed.

An LMS usually comprises a relational database, software to interact with that database, and two
graphical user interfaces (one for patrons, one for staff). Most LMS separate software functions
into discrete programs called modules, each of them integrated with a unified interface.

LMS is an application which refers to library systems which are generally small or medium in
size. It is used by librarian to manage the library using a computerized system where he/she can
record various transactions like issue of books, return of books, addition of new books, addition
of new students etc.

Books and student maintenance modules are also included in this system which would keep track
of the students using the library and also a detailed description about the books a library
contains. With this computerized system there will be no loss of book record or member record
which generally happens when a non-computerized system is used.

In addition, report module is also included in Library Management System. If user’s position is
admin, the user is able to generate different kinds of reports like lists of students registered, list
of books, issue and return reports.

7
2. OBJECTIVES
The objectives of our project are as follows:
 It will help student or library administrator to access library easily.
 To reduce people’s haphazard.
 Searching process of a book becomes very easy.
 Maintenance of these books becomes very easy.
 To assure the information of the library such as book types, copy number of books, authors
name, availability of particular book etc.
 To make secured data storage of library information.
 Manage the library as a systematic way.
 Huge information can be store

8
3. SOFTWARE REQUIREMENT SPECIFICATION
3.1. GENERAL DESCRIPTION
3.1.1. PRODUCT DESCRIPTION:
Library Management System is a computerized system which helps
user(librarian) to manage the library daily activity in electronic format. It reduces the risk
of paper work such as file lost, file damaged and time consuming. It can help user to
manage the transaction or record more effectively and timesaving.

3.1.2. PROBLEM STATEMENT:

The problem occurred before having computerized system includes:
 File lost
When computerized system isn’t implemented file is always lost because of human
environment. Sometimes due to some human error there may be a loss of records.
 File damaged
When a computerized system isn’t there file is always lost due to some accident like
spilling of water by some member on file accidentally. Besides some natural disaster
like fires may also damage the files.
 Difficult to search record
When there is no computerized system there is always a difficulty in searching of
records if the records are large in number.
 Space consuming:
After the number of records become large the space for physical storage of file and
records also increases if no computerized system is implemented.
 Cost consuming:
As there is no computerized system then to add each record, paper will be needed
which will increase the cost for the management of library.

3.1.3. SYSTEM OBJECTIVES

 Improvement in control and performance
The system is developed to cope up with the current issues and problems of library.
The system can add user, validate user and is also bug free.
 Save cost
After computerized system is implemented less human force will be required to
maintain the library thus reducing the overall cost.
 Save time
Librarian is able to search record by using few clicks of mouse and few search
keywords thus saving his valuable time.

9
 Option of online Notice board
Librarian will be able to provide a detailed description of workshops going in the
college as well as in nearby colleges.
 Lecture Notes
Teacher have a facility to upload lectures notes in a pdf file.

10
4. SYSTEM REQUIREMENTS
4.1. NON-FUNCTIONAL REQUIREMENTS
 Product Requirements
 EFFICIENCY REQUIREMENT:
When a library management system will be implemented librarian and user will
easily access library as searching and book transaction will be very faster.
 RELIABILITY REQUIREMENT:
The system should accurately perform member registration, member validation,
report generation, book transaction and search
 USABILITY REQUIREMENT:
The system is designed for a user-friendly environment so that student and staff
of library can perform the various tasks easily and in an effective way.
 ORGANIZATIONAL REQUIREMENT
 IMPLEMENTATION REQUIREMNTS
In implementing whole system, it uses html in front end with PHP as server-
side scripting language which will be used for database connectivity and the
backend i. the database part is developed using MYSQL.
 DELIVERY REQUIREMENTS
The whole system is expected to be delivered in six months of time with a
weekly evaluation by the project guide.

4.2. FUNCTIONAL REQUIREMENTS

4.2.1. NORMAL USER

4.2.1.1. USER LOGIN
 Description of feature
This feature used by the user to login into system. They are required to enter
user id and password before they are allowed to enter the system. The user id
and password will be verified and if invalid id is there user is allowed to not
enter the system.
 Functional requirements
 user id is provided when they register
 The system must only allow user with valid id and password to enter the
system
 The system performs authorization process which decides what user level
can access to.
 The user must be able to logout after they finished using system.

11
4.2.1.2. REGISTER NEW USER
 Description of feature
This feature can be performed by all users to register new user to create
account.
 Functional requirements
 System must be able to verify information
 System must be able to delete information if information is wrong

4.2.1.3. REGISTER NEW BOOK

 Description of feature
This feature allows to add new books to the library.
 Functional requirements
 System must be able to verify information
 System must be able to enter number of copies into table.
 System must be able to not allow two books having same book id.

4.2.1.4. SEARCH BOOK

 Description of feature
This feature is found in book maintenance part. we can search book based on
book id, book name, publication or by author name.
 Functional requirements
 System must be able to search the database based on select search type
 System must be able to filter book based on keyword entered
 System must be able to show the filtered book in table view

4.2.1.5. ISSUE BOOKS AND RETURN BOOKS

 Description of feature
This feature allows to issue and return books and also view reports of book
issued.
 Functional requirements
 System must be able to enter issue information in database.
 System must be able to update number of books.
 System must be able to search if book is available or not before issuing
books
 System should be able to enter issue and return date information

12
4.3. SOFTWARE AND HARDWARE REQUIREMENTS
This section describes the software and hardware requirements of the system

4.3.1. SOFTWARE REQUIREMENTS

 Operating system
Windows 10 is used as the operating system as it is stable and supports more
features and is more user friendly
 Database MYSQL
MYSQL is used as database as it easy to maintain and retrieve records by
simple queries which are in English language which are easy to understand and
easy to write.
 Development tools and Programming language
HTML is used to write the whole code and develop webpages with java script
for styling work and PHP for sever side scripting.

4.3.2. HARDWARE REQUIREMENTS

 Intel core i5/i7 7th generation is used as a processor because it is fast than
others processor and provide reliable and stable and we can run our pc for
longtime. By using this processor, we can keep on developing our project
without any worries.
 Ram 4-8 Gb is used as it will provide fast reading and writing capabilities and
will in turn support in processing

13
5. EXISTING VS PROPOSED SYSTEM
 Existing system does not have any facility of teacher’s login or student login whereas
proposed system will have a facility of student login as well as teacher’s login.
 Existing system does not have a facility of online reservation of books whereas proposed
system has a facility of online reservation of books.
 Existing system does not have any facility of online notice board where description of
workshops happening in our college as well as nearby colleges is being provided.
 Existing system doesn’t have any option of lectures notes uploaded by teachers whereas
proposed system will have this facility.
 Existing system does not have any facility to generate student reports as well book issue
reports whereas proposed system provides librarian with a tool to generate reports.
 Existing system doesn’t have any facility for book request and suggestions where as in
proposed system after logging in to their accounts student can request books as well as
provide suggestions to improve library

14
6. Feasibility Study

Feasibility study is the preliminary investigation into the system to evaluate the possibility of
a computer system and estimate costs and benefits where quality and time also involve. This
is the most effective method of solution.
Three key considerations are involved in feasibility study:

6.1. Economic feasibility

Economic feasibility usually known as cost analysis; determines whether the
adoptions of a system can be cost justified. Economic justification is generally the
“bottom-line” consideration for most system. Economic justification includes cost-benefit
analysis, long-term corporate income strategies, impact on other profit centers or
products, cost of resources needed for development, and potential system growth to
survive the system into automation in a profitable manner.

6.2. Technical feasibility

Technical feasibility is the most difficult area to access for the automation system
engineering process. We can strongly say’s 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. Some considerations for technical feasibilities are:

 Development risk
 Resource availability.
 Technological risk
 Technical management

6.3. Operational Feasibility

Operational feasibility asks if the system will work when developed and installed.
The following points were taken into account for operational feasibility of the
proposed system:

a. The proposed system causes no harm because it only provides information to the
system users.
b. The system is user friendly so the user can use this system more efficiently.
c. The system is affordable and has low operational cost because it requires no
special equipment other than a normal computer with the internet connection.
d. The system is easily accessible from any place because it is kept live.

15
7. SYSTEM TESTING
The aim of the system testing process was to determine all defects in our project. The program
was subjected to a set of test inputs and various observations were made and based on these
observations it will be decided whether the program behaves as expected or not. Our Project
went through two levels of testing

1.Unit testing

2.integration testing

7.1. UNIT TESTING

Unit testing is undertaken when a module has been created and successfully
reviewed. In order to test a single module, we need to provide a complete environment ie
besides the module we would require


The procedures belonging to other modules that the module under test calls

Non-local data structures that module accesses
A procedure to call the functions of the module under test with appropriate
parameters Unit testing was done on each and every module that is described
under module
1. Test For the admin module
 Testing admin login form
This form is used for log in of administrator of the system. In this we enter the
username and password if both are correct administration page will open
otherwise if any of data is wrong it will get redirected back to the login page and
again ask for username and password.
 Student account addition
In this section the admin can verify student details from student academic info
and then only add student details to main library database it contains add and
delete buttons if user click add button data will be added to student database and
if he clicks delete button the student data will be deleted.
 Book Addition
Admin can enter details of book and can add the details to the main book table
also he can view the books requests.

2. Test for Student login module

 Test for Student login form
This form is used for log in of Student. In this we enter the library id, username
and password if all these are correct student login page will open otherwise if any
of data is wrong it will get redirected back to the login page and again ask for
library id, username and password.

16
  Test for account creation
This form is used for new account creation when student does not fill the form
completely it asks again to fill the whole form when he fill the form fully it gets
redirected to page which show waiting for conformation message as his data will
be only added by administrator after verification.
3. Test for teacher login module
 Test for teacher login form
This form is used for login of teacher. In this, we enter the username and
password if all these are correct teacher login page will open otherwise if any of
data is wrong it will get redirected back to the login page and again ask for
username and password.

7.2. INTEGRATION TESTING

In this type of testing we test various integration of the project module by providing
the input. The primary objective is to test the module interfaces in order to ensure that no
errors are occurring when one module invokes the other module.

 Top-down integration
 Develop the skeleton of the system and populate it with components.
 Start with high-level system and integrate from the top-down replacing
individual components by stubs where appropriate
 Bottom-up integration
 Integrate infrastructure components then add functional components.
 Integrate individual components in levels until the complete system is created

7.3. BLACKBOX TESTING

Black box testing focuses on the fundamental requirements of the software. This is
black box testing enables the software engineering to derive a set of input conditions that
will fully exercise all functional requirements for a program. Black box testing is not an
alternate to white box testing rather it is complementary approach that is likely to uncover
a different class of errors that white box method like.

1. Interface errors
2. Performance in data structure
3. Performance errors
4. Initializing and termination errors

17
7.4. WHITEBOX TESTING
(This is also known as glass box, clear box, and open box testing. White box testing
is testing that takes into account the internal mechanism of a system or component. Using
white box testing methods, the following tests were made on the system
1. All independent paths within a module have been exercised once. In our system,
ensuring that case was selected and executed checked all case structures. The bugs that
were prevailing in some part of the code were fixed.
2. All logical decisions were checked for the truth and falsity of the values.

18
8. TABLE DESIGN

VARIOUS TABELS TO MAINTAIN INFORMATION

 BOOK TABLE FOR KEEPING TRACK OF BOOKS

S. No. Field Name Data Type Size

1 Code Int 10
2 Book Name Char 25
3 Author Char 20
4 Publication Char 20
5 Subject Char 10
6 No. of copies Int 2

 STUDENT TABLE FOR STUDENT INFORMATION

S. No. Field Name Data Type Size

1 Id Int 20
2 Registration no. Int 8
3 Name Char 20
4 Class Char 20
5 Book issued Char 10

 TEACHER TABLE TO KEEP TEACHER NFORMATION

S. No. Field Name Data Type Size

1 Id Int 20
2 Name Char 20
3 Branch Char 20
4 Contact no Int 10
5 Book issued Char 10

 ISSUE TABLE TO KEEP TRACK OF BOOKS ISSUED

S. No. Field Name Data Type Size

1 Book Id Int 20
2 Id Int 20
3 Issue-date Date 10
4 Return-date Date 10

19
 STUDENT LOGIN TABLE

S. No. Field Name Data Type Size

1 login Id Int 10
2 Username Char 20
3 Password Char 10

 TEACHER LOGIN TABLE

S. No. Field Name Data Type Size

1 login Id Int 10
2 Username Char 20
3 Password Char 10

 LOST BOOK RECORD TABLE

S. No. Field Name Data Type Size

1 Book Id Int 20
2 Code Int 20
3 Book Name Char 10
4 Lost date Date 10

 UPDATE BOOK TABLE

S. No. Field Name Data Type Size

1 Book Id Int 20
2 Code Int 20
3 Old Book Name Char 10
4 New Book Name Date 10

20
9. GANTT CHART

21
10. SYSTEM DIAGRAM
10.1. USECASE DIAGRAM

22
10.2. SEQUENCE DIAGRAM

23
10.3. ER DIAGRAM

24
10.4. CLASS DIAGRAM

25
10.5. DFD DIAGRAM
10.5.1. LEVEL 0

26
10.5.2. LEVEL 1

27
10.5.3. LEVEL 2
DATA FLOW DIAGRAM FOR LIBRARY PATRON LOGIN

DATA FLOW DIAGRAM FOR BOOK ISSUE

28
11. CONCLUSION AND FUTURE SCOPE
This project provides a computerized version of library management system which will
benefit the students, teachers as well as the staff of the library. It makes entire process online
where student can search books, teachers can provide notes and other important task,
assignment as well as information related to administrations, staff can generate reports and
do book transactions. It also has a facility for student login where student can login and can
see status of books issued as well request for book or give some suggestions. It has a facility
of teacher’s login where teachers can add lectures notes and also give necessary suggestion to
library and also add info about workshops or events happening in college or nearby college
in the online notice board.
There is a future scope of this facility that many more features such as online lectures video
tutorials can be added by teachers as well as online assignments submission facility, a feature
of group chat where students can discuss various issues of engineering can be added to this
project thus making it more interactive more user friendly and project which fulfills each
user’s need in the best way possible

29
12. REFERENCES
 Software engineering book by Ian Sommerville (9th edition)
 Online resources
 Website
 www.wikipedia.orghttp://

30