Library Management System

LIBRARY MANAGEMENT SYSTEM
1. INTRODUCTION
The main objective of the Library Management system is organizing and managing the library
tasks. Library is place where all kind of books are available. This is a web base application and
only a registered user can access the application. Library Management system is developed to
automate the task of entering the records of new book and retrieving the details of book available
in the library. This system contains list of all the books. Using this system user can issue book to
the library member, maintain their records, and can checks how many book are issued and how
many books are available in the library. This system provides separate interface and login for
librarian, students and faculties. Librarian can modify database. Using the library management
system, user can also maintain the late fine of library member who return the issued book after
the due date.
Users can search for books and renewal books online. In the proposed system, we assume that
each member will be having a identity card which can be used for the library book issue, fine
payment etc. They can recommend for new books by just sending messages to the librarian from
anywhere in the college. Whenever library member wish to take a book, the book issued by the
library authority will be check both the book details as well as the student details and store it in
library database. They can view the issue and return dates of any book and due they have to pay.
SVEC-2021 Page 1
2. LITERATURE SURVEY
Most of the research and writings on library management have focused on academic libraries and
only recently has there been more interest in the administration of public libraries. The skill and
style of public library managers – the directors, branch managers, and department and service
managers who are leading these institutions – strongly affects the culture of a public library.
Library staff looks to these managers to help them navigate through the rapid changes that are
occurring in public libraries as these changes in technology, roles, and user expectations strongly
alter their daily routines of public service. Contemporary library managers need a wider array of
skills and attributes than their earlier and more traditional counterparts and will need to seek
continual professional development to remain effective as public libraries transition into the
twenty-first century [1].
These managers will also need to distinguish between management and leadership skills and
learn to identify and mentor leaders within their staff who can assist in the transition. This paper
on academic as well as public libraries due to the above-mentioned lack of public library
material. Weiner reviewed the literature extant on leadership in academic libraries and surveyed
materials on “recruitment, leadership potential identification, career development, roles and

responsibilities, and characteristics and management style”
Since she chose to focus on leadership as well as management attributes, her review
encompasses materials on library directors as well as university librarians. A discussion of the
changes and trends affecting academic libraries is valuable as it provides the context of the
article and helps to enlighten readers who might not be familiar with the academic environment.
Research studies and models, other literature reviews, and books and articles written are
discussed and an extensive bibliography leads the readers to further study [2].
SVEC-2021 Page 2
Hernon and Rossiter (2006) studied the emotional intelligence concepts that are relevant to
university library directors. Their research involved two different activities for gathering
information. They analyzed all of the job advertisements for library directors in College &
Research Libraries News from 2000 to 2004 and looked for any mention of leadership skills.
Then they interviewed university library directors to compare their career experiences with the
information taken from the advertisements.
By comparing the expectations of search committees with the actual experiences of the directors,
they suggest which emotional intelligence traits are most useful in academic library
management. The authors conclude that identifying these traits and helping to “cultivate the ones
deemed most critical” is important for the development of future leaders. Mullins and Linehan
(2006) provided a public library context for leadership and management in their study of thirty
public library managers in Ireland, Britain, and the United States.
Their focus was on whether or not these managers understand and utilize the differing concepts
of leadership and management. According to their findings, eighty percent of the respondents did
not comprehend the difference in these concepts and focused on administration and management
over leadership skills to accomplish their work. Public librarians who exhibit an aptitude for
[3].
leadership should be encouraged to develop and apply their talents in their field of influence
SVEC-2021 Page 3
3. PROBLEM DEFINITION
• Libraries are used to store books, but require a system to navigate to a specific book or specific
content within a book. A library database system is an infrastructure that allows users to search
books and book content, add/remove, and download selected books.
• The problem faced is that library users require an efficient method to find a specific book or
keyword(s) within a book given a continuously expanding library. Efficiency requires that the
processing time should stay relatively the same even as the library contents increases.
SVEC-2021 Page 4
4. DATA COLLECTION
The data collection methods used in this project are:
Interviews - Interviewing the stakeholders such as librarians
Questioner-by asking open questions to the librarian Observing Users at library- Watching users
performing their study at library.
For the analysis and design of this project we will be using an Object Oriented Approach (OOA)
in which Objects describe re -usable components. We used this OOA because Object-
orientational user’s of a system (an actor) and the system itself..
Helps us in identifying the requirements of the system, rather than how the Software should be
structured or implemented
SVEC-2021 Page 5
5. SYSTEM ANALYSIS
5.1 EXISTING SYSTEM:
System Analysis is a detailed study of the various operations performed by a system andtheir
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.
5.1.1. DISADVANTAGES OF EXISTING SYSTEM:
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
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.
.
SVEC-2021 Page 6
5.2.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.
5.2.1. ADVANTAGES OF PROPOSED SYSTEM:
 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.
