Project Report On Library Management System

PUSTAKAALAY PRANALEE
A PROJECT REPORT
Submitted in partial fulfilment of the Requirements for the award of the Degree of
BACHELOR OF COMPUTER APPLICATION
BY
Shashank Shekhar Swain & Yuvraj Singh

AJU/181146 & AJU/181127
Under the esteemed guidance of
Mr./Mrs. Name of The Guide

Designation
DEPARTMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY
ARKA JAIN UNIVERSITY, JHARKHAND

JAMSHEDPUR
2021
ARKA JAIN UNIVERSITY, JHARKHAND
JAMSHEDPUR
DEPARTMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY
CERTIFICATE
This is to certify that the project entitled, "PUSTAKAALAY PRANALEE", is bonafied work
of SHASHANK SHEKHAR SWAIN & YUVRAJ SINGH bearing Roll No: (144) & (143)
submitted in partial fulfillment of the requirements for the award of degree of BACHELOR OF
COMPUTER APPLICATION from ARKA JAIN University, JHARKHAND.
Internal Guide Coordinator
External Examiner
Date: University Seal

ABSTRACT
Pustakaalay Pranaalee 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 admin and
all.
This is very difficult to organize manually as 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 system would provide basic set of features to add/update members, add/update books, and
manage check in specifications for the systems based on the client’s statement of need.
It reduces the workload of management as most of the manual work done is automated and
reduce.
Pustakaalay Pranaalee is a typical management Information system (MIS), its Development

include the establishment and maintenance of back-end database and front-end application
development aspects.
For the former require the establishment of data consistency and integrity of the strong data
security and good libraries.
As for the latter requires the application fully functional, easy to use and so on.
ACKNOWLEDGEMENT
We take this occasion to thank God, almighty for blessing us with his grace and taking Our
endeavor to a successful culmination. We extend our sincere and heartfelt thanks to our
Esteemed guide,__________________, for providing us with the right guidance and Advice at
the crucial junctures and for showing me the right way. We also take this opportunity to Express
a deep sense of gratitude to our class coordinators, Ms. DIVYA PAIKARAY and Mrs.
PREETHA S for their cordial support, valuable suggestions and guidance. We extend our
Sincere thanks to our respected Head of the division Mr. ARVIND PANDEY, for Allowing us
to use the facilities available. We would like to thank the other faculty members also, at this
occasion. Last but not the least, we would like to thank our friends and family for the Support
and encouragement they have given us during the course of our work.
DECLARATION
I hereby declare that the project entitled, “Pustakaalay Pranalee” done at Arka Jain
University, has not been in any case duplicated to submit to any other university for the award of
any degree. To the best of my knowledge other than me, no one has submitted to any other
university.
The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF COMPUTER APPLICATION to be submitted as final semester project as
part of our curriculum.
Shashank Shekhar Swain Yuvraj Singh

TABLE OF CONTENTS
Chapter 1 : Introduction.……………………………………………………… 01
1. Background of Project…………………………..……………………………………01
2. Project Aims And Objectives…………………………………….…………………..02
3. Purpose and Scope……………………………………………………..……………..03
4. Features Of Pustakaalay Pranalee………………………………………….……...04
5. Benefits Of Pustakaalay Pranalee………………………………………………….04
Chapter 2 : System Analysis………………………………………………..…. 05
1. Existing System………………………………………………………………………05
2. Proposed System……………………………………………………………………..06
3. Requirement Analysis……………………………………………………………….07
4. System Requirements………………………………………………………………..08
5. Hardware Requirements…………………………………………………………….10
6. Software Requirements……………………………………………………………...11
7. Justification of selection of Technology…………………………………………….11
Chapter 3 : System Design……………………..…………………………........ 15
1. Module Division……………………………………………………………………...15
2. Data Dictionary………………………………………………………………………16
3. ER Diagrams…………………………………………………………………………19
4. DFD/UML Diagrams………………………………………………………………...20
Chapter 4 : Implementation and Testing………………………...................... 23
1. Coding Phase (Place Core segments)………………………………………………23

2. Testing Approach…………………………………………………………………...44
3. Unit Testing (Test cases and Test Results)………………………………………...44
4. Integration System (Test cases and Test Results)………………………………....46
Chapter 5 : Results and Discussions (Output Screens)……………………… 47
Chapter 6 : Conclusion and Future Work…………………………………… 59
Chapter 7 : References………………………………………………………… 60
List Of Figures
1. Chapter 3 : System Design……………………………………………… 15

 Fig 1 : Admin data table…………………………………………….…16
 Fig 2 : Book data table…………………………………………………17
 Fig 3 : Comments data table…………………………………………..17
 Fig 4 : Fine data table………………………………………………….17
 Fig 5 : Issue_book data table…………………………………………..18
 Fig 6 : Student data table………………………………………………18
 Fig 7 : ER Diagram……………………………………………………..19
 Fig 8 : Data Flow Diagram (DFD) level 0.............................................20
 Fig 9 : Data Flow Diagram (DFD) level 1……………………………..21
 Fig 10 : Data Flow Diagram (DFD) level 2…………...........................22
