LIBRARY MANAGEMENT SYSTEM

SOFTWARE ENGINEERING PROJECT

BACHELOR OF COMPUTER APPLICATION

FROM

JAMIA HAMDARD
(DEEMED TO BE UNIVERSITY)

SUBMITTED BY: -
● Md Saquib Anwar (2021-301-112) Team leader
● Md Sahil (2021-301-109)
● Md Razik Khan (2021-301-108)
● Madhusudhan Kumar Pandey (2021-301-096)
● Md Amir Khan (2021-301-105)
● Md Anas Ansari (2021-301-106)
 ACKNOWLEDGEMENT

We have taken efforts in this project. However, it would not have been possible without the kind
support and help of many individuals. We would like to thank all of them.

We are sincerely thankful to our project guide Mr Nafisur Rehman, Assistant professor in Jamia
Hamdard University for his guidance and constant supervisions as well as providing necessary
information regarding the project. We feel honoured to work under his guidance. This project
would not have been possible without his guidance.

Thank you,

Md Saquib Anwar (2021-301-112)

Md Sahil (2021-301-109)
Md Razik Khan (2021-301-108)
Madhusudhan Kumar Pandey (2021-301-096)
Md Amir Khan (2021-301-105)
Md Anas Ansari (2021-301-106)
 CERTIFICATE

This is to certify that the project titled “Library Management System” is the bona fide work
carried out by Md Saquib Anwar and his those are students of Bachelor of Computer Application
in Jamia Hamdard University, in partial fulfillment of the requirements of Bachelor of Computer
Application, V semester under the supervision of Mr. Nafisur Rehman, Assistant professor in
Jamia Hamdard University.

Mr. Nafisur Rehman

(Mentor)
 ABSTRACT

The ‘Library Management system’ undertaken as a project is based on relevant technologies,

which is an attempt to automate the existing library. The project enables its user to perform all
the operations regarding a library. The project enables the user to make an entry of a new book,
deleting the record of a book from the library, issuing a book to a member, making an entry of a
new member, deleting the record of a member from the library etc. The process model we have
used for our project is Linear Sequential because the requirements are well stated and understood
beforehand. In the analysis phase we analysed the requirements of what the project will do. We
collected the requirements needed to develop the project. Then in the design phase we designed
our project according to user satisfaction. We created a database to store the details of members,
books in tables. We designed DFD diagrams based upon the operations that were carried out in
the project. Then cost and effort estimations are calculated and testing and coding processes have
been carried out.

Hence in the existing system for LIBRARY MANAGEMENT SYSTEM, the performance
evaluation system and the maintenance are done manually. The proposed system will maintain
all the information in a standard database and will be able to generate reports when necessary.
Table of Contents

1. Problem Statement..................................................................................................

2. Process Model

3. Software Requirement Specifications

1. Introduction......................................................................................................................

1.1 Purpose...............................................................................................................

1.2 Scope................................................................................................................

1.3 Definitions................................................................................................

1.4 Overview............................................................................................

2. Project Description

2.1 Product Perspective

2.1.1 System Interfaces

2.1.2 System Specifications

2.1.2.1 H/W Requirement

2.1.2.2 S/W Requirement

2.1.3 Communication Interfaces

2.1.4 Memory Constraints

2.1.5 Operations

2.1.6 Site Adaptation Requirements

2.2 Product functions

2.3 User characteristics

2.4 Constraints

2.5 Assumptions and dependencies

 2.6 Apportioning of Requirements

3. Specific Requirements

3.1 External interfaces

3.2 Functions

3.3 Performance requirements

3.4 Logical database requirements

3.6 Software system attributes

3.4.1 Reliability

3.4.2 Availability

3.6.2 Security

3.6.3 Maintainability

4. Data Flow Diagram (DFD) & Structure

4.1 Context Flow diagram
4.2 DFD-Level-1
4.3 DFD-Level-2

5. Use Case Diagram

6. Structural View Diagram

6.1 Class diagram

