LIBRARY MANAGEMENT SYSTEM:

PROGRAM-1: DEVELOPMENT OF PROBLEM STATEMENT FROM THE USER

STORIES.

AIM: -To identify how the user registered for their account for the library.

Types of users of Library management system:

a) Librarians: This type of user is responsible for managing the library's collection,
including cataloguing new items, processing loan requests, and ensuring that
materials are properly organised.

b) Patrons: Patrons are the library's users and may use the library management
system to search for materials, request items, and manage their accounts.

c) Administrators: Administrators have full access to the library management

system and are responsible for configuring the system, managing user accounts,
and monitoring system performance. They may also generate reports on library
usage and other metrics.

User Story template:

Syntax for creating user stories:
As a/an [type of user] I want to [action] so that [benefit].

User Stories for Library Management System:

a) As a librarian, I want to catalogue new items in the library's collection, so that

patrons can easily find them.

b) As a patron, I want to search for specific books or authors, so that I can find the
materials I need.

c) As an administrator, I want to generate reports on library usage and other metrics,

so that I can make data-driven decisions about the library's collection.

USER PROBLEM STATEMENTS BASED ON USER STORIES:

Syntax for problem statements from user stories:

[user type] is/an [user characteristics] who needs [user needs] because [insight]

Problem Statements for Library Management System:

a) Librarians are efficient and systematic individuals who need to catalogue new
items in the library's collection because they want to ensure
that patrons can easily find them.

b) Patrons are avid readers who need to search for specific books or authors
because they want to find the materials they need quickly and easily.

c) Administrators are data-driven individuals who need to generate reports on library

usage and other metrics because they want to make informed decisions about the
library's collection to ensure that it meets the needs of its users.

PROBLEM STATEMENT :

Combined Goal Statement for Library Management System: Our Library

management system will enable users to catalogue new items in the library's
collection, search for specific books or authors, and generate reports on library
usage and other metrics, which will affect librarians by enabling them to organise
materials efficiently, patrons by enabling them to find the materials they need quickly
and easily, and administrators by enabling them to make informed decisions about
the library's collection to ensure that it meets the needs of its users.
PROGRAM-2: PREPARATION OF SOFTWARE REQUIREMENTS DOCUMENT
AND CONVERT INTO USE CASES.

USE-CASE NAME:-LOGIN

Both student and librarian login into the library management system by entering their
login credentials.

USE-CASE NAME:-ADD BOOK

The librarian can add the details of the book purchased from shops along with the
shop name.He can also add other details like cost of the book and author.
USE-CASE NAME:-ADD STUDENT

Adding a new student to the system so that he can get a membership and access to
the library.The librarian will add the student details like name,department,roll number.

USE-CASE NAME:-ISSUE BOOK

Librarian issue the book to the candidate based on some conditions:-

1.If he is an existing member,the librarian will check whether the member have any
previous dues,and the total number of books he has taken on that particular library
card.

USE-CASE NAME:-RETURN BOOK

The librarian will check whether the student has returned the book within the due
date ,if not the student has to pay a fine.

USE-CASE NAME:-ADD PENALTY

The librarian will add a penalty for the students who have not returned the book in
time.

USE-CASE NAME:-CHANGE PASSWORD

If the student or librarian forgets his/her password ,they can change it here and get
back the access.

USE-CASE NAME:-VIEW REPORTS

The librarian adds the records in the library database about each student or user
every time issuing the book, returning the book or paying a fine.

By observing these reports ,the student can know the due date so that he can return
the book in time.He can also verify whether he had any fines for the book or not.
PROGRAM-3: DO REQUIREMENTS ANALYSIS AND DEVELOP SOFTWARE
REQUIREMENT SPECIFICATION DOCUMENT FOR PROPOSED SYSTEM.

Introduction:

The proposed Library Management System (LMS) is a software application that aims
to automate and manage the entire library process efficiently. The purpose of this
document is to provide a detailed analysis of the requirements for the proposed LMS
and develop a software requirement specification (SRS) document that outlines the
features, functionalities, and constraints of the system.

1. Functional Requirements:

1.1 User Management

The system should provide user registration and authentication for staff and

students with different roles such as admin, librarian, and member.

1.2 Book Management

