PES UNIVERSITY BENGALURU

Department of Computer Science and Engineering

Deliverable 4: Final Report

Department of Computer Science and Engineering

BENGALURU, KARNATAKA, INDIA.
B. TECH.(CSE) V
SEMESTER
Aug. – Dec. 2024

UE22CS341A – SOFTWARE ENGINEERING PROJECT REPORT

ON

LIBRARY MANAGEMENT SYSTEM

SUBMITTED BY

SRN -- NAME
1) PES2UG2CS400 – Pranav Maiya
2) PES2UG22CS418 – Pullagura Santosha
 Table of contents

Sl. No. Topic Page No.

1. Proposal of the Project 3
2. Software Requirements 4
Specification
3. Project Plan 17
4. Design Diagrams 22
5. Test Cases 28
6. Results (Screen Shots) 32
 PES UNIVERSITY
Department of Computer Science and Engineering

UE22CS341A: So ware Engineering Deliverable 1:

Abstract and SRS

So ware Requirements Specifica on

for

Library Management Database System

Prepared by Pranav Maiya and Pullagura Santosha

Pranav Maiya PES2UG22CS400

Pullagura Santosha PES2UG22CS418

 Table of Contents
1. Introduc on.......................................................................................................................… 1
1.1 Purpose .......................................................................................................................1
1.2 Intended Audience and Reading Sugges ons...............................................................1
1.3 Product Scope.............................................................................................................1

2. Overall Descrip on ...............................................................................................................2

2.1 Product Perspec ve .....................................................................................................2
2.2 Product Func ons........................................................................................................2
2.3 User Classes and Characteris cs...................................................................................3
2.4 Opera ng Environment................................................................................................4
2.5 Design and Implementa on Constraints......................................................................4

3. External Interface Requirements...........................................................................................4

3.1 User Interfaces.............................................................................................................5
3.2 So ware Interfaces......................................................................................................5

4. System Features....................................................................................................................6

5. Other Nonfunc onal Requirements......................................................................................6

Abstract
This project aims to develop a comprehensive University Library Management Database
System to streamline library opera ons. The system will automate key func ons such as
cataloging, member management, book issuance, and returns, thereby enhancing
efficiency and accuracy. U lizing a robust database design, the system will ensure secure
and efficient data handling. The project will also incorporate user-friendly interfaces for
both library staff and patrons, facilita ng easy access to library resources. Ul mately,
this system will support the library’s mission to provide seamless access to informa on
and improve overall user experience.

1. Introduc on
1.1 Purpose

The purpose of this project is to develop a dedicated University Library Management

Database System for our campus, addressing the current lack of an accessible library
website. While the other campus has a func onal library system, our branch faces
significant challenges in managing library resources efficiently. This project aims to
bridge this gap by providing a robust, user-friendly pla orm that will streamline library
opera ons, enhance resource accessibility, and improve the overall user experience for
students and staff at our campus.

1.2 Intended Audience

The primary audience for this project includes students and teachers at the university.
Students, who will act as both borrowers and depositors, will benefit from streamlined
access to library resources, efficient book issuance, and return processes. Teachers,
serving as administrators, will u lize the system to manage library opera ons, oversee
cataloging, and ensure the smooth func oning of library services. Addi onally, library
staff will use the system to maintain accurate records and facilitate user interac ons,
enhancing the overall efficiency and user experience.

1.3 Product Scope

The scope of this project encompasses the development of a comprehensive library

management system tailored for our campus. The system will include modules for
cataloging, member management, book issuance, and returns. It will feature
userfriendly interfaces for students and teachers, ensuring easy access to library
resources and efficient management of library opera ons. Addi onally, the system will
incorporate robust security measures to protect user data and maintain the integrity of
library records. The project aims to deliver a reliable, scalable solu on that enhances
the overall efficiency and user experience of the university library.
 2. Overall Descrip on

This project involves the crea on of a University Library Management Database System
specifically designed for our campus. The system aims to automate and streamline
various library opera ons, including cataloging, member management, book issuance,
and returns. It will feature intui ve interfaces for students and teachers, facilita ng easy
access to library resources and efficient management of library ac vi es. The system
will also incorporate robust security measures to ensure data integrity and protect user
informa on. By addressing the current lack of a dedicated library website for our
campus, this project seeks to enhance the overall efficiency, accessibility, and user
experience of the university library.