6.2 Object diagram

7. Behavioral View Diagram

7.1 State Chart diagram

7.2 Activity diagram

7.3 Sequence diagram

7.4 Collaboration diagram

1. PROBLEM STATEMENT

A college library management is a project that manages and stores books information
electronically according to student’s needs. The system helps both students and library manager
to keep a constant track of all the books available in the library. It allows both the admin and the
student to search for the desired book. It becomes necessary for colleges to keep a continuous
check on the books issued and returned and even calculate fine. This task if carried out manually
will be tedious and includes chances of mistakes. These errors are avoided by allowing the
system to keep track of information such as issue date, last date to return the book and even fine
information and thus there is no need to keep manual track of this information which thereby
avoids chances of mistakes.

Thus, this system reduces manual work to a great extent allows smooth flow of library activities
by removing chances of errors in the details.

2. Process Model
A process model for software engineering is chosen based upon: - ●

Nature of the Project.

● Methods and Tools to be used.

 ● Control and desired deliverable.

The process model we have chosen to develop this software is a Linear Sequential Model
(Waterfall Model). Linear Sequential Model suggests a systematic, sequential approach to
software development that begins at the system level and progresses through analysis, design,
coding, testing and support.

Linear Sequential Model approach has the following phases: -

Software requirements analysis: -

In this, a software engineer understands the nature of a program to be built, he must understand
the information domain for the software as well as required function, behavior, performance and
interface. Requirements for both the system and the software are documented and reviewed with
the customer.

Design: -
It has four distinct attributes of a program: data structure, software architecture, interface
representations and procedural detail. It is documented and becomes part of the software.

Code generation: -
Design must be translated into a machine-readable form which is done by code generation.

Testing: -
It focuses on the logical internals of the software, ensuring that all the statements have been
tested, and on the functional externals; that is conducting test to uncover errors and ensure that
defined input will produce actual results.

3. SOFTWARE REQUIREMENT SPECIFICATIONS

1. INTRODUCTION

Library Management System is a comprehensive library management solution that is suitable for
both large and small libraries. Its flexible design enables Library Management System to be
installed in a range of Library organizations, ranging from public libraries, through to academic,
joint use and special libraries. This Library Management System Software is capable of handling
Books with equal ease and efficiency. This is a Windows-based Library Management System,
utilizing the latest advancements in Information Technology to provide and improve Library
Services.

1.1 Purpose

The purpose of this project is to develop an application that will automate the whole procedure of
a library. The software that would be developed should have facilities like Add / Delete
Members, Add / Delete Books, Issue & Return. The application should be secured, as well as
with limited access. The main requirement of the project will be the ease of use, besides being
the most efficient and effective tool for the purpose. The application should be user friendly. It
should be robust and scalable. An automated solution would be very beneficial to the
organization, as it would bring structure to the whole process so that it can be traced for any kind
of query. Also, an automated solution will lead to optimal utilization of the available resources,
reducing duplication of effort, increasing efficiency and minimizing time-delays. Following are
the main purpose of computerization:

● To provide services to all the employees for issue, return & search etc. at one place.

● To improve coordination in staff.

● To reduce paper filling work.

● To reduce risk of fraud.

● To reduce chances of information leaking.

1.2 Scope

For Members: -

● Facility for search of Books based on Access Number, Title, Author, Subject, Keyword.

● Facility for ISSUE / RETURN Books.

● Facility for RENEWAL of Books.

For Library Staff: -

● Automatic installation.

● Simple and intuitive GUI for performing all functions.

● Short-cut keys and point-and-click operation.

 ● Security features like access control using passwords and login-i.d.

● Automatic calculation of late-fee.

● Facility to ADD / DELETE Members, Library Staff & Books and Maintain an easy
record of all these.

1.3 Acronyms used

LMS - Library Management System

UI - User Interface

DBMS - Database Management System

1.4 Overview