The system should provide book inventory management, cataloguing, and searching
of books. The system should also enable book issuing and returning functionality.

1.3 Fine Management

The system should manage fines for late return of books and track the payment of

the fines.

1.4 Reservation Management

The system should provide a reservation system for books that are currently

checked out, allowing members to reserve books online.

1.5 Reporting

The system should generate reports on book inventory, issued books, returned

books, fines, reservations, and overdue books.

2. Non-Functional Requirements:

2.1 Usability

The system should have a user-friendly interface and be easy to use for all types of

users.

2.2 Performance

The system should be able to handle a large number of users and books, without any

significant delays.

2.3 Security

The system should provide secure authentication and authorization, preventing

unauthorised access to the system.

2.4 Availability

The system should be available 24/7, with minimal downtime for maintenance.

2.5 Reliability

The system should be reliable and free from errors, ensuring that all data is accurate

and up-to-date.

3. Constraints:

3.1 Hardware

The system will require a server and storage devices to store data.

3.2 Software

The system will require a web server, a database management system, and

programming languages such as Java, JavaScript, and HTML.

3.3 Legal

The system should comply with all applicable laws and regulations related to data

privacy and security.

Conclusion:

This software requirement specification document outlines the features,

functionalities, and constraints of the proposed Library Management System. The

system should enable user management, book management, fine management,

reservation management, and reporting. The system should also be user-friendly,

secure, reliable, and available 24/7. This document will serve as a basis for the

development of the proposed LMS, ensuring that it meets the requirements of its

stakeholders.
PROGRAM-4: DEVELOPMENT OF ENTITY RELATIONSHIP(E-R) DIAGRAM.

FIG:ENTITY RELATIONSHIP(E-R) DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM.

PROGRAM-5: DESIGN HIGH-LEVEL DESIGN OF THE LIBRARY MANAGEMENT
SYSTEM.

A high-level design of a library management system would typically involve the

following components:

1. User Interface:

The user interface is the front-end of the library management system that allows
users to interact with the system. It should be easy to use and provide a seamless
experience for users.

2. Database Management System:

The database management system is the backbone of the library management

system. It stores all the data related to books, borrowers, loans, and other relevant
information.

3. Search and Retrieval:

The search and retrieval component allows users to search for books based on
various criteria such as author, title, ISBN, etc. It should also allow users to browse
the collection and view information about individual books.

4. Borrowing and Returns:

The borrowing and returns component handles the borrowing and returning of books
by users. It should allow users to check out books and keep track of the due dates. It
should also handle the returns process and update the database accordingly.

5. Notifications and Reminders:

The notifications and reminders component sends notifications and reminders to

users about their due dates and overdue books. It should also notify users when their
reserved books are available.

6. Administrative Functions:

The administrative functions component allows librarians and administrators to

manage the library system. This includes adding and removing books, managing
user accounts, and generating reports.

7. Security and Authentication:

The security and authentication component ensures that the library management
system is secure and accessible only to authorised users. It should require users to
authenticate themselves before accessing the system, and it should enforce
role-based access control to ensure that users can only access the functions they
are authorised to use.

8. Book Management:

This module deals with the management of the library's book collection. It includes
functionalities like book acquisition, cataloguing, circulation, and inventory
management.

9. Circulation Management:

This module handles the circulation of books in the library. It includes functionalities
like book issue, book return, reservation, and renewal.

10. Reporting and Analytics:

This module provides analytics and reports about the library's operations, including
inventory, circulation, and user statistics.

11.Security:
This module ensures that the system is secure and protected against unauthorised
access or data breaches.

Overall, the high-level design of a library management system should be scalable,

reliable, and easy to use. It should be designed with the needs of both users and
administrators in mind, and it should be flexible enough to accommodate future
changes and additions to the system.
PROGRAM-6: DRAW USE CASE AND CLASS DIAGRAMS.

FIG: USE CASE DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM.

USE-CASE NAME:-LOGIN

Both student and librarian login into the library management system by entering their
login credentials.

USE-CASE NAME:-ADD BOOK

The librarian can add the details of the book purchased from shops along with the
shop name.He can also add other details like cost of the book and author.

USE-CASE NAME:-ADD STUDENT

