P.E.

Society’s
MODERN COLLEGE OF ARTS,COMMERCE &
SCIENCE, SHIVAJINAGAR,PUNE-05

Project report on

library management system

Submitted by :
BHAGWAT VISHNUPANT KOKATE

AKASH SURESH LOKARE

ABHAY SHANKAR PAWAR

Under the Guidance of :

PROF PUSHPLATA GORADE
 Progressive Education Society’s
Modern College of Arts, Science And Commerce
Shivajinagar, Pune-411005
Certificate

This is to certify that Mr./Ms.______________________, Roll No. _____of

Class ______ has completed her Project Work Titled _________ as a part of
the curriculum during the Academic Year 2022-2023.

Project Guide Head,

Dept of Computer Science

Name Sign

Examiners:

1.________________________________

2.________________________________

3.________________________________
 ACKNOWLEDGEMENT

I would like to express my sincere thanks to everyone who has directly or

indirectly helped me in completing my project successfully.

I am very grateful to Prof. ________ for not only giving me her valuable
support and encouragement but also guiding me with her vast knowledge and
experience.

They have been taking keen interest in each and every aspect of my project.
Without them it would be like walking in dark.

Lastly I would like to thank all my friends, college and company colleagues
who stood by me in completing this project.
 INDEX

❖ 1.Introduction
1.1 PROJECT AIMS AND OBJECTIVES

1.2 BACKGROUND OF PROJECT

1.3 OPERATION ENVIRONMENT

❖ 2.SYSTEM ANALYSIS
2.1 SOFTWARE REQUIREMENT SPECIFICATION 9

2.2 SOFTWARE TOOL USED

❖ 3.SYSTEM DESIGN
3.1 TABLE DESIGN 20

3.2 DATA FLOW DIAGRAM’S

• Diagram Object
a. DFD diagrams
b. E-R Diagrams
c. Use case Diagram
d. Activity Diagram
e. Sequence Diagram

❖ 4. SYSTEM IMPLEMENTATION
4.1 MODULE DESCRIPTION

4.2 SCREEN SHOTS

❖ 5. SYSTEM TESTING
5.1 UNIT TESTING 85

5.2 INTEGRATION TESTING

❖ Conclusion & FUTURE SCOPE

❖ Bibliography
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:

• Adding new books in the library, issuing books to students and

maintaining the record of the book that is returned.

• User login page where user (student/ teacher) can find books issued by
him/her and date of return.

• Book report page where you can see book name, quantity, available
quantity and price of book

• Request column for user for take new books

• To avoid duplication of work.

• To use the services of the existing staff effectively

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 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 Library Management System. If

user’s position is admin, the user is able to generate different kinds of reports
like lists of students registered, list of books, issue and return reports.

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.3 OPERATION ENVIRONMENT

• PROCESSOR :

INTEL CORE PROCESSOR OR BETTER PERFORMANCE

• OPERATING SYSTEM :

WINDOWS VISTA ,WINDOWS7, UBUNTU

• MEMORY :

1GB RAM OR MORE HARD DISK SPACE MINIMUM 3 GB FOR

• DATABASE USAGE FOR FUTURE :

DATABASE MY SQL
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 timesaving.
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 accdent
like spilling of water by some member on file accidentally.Besides some natural
disaster like floods or fires may also damage the files.

• 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 .

• 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.

• Cost consuming

As there is no computerized system the to add each record paper will be needed

which will increase the cost for the management of library.

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.

2.1.3 SYSTEM REQUIREMENTS

2.1.3.1 NON FUNCTIONAL REQUIREMENTS

• Product Requirements

EFFICIENCY REQUIREMENT

When a library management system will be implemented librarian and user will

easily acess 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.

• Organizational requirement

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
ie the database part is developed using mysql.

DELIVERY REQUIREMENTS

The whole system is expected to be delivered in six months of time with a

weekly evaluation by the project guide.
2.1.3.2 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
acess to.

-The user must be able to logout after they finished using 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

 1.3 REGISTER NEW BOOK

Description of feature

This feature allows to add new books to the library

Functional requirements

-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.

1.4 ISSUE BOOKS AND RETURN BOOKS

Description of feature

This feature allows to issue and return books and also view reports of book
issued.

Functional requirements

-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.1.4 SOFTWARE AND HARDWARE REQUIREMENTS

This section describes the software and hardware requirements of the system

2.1.4.1 SOFTWARE REQUIREMENTS

• Operating system- Windows 7 is used as the operating system as it is stable

and supports more features and is more user friendly

• 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.

• Development tools and Programming language- HTML is used to write the

whole code and develop webpages with css, java script for styling work and
php for sever side scripting.

2.1.4.2 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
2.2 SOFTWARE TOOLS USED

The whole Project is divided in two parts the front end and the back end.

2.2.1 Front end

The front end is designed using of html , Php ,css, Java script

• HTML-Hyper Text Markup Language

HTML 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, quotes and other
items. It can embed scripts written in languages such as JavaScript which affect
the behavior of HTML web pages.
• CSS- Cascading Style Sheets (CSS)

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 Library Management
System 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.
• JAVA SCRIPT- JavaScript (JS)

Js is a dynamic computer programming language. It is most commonly used

as part of web browsers, whose implementations allow client-side scripts to
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 firstclass 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 multiparadigm 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
byrecent (post-2012) browsers.

• 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. 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.2.2 BACK END- The back end is designed using mysql which is used to
design the Databases

• 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
CHAPTER 3

SYSTEM DESIGN

3.1 TABLE DESIGN

ADMIN TABLE

BOOK TABLE
ISSUEBOOK TABLE

REQUESTBOOK TABLE
USERDATA TABLE
3.2 DFD diagrams

A data flow diagram (DFD) maps out the flow of information for any process or
system. It uses defined symbols like rectangles, circles and arrows, plus short
text labels, to show data inputs, outputs, storage points and the routes between
each destination. Data flowcharts can range from simple, even hand-drawn
process overviews, to in-depth, multi-level DFDs that dig progressively deeper
into how the data is handled. They can be used to analyze an existing system or
model a new one. Like all the best diagrams and charts, a DFD can often
visually “say” things that would be hard to explain in words, and they work for
both technical and nontechnical audiences, from developer to CEO. That’s why
DFDs remain so popular after all these years. While they work well for data
flow software and systems, they are less applicable nowadays to visualizing
interactive, real-time or database-oriented software or systems.

• Zero level DFD

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.
• First Level DFD

Level 1 DFDs are still a general overview, but they go into more detail than a
context diagram. In level 1 DFD, the single process node from the context
diagram is broken down into sub-processes. As these processes are added, the
diagram will need additional data flows and data stores to link them together.
• Second Level DFD

second level DFD goes one process deeper into parts of 1-level DFD. It can be
used to project or record the specific/necessary detail about the system's
functioning.

ADMIN

USER
• 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.
• Usecase diagram

• Login activity diagram

• Activity Diagram
• User Sequence Diagram
• Admin sequence diagram
Admin Module

• Add book

• Book report
• Book request

• Add student
• Student report

• Issue book
• Issue report
User Module

• My account

• Request book
• Book report & Return book

__________________________________________________________________________________
CHAPTER 4

SYSTEM IMPLEMENTATION

4.1.1 Screenshot for homepage

4.1 MODULE DESCRIPTION

For Library Management System it is divided into the following Modules:

• 4.1.1 Admin Module

The following module contains various facilities like student validation, teacher
registration, book addition, and report generation.
4.1.1 Screenshot for Admin

• Add book page

• Book report page

• Book request page

• Add student
• Student report

• Issue book
• Issue report
• 4.1.2 User Module

The following module contains various facilities like my account section ,

request book and book report page

Screenshot for user login

• My account
• Request book

• Book report
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

1.Unit testing

2.integration testing

• UNIT 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

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
• user account addition

In this section the admin can verify student details from student academinc 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 user 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 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.
• INTEGRATION TESTING

Integration testing (sometimes called integration and testing, abbreviated I&T)

is the phase in software testing in which individual software modules are
combined and tested as a group. Integration testing is conducted to evaluate the
compliance of a system or component with specified functional requirements.

It occurs after unit testing and before system testing. Integration testing takes as
its input modules that have been unit tested, groups them in larger aggregates,
applies tests defined in an integration test plan to those aggregates, and delivers
as its output the integrated system ready for system testing.

Why Perform Integration Testing?

• Incompatibility between software modules can cause errors

• Developers must confirm that every software module can interact with the
database
• Requirements change, thanks to client input. However, maybe those new
requirements haven't been thoroughly tested yet and should be
• Every software developer has their understanding and programming logic.
Integration testing ensures that these various units function smoothly
• There may be potential problems with hardware compatibility
• Modules often interact with third-party APIs or tools, so we need integration
testing to verify that the data these tools accept is correct

Advantages of Integration Testing

• Integration testing ensures that every integrated module functions correctly

• Integration testing uncovers interface errors
• Testers can initiate integration testing once a module is completed and
doesn’t require waiting for another module to be done and ready for testing
• Testers can detect bugs, defects, and security issues
• Integration testing provides testers with a comprehensive analysis of the
whole system, dramatically reducing the likelihood of severe connectivity
issues
Challenges of Integration Testing

Unfortunately, integration testing has some difficulties to overcome as well.

• If testing involves dealing with two different systems created by two

different vendors, there will be questions about how these components will
affect and interact with each other
• Integrating new and legacy systems demands many testing efforts and
potential changes
• Integration testing becomes complex due to the variety of components
involved (e.g., platforms, environments, databases)
• Integration testing requires testing not only the integration links but the
environment itself, adding another layer of complexity to the process
CHAPTER 6

CONCLUSION & 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

• 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
Bibliography

During the Development of our system, we have taken the References Books
which I would like to mention in this Section.

Books:

▪ PHP and mysql Web Devlopment

▪ html w3schools
▪ css w3schools
▪ Javascript w3schools
▪ Programming in PHP

Links:

• www.code4u.com
• www.codeproject.com
• www.yahoosearch.com
• www.wikipedia.com