The rest of the document deals with all the main features of this software. It not only describes
various functions but also gives details about how these functions are related to each other. Apart
from the data flow diagrams, the document also contains cost estimates for developing this
system. Various risks associated with the system have also been mentioned along with the ways
to mitigate them.

The timeline chart describing how the entire project was scheduled has been attached. At the end
a pseudo code for the customer management module” has been provided. A flow graph has been
generated corresponding to this module and test cases that were used to test the system have also
been mentioned.

2. PROJECT DESCRIPTION

2.1 Product Perspective

The manual library management system includes following drawbacks:

● The existing system involves a lot of paperwork and manual calculation. This has led to
inconsistency and inaccuracy in the maintenance of data.
 ● The data, which is stored on the paper only, may be lost, stolen or destroyed due to
natural calamity like fire and water.

● The existing system is sluggish and time-consuming causing inconvenience to library

staff.

● Since there are many books related to different scopes thus it would be very difficult to
find a specific book, or edit the data of some book.

Hence the library management system is proposed with the following Product perspective:

● The computerization of the library system will reduce a lot of paperwork and hence the
load on the library staff.

● It would be easy to search for a specific book.

● The machine performs all calculations for fines and all. Hence chances of error are nil.

● The system provides for user-ID validation, hence unauthorized access is prevented.

2.1.1 System Interfaces

Software will work on Windows OS. The database used will be an open source database like
MySQL and the system will work on JVM.

2.1.2 System Specification

Software requirements

Operating System: we have chosen windows operating system for its best support and user
friendliness.

Database: to save the records of the applicants and their details, SQL database is used.

Hardware requirements

LMS uses standard java classes and databases. The database should have backup capabilities.

2.1.3 Communication interfaces

No additional specific communication interfaces are needed during the operation of LMS.

2.1.4 Memory constraints

The system is expected to have a memory of 256 MB and disk space of 500 MB. But it is
recommended that the system has memory capacity of 1 GB and disk space of 1GB.
2.1.5 Operations

The basic operations of the ‘Library Management System’ are described as follows:

● The staff member first has to register him/herself before using the system.
● The staff member can then login into the system with his/her username and password.
● The staff member can then add, delete or update the book records within the system.
● The staff member can issue books when requested by the members and then update the
book record too.
● The system will generate the fine slip according to the returned date when the book is
returned by the member.
● The staff member will update the book issue and return records into the book
management system.
● The member can search for a specific book by entering book information.
● The staff member can update member records within the system.

2.1.6 Site Adaptation Requirements

The system will require an application server for the runtime components and a database for
storage. The system will run on select popular application servers and use select popular
database for data storage.

2.2 Product Functions

There are two different users who will be using this product:
● Librarian who will be acting as the administrator.
● Members who can also use products for search operations.

The features that are available to the Librarian are:

● A librarian can issue a book to the member.
● Can view different categories of books available in the library.
● Can view the List of books available in each category
● Can take the book returned from students
● Add books and their information of the books to the database ● Edit the information of
the existing books.
● Can check the report of the issued Books.
● Can access all the accounts of the students.
 The features available to the Member are:

● Can view the different categories of books available in the library

● Can view the List of books available in each category
● Can search for a particular book

2.3 User characteristics

User1: Staff- Staff will add, delete or update book records within the system. He/she will issue
the books as per requested by the member and will calculate the fine according to the returned
date of the book. Staff needs to have a complete understanding of functionalities and internal
processing of the system.

User2: Member- Member will request for a book issue and then will return the book. They can
search for a specific book. The user does not need to have a complete understanding of complex
functionalities and internal processing of the system.

2.4 General Constraints

Any update regarding the book from the library is to be recorded to have update and correct
values and any fine on a member should be notified as soon as possible and should be calculated
correctly.

2.5 Assumptions and Dependencies The

assumptions are:

● The coding should be error free.

● The system should be user-friendly so that it is easy to use for the users.
● The information of all users, books and libraries must be stored in a database.
● The system should have more storage capacity and provide fast access to the database.

The dependencies are:

