Library Management System Design

This document discusses the design and development of a library management system, including its features, operations, and algorithms. It covers topics such as student and staff registration, login functionality, issuance of resources, timeliness and boundaries, data entry, material return status, penalties, and algorithms used in the system. The document also suggests changes for implementing the system in a larger university setting.

LIBRARY MANAGEMENT SYSTEM DESIGN
STUDENT NAME
COLLEGE

INTRODUCTION
The LMS is a technological advancement in terms of a an application which constitute several
subsystems within itself. The application is a resource I various institutions of leaning and the
custodian of the same is the librarian, the clients who use the resources in terms of the books and
literature are the students and other academicians. There are several aspects that are inclusive in
the LMS (Library Management System) all of them which are managed by the librarian. Right
from management of the users who are main clients both new and old, how if for example they
are books are distributed to the users and also how they can be returned in case the given period
has expired, (Basch, Guibas and Hershberger, 2016). In the modern age of many needs and
development especially in terms of resources, there has arisen a great need to have automated
systems where the resources can be managed and the users must have very defined roles and
responsibilities. In the proposed Kent Institute Library Management system , both the
administrator and the student privileges are clearly mapped out so that there is reduction of
queuing and accountability is arrived at, (Demaine, Iacono and Langerman, 2018).
PROJECT AIMS AND OBJECTIVES
The following are some of the objectives that are aimed to be arrived at in the long run .
i. To provide an environment where library resources can be shared more dynamically.
ii. The ability for the client to communicate with the admin of the what resources which could be
lacking in the library management system.
iii. The clients and the employees features that allow them to log into system , and request for
resources.
iv. The feature that will allow the users to search for the resources available by all the various
categories.
LIBRARY SYSTEM DEVELOPMENT
Project Variables
In any system development, space is a very important element that is needed to store data before
the transactions take place. Programming defines this space as a variable. They act as the
intermediary storage locations especially of the system are using a database , front end and back
end administration components (Roura, 2015). Each system consists of the major building blocks

which are called the modules which defines the major functionalities of the entire system . Each
of this need variables which will be used as memories. For the KLMS (Kent Library
Management System), the following will be the variables
Student Registration
Variables
Campus
Student_level
Student_name
Student_id
Username
Password
Staff Registration
Variables
staff_category
staff_name
staff_id
Username
Password
Student Login
Variables
Student_id
Password
Staff login
Variables
Staff_id
Password

Admin Login
Variables
Admin_username
Password
Project Keys
There is a great difference between the traditional filling system and the database system. In
traditional view , redundancy is often one of the most hardy challenges that that the
administrators have faced. In the database , each record must be distinct from one another, the
keys in their various capacities work to make this a reality. The relationships between these
records and fields are also made sure by the use of the keys like primary , candidate and the
others like foreign keys. When tables are created , the keys to identify the records are also defined
in the same process. The following are some of the manifestations (Sadakane, 2015).
Database Tables
Books table which will be used for keeping track of the records of books
Primary key :Book_id
Student table which will be used for keeping student information
Primary key: Student_id
Staff table which will be used for keeping staff information
Primary key: Staff_id
Issue table which will be used for tracking issued books
Foreign keys: book_id and student_id
Student login table to track login transactions
Foreign_key: Student_id
Student login table to track login transactions
Foreign_key: Staff_id

OPERATIONS SUPPORTED BY LIBRARY SYSTEM
In order for the system to be adopted as complete and fulfilling the initial user requirements , then
it must be able to meet the threshold goals and objectives that are set. As a matter of fact , the
library management should and must satisfy the user that there is a difference between it and the
manual record management system. The system should posses , key modules which when they
are integrated are able to produce the desired output. The main features that the library
management should have are as follows.
i. Student login
If the students cannot be able to access the resources , then the system fails to meet the goal. The
system provides the student with an opportunity to create their own accounts before they can
login, any stranger in the institute cannot be allow to access the LMS. The nature of the database
design can only allow up to a certain number to register. This first feature allows for the security
of the system.
ii. Staff Login
The system has various capabilities and functionalities depending on the various organizational
structure. The employees from different departments should also interact with the system
depending on where they serve. Each of the staff is required to open an account with the system
and register with the department he or she works from. These details go the database which stores
then in their respective tables denoting the various levels of operations and privileges also they
shall have as they work with the system . when it comes to the moment of interacting with the
LMS, the staff logs with the details he or she registered with, then the system opens to a specifc
dashboard which defines , the privileges the user should have (Wirth, 2013). With this , various
academicians can log to their areas of specialization and meet tall the needs of their fields.
iii. Issuance of Resources
This lies at the core of any library management system, this actually the main reason for the
implantation of the same. The interaction between the clients and the materials therein including
books , research papers and other components makes it a reality. The LMS will ensure that the
uses both the staff and the students are able to inquire for a material when they are logged into the
system. The system provides a customized search where a book or a journal can be search by
various parameters. They can search for the materials and once they succeed to find, they request