2.1 Product Perspec ve

The University Library Management Database System will func on as a centralized

pla orm within the broader context of the university’s IT infrastructure. It is designed to
replace or complement exis ng manual or semi-automated library systems that may be
fragmented or outdated. The system will interact with various other subsystems, such as
student informa on systems and faculty management systems, to ensure seamless
integra on and data consistency. Built using Node.js for the backend, React for the
frontend, and MySQL as the database, the system will leverage modern web
technologies to provide a scalable, secure, and efficient solu on. This will facilitate
future enhancements and ensure compa bility with other contemporary technologies
used within the university

2.2 Product Func ons

The University Library Management Database System will offer a range of core
func ons, including:

• Data Management: Storing and managing data related to books, journals,

members, and transac ons.
 • Cataloging: Automa ng the cataloging process for new acquisi ons, including
classifica on and indexing.

• Member Management: Handling member registra ons, renewals, and profile

updates.

• Book Issuance and Returns: Streamlining the process of issuing and returning
books, including tracking due dates and fines.

• Search and Retrieval: Providing advanced search capabili es to locate books and
other resources quickly.

• Repor ng and Analy cs: Genera ng detailed reports on library usage, inventory
status, and member ac vity for analysis and decision-making.

• User No fica ons: Sending no fica ons to users about due dates, overdue
items, and new arrivals.

2.3 User Classes and Characteris cs

The system will be used by different classes of users, each with dis nct characteris cs:

• Students: Ac ng as both borrowers and depositors, students require a

userfriendly interface to search for books, check availability, and manage their
borrowing ac vi es. They need quick access to accurate data and no fica ons
about due dates and new arrivals.
 • Teachers: Serving as administrators, teachers will use the system to manage
library opera ons, oversee cataloging, and ensure the smooth func oning of
library services. They need tools for managing book issuance, returns, and
member records efficiently.

• Library Staff: These users will handle the day-to-day opera ons of the library,
including cataloging new acquisi ons, managing member registra ons, and
maintaining the database. They require advanced tools for database
management, system updates, and ensuring data integrity.

• System Administrators: Responsible for the backend, system administrators will

manage database maintenance, system updates, and security. They need robust
tools for managing the database, ensuring system integrity, and troubleshoo ng
issues.

2.4 Opera ng Environment

The University Library Management Database System will be deployed in a robust,

secure environment, tailored to the university’s IT infrastructure. The backend will be
developed using Node.js and will be compa ble with MySQL as the database
management system. The frontend will be built using React, ensuring it is web-based
and accessible via modern browsers on both desktop and mobile devices. The system
must operate reliably under varying load condi ons, as it will handle significant volumes
of data and transac ons related to library opera ons. Addi onally, it will incorporate
security measures to protect user data and ensure system integrity.
2.5 Design and Dependencies

The design of the University Library Management Database System will follow a
modular architecture, ensuring that each component can be developed, tested, and
maintained independently. The backend will be developed using Node.js, with a focus
on scalability and high performance, and will rely on MySQL for efficient data storage.
For the user interface, we will use React, a JavaScript library that simplifies the
crea on of interac ve web applica ons. React will enable us to build a responsive and
intui ve interface for students, teachers, and library staff. Key dependencies for the
project include the chosen DBMS (MySQL), the React library for the user interface,
and any addi onal Node.js packages or APIs necessary for real- me data processing,
analy cs, and integra on with external systems.

3. External Interface Requirements

The External Interface Requirements describe the interac on between the University
Library Database System and external en es, including users and other so ware
systems. This sec on focuses on the User Interfaces (UIs) and So ware Interfaces,
detailing how users will interact with the system and how it will integrate with other
so ware components.

3.1 User Interface

The user interface for the University Library Management Database System will be built
using React, a JavaScript library designed for crea ng interac ve and intui ve web
applica ons. The UI will be accessible via a web browser, providing a responsive and
user-friendly experience for students, teachers, and library staff. Interfaces for managing
book data, member informa on, and transac on records will be available, allowing
users to add, update, or delete records easily. The UI will be designed to be intui ve,
with clear naviga on and visual elements that make it easy for users to find and interact
with the necessary features. Addi onally, the interface will include search
func onali es, no fica ons, and repor ng tools to enhance user experience and
opera onal efficiency.