Adding a new student to the system so that he can get a membership and access to
the library.The librarian will add the student details like name,department,roll number.

USE-CASE NAME:-ISSUE BOOK

Librarian issue the book to the candidate based on some conditions:-

1.If he is an existing member,the librarian will check whether the member has any
previous dues,and the total number of books he has taken on that particular library
card.

USE-CASE NAME:-RETURN BOOK

The librarian will check whether the student has returned the book within the due
date ,if not the student has to pay a fine.

USE-CASE NAME:-ADD PENALTY

The librarian will add a penalty for the students who have not returned the book in
time.

USE-CASE NAME:-CHANGE PASSWORD

If the student or librarian forgets his/her password ,they can change it here and get
back the access.

USE-CASE NAME:-VIEW REPORTS

The librarian adds the records in the library database about each student or user
every time issuing the book, returning the book or paying a fine.

By observing these reports ,the student can know the due date so that he can return
the book in time.He can also verify whether he had any fines for the book or not.
FIG: CLASS DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM.
PROGRAM-7: DRAW SEQUENCE AND ACTIVITY DIAGRAMS.

FIG: SEQUENCE DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM.

FIG: ACTIVITY DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM.
PROGRAM-8: DEVELOP THE PROTOTYPE OF THE PRODUCT.

1.login_page: The first page is the login page for students,faculty separately.

2.After faculty login the homepage:

This homepage is displayed for faculty. he/she can have access to all commands in

the menu-bar.

3.requesting BOOK :

After student login. he/she has this type of interface. he/she commands access to

displayed commands in menu bar. he/she selected request book command and

filling form for required book. After filled and clicking on the submit button the

related books are displayed.

4.Book issued:

After the selection of required-books from books available in the above interface.

The details of book issued and deadline are displayed.

5.login issues:

If any issues found in login like username,password wrong then alert box is

displayed and entered credentials are erased.

PROGRAM-9: DEVELOP THE TESTING OF THE PRODUCT.

USE- CASE NAME: - LOGIN PAGE

USE-CASE SPECIFICATION: -

DESCRIPTION: -

Any registration user can login

After cleaning the verification, he/she can initiate subsequent actions.

A registered user can login and upon verification, can initiate subsequent actions.

SPECIAL REQUIREMENTS: -

The minimum length of the username is 8 characters and the maximum length is 20

characters.

The password must include a combination of characters and at-least one

non-alphabetic character. And at least one special character.

If the user gives the wrong input of the username or password the alert
message gets displayed. Passwords should display in dot format.

User must have an account with the library system i.e., he/she must be a registered
user.

POST-CONDITIONS: -

PRIMARY SUCCESS POST-CONDITION: -

It is considered that the user is authenticated and is viewing the main page from

which initiation of the additional actions can be done.

LOGIN FAILURE: -

If the login fails owing to certain reasons described in the alternatives, an appropriate
message will be displayed. Eventually, the user is not considered authenticated.

TEST CASE NAME: - LOGIN PAGE

Test-cases:-username

Test-case-name-1:positive value within maximum boundary length.

input Expected output Actual output remark

veera234 veera234 veera234 Pass

Test-case-name-2:positive value within boundary length.

input Expected output Actual output remark

divya234 divya234 divya234 Pass

Test-case-name-3:positive value within minimum boundary length.

input Expected output Actual output remark

chalice12 chalice12 chalice12 Pass

Test-case-name-4:positive values < boundary length.

input Expected output Actual output remark

govardhan govardhan66 govardhan fail

Test-case-name-5: positive values > boundary length.

input Actual output Expected output remark

Veerababu veerababu Veerababu fail

Test-cases:-password

Test-case-password-1:password checking for combination of alphabets and

non-alphabets

input Actual output Expected output remark

xyzA123** xyzA123** xyzA123** Pass

Test-case-password-2

input Expected output Actual output remark

xyzA123* XyzA123* xyzA123* fail

Test-case-password-3:positive value within minimum boundary length.

input Expected output Actual output remark

123Xyz 123XYZ* 123Xyz fail

Test-case-password-4:

input Expected output Actual output remark

XYZ123* ****** XYZ123* Pass

Test-case-password-5: positive values > boundary length.

input Expected output Actual output remark

xy12ab* ***** xy12ab* Pass