2. Chapter 5 : Results and Discussions…………………………………... 47

 Fig 11 : Home page…………………………………………………….47
 Fig 12 : List of Books page…………………………………………….48
 Fig 13 : Feedback page………………………………………………...48
 Fig 14 : Sign up page selection………………………………………...49
 Fig 15 : Sign up page…………………………………………………..49
 Fig 16 : Login page…………………………………………………….50
 Fig 17 : Change Password page...........................................................50
 Fig 18 : Admin - Profile page…………………………………………51
 Fig 19 : Admin - Side Navigation page……………………………….51
 Fig 20 : Admin - Add Book page……………………………………...52
 Fig 21 : Admin - Book Request page………………………………….52
 Fig 22 : Admin - Issued book page…………………………………...53
 Fig 23 : Admin - Student Information page…………………………53
 Fig 24 : Admin - Book Expired page…………………………………54
 Fig 25 : Admin - Fine page……………………………………………54
 Fig 26 : Student - Profile page………………………………………..55
 Fig 27 : Student - Side Navigation page……………………………...55
 Fig 28 : Student - Book Request Info page…………………………..56
 Fig 29 : Student - Issued book page……………………...…...……...56
 Fig 30 : Student - Book Expired page………………………………..57
 Fig 31 : Student - Fine page…………………………………………..57
 Fig 32 : Fine Payment Page…………………………………………..58
Chapter 1
Introduction
The project titled Pustakaalay Pranaalee is Library Management software for monitoring and
controlling the activities in a library .
The project “Pustakaalay Pranaalee” is developed in php, which mainly focuses on basic
operations in a library like adding new books, and updating new information, searching books
and members and return books.
This chapter gives an overview about the background, objectives, purpose and scope.
1.1 Background Of Project
Pustakaalay Pranaalee 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
record various transactions like issue of books, return of books, addition of new books, addition
of new students etc.
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. In addition, report module is also
included in Pustakaalay Pranaalee. If user’s position is admin, the user is able to generate
Page 11
different kinds of reports like lists of students registered, list of books, issue and return reports.
Pay his/her fine online.
All these modules are able to help librarian to manage the library with more convenience and in
a more efficient way as compared to library systems which are not computerized.
1.2 Project Aims and Objectives
The project aims and objectives that will be achieved after completion of this project are as
follows :-
1. Online book issue.
2. Generate reports on user information & books information.
3. Admin can add, update or delete books.
4. Request column for Admin for providing new books.
5. A search column to search availability of books.
6. Student login page where student can search and finds all the books.
7. Student can request books which will be issued by Admin and date of return will be given.
8. Student can request to Admin to reschedule book's date of return.
9. Admin can send reminders to user when date of returns is about come.
10. Fine will be calculated on late submission of book.
11. Online payment system helps student to pay their fine online mode.
Page 12
1.3 Purpose and Scope
1.3.1 Purpose
The purpose of this project is to provide a friendly environment to maintain the details of books
and library members.
The main purpose of this project is to maintain easy circulation system using computers and to
provide different reports.
1.3.2 Scope
The document only covers the requirements specifications for the Library Management System.
This document does not provide any references to the other component of the Library
Management System.
All the external interfaces and the dependencies are also identified in this document.
Feasibility study: The overall scope of the feasibility study was to provide sufficient
information to allow a decision to be made as to whether the project Pustakaalay Pranaalee
should proceed
and if so, its relative priority in the context of other existing Library Management Technology.
The feasibility study phase of this project had undergone through various steps which as describe
as under:
1. Identify the origin of the information at different level.
Page 13
2. Identify the expectation of user from computerized system.
3. Analyze the drawback of existing system (manual system)
1.4 Features Of Pustakaalay Pranalee
1. Using Pustakaalay Pranalee the Admin can catalogue and maintain all types of books,
journals, User Information etc.
2. Provision to request for new titles, Authors &Editions.
3. Powerful search engine allows users to find information in the library in no time.
4. Charge users for lost/damaged books.
5. Automatic fine fees calculation.
1.5 Benefits Of Pustakaalay Pranalee
1. User friendly.
2. Highly flexibility.
3. Highly secure.
4. Online Fine Payment.
5. Inventory and stock management.
6. Complete reports.
Page 14
CHAPTER 2
SYSTEM ANALYSIS
In this chapter, we will discuss and analyze about the developing process of Pustakaalay
Pranalee 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 Existing System
In the available Online Library Management System, librarian maintains the details of each book
on the registers so to find out the number of books available in the library they need to go to
check the entire entry which makes the process slow.
While they need to spend an extra hour to maintain the records of books. For a student who
wants to know about a book in the library need to search the entire book section. The student
needs to check the status of the book means the last date of book, how many books has issued.
Page 15
2.2 Proposed System
Proposed system is an automated Pustakaalay Pranalee. This project will help the students and
Admin to maintain the details of the library.
It will assist the Admin before the shortage of books while they can know the details of the
number of currently available in the library according to the author by accessing the system. A
student can view the details of the book issued by them, and the system will notify the students
about the last date of submission of books.
At the time of issue of a book, the student will get assisted by the system about different authors
of a similar book so that they can get the best available book from the library.
Our proposed system has the following advantages :-
1. User friendly interface
2. Fast access to database
3. Payment Gateway
4. More Storage Capacity
5. Search facility
6. Look and Feel Environment All the manual difficulties in managing the Library have been
rectified by implementing computerization.
Page 16
2.3 Requirement Analysis
2.3.1 Product Description
Pustakaalay Pranalee is a computerized system which helps Admin 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 Admin to manage the transaction or record more effectively and timesaving.
2.3.2 Problem Statement
The problem occurred before having computerized system includes:
1. File lost - When computerized system is not implemented file is always lost because of human
environment. Sometimes due to some human error there may be a loss of records.
2. 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.
3. Difficult to search record - When there is no computerized system there is always a difficulty
in searching of records if the records are large in number.
4. Space consuming - After the number of records become large the space for physical storage of
file and records also increases if no computerized system is implemented.
5. Cost consuming - As there is no computerized system to add each record paper will be needed
which will increase the cost for the management of library.
Page 17
2.4 System Requirements
2.4.1 Non Functional Requirements
1. EFFICIENCY REQUIREMENT - When a library management system will be implemented

librarian and user will easily access library as searching and book transaction will be very faster .
2. RELIABILITY REQUIREMENT - The system should accurately performs member

registration, member validation, report generation, book transaction and search.
3. 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.
4. IMPLEMENTATION REQUIREMNTS - In implementing whole system it uses html in front

end with php as server side scripting language which will be used for database connectivity and
the backend i.e, the database part is developed using mysql.
2.4.2 Functional Requirements
2.4.2.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
Page 18
 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 access to.
 The user must be able to logout after they finished using system.
2.4.2.2 Register New User
Description of feature-This feature can be performed by all users to register new user to create
account.
 System must be able to verify information

 System must be able to delete information if information is wrong
2.4.2.3 Register New Book
Description of feature-This feature allows to add new books to the library
 System must be able to verify information

 System must be able to enter number of copies into table.
 System must be able to not allow two books having same book id.
Page 19
2.4.2.4 Search Book
Description of Feature - This feature is found in book maintenance part. we can search book
based on book id & book name.
 System must be able to search the database based on select search type
 System must be able to filter book based on keyword entered
 System must be able to show the filtered book in table view
2.4.2.5 Issue Books and Return Books
Description of Feature - This feature allows to issue and return books and also view reports of
book issued.
 System must be able to enter issue information in database.

 System must be able to update number of books.
 System must be able to search if book is available or not before issuing books
 System should be able to enter issue and return date information
2.5 Hardware Requirements
1. Intel core i5 7th 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.
2.Ram 8GB is used as it will provide fast reading and writing capabilities and will in turn
support in processing.
Page 20
2.6 Software Requirements
1. Operating system - Windows 10 is used as the operating system as it is stable and supports
more features and is more user friendly.
2. Database MYSQL - MYSQL 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.
3. Development tools and Programming language - HTML is used to write the whole code and
develop webpages with CSS, Javascript for styling work and PHP for sever side scripting.
2.7 Justification of Platform
2.6.1 Front End-The front end is designed using of html , Php ,css, Java
script.
1.HTML-HTML or Hyper Text Markup Language is the main markup language for creating web
pages and other information that can be displayed in a web browser.HTML is written in the form
of HTML elements consisting of tags enclosed in angle brackets (like <html>), within the web
page content. HTML tags most commonly come in pairs like <h1> and </h1>, although some
tags represent empty elements and so are unpaired, for example <img>. The first tag in a pair is
the start tag, and the second tag is the end tag (they are also called opening tags and closing
tags). In between these tags web designers can add text, further tags, comments and other types
of text-based content. The purpose of a web browser is to read HTML documents and compose
them into visible or audible web pages. The browser does not display the HTML tags, but uses
the tags to interpret the content of the page.
HTML elements form the building blocks of all websites. HTML allows images and objects to
be embedded and can be used to create interactive forms. It provides a means to create structured
documents by denoting structural semantics for text such as headings, paragraphs, lists, links,
Page 21
quotes and other items. It can embed scripts written in languages such as JavaScript which affect
the behavior of HTML web pages.
2.CSS- Cascading Style Sheets (CSS) is a style sheet language used for describing the look and
formatting of a document written in a markup language. While most often used to style web
pages and interfaces written in HTML and XHTML, the language can be applied to any kind of
XML document, including plain XML, SVG and XUL. CSS is a cornerstone specification of the
web and almost all web pages use CSS style sheets to describe their presentation.
CSS is designed primarily to enable the separation of document content from document
presentation, including elements such as the layout, colors, and fonts.
This separation can improve content accessibility, provide more flexibility and control in the
specification of presentation characteristics, enable multiple pages to share formatting, and
reduce complexity and repetition in the structural content (such as by allowing for table less web
design).CSS can also allow the same markup page to be presented in different styles for different
rendering methods, such as on-screen, in print, by voice (when read out by a speech-based
browser or screen reader) and on Braille-based, tactile devices.
It can also be used to allow the web page to display differently depending on the screen size or
device on which it is being viewed. While the author of a document typically links that document
to a CSS file, readers can use a different style sheet, perhaps one on their own computer, to
override the one the author has specified.
However if the author or the reader did not link the document to a specific style sheet the default
style of the browser will be applied.CSS specifies a priority scheme to determine which style
rules apply if more than one rule matches against a particular element. In this so-called cascade,
priorities or weights are calculated and assigned to rules, so that the results are predictable.
3.JAVA SCRIPT- JavaScript (JS) is a dynamic computer programming language. It is most

commonly used as part of web browsers, whose implementations allow client-side scripts to
Page 22
interact with the user, control the browser, communicate asynchronously, and alter the document
content that is displayed.
It is also being used in server-side programming, game development and the creation of desktop
and mobile applications. JavaScript is a prototype-based scripting language with dynamic typing
and has first class functions. Its syntax was influenced by C. JavaScript copies many names and
naming conventions from Java, but the two languages are otherwise unrelated and have very
different semantics.
The key design principles within JavaScript are taken from the Self and Scheme programming
languages. It is a multi-paradigm language, supporting object-oriented, imperative, and
functional programming styles. The application of JavaScript to use outside of web pages—for
example, in PDF documents, site-specific browsers, and desktop widgets—is also significant.
Newer and faster JavaScript VMs and platforms built upon them (notably Node.js) have also
increased the popularity of JavaScript for server-side web applications.
On the client side, JavaScript was traditionally implemented as an interpreted language but just-
in-time compilation is now performed by recent browsers.
4.PHP- PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language.
PHP is now installed on more than 244 million websites and 2.1 million web servers. Originally
created by Rasmus Lerdorf in 1995, the reference implementation of PHP is now produced by
The PHP Group. While PHP originally stood for Personal Home Page, it now stands for PHP:
Hypertext Preprocessor, a recursive backronym.
PHP code is interpreted by a web server with a PHP processor module, which generates the
resulting web page: PHP commands can be embedded directly into an HTML source document
rather than calling an external file to process data.
It has also evolved to include a command-line interface capability and can be used in standalone
graphical applications. PHP is free software released under the PHP License.
Page 23
PHP can be deployed on most web servers and also as a standalone shell on almost every
operating system and platform, free of charge.
2.6.2 Back End- The back end is designed using mysql which is used to design
the databases.
1.MYSQL- MySQL ("My S-Q-L", officially, but also called "My Sequel") is (as of July 2013)
the world's second most widely used open-source relational database management system
(RDBMS). It is named after co-founder Michael Widenius daughter, My. The SQL phrase stands
for Structured Query Language.
The MySQL development project has made its source code available under the terms of the
GNU General Public License, as well as under a variety of proprietary agreements. MySQL was
owned and sponsored by a single forprofit firm, the Swedish company MySQL AB, now owned
by Oracle Corporation .\
MySQL is a popular choice of database for use in web applications, and is a central component
of the widely used LAMP open source web application software stack (and other 'AMP' stacks).
LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open
source projects that require a full-featured database management system often use MySQL.
For commercial use, several paid editions are available, and offer additional functionality.
Applications which use MySQL databases include: TYPO3, MODx, Joomla, WordPress,
phpBB, MyBB, Drupal and other software. MySQL is also used in many high-profile, large-
scale websites, including Wikipedia, Google (though not for searches), Facebook, Twitter,
Flickr, and YouTube.
Page 24
CHAPTER 3
SYSTEM DESIGN
3.1 Module Division
PUSTAKALAAY PRANALEE is divided into two module:-
1. USER SIDE
2. ADMIN SIDE
3.1.1 User Side
Only registered user can get every facility of this website.
 USER can log into their account and see their personal information and modify them.
 USER can search for a book by the name or search in a particular department
 USER can easily order a book.
 After the admin approve it they can see the issue and return date beside the book
name.
 Student will able to pay their fine online through Pustakalaay Pranalee Payment
Gateway.
 Also, there is a public comment section where registered users can comment on their
suggestions and can ask questions.
Page 25
3.1.2 Admin Side
 ADMIN can log into their account and see their personal information and modify them.
 See which student is online right now.
 See all the student information.
 The admin approve student’s request for book.
 Add new books & delete a book from the list.
 Reply in the comment box.
3.2 Data Dictionary
1.Admin data table
Fig 1 : Admin data table
Page 26
2.Books data table
Fig 2 : Books data table
3. Comments data table
Fig 3 : Comments data table
4.Fine data table
Fig 4 : Fine data table
Page 27
5.Issue_book data table
Fig 5 : Issue_book data table
6.Student data table
Fig 6 : Student data table
Page 28
3.3 ER-Diagram
An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities” such as
people, objects or concepts relate to each other within a system. ER Diagrams are most often
used to design or debug relational databases in the fields of software engineering, business
information systems, education and research. Also known as ERDs or ER Models, they use a
defined set of symbols such as rectangles, diamonds, ovals and connecting lines to depict the
interconnectedness of entities, relationships and their attributes.
Fig 7 : ER Diagram
Page 29
They are five entity Admin, Books, Issue info, Student and Feedback.Entity Admin and Books
has a relationship Maintain between them i.e; Admin can maintain books. Similarly, Students
and Book has relationship Issue between them as well as Books and Issue Info has relationship
Issue between them, i.e; Student can request for book and book is being issued to student and
issued information is being shared by book. The last relationship between Admin and Feedback
is Send i.e; Admin can send reply to the question asked or comment given by student in feedback
page.
3.4 Data Flow Diagram
Data Flow Diagram (DFD) depicts the flow of information and the transformation applied when
a data moves in and out from a system. The overall system is represented and described using
input, processing and output in the DFD.
As there are two module in PUSTAKALAAY PRANALEE user side and admin side therefore,
there will two different data flow diagram. There will be common activities done in both side of
module like Account creation, resetting password etc.
Data Flow Diagram (DFD) Level 0 :-
Fig 8 : Data Flow Diagram (DFD) level 0
DFD Level 0 is also called a Context Diagram. It's a basic overview of the whole system or
process being analyzed or modeled. It's designed to be an at-a-glance view, showing the system
as a single high-level process, with its relationship to external entities.
Page 30
Data Flow Diagram (DFD) level 1 :-
At this level, the system has to show or exposed with more details of processing. The processes
that are important to be carried out are.
Data Flow Diagram (DFD) Level 2 :-
Page 31
This level two data flow diagram (DFD) template can map out information flow, visualize an
entire system, and be shared with our stakeholders.
Page 32
CHAPTER 4
IMPLEMENTATION AND TESTING
4.1 Coding Phase
There are two modules in Pustakaalay Pranalee - ADMIN SIDE and STUDENT SIDE but both
share a common homepage and login page.
4.1.1 Code Of Home Page
<?php
include "navbar.php";
?>
<!DOCTYPE html>
<html>
<head>
<title>
PUSTAKAALAY PRANAALEE
</title>
<link rel="stylesheet" type="text/css" href="style.css">
Page 33
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<body>
<section>
<div class="sec_img">
<br><br><br>
<div class="box">
<img src="images/pp.jpg" width="90" height="90" style="margin-

left: 160px;"><br><br>
<h1 style="text-align: center; font-size: 25px;">WELCOME TO

LIBRARY</h1><br><br><br>
<h2 style="text-align: center; font-size: 25px;">ABOUT

US</h2><br><br><br>
<h3 style="text-align: left; font-size: 25px;">NAME - YUVRAJ

SINGH</h3><br><br>
<h3 style="text-align: left; font-size: 25px;">EMAIL -

yuvsingh766@gmail.com</h3><br><br>
<h3 style="text-align: left; font-size: 25px;">NAME - SHASHANK

SWAIN</h3><br><br>
<h3 style="text-align: left; font-size: 25px;">EMAIL -

shashankish53@gmail.com</h3><br>
Page 34
</div>
</div>
</section>
</body>
</html>
4.1.2 Code Of Login Page
<?php
if(isset($_POST['submit']))
if ($_POST['user']=='admin')
$count=0;
$res=mysqli_query($db,"SELECT * FROM àdmin` WHERE

username='$_POST[username]' && password='$_POST[password]';");
$row= mysqli_fetch_assoc($res);
Page 35
$count=mysqli_num_rows($res);
if($count==0)
?>
<div class="alert alert-danger" style="width: 600px; margin-left: 370px; background-color:

#de1313; color: white">
<strong>The username and password doesn't match</strong>
</div>
<?php
else
/*-------------if username & password matches---*/
$_SESSION['login_user'] = $_POST['username'];
$_SESSION['pic']= $row['pic'];
?>
Page 36
<script type="text/javascript">
window.location="Admin/profile.php"
</script>
<?php
else
$count=0;
$res=mysqli_query($db,"SELECT * FROM `student` WHERE

username='$_POST[username]' && password='$_POST[password]';");
$row= mysqli_fetch_assoc($res);
$count=mysqli_num_rows($res);
if($count==0)
?>
<div class="alert alert-danger" style="width: 600px; margin-left: 370px; background-color:

#de1313; color: white">
<strong>The username and password doesn't match</strong>
Page 37
</div>
<?php
else
$_SESSION['login_user'] = $_POST['username'];
$_SESSION['pic']= $row['pic'];
?>
window.location="Student/profile.php"
</script>
<?php
?>
Page 38
4.1.3 Code Of Book Page
<?php
$q=mysqli_query($db,"SELECT * from books where name like '%

$_POST[search]%' ");
if(mysqli_num_rows($q)==0)
echo "Sorry! No book found. Try searching again.";
else
echo "<table class='table table-bordered table-hover' >";
echo "<tr style='background-color: #6db6b9e6;'>";
//Table header
echo "<th>"; echo "ID"; echo "</th>";
echo "<th>"; echo "Book-Name"; echo "</th>";
echo "<th>"; echo "Authors Name"; echo "</th>";
Page 39
echo "<th>"; echo "Edition"; echo "</th>";
echo "<th>"; echo "Status"; echo "</th>";
echo "<th>"; echo "Quantity"; echo "</th>";
echo "<th>"; echo "Department"; echo "</th>";
echo "</tr>";
while($row=mysqli_fetch_assoc($q))
echo "<tr>";
echo "<td>"; echo $row['bid']; echo "</td>";
echo "<td>"; echo $row['name']; echo "</td>";
echo "<td>"; echo $row['authors']; echo "</td>";
echo "<td>"; echo $row['edition']; echo "</td>";
echo "<td>"; echo $row['status']; echo "</td>";
echo "<td>"; echo $row['quantity']; echo "</td>";
echo "<td>"; echo $row['department']; echo "</td>";
echo "</tr>";
echo "</table>";
Page 40
}
/*if button is not pressed.*/
else
$res=mysqli_query($db,"SELECT * FROM `books` ORDER BY

`books`.`name` ASC;");
//Table header
echo "<th>"; echo "ID"; echo "</th>";
echo "<th>"; echo "Book-Name"; echo "</th>";
echo "<th>"; echo "Status"; echo "</th>";
echo "<th>"; echo "Quantity"; echo "</th>";
echo "<th>"; echo "Department"; echo "</th>";
echo "</tr>";
while($row=mysqli_fetch_assoc($res))
Page 41
echo "<tr>";
echo "<td>"; echo $row['status']; echo "</td>";
echo "<td>"; echo $row['quantity']; echo "</td>";
echo "<td>"; echo $row['department']; echo "</td>";
echo "</tr>";
echo "</table>";
if(isset($_POST['submit1']))
if(isset($_SESSION['login_user']))
mysqli_query($db,"INSERT INTO issue_book

Values('$_SESSION[login_user]', '$_POST[bid]', '', '', '');");
?>
Page 42
window.location="request.php"
</script>
<?php
else
?>
alert("You must login to Request a book");
</script>
<?php
4.1.4 Code Of Feedback Page
<?php
$sql="INSERT INTO `comments` VALUES('',

'$_SESSION[login_user]', '$_POST[comment]');";
Page 43
if(mysqli_query($db,$sql))
$q="SELECT * FROM `comments` ORDER BY

`comments`.ìd` DESC";
$res=mysqli_query($db,$q);
echo "<table class='table table-bordered'>";
while ($row=mysqli_fetch_assoc($res))
echo "<tr>";
echo "<td>"; echo $row['username']; echo

"</td>";
echo "<td>"; echo $row['comment']; echo

"</td>";
echo "</tr>";
echo "</table>";
Page 44
else
$q="SELECT * FROM `comments` ORDER BY `comments`.ìd`

DESC";
$res=mysqli_query($db,$q);
echo "<table class='table table-bordered'>";
while ($row=mysqli_fetch_assoc($res))
echo "<tr>";
echo "<td>"; echo $row['username']; echo

"</td>";
echo "<td>"; echo $row['comment']; echo

"</td>";
echo "</tr>";
echo "</table>";
?>
Page 45
4.1.5 Admin Side Coding
4.1.5.1 Code For Issuing Book
<?php
$c=0;
$sql="SELECT
student.username,roll,books.bid,name,authors,edition,issue,issue_book.return FROM student
inner join issue_book ON student.username=issue_book.username inner join books ON
issue_book.bid=books.bid WHERE issue_book.approve ='Yes' ORDER BY
ìssue_book`.`return` ASC";
$res=mysqli_query($db,$sql);
echo "<table class='table table-bordered' style='width:100%;' >";
//Table header
echo "<th>"; echo "Username"; echo "</th>";
Page 46
echo "<th>"; echo "Roll No"; echo "</th>";
echo "<th>"; echo "BID"; echo "</th>";
echo "<th>"; echo "Book Name"; echo "</th>";
echo "<th>"; echo "Issue Date"; echo "</th>";
echo "<th>"; echo "Return Date"; echo "</th>";
echo "</tr>";
echo "</table>";
echo "<div class='scroll'>";
echo "<table class='table table-bordered' >";
$d=date("Y-m-d");
if($d > $row['return'])
$c=$c+1;
$var='<p style="color:yellow; background-color:red;">EXPIRED</p>';
Page 47
mysqli_query($db,"UPDATE issue_book SET approve='$var' where
`return`='$row[return]' and approve='Yes' limit $c;");
echo $d."</br>";
echo "<tr>";
echo "<td>"; echo $row['username']; echo "</td>";
echo "<td>"; echo $row['roll']; echo "</td>";
echo "<td>"; echo $row['issue']; echo "</td>";
echo "<td>"; echo $row['return']; echo "</td>";
echo "</tr>";
echo "</table>";
echo "</div>";
Page 48
else
?>
<h3 style="text-align: center;">Login to see information of Borrowed Books</h3>
<?php
?>
4.1.6 Student Side Coding
4.1.6.1 Code Of Requesting Book
<?php
$q=mysqli_query($db,"SELECT * from issue_book where

username='$_SESSION[login_user]' and approve='' ;");
if(mysqli_num_rows($q)==0)
echo "There's no pending request";
Page 49
}
else
//Table header
echo "<th>"; echo "Book-ID"; echo "</th>";
echo "<th>"; echo "Approve Status"; echo "</th>";
echo "<th>"; echo "Issue Date"; echo "</th>";
echo "<th>"; echo "Return Date"; echo "</th>";
echo "</tr>";
while($row=mysqli_fetch_assoc($q))
echo "<tr>";
echo "<td>"; echo $row['approve']; echo "</td>";
echo "<td>"; echo $row['issue']; echo "</td>";
echo "<td>"; echo $row['return']; echo "</td>";
Page 50
echo "</tr>";
echo "</table>";
else
echo "</br></br></br>";
echo "<h2><b>";
echo " Please login first to see the request information.";
echo "</b></h2>";
?>
4.1.6.2 Code ofPayment System
<?php
$_p="paid";
if (isset($_POST['submit']))
$uname=$_POST['username'];
$b=$_POST['bookid'];
Page 51
$amt=$_POST['amount'];
$sql="SELECT * from `fine`";
$res=mysqli_query($db,$sql);
if($row['username']==$uname)
if ($row['bid']==$b)
if ($row['fine']==$amt)
mysqli_query($db,"UPDATE `fine` SET `status`='PAID' WHERE `bid`=" . $b . ";");
else
?>
alert("PAYMENT FAILED");
</script>
<?php
Page 52
else
?>
</script>
<?php
else
?>
</script>
<?php
?>
Page 53
4.2 Test Approach
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 :-
1.Unit Testing
2.Integration Testing
4.3 Unit Testing
Unit testing is undertaken when a module has been created and successfully reviewed .In order to
test a single module we need to provide a complete environment i.e, 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 .
Page 54
1. Test For the admin module .
 Testing admin login form-This form is used for log in of administrator of the system.In
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  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
thelibraryid, 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 libraryid, 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.
Page 55
4.4 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 module.
Page 56
CHAPTER 5
RESULTS AND DISCUSSIONS
Fig 11 : Home page
This is the common home page for both admin and user.Through this page user or admin can
choose if he/she wants to see list of book without login or choose to login or signup.
Page 57
Fig 12 : List of Books Page
List of all books are available in this page.
Fig 13 : Feedback page
ADMIN or USER can give feedback on through this page. which will help developer to add
update or modify the application if required.
Page 58
Fig 14 : Sign up page selection
There is an option for first time user to select whether he/she wants to signup as user or admin.
Fig 15 : Sign up page
In this page user can fill in theirs details required to sign in to PUSTAKAALAY PRANALEE
Page 59
Fig 16 : Login page
In this page user can login to their account and can use all the feature of PUSTAKAALAY
PRANALEE.
Fig 17 : Change Password page
If any ADMIN or USER forgot their password can easily reset it through this page.
Page 60
Fig 18 : Admin - Profile page
After ADMIN login in to their account he/she will see this page where he/she can see his/her
information and can edit it if required.
Fig 19 : Admin - Side Navigation page
In this page admin can list of all book as well as can delete any book if he/she want or can
choose to use other feature of PUSTAKAALAY PRANALEE listed in this page.
Page 61
Fig 20 : Admin – Add book page
Admin can add new books through this page.
Fig 21 : Admin - Book Request page
In this page ADMIN can see all the book request send by user to them and can approve or denied
it .
Page 62
Fig 22 : Admin - Issued book page
In this page ADMIN can see information of all borrowed books.
Fig 23 : Admin - Student Information page
In this page ADMIN can see the information of all the student logged into PUSTAKAALAY
PRANALEE.
Page 63
Fig 24 : Admin - Book Expired page
In this page admin can see which student's book approval had been expired or the student had
returned it and importantly ADMIN can modify the list if the student had returned the book or
not accordingly.
Fig 25 : Admin - Fine page
In this page ADMIN can see fine of all students who have returned book late or have not yet
returned it even if date of return is expired.
Page 64
Fig 26 : Student - Profile page
After STUDENT login in to their account he/she will see this page where he/she can see his/her
information and can edit it if required.
Fig 27 : Student - Side Navigation page
In this page STUDENT can list of all book as well as can request any book if he/she want or can
choose to use other feature of PUSTAKAALAY PRANALEE listed in this page.
Page 65
Fig 28 : Student - Book Request Info page
In this page STUDENT/USER can see all the book request send to ADMIN and status of
approval .
Fig 29 : Student - Issued book page
In this page STUDENT can see information of all borrowed books.
Page 66
Fig 30 : Student - Book Expired page
In this page student can see their total fine or expired date of returning books he/she had
borrowed or returned book.
Fig 31 : Student - Fine page
In this page STUDENT can see their list of fine according to the book borrowed and returned
late.
Page 67
Fig 32 : Fine Payment Page
In this page student can pay their Fine through Online Mode by entering their Credit Card / Debit
Card details, Username, Book Id & Amount.
Page 68
CHAPTER 6
CONCLUSION AND FUTURE WORK
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.
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 notes of lecture and online assignments submission
facility ,Online book reading feature which will student to get connected to their studies from
where ever they want, A feature Of group chat where students can discuss on various topic
related to the books their reading together online. This all feature 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.
Page 69
CHAPTER 7
REFERENCES
 http://www.w3schools.com/html/html_intro.asp
 http://www.w3schools.com/css/css_background.asp
 http://www.w3schools.com/js/js_datatypes.asp
 http://www.w3schools.com/sql/sql_insert.asp
 http://www.w3schools.com/sql/sql_update.asp
 http://www.w3schools.com/php/php_forms.asp
 https://www.w3schools.com/bootstrap4/default.asp
 https://www.udemy.com/course/the-complete-web-development-bootcamp/
Page 70

Project Report On Library Management System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Report On Library Management System

Uploaded by

Copyright:

Available Formats

PUSTAKAALAY PRANALEE

Shashank Shekhar Swain & Yuvraj Singh

Under the esteemed guidance of

Mr./Mrs. Name of The Guide

DEPARTMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY

ARKA JAIN UNIVERSITY, JHARKHAND

DEPARTMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY

Internal Guide Coordinator

Date: University Seal

Owing to the advancement of technology, organization of an Online Library becomes much

Pustakaalay Pranaalee is a typical management Information system (MIS), its Development

Shashank Shekhar Swain Yuvraj Singh

Chapter 2 : System Analysis………………………………………………..…. 05

Chapter 3 : System Design……………………..…………………………........ 15

1. Coding Phase (Place Core segments)………………………………………………23

Chapter 5 : Results and Discussions (Output Screens)……………………… 47

Chapter 6 : Conclusion and Future Work…………………………………… 59

1. Chapter 3 : System Design……………………………………………… 15

2. Chapter 5 : Results and Discussions…………………………………... 47

1.1 Background Of Project

1.2 Project Aims and Objectives

1. Online book issue.

2. Generate reports on user information & books information.

3. Admin can add, update or delete books.

4. Request column for Admin for providing new books.

5. A search column to search availability of books.

8. Student can request to Admin to reschedule book's date of return.

10. Fine will be calculated on late submission of book.

1. Identify the origin of the information at different level.

3. Analyze the drawback of existing system (manual system)

1.4 Features Of Pustakaalay Pranalee

2. Provision to request for new titles, Authors &Editions.

4. Charge users for lost/damaged books.

5. Automatic fine fees calculation.

1.5 Benefits Of Pustakaalay Pranalee

4. Online Fine Payment.

5. Inventory and stock management.

2.1 Existing System

Our proposed system has the following advantages :-

1. User friendly interface

2. Fast access to database

4. More Storage Capacity

2.3.1 Product Description

2.3.2 Problem Statement

The problem occurred before having computerized system includes:

2.4.1 Non Functional Requirements

1. EFFICIENCY REQUIREMENT - When a library management system will be implemented

2. RELIABILITY REQUIREMENT - The system should accurately performs member

3. USABILITY REQUIREMENT - The system is designed for a user friendly environment so

4. IMPLEMENTATION REQUIREMNTS - In implementing whole system it uses html in front

2.4.2 Functional Requirements

2.4.2.1 User Login

 user id is provided when they register

2.4.2.2 Register New User

 System must be able to verify information

2.4.2.3 Register New Book

Description of feature-This feature allows to add new books to the library

 System must be able to verify information

2.4.2.5 Issue Books and Return Books

 System must be able to enter issue information in database.

2.5 Hardware Requirements

2.7 Justification of Platform

/-------------if username & password matches---/

/if button is not pressed./