through a simple request form which is sent to the databases and the librarian authorizes the
issuance of the same.
iv. Timeliness and boundaries
Sometimes, after the client has borrowed the resources , he or she tends to forget the deadlines
that are attached to the same privilege. A good library management system should be sensitive to
this so that avoiding losses may be a reality. The system is designed in a manner that when the
users are registering, it captures their details and contacts which can be used to communicate with
them back. In fact there is a message facility in the system whose responsibility is notification of
either deadlines or the penalties if the book or a resource is overdue (Zhang et al 2010).
v. Data entry into LMS
This privilege is only reserved to the Librarian who is the is the Super Admin of the system.
Through this feature, materials’ details can be entered into the system. The quantity of a certain
material, the location and other descriptive issues attached to the same. This cannot be visible to
the normal user, it makes the more flexible and a great stride because the admin can either key in
one by one element or he can prepare an excel document containing the resources and upload
them to the system , which makes it more adaptable and efficient (Yang, Chen & Chen 2017).
vi. Material Return status
Assurance that the returned material has been updated in the system is great relief to the
borrower. Many of the library systems do not have this feature and the user in a very tricky
condition since he or she is not sure of the status of the resource he borrowed. Because of the
same, there are penalties that can be accrued. But, not so with the KLMS which provides the
librarian with the ability to update the books, journals and other media materials once they are
returned. Once the clients log into their respective accounts they should be able to see the status
of their accounts (Anon n.d).
vii. Penalties
Any library management system must have this feature in order to maintain the integrity. Any
time the client goes beyond the agreed time of returning a resource, a penalty should immediately
implement. The system has an inbuilt mechanism that calculates how long the deadline has

passed and how much should one pay. This applies also when the resource has been lost, it must
be replaced.
ALGORITHMS
It is always a good practice for many programmers to look into all the issues before he or she can
make up a system. There is need to defined the fundamental steps which the program shall
follow so that nay one who may be in need of understanding the same may easily achieve it. This
is actually referred to as an algorithm, in a human language it preempts what the system is about
to do in the real practice (Anon n.d). The computer understands this language and it is from this
basis, the coding is done from. So many programming algorithms exists which are designed for a
specific form of a programming, some are easy to use and implement while others are
challenging in the same manner. The author proposes the following as the choicest algorithms
that will be used in the LMS development (Kumar & Gupta 2015).
Recursive algorithm
This is used for solving base cases directly and it has been used in the design of the following
supportive operations in the system
Logins
This can be represented by the following pseudocode
Begin
Enter id
Enter password
If (id and password exist in the database)
{
If (id and password are equal)
Login
Else
Deny access
}
Else
Deny access
End

Resource Insurance
Begin
Search resource
If (resource available) {
Proceed to fill request form
}
Else
Notify the resource is not available
End
Reminders and Notifications
Begin
Check books borrowed
Check resources with less than 24 hours to return deadline
Select all borrowers emails
Send the email
End
CHANGE FOR THE LARGER UNIVERSITY
The designed Library management system of Kent Institute was warranted by the size of the
population they had. The few number of students in their institution could permit the system to
work without any failure. The manner of the database the hosting style also is adaptable to such
kind of a situation. The author when considering a larger estate of population like a university
consisting of members plus students of over 26000, proposes several changes to be put in place
which will ensure smooth flow of transactions to and from in the system. Some of the proposals
are as discussed below (Anon n.d).
1. Transitioning from a local hosting platform to a cloud hosting environment.
Focusing on the current library management system, there is a great demand to change the
hosting standard if it will make to serve over 26000 clients. Form the current set up, the KLMS
was designed only to be a local system restricted within a small geographical environment as well
as the number of users. In fact, this is justifiable for the original minds set but the current desire
to migrate to larger service delivery circumference will increase efficiency and operation of the

library management system. This change will ensure that the users can be able to login wherever
they are provided they are provided they are connected to the internet, great relief and move
essentially. With the experts in the system administration, this will ensure powerful service
delivery to the many users who are scattered in all many areas.
2. Changing the model of database to a more advanced level
The relational model of a database has been the most widely used by so many organization
formerly because of how it has always served a few group of clients, this is why the institutional
at hand borrowed its functionalities in their LBS. in order to sever a large population it is
paramount to transition to other advanced models like hierarchical or networked so that the real
demand is achieved. The relational databases designs are fond of breaking down when they
cannot bear the burden of the user requests provided (Anon n.d). In this case it will be able to
adapt to the number of users which otherwise it would have been impossible to handle.

References
Anon, (n.d.). Data Structures and Algorithms | Coursera. [online] Available at:
https://www.coursera.org/specializations/data-structures-algorithms [Accessed 27 May 2019].
Anon, (n.d.). Data Structures and Algorithms | Udacity. [online] Available at:
https://www.udacity.com/course/data-structures-and-algorithms-nanodegree--nd256 [Accessed
27 May 2019].
Anon, (n.d.). Data Structures and Algorithms. [online] Available at:
https://www.cs.princeton.edu/courses/archive/spr11/cos217/lectures/08DsAlg.pdf [Accessed 27
May 2019].
Basch, J., Guibas, L. and Hershberger, J. (2016). Data Structures for Mobile Data. Journal of
Algorithms, 31(1), pp.1-28.
Demaine, E., Iacono, J. and Langerman, S. (2018). Retroactive data structures. ACM
Transactions on Algorithms, 3(2), p.13-es.
Kumar, S. and Gupta, P. (2015). Phrase Prioritization Algorithm and Supporting Data Structure
for Retrieval. International Journal of Computer Applications, 126(12), pp.29-35.
Roura, S. (2015). Digital Access to Comparison-Based Tree Data Structures and Algorithms.
Journal of Algorithms, 40(1), pp.1-23.
Sadakane, K. (2015). Succinct data structures for flexible text retrieval systems. Journal of
Discrete Algorithms, 5(1), pp.12-22.
Wirth, N. (2013). Data Structures and Algorithms. Scientific American, 251(3), pp.60-69.
Yang, S., Chen, A. and Chen, H. (2017). Seismic data filtering using non-local means algorithm
based on structure tensor. Open Geosciences, 9(1).
Zhang, B., Tang, X., Yang, Y. and YAan, W. (2010). Sub-region data structure and its
composition algorithm in pattern generator. Journal of Computer Applications, 29(12), pp.3314-
3316.