● On the basis of listing requirements and specifications the project will be developed.
● The end users should have a proper understanding of the product.
● The information of all users must be stored in a database that is accessible by the LMS.
 ● Any update regarding the book from the library is to be recorded to the database and the
data entered should be correct.

2.6 Apportioning of Requirements

This is an academic project and hence all the requirements will be completed before the end of
the semester. There will be no delay in the delivery of any of the requirements

3. SPECIFIC REQUIREMENTS

3.1 External Interfaces

User Interface

Various GUI elements like forms, images and standard buttons will be included in the User
Interface.

3.2 Functional Requirements ●

Login:
Description: Staff member will login to the system. The user must be registered in the
system before login.
Input: Enter the username and password.
Output: Staff will be able to use the features of software.
Processing: Username and password will be checked by the system. If they are incorrect
a message will be displayed.
● Add/Remove books:
Description: The staff can add or remove book by entering details.
Input: Enter the book detail you want to remove or add within the stock.
Output: Confirmation of addition or deletion and update list of books available.
Processing: The details of books must be right in order to add them else there will be
problems in future. ● Search:
Description: The users can search a book by entering book details such as author’s name,
book name etc.
Input: Enter the details you know about the book.
Output: The list of available books is displayed.
Processing: A message is displayed if the book related to the entered details is not
available.
 ● Issues book:
Description: The staff member checks the availability of books which the member wants
to get issued.
Input: Enter book code.
Output: Confirmation for book issue or apology for failure in issue.
Processing: If selected book is available then the book will be issued and the record is
updated else error will be displayed.
● Return book:

Description: The member wants to return the book.

Input: return the book to the library.
Output: The record will be updated.
Processing: If a book is not returned on time then a fine is calculated.
● Fine:
Description: If a book is not returned on time by a member then a fine is charged on a per
day basis.
Input: check for the fines.
Output: Details about fines on the book issued by the staff.
Processing: The fine will be calculated, if it crossed the date of return.

3.3 Performance requirements

There are no particular extra performance requirements at this point of time.

3.4 Logical Database Requirements

Proposed database is intended to store, retrieve, update and manipulate information related to
college which include:
● Books availability
● Staff information
● Member details ● Calculation of fines
.

3.6 Software System Attributes

Reliability:
The application would efficiently store all the information related to the various processes in the
system and output the relevant information.

Availability:
The application would be available to all the employees of the organizations with an authorized
access to the workstations and those who are subject to the authorization permissions.

Security:
The system would have adequate security checking through the authentication of the users. The reports
would only be available to the employees of the library as per their specific requirements.

Maintainability:
The software should not require any additional maintenance. If any errors occur, the user should
be able to login again with his credentials. The system shall be flexible enough to add new
modules and upgrade the existing modules.

4. Data Flow Diagram (DFD) & Structure

4.1 Context Diagram

4.2 DFD-Level-1

4.3 DFD-Level-2
DFD LEVEL ‘2’ : BOOK STOCK MANAGEMENT

DFD LEVEL ‘2’ : ISSUE A BOOK

DFD LEVEL ‘2’ : RETURN A BOOK
5. Use Case Diagram
A use case diagram is a visual representation of how a user can interact
with a system. It shows the system's use cases, users, and their relationships.
Use cases are a set of actions, services, and functions that the system needs
to perform.
6. Structural View Diagram
A structural view diagram is a conceptual modeling tool that shows the
static structure of a system. It shows how the components of a system are
organized, how they relate to each other, and how they interact.

6.1 Class diagram - Aggregation and Multiplicity are two important points that
need to take into consideration while designing a Class Diagram.
 6.2 Object diagram

7. Behavioral View Diagram

behavioral view diagrams visualize, specify, construct, and document
the dynamic aspects of a system. The behavioral view diagrams are
categorized as follows: state–chart diagrams, and activity diagrams,
sequence diagram, collaboration diagram,
7.1 State Chart diagram
7.2 Activity diagram
7.3 Sequence diagram

7.4 Collaboration diagram