3.2 So ware Interface

The University Library Management Database System will interact with various other
so ware systems and components, requiring well-defined so ware interfaces. The
backend will connect to a rela onal database management system (DBMS) such as
MySQL. The so ware interface will handle CRUD (Create, Read, Update, Delete)
opera ons on the database, ensuring efficient data storage and retrieval. Interfaces for
expor ng and impor ng data (e.g., CSV, JSON) will be provided to facilitate data
exchange with other systems or for backup purposes. These so ware interfaces will be
designed to be robust, secure, and scalable, ensuring smooth and reliable interac ons
between the University Library Management Database System and external systems.

4. System Features
• User-Friendly Interface: An intui ve web interface that allows easy naviga on for
all users, including students, teachers, and library staff.

• Catalog Management: Simple tools to manage book cataloging efficiently,

including adding, upda ng, and dele ng book records.

• Member Management: Features for handling member registra ons, renewals,

and profile updates.

• Book Issuance and Returns: A streamlined process for issuing and returning
books, including tracking due dates and fines.
 • Basic Analy cs Dashboard: A dashboard providing key performance indicators
about library usage, inventory status, and member ac vity.

• Search Func onality: A search feature to quickly find specific books, journals, or
other library resources.

• Mul -Device Access: Compa bility with desktop and mobile devices for easy
access by users on the go.

5. Non-Func onal Requirements

Non-func onal requirements define the quality a ributes, system performance, and
constraints that the University Library Management Database System must meet. These
requirements ensure that the system operates effec vely and efficiently. Key
nonfunc onal requirements include:
• Performance: The system should provide responses to user queries within 2
seconds under normal load. It must handle at least 100 concurrent users without
performance degrada on.
• Scalability: The system should be designed to scale horizontally to accommodate
increased user demand and addi onal data without significant re-engineering.
• Reliability: The system should achieve 99.9% up me, ensuring availability for
users at all mes. It must maintain data accuracy and consistency, even in the
event of failures.
• Usability: The user interface must be intui ve and easy to navigate, minimizing
the learning curve for new users and enabling efficient task comple on.
Requirements traceability matrix :
Use case diagram :
 PES UNIVERSITY, BANGALORE
Department of Computer Science and Engineering
B. Tech (CSE) – 5th Semester – Aug-Dec 2024

UE22CS303 - Software Engineering

DESIGN DOCUMENT
PROJECT TITLE

Library Management System Team #: __TEAM 6____

SRN1 Name 1
PES2UG22CS400 Pranav Maiya
Name 2
SRN 2
Pullagura
PES2UG22CS418
Santosha

General Instructions ( Delete these instructions from the document before submission) :
● Formatting Guidelines : Submit in pdf format
● Naming convention : Design SRN1-SRN2-SRN3-SRN4 (Write SRNs in ascending order)
● Don’t forget to fill the Project Title on the first page as well as the footer

Aug-
Design of < PROJECT TITLE > Team#: ______

Dec 2024 UE22CS341A : SE Page 1

Design Diagrams

Architectural Design

Aug-Dec 2023 UE21CS341A : SE Page 2 / 6

Design of < PROJECT TITLE > Team#: ______

UML

Use Case Diagram

Aug-Dec 2023 UE21CS341A : SE Page 3 / 6

Design of < PROJECT TITLE > Team#: ______

Class Diagram

Aug-Dec 2023 UE21CS341A : SE Page 4 / 6

Design of < PROJECT TITLE > Team#: ______

Aug-Dec 2023 UE21CS341A : SE Page 5 / 6

Design of < PROJECT TITLE > Team#: ______

Aug-Dec 2023 UE21CS341A : SE Page 6 / 6

 Project Plan for Library Management System
Name : Pranav Maiya , Pullagura Santosha

Section : G

Team No : 6

1. Lifecycle Model Selection

For the Library management system , we have chosen the Waterfall Model.
Justification:
The Waterfall Model is a sequential and structured approach that works well when the project
requirements are well-understood and stable. In the case of the Library Management System, the core
functionalities (book inventory management, user management, borrowing/returning system, overdue
notifications, reporting, and role-based access control) are defined clearly, and major changes in
requirements are not expected during the development process.
The Waterfall Model follows a step-by-step progression, ensuring that each phase—requirements
gathering, system design, implementation, testing, deployment, and maintenance—is completed before
moving on to the next. This provides clarity, minimizes ambiguity, and ensures that each phase is
thoroughly documented and reviewed.
This makes the Waterfall Model an ideal choice because it ensures that the foundation (e.g., database
schema for managing books, users, transactions) is solid before moving to the next phases, reducing the
risk of rework or inconsistencies.

