ITAHAR GOVERNMENT POLYTECHNIC
ITAHAR, UTTAR DINAJPUR
DEPARTMENT OF COMPUTER SCIENCE & TECHNOLOGY
Major Project Report On
“Library Management System"
Semester – 5th
Submitted By:
Akash Kumar Saha (D222313186)
Munmun Podder (D222313169)
Subhankar Thakur (D212209217)
Hajikul Islam (D232415842)
Under the guidance of
Somnath Roy
Department of Computer Science and Technology
Itahar Government Polytechnic
1
Library Management System
TABLE OF CONTENTS
ABSTRACT 3
1. INTRODUCTION 4
1.1 PROJECT AIMS AND OBJECTIVES 4
1.2 BACKGROUND OF PROJECT 4
1.3 OPERATION ENVIRONMENT 4
2. SYSTEM ANALYSIS 5-11
2.1 SOFTWARE REQUIREMENT SPECIFICATION 5-9
2.2 EXISTING VS PROPOSED 9
2.3 SOFTWARE TOOL USED 10-11
3. SYSTEM DESIGN 11-16
3.1 DATA FLOW DIAGRAM’S 12
4. SYSTEM IMPLEMENTATION 17-20
4.1 SCREENSHOT 17-20
4.2 MODULE DESCRIPTION 20-21
5. SYSTEM TESTING 21-23
5.1 UNIT TESTING 21
5.2 INTEGRATION TESTING 23
6.
2
Library Management System
ABSTRACT
Online Library Management System is a system which maintains the
information about the books present in the library, their authors, the
members of library to whom books are issued, library staff and all. This
is very difficult to organize manually. Maintenance of all this
information manually is a very complex task.
Owing to the advancement of technology, organization of an Online
Library becomes much simple. The Online Library Management has
been designed to computerize and automate the operations performed
over the information about the members, book issues and returns and all
other operations. This computerization of library helps in many instances
of its maintenances. It reduces the workload of management as most of
the manual work done is reduced.
3
Library Management System
CHAPTER 1
INTRODUCTION
This chapter gives an overview about the aim , objectives ,background and
operation environment of the system.
1.1 PROJECT AIMS AND OBJECTIVES
The project aims and objectives that will be achieved after completion of this
project are discussed in this subchapter. The aims and objectives are as follows:
Online book reading.
A search column to search availability of books.
Facility to download required book.
Video tutorial for students.
An Admin login page where admin can add books, videos or page sources
Open link for Learning Websites
1.2 BACKGROUND OF PROJECT
Library Management System is an application which refers to library systems
which are generally small or medium in size. It is used by librarian to manage the
library using a computerized system where he/she can add new books, videos and
Page sources.
Books and student maintenance modules are also included in this system which
would keep track of the students using the library and also a detailed description
about the books a library contains. With this computerized system there will be no
loss of book record or member record which generally happens when a non
computerized system is used.
1.3 OPERATION ENVIRONMENT
PROCESSOR INTEL CORE PROCESSOR OR BETTER
PERFORMANCE
OPERATING SYSTEM WINDOWS7, WINDOWS10
MEMORY 1 GB RAM OR MORE
HARD DISK SPACE MINIMUM 3 GB FOR DATABASE USE FOR
FUTURE
DATABASE MONGODB
4
Library Management System
CHAPTER 2
SYSTEM ANALYSIS
In this chapter, we will discuss and analyze about the developing process
of Library Management System including software requirement
specification (SRS) and comparison between existing and proposed
system . The functional and non functional requirements are included in
SRS part to provide complete description and overview of system
requirement before the developing process is carried out. Besides that,
existing vs proposed provides a view of how the proposed system will be
more efficient than the existing one.
2.1 SOFTWARE REQUIREMENT SPECIFICATION
2.1.1 GENERAL DESCRIPTION
PRODUCT DESCRIPTION:
Library Management System is a computerized system which helps user(librarian)
to manage the library daily activity in electronic format. It reduces the risk of paper
work such as file lost, file damaged and time consuming.
It can help user to manage the transaction or record more effectively and time-
saving.
PROBLEM STATEMENT:
The problem occurred before having computerized system includes:
●File lost :- When computerized system is not implemented file is always lost
because of human environment. Some times due to some human error there may be
a loss of records.
●File damaged :- When a computerized system is not there file is always lost due
to some accident like spilling of water by some member on file accidentally.
Besides some natural disaster like floods or fires may also damage the files.
5
Library Management System
2.1.2 SYSTEM OBJECTIVES
●Improvement in control and performance:-
The system is developed to cope up with the current issues and problems of library
The system can add user, validate user and is also bug free.
●Save cost :-
After computerized system is implemented less human force will be required to
maintain the library thus reducing the overall cost.
●Save time:-
Librarian is able to search record by using few clicks of mouse and few search
keywords thus saving his valuable time.
●Option of online Notice board :-
Librarian will be able to provide a detailed description of workshops going in the
college as well as in nearby colleges.
●Lecture Notes:-
Teacher have a facility to upload lectures notes in a pdf file having size not more
than 10mb.
6
Library Management System
2.1.3 SYSTEM REQUIREMENTS
[Link] NON FUNCTIONAL REQUIREMENTS
● Product Requirements
EFFICIENCY REQUIREMENT:-
When a library management system will be implemented librarian and user will
easily aces library as searching and book transaction will be very faster .
RELIABILITY REQUIREMENT:-
The system should accurately performs member registration ,member validation ,
report generation, book transaction and search
USABILITY REQUIREMENT:-
The system is designed for a user friendly environment so that student and staff of
library can perform the various tasks easily and in an effective way.
[Link] FUNCTIONAL REQUIREMENTS
1. NORMAL USER
1.1 USER LOGIN
Description of feature :-
This feature used by the user to login into system. They are required to enter user id
and password before they are allowed to enter the system .The user id and
password will be verified and if invalid id is there user is allowed to not enter the
system.
Functional requirements :-
-user id is provided when they register
-The system must only allow user with valid id and password to enter the system
-The system performs authorization process which decides what user level can aces
to.
-The user must be able to logout after they finished using system.
7
Library Management System
1.2 REGISTER NEW USER
Description of feature :-
This feature can be performed by all users to register new user to create account.
Functional requirements:-
-System must be able to verify information
-System must be able to delete information if information is wrong
2.1.4 SOFTWARE AND HARDWARE REQUIREMENTS
This section describes the software and hardware requirements of the system
[Link] SOFTWARE REQUIREMENTS
●Operating system :- Windows 11 pro is used as the operating system as it is stable
and supports more features and is more user friendly
●Database MONGO :- DB is used as database as it easy to maintain and retrieve
records by simple queries which are in English language which are easy to
understand and easy to write.
●Development tools and Programming language :- React with Type script, Vite is
used to write the whole code and develop webpages with Tailwind CSS, java script
for styling work and [Link] for sever side scripting.
8
Library Management System
[Link] HARDWARE REQUIREMENTS
●Intel core i5 2nd generation is used as a processor because it is fast than other
processors an provide reliable and stable and we can run our pc for longtime. By
using this processor we can keep on developing our project without any worries.
●RAM 1 GB is used as it will provide fast reading and writing capabilities and will
in turn support in processing.
Existing System:
● Early days Libraries are managed manually. It required lot of time to record or to
retrieve the details. The employees who have to record the details must perform
their job very carefully. Even a small mistake would create a lot of problems.
Security of information is very less. Report generations of all the information is
very tough task.
● Maintenance of Library catalogue and arrangement of the books to the catalogue
is very complex task. In addition to its maintenance of member details, issue dates
and return dates etc. manually is a complex task.
● All the operations must be performed in perfect manner for the maintenance of
the library with out any degradation which may finally result in the failure of the
entire system.
Proposed System:
To solve the inconveniences as mentioned in the existing system, an Online
Library is proposed. The proposed system contains the following features:
●Individually each member will have his account through which he can access the
information he needs.
●Book details like authors, number of copies totally maintained by library, present
available number of books, reference books, non-reference books etc. all this
information can be made handy.
●Regarding the members designation, number of books was issued.
●Issue dates and returns of each member is maintained separately and fine charged
if there is any delay in returning the book.
●Administrator can add, update the books.
●Time consuming is low, gives accurate results, reliability can be improved with
the help of security.
9
10
2.3 SOFTWARE TOOLS USED
The whole Project is divided in two parts the front end and the back end.
2.3.1 Front end
The front end is designed using of React, TypeScript, Vite, Tailwind CSS
[Link]
● What it is: React is a JavaScript library for building user interfaces (UIs). It's maintained by
Facebook (now Meta) and a large community of developers.
Key features:
● Component-based :- React allows you to build UIs by creating reusable components, which are
like building blocks. This makes code more organized, maintainable, and reusable.
● Declarative :- You describe what you want the UI to look like, and React takes care of updating
the actual DOM (Document Object Model) efficiently. This simplifies development and makes
code more predictable.
● Virtual DOM :- React uses a virtual DOM, which is a lightweight representation of the actual
DOM. This allows React to optimize updates and minimize direct manipulations to the real DOM,
improving performance.
[Link]
● What it is: TypeScript is a superset of JavaScript that adds static typing. This means you can
define the types of variables, function parameters, and return values.
Key benefits:
● Early error detection: TypeScript can catch type-related errors during development, before they
even reach the browser.
● Improved code maintainability: Types make code easier to understand and refactor, especially in
large projects.
● Better code completion and navigation: IDEs (Integrated Development Environments) can
provide better code completion, suggestions, and navigation thanks to type information.
10
11
3. Vite
What it is: Vite is a build tool that aims to provide a faster and leaner development experience for
modern web projects.
Key advantages:
● Fast cold start: Vite leverages native ES modules, which allows it to start the development server
almost instantly.
● Instant updates: Vite uses hot module replacement (HMR) to provide near-instant updates in the
browser when you make changes to your code.
● Optimized production builds: Vite also optimizes production builds with features like code
splitting and tree-shaking.
4. Tailwind CSS
● What it is: Tailwind CSS is a utility-first CSS framework. Instead of providing pre-designed
components, it gives you a large set of low-level utility classes that you can use to style your
HTML directly.
● Key characteristics:
●Utility-first: You compose styles by applying small, single-purpose utility classes (e.g., text-red-
500, bg-gray-200, p-4).
● Highly customizable: You can customize the default styles and create your own utility classes to
match your design.
● Rapid development: Tailwind CSS allows you to style elements quickly without writing custom
CSS from scratch.
11
12
CHAPTER 3
SYSTEM DESIGN
3.1 DATA FLOW DIAGRAMS
DATA FLOW DIAGRAM FOR ADMIN LOGIN
After entering to the home page of the website , Admin can choose the Admin Login option
where they are asked to enter username & password , and if he/she is a valid user then a teacher
login page will be displayed.
12
13
USE CAESE DIAGRAM FOR USER
After entering to the home page of the website , student can choose the USER LOGIN option
where they are asked to enter username & password , and if he/she is a valid user then a student
login page will be displayed.
13
14
DATA FLOW DIAGRAM FOR USER
14
15
USER CASE DIAGRAM FOR ADMIN
15
16
SEQUENCE DIAGRAM
16
17
CHAPTER 4
SYSTEM IMPLEMENTATION
4.1 Screenshot for homepage
17
18
4.2 Screenshot of Signup /Login for user
18
19
4.3 Screenshot of Dashboard for user
4.4 Screenshot of signup/login for admin
19
20
4.5 Screenshot of Dashboard for admin
5. MODULE DESCRIPTION
For Library Management System it is divided into the following Modules:
5. [Link] Code for frontend
import { BrowserRouter as Router, Routes, Route } from 'react-router-dom';
import { Toaster } from 'react-hot-toast';
import { AuthProvider } from './context/AuthContext';
import LandingPage from './components/LandingPage';
import LoginForm from './components/auth/LoginForm';
import SignupForm from './components/auth/SignupForm';
// For admin
import AdminLogin from './components/auth/AdminLogin';
import AdminSignup from './components/auth/AdminSignup';
import UserDashboard from './components/dashboard/UserDashboard';
import AdminDashboard from './components/dashboard/AdminDashboard';
import Navbar from './components/layout/Navbar';
20
21
import ProtectedRoute from './components/layout/ProtectedRoute';
function App() {
return (
<AuthProvider>
<Router>
<div className="min-h-screen bg-gray-50">
<Navbar />
<Routes>
{/* Public routes */}
<Route path="/" element={<LandingPage />} />
<Route path="/login" element={<LoginForm />} />
<Route path="/signup" element={<SignupForm />} />
<Route path="/admin/login" element={<AdminLogin />} />
<Route path="/admin/signup" element={<AdminSignup />} />
{/* Protected routes */}
<Route
path="/dashboard"
element={
<ProtectedRoute>
<UserDashboard />
</ProtectedRoute>
}
/>
<Route
path="/admin"
element={
<ProtectedRoute requireAdmin>
<AdminDashboard />
</ProtectedRoute>
}
/>
</Routes>
<Toaster position="top-right" />
</div>
</Router>
</AuthProvider>
);
}
export default App;
21
22
CHAPTER 5
SYSTEM TESTING
The aim of the system testing process was to determine all defects in our project.
The program was subjected to a set of test inputs and various observations were
made and based on these observations it will be decided whether the program
behaves as expected or not. Our Project went through two levels of testing
[Link] Testing.
2. Integration Testing.
[Link] TESTING:-
Unit testing is undertaken when a module has been created and succesfully reviewed .In order to
test a single module we need to provide a complete environment ie besides the module we would
require
● The procedures belonging to other modules that the module under test calls
● Non local data structures that module accesses
● A procedure to call the functions of the module under test with appropriate parameters
Unit testing was done on each and every module that is described under module description of
chapter 4
[Link] For the admin module
●Testing admin login form-This form is used for log in of administrator of the [Link] this we
enter the username and password if both are correct administration page will open other wise if
any of data is wrong it will get redirected back to the login page and again ask for username and
password.
●Student account addition- In this section the admin can verify student details from student
academic info and then only add student details to main library database it contains add and
delete buttons if user click add button data will be added to student database and if he clicks delete
button the student data will be deleted.
22
23
●Book Addition- Admin can enter details of book and can add the details to the main book table
also he can view the books requests .
2. Test for Student login module
●Test for Student login Form-This form is used for log in of Student .In this we enter the library,
username and password if all these are correct student login page will open other wise if any of data
is wrong it will get redirected back to the login page and again ask for library, username and
password.
●Test for account creation- This form is used for new account creation when student does not fill
the form completely it asks again to fill the whole form when he fill the form fully it gets redirected
to page which show waiting for conformation message as his data will be only added by
administrator after verification.
Test for Admin login module-
Test for teacher login form- This form is used for logg in of teacher .In this we enter the username
and password if all these are correct teacher login page will open other wise if any of data is wrong
it will get redirected back to the login page and again ask for username and password.
2. INTEGRATION TESTING :-
In this type of testing we test various integration of the project module by providing the input.
The primary objective is to test the module interfaces in order to ensure that no errors are
occurring when one module invokes the other modules.
23
24
CHAPTER 6
FUTURE SCOPE
This website provides a computerized version of library management system which will benefit
the students as well as the staff of the library.
It makes entire process online where student can search books, staff can generate reports and do
book transactions. It also has a facility for student login where student can login and can see status
of books issued as well request for book or give some suggestions. It has a facility of teacher’s
login where teachers can add lectures notes and also give necessary suggestion to library and also
add info about workshops or events happening in our college or nearby college in the online
notice board.
There is a future scope of this facility that many more features such as online lectures video
tutorials can be added by teachers as well as online assignments 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.
24