5.3. MODULES:
This project has two main modules such as,
1. Admin
2. Student
 Admin has five sub modules as following,
1. Admin login
2. Add and update books
3. View order
4. Place order
5. Search option
6. Calculate Fine
SVEC-2021 Page 7
 Student has three sub modules as following,

1. Registration
2. Search books
5.3.1. Admin
 Admin login:
Admin is the one who administers the system by adding or removing e-books into and
from the system respectively.
 Add and Update Books:
The admin can add books to the system by entering the details of the books and can even
update the details.
 Search option:
Admin and Students can even search for books by entering the name of the book.
 View Order-
The admin can view order for the books.
 Place order-
The students can place order for the books and simultaneously the quantity of the book
ordered will be decremented.
 Calculate Fine-
The student can view the issue and expiry date for the book issued and can even calculate
fine.
SVEC-2021 Page 8
5.3.2. Student:
 Student login:
Students have to register themselves into the system to create an account. After
registering successfully, they can then login into the system by entering 10 digit mobile
number and their email id.
 Search option:
Admin and Students can even search for books by entering the name of the book.
SVEC-2021 Page 9
5.4. SYSTEM ARCHITECTURE
Library System Architecture
SVEC-2021 Page 10
6. SYSTEM ENVIRONMENT
6.1HardwareRequirements:-
1. System : HP
2. Hard Disk : 40 GB.
3. Floppy Drive : 1.44 Mb.
4. Ram : 512 Mb.
6.2 Software System Configuration:-
1. Operating system : Windows10

2. Coding Language : PHP, MYSQ
3. Front End : PHP
4. Backend : MYSQL
SVEC-2021 Page 11
7. SYSTEM DESIGN
7.1 DIAGRAMS:
UML stands UML for Unified Modeling Language. UML is a standardized general-
purpose modeling language in the field of object-oriented software engineering. The standard
is managed, and was created by, the Object Management Group.
The goal is for UML to become a common language for creating models of object
oriented computer software. In its current form UML is comprised of two major components:
a Meta-model and a notation. In the future, some form of method or process may also be
added to; or associated with, UML.
The Unified Modeling Language is a standard language for specifying, Visualization,
Constructing and documenting the artifacts of software system, as well as for business
modeling and other non-software systems.
The UML represents a collection of best engineering practices that have proven
successful in the modeling of large and complex systems.
The UML is a very important part of developing objects oriented software and the
software development process. The UML uses mostly graphical notations to express the
design of software projects.
7.1.1 USE CASEDIAGRAM:
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals (represented
as use cases), and any dependencies between those use cases. The main purpose of a use case
diagram is to show what system functions are performed for which actor. Roles of the actors
in the system can be depicted.
SVEC-2021 Page 12
SVEC-2021 Page 13
7.1.2 CLASS DIAGRAM:
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations (or methods), and the relationships among the classes. It
explains which class contains information.
SVEC-2021 Page 14
7.1.3 SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram

that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams
SVEC-2021 Page 15
7.1.4 CollaborationDiagram:
In collaboration diagram the method call sequence is indicated by some numbering

technique as shown below. The number indicates how the methods are called one after
another. We have taken the same order management system to describe the collaboration
diagram. The method calls are similar to that of a sequence diagram. But the difference is that
the sequence diagram does not describe the object organization where as the collaboration
diagram shows the object organization.
SVEC-2021 Page 16
7.1.4 ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified Modelling
Language, activity diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall flow ofcontrol.
SVEC-2021 Page 17
7.1.5 State chart Diagram