2. Tools Required

Planning Tool:
• Jira: Jira helps break big ideas down into achievable steps. This tool will be used to track all
aspects of the software development cycle. For managing tasks and tracking progress to make sure
that deliverables are delivered on schedule.
Design Tool:
• draw.io: We can use it to design Entity-Relationship Diagrams, Data Flow Diagrams, Wireframes
and Mockups and system architecture. This helps us create a easy to understand abstraction of the
databases that make up our metro system.
Version Control Tool:
 • Git & GitHub: For version control we use git, it allows us to maintain branches and allow multiple
developers to work on the project. Github allows for a platform where we can host code, enabling
collaboration among developers and tracking code changes.
Development Tool:
• Node.js: Node.js will be used for backend programming, React for the frontend, and MySQL for
database management.
Bug Tracking Tool:
• Jira: Jira will be used for bug tracking and issue management alongside its primary use as a
planning and collaboration tool.
Testing Tool:
• Jest: Jest will be used for automated testing of the JavaScript codebase for unit testing. It will test
backend logic and frontend components to ensure each module (such as user management, book
borrowing/return, and overdue notifications) works as expected.
• Postman: Postman is a tool for testing APIs. Since the backend of the Library Management
System will expose APIs to interact with the database and user interface, Postman will be used to
test the requests, such as adding new books, checking availability, or fetching user records,
ensuring correct data return and proper error handling.
• MySQL Workbench: MySQL Workbench can be used to design, model, and test the MySQL
database. This will ensure that queries, stored procedures, and database integrity are functioning
properly, such as ensuring book checkouts are correctly recorded and that no data anomalies
occur.
Database Management System:
• MySQL: MySQL will be used for managing the relational database. It is an open-source
relational database management system widely used for web applications, ensuring efficient
handling of book inventory, user records, and transactions.

3. Deliverables
This is the respective Work Breakdown Structure (WBS) for the following projcet that we
are doing, it contains all the main subprojects that will be required as well as all their
respective subtasks.
5. Effort Estimation

Gantt Chart :-

6. Coding Details
Frontend Code
• Technology: React
• Description: Use React to build a user-friendly interface for the Library Management System. The
frontend will include components for displaying book inventories, user information, borrowing
history, and overdue notifications.
• Key Features:
o Input forms for searching books by title, author, or genre. o Display of book
availability, user borrowing history, and due dates. o Responsive layout for different
user roles (admin, librarian, and student).
Backend Code
• Technology: Node.js
• Description: The backend will be developed using Node.js to handle business logic, data processing,
and interactions with the MySQL database. This layer will expose APIs for the frontend to fetch and
manipulate library data.
• Key Features:
o Implementing RESTful API endpoints for CRUD operations (books, users, transactions).
o Business logic for managing book borrowing/returning, fine calculations, and overdue
notifications.
o Integration with user authentication and role-based access control (RBAC).
Database Code
• Technology: SQL (MySQL)
• Description: SQL will be used to design and manage the relational database that stores all library
management data. The database schema will include tables for books, users, transactions
(borrowing/return), and fines.
• Key Features:
o Define relational tables with appropriate relationships (e.g., foreign keys for users and
book transactions).
o Write SQL queries for data retrieval, insertion, updating, and deletion.
o Implement database triggers for overdue fine calculation and status updates.
Testing Code
• Tools: Postman and MySQL Workbench
• Description: Use Postman to test the API endpoints and MySQL Workbench for database testing. This
will ensure that all components of the system function correctly and that data integrity is maintained.
• Key Features:
o Postman: Create and run test cases for each API endpoint, validating responses, status
codes, and data formats.
o MySQL Workbench: Write unit tests for stored procedures, queries, and database triggers
to ensure correct behaviour and performance.
Test Plan Details – Library Management
System
PES2UG22CS418 – Pullagura Santosha
PES2UG22CS400 -Pranav Maiya
Test Results: