1.

1Overview:
2 Library Management System is an application which refers to library systems which are
3 generally small or medium in size. It is used by librarian to manage the library using a
4 computerized system where he/she can record various transactions like issue of books,
return of
5 books, addition of new books, addition of new students etc.
6 Books and student maintenance modules are also included in this system which would
keep
7 track of the students using the library and also a detailed description about the books a
library
8 contains. With this computerized system there will be no loss of book record or member
record
9 which generally happens when a non computerized system is used.
10 All these modules are able to help librarian to manage the library with more convenience
and in
11 a more efficient way as compared to library systems which are not computerized.
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.
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. Problem Statement:

Library Management System

 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
Library Management System
 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

1.3. 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 issue
 Request column for librarian for providing new books
 Student login page where student can find books issued by him/her and date of return.
 A search column to search availability of book
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 issue

 Request column for librarian for providing new books
 Student login page where student can find books issued by him/her and date of return.
 A search column to search availability of book

2.4. Feasibility Study:

A feasibility analysis is undertaken to determine the possibility or probability of either

improving the existing system or developing a completely new system. It helps to obtain an
overview of the problem and to get rough assessment of whether feasible solution exists.
There are three aspects in feasibility study portion of the preliminary investigation.

1) Operational feasibility
2) Technical feasibility
3) Economical feasibility
1. Operational feasibility:- It is a measure of how well a proposed system solves the
problems, and takes advantages of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements analysis phase of
system development. Operational feasibility covers two aspects. One is the technical
performance aspect and other is the acceptance within the organization. Operational
feasibility determines how the proposed system will fit the current operations and
what, if any job restructuring and retraining may be needed to implement the system.
In the system operational feasibility checks, whether the user who is going to use the
system is able to work with the software with which the system id coded and also the
mind of the user going to use system. If the user does not understand or is able to
work on the system further development is waste.

2. Technical feasibility:- This involves questions such as whether the technology

needed for the system exists, how difficult it will be to build, and whether the firm has
 enough experience using that technology. The assessment is based on an outline
design of system requirements in terms of Input, Processes, Output, Fields, Programs,
and Procedures. This can be quantified in terms of volumes of data, trends, frequency
of updating, etc. in order to estimate whether the new system will perform adequately
or not. The technical feasibility in the proposed system deals with the technology used
in the system. It deals with the hardware and software used in the system whether they
are of latest technology or not. It happens that after a system is prepared a new
technology arises and the user wants the system based on that technology. Thus it is
important to check the system to be technically feasible. The minimum memory
requirement is 32MB of RAM while 64MB is better to have for better performance.
As far as software is concerned, MySQL and PHP should be installed on the server.

3. Economic feasibility:- Economic analysis is the most frequently used method for
evaluating the effectiveness of a new system. More commonly known as cost/benefit
analysis, the procedure is to determine the benefits and savings that are expected from
a candidate system and compare them with costs. If benefits outweigh costs, then the
decision is made to design and implement the system. Implementation of this system
will be a lifetime investment, which will ensure returns to the store of good services
and market value throughout the future. So the system is found economically feasible.

3.3 Work Plan:

To create a work plan for an super library management system,

1. Define the scope and requirements of the online library management system:
 What functions should the system have (e.g., cataloging, borrowing, returning,
renewing, searching, reporting, etc.)?
 Who are the users of the system (e.g., librarians, staff, patrons, etc.)?
 What are the technical requirements (e.g., hardware, software, database, hosting,
security, etc.)?
2. Create a project plan:
 Define the timeline, budget, resources, and deliverables for the project.
 Break down the project into smaller tasks and assign them to team members.
 Establish a communication plan and a project management tool to track progress and
resolve issues.
3. Design the user interface and database schema:
 Create wireframes and mock ups of the user interface.
 Design the database schema to store the data related to books, users, loans, etc.
 Decide on the programming language, framework, and libraries to use for the
implementation.
4. Implement the system:
 Develop the front-end and back-end of the system based on the design.
 Test the system for bugs and errors.
 Incorporate feedback from users and stakeholders.
5. Deploy and maintain the system:
 Deploy the system on a server or cloud platform.
 Set up monitoring and logging to detect and fix issues.
 Provide support and training to users.
 Plan for future enhancements and upgrades.
6. Evaluate the system:
 Conduct a post-implementation review to evaluate the system's effectiveness and
efficiency.
 Collect feedback from users and stakeholders to identify areas for improvement.
 Use the results to inform future development and maintenance.
 Overall, developing an online library management system requires a systematic
approach, collaboration among team members, and continuous communication with
users and stakeholders.

4.1 Software Requirements:

 Operating System : Windows User

 Front End- HTML ,CSS, Java script
 Back End- PHP, MYSQL, Tomcat

4.2 Hardware Requirement:

 Processor: Core i3 and above

 RAM: 512MB
 Hard Disk: 256GB
  Monitor-15” Color Monitor

5.2. Data Structures and Tables:

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.
5.3 DFD:
5.4 System Flowchart:
5.5 ER- Diagram

7.1 Testing:

7.1 Testing

Testing System testing is a series of different test whose primary purpose is to fully
exercise computer based system. We can say that it will run according to its
specifications and in the way users expect. Special test data are input for processing,
and the results examined. A limited number of users may be allowed to use the system
so that analyst can see whether they try to use it in unforeseen ways. It is desirable to
discover any surprises before the organization implements the system and depends on
it. We follow different testing.

• Black box testing attempts to find errors in following

• Incorrect or missing function
• Interface errors
• Errors in data structure
• Initialization and termination errors
7.1.1 White Box Testing

Using the white-box testing techniques, a software engineer can design test case that

• Exercise independent paths within a module or unit

• Exercise logical decisions on both their true and false side

• Execute loops at their boundaries and within their operational bounds

• Exercise internal data structures to ensure their validity

7.1.2 Unit Testing

Code is written by people, and we make mistakes. Bugs to prevent us from shipping
bugs to our users, we test our software to verify that it works as it should. Java
developers have learned that not all testing is created equal. In addition to traditional
functional testing, many shops are adopting developer testing techniques such as unit
testing. These leading craftsmen create specific, automated tests to verify the accuracy
and function of code while it's being written - or even before it's written - because they
want to catch bugs early. Better still, new tools and processes make unit testing even
more attractive to Java developers. Unit Testing in Java is written to show how to write
good tests that are concise and to the point, expressive, useful, and maintainable.

The Art of Unit Testing, this focuses on tools and practices specific to the Java world.
It introduces you to emerging techniques like behaviour-driven development and
specification by example, and shows you how to add robust practices into your toolkit.

7.1.3 Integration Testing

Once unit tested components are delivered we then integrate them together. These

“integrated” components are tested to weed out errors and bugs caused due to the
integration. This is a very important step in the Software Development Life Cycle. It is
possible that different programmers developed different components. A lot of bugs
emerge during the integration step. In most cases a dedicated testing team focuses on
Integration Testing Prerequisites for Integration Testing: Before we begin Integration
Testing it is important that all the components have been successfully unit
 tested. .Integration Testing Steps: Integration Testing typically involves the following
Steps:

Step 1: Create a Test Plan

Step 2: Create Test Cases and Test Data

Step 3: If applicable create scripts to run test cases

Step 4: Once the components have been integrated execute the test cases

Step 5: Fix the bugs if any and re test the code

Step 6: Repeat the test cycle until the components have been successfully integrated

9.1 Finding & Conclusion :

Finding:

An online library management system is a valuable tool for libraries to manage their
collections, patrons, and operations efficiently. The system allows librarians to catalog books,
track loans, handle requests, generate reports, and provide online access to resources. Patrons
can search and reserve books, view their loan history, and renew items online. The system
provides a centralized and automated way to manage the library, reducing manual tasks,
improving accuracy, and enhancing user experience.

Conclusion:

In conclusion, an online library management system is a critical component of modern library

operations. The system provides a comprehensive set of features to manage books, patrons,
loans, and requests effectively. The system streamlines library workflows, enhances user
experience, and provides a platform for digital resources. By implementing an online library
management system, libraries can improve their services, reduce costs, and increase their
reach to a wider audience.

This project is going to provide a solution for the librarian and students to access the library
in an easy and smooth manner. It will help the libraries which have a computerized system as
well as libraries which don’t have a computerized system. Along with making the record
keeping process simple, it also simplifies the issue and return process. It also provides a
solution for fine collection by enabling the students to pay fine online. It also gives a system
for the librarian and student to communicate with each other.