State chart diagram is used to find out the state of the object and we can define state
chart diagram is define flow of states from one object to another object.
SVEC-2021 Page 18
7.1.6 COMPONENTDIAGRAM
Component diagrams are used to describe the physical artifacts of a system. This
artifact includes files, executables, libraries etc. So the purpose of this diagram is different,
Component diagrams are used during the implementation phase of an application. But it is
prepared well in advance to visualize the implementation details. Initially the system is
designed using different UML diagrams and then when the artifacts are ready component
diagrams are used to get an idea of the implementation.
SVEC-2021 Page 19
7.1.8 DEPLOYMENT DIAGRAM
Deployment diagram represents the deployment view of a system. It is related to the

component diagram. Because the components are deployed using the deployment diagrams.
A deployment diagram consists of nodes. Nodes are nothing but physical hardwires used to
deploy the application.
SVEC-2021 Page 20
7. IMPLEMENTATION
This report focuses on the design and implementation of the library management system. It deals
with the complete processes on building and implementing it. It focuses in the technical aspects
of the system starting with identifying the necessary components and building the relevant
relationship between or among them as needed for the smooth and efficient operation of the
system.
The process starts with the entities involved in the system, with proceeding towards the ER
Diagram in order to identify the meaningful relationship between the entities. Next is the table
design which fulfils the normalization principle of relational database system and finally the
physical tables are created with the necessary and relevant data in them.
The system can keep track of the members joining and leaving the library, borrowing and
returning of the books. Checking the availability of the books using different attributes as
parameters. Finally checking of the overdue books and fines payable is another feature of the
system.
SVEC-2021 Page 21
8.2 Screenshots:
Login Page:
Screen 8.1.1 LOGIN PAGE
SVEC-2021 Page 22
Home Page:
Screen8.1.2 HOME PAGE

Admin Account Page:
Screen8.1.3 ADMIN ACCOUNT PAGE
SVEC-2021 Page 23
STUDENT ACCOUNT PAGE:
Screen8.1.4STUDENT ACCOUNT PAGE

BOOK PAGE:
Screen8.1.5 BOOK PAGE
SVEC-2021 Page 24
BORROWING TRANSACTION PAGE:
Screen8.1.6 BORROWING TRANSACTION PAGE
RETURNING TRANSACTION PAGE:
Screen8.1.7 BORROWING TRANSACTION PAGE
SVEC-2021 Page 25
LOGOUT PAGE:
Screen8.1.8 LOGOUT PAGE
SVEC-2021 Page 26
9. SYSTEMTESTING
9.1. Introduction
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.
9.2 TYPES OFTESTS

9.2.1 Unit testing
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of the application .it is done after the completion of an individual unit before
integration. This is a structural testing, that relies on knowledge of its construction and is
invasive. Unit tests perform basic tests at component level and test a specific business
process, application, and/or system configuration. Unit tests ensure that each unique path of a
business process performs accurately to the documented specifications and contains clearly
defined inputs and expected results.
9.2.2Integrationtesting
Integration tests are designed to test integrated software components to determine if

they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination ofcomponents.
SVEC-2021 Page 27
9.2.3 Functional test:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is cantered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must be
considered for testing. Before functional testing is complete, additional tests are identified
and the effective value of current tests is determined.
9.2.4 System Test
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An example of
system testing is the configuration oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration points.
9.2.5 White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge
of the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
9.2.6 Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most other
kinds of tests, must be written from a definitive source document, such as specification or
SVEC-2021 Page 28
requirements document, such as specification or requirements document. It is a testing in

which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.
9.3 Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.
9.4 Test objectives
9.4.4.1 All field entries must work properly.

9.4.4.2 Pages must be activated from the identified link.
9.4.4.3 The entry screen, messages and responses must not be delayed.
9.5 Features to be tested
9.5.4.1 Verify that the entries are of the correct format

9.5.4.2 No duplicate entries should be allowed
9.5.4.3 All links should take the user to the correct page.
9.6 Test Cases:
9.6.1 Login page:
Tested By: P Yamuna
Test Type Block box testing
Test Case Number 001
Test Case Name Enter Admin Login
Test Case Description By entering the required fields of the registration form they are
going to get the login credentials.
Items(s) to be tested
1 User Id, password, email id, contact number to be tested.
2 User id And Password to be tested.
SVEC-2021 Page 29
Specifications
Input Expected
Output/Result
Enter Valid Details The user registered successfully
Procedural steps
1 Enter the password and conform password as same otherwise it will
show the error message.
9.6.2 Booking conformation:
Tested By: P Yamuna
Test Type Unit testing
Test Case Number 002
Test Case Name For students booking conformation
Test Case Description By entering the required fields of the registration form they are
going to get the conformation order.
Items(s) to be tested
1 Item Name, Quantity, coupons, contact number to be tested.
2 Email And contact Number to be tested.
Specifications
Input Expected
Output/Result
Enter Valid Details The booking conform successfully
Procedural steps
1 Enter the valid email and contact Number as same otherwise it will
show the error message.
SVEC-2021 Page 30
10. CONCLUSION
Our project is only a humble venture to satisfy the needs in a library. Several user friendly
coding have also adopted. 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 manger 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 .
10.1 FUTURE ENHANCEMENT:
There is a future scope of this facility that many more features such as online lectures video
Tutorials can be added by a teachers as well as online assignment 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 users
need in the best way possible.
SVEC-2021 Page 31
BIBILOGRAPHY
References:
[1].Bao Sun, JiangweiFeng and Ling Liu, “A Study on How to Construct the
Prediction Model of Library Lending of University Library”, International
Conference on Information Science and Technology March 26-28, 2011 Nanjing,
Jiangsu, China.
[2].Erxiang Chen,Minghui Liu,“Research and Design on Library Management System
Based on Struts and Hibernate Framework”, WASE International Conference on
Information Engineering2009.
[3].HonghaiKan, Zhimin Yang, Yue Wang, Nana Qi, “Research on Library
Management System for CDs Attached to Books Based on Cloud Computing”, in
Proceedings of the 14th International Conference on Computer Supported
CooperativeWork in Design 2010.
[4].Weihong Yang, “Design and Implementation of Library Management System”,
International Conference on Management Science and Innovative Education
(MSIE 2015).
Websites
 http://www.w3schools.com
 http://www.quibids.com
 http://www.ubid.com
 http://www.i-bidder.com
 https://www.tutorialspoint.com
SVEC-2021 Page 32

Library Management System

Uploaded by

Copyright:

Available Formats

Library Management System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Library Management System

Uploaded by

Copyright:

Available Formats

LIBRARY MANAGEMENT SYSTEM

twenty-first century [1].

materials on “recruitment, leadership potential identification, career development, roles and

encompasses materials on library directors as well as university librarians. A discussion of the

information taken from the advertisements.

public library managers in Ireland, Britain, and the United States.

The data collection methods used in this project are:

Interviews - Interviewing the stakeholders such as librarians

5.1 EXISTING SYSTEM:

 User friendly interface

This project has two main modules such as,

 Admin has five sub modules as following,

 Student has three sub modules as following,

 Add and Update Books:

The admin can view order for the books.

5.4. SYSTEM ARCHITECTURE

Library System Architecture

6.2 Software System Configuration:-

1. Operating system : Windows10

7.1.1 USE CASEDIAGRAM:

7.1.2 CLASS DIAGRAM:

7.1.3 SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram

In collaboration diagram the method call sequence is indicated by some numbering

7.1.4 ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise activities

7.1.5 State chart Diagram

Deployment diagram represents the deployment view of a system. It is related to the

Screen 8.1.1 LOGIN PAGE

Screen8.1.2 HOME PAGE

Screen8.1.3 ADMIN ACCOUNT PAGE

STUDENT ACCOUNT PAGE:

Screen8.1.4STUDENT ACCOUNT PAGE

Screen8.1.5 BOOK PAGE

BORROWING TRANSACTION PAGE:

Screen8.1.6 BORROWING TRANSACTION PAGE

RETURNING TRANSACTION PAGE:

Screen8.1.7 BORROWING TRANSACTION PAGE

Screen8.1.8 LOGOUT PAGE

9.2 TYPES OFTESTS

Integration tests are designed to test integrated software components to determine if

9.2.3 Functional test:

Functional testing is cantered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

9.2.4 System Test

9.2.5 White Box Testing

9.2.6 Black Box Testing

requirements document, such as specification or requirements document. It is a testing in

9.3 Test strategy and approach

9.4 Test objectives

9.4.4.1 All field entries must work properly.

9.5 Features to be tested

9.5.4.1 Verify that the entries are of the correct format