DOCUMENTATION

LIBRARY
MANAGEMENT
SYSTEM
Group:
Nithin Kumar – AAA0433
Akhil Reddy – AAA0455
Pranay Ganesh – AAA0550
Roopesh Kumar – AAA0452

ACKNOWLEDGEMENT:
The satisfaction that accompanies that the successful completion of any
task would be incomplete without the mention of people whose
ceaseless cooperation made it possible, whose constant guidance and
encouragement crown all efforts with success. We are grateful to our
project guide Mrs. Snigdha Biswas for the guidance, inspiration and
constructive suggestions that helpful us in the preparation of this
project.
We also thank our colleagues who have helped in successful
completion of the project.
K.NithinKumar
G. Sai Akhil Reddy
K Pranay Ganesh
K Roopesh

1.INTRODUCTION:
The project titled Library Management System is Library management software for monitoring
and controlling the transactions in a library .The project “Library Management System” is
developed in html, php, css, java script which mainly focuses on basic operations in a library like
adding new member, new books, and updating new information, searching books and
members and facility to borrow and return books. A back up database can be maintained in
case of emergency or data loss. Hence a library management software systemis useful
software for University library management.
“Library Management System” is a windows application written for 32-bit Windows operating
systems, designed to help users maintain and organize library. Our software is easy to use for
both beginners and advanced users. It features a familiar and well thought-out, an attractive
user interface, combined with strong searching Insertion and reporting capabilities. The report
generation facility of library systemhelps to get a good idea of which are the books borrowed
by the members, makes users possible to generate reports’ hard copy.
The software Library Management System has four main modules.
1. Insertion to Database Module – User friendly input screen
2. Extracting from Database module – Attractive Output Screen
3. Report Generation module – borrowed book list & Available book list
Search Facility system – search for books and members.
2. FEASIBILITY ANALYSIS:
Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the organization by
the development of a system. The impact can be either positive or negative. When the positives
nominate the negatives, then the system is considered feasible. Here the feasibility study can
be performed in two ways such as technical feasibility and Economical Feasibility.
 TechnicalFeasibility:

We can strongly say that it is technically feasible, since there will not be
much difficulty in getting required resources for the development and maintaining the system
as well. All the resources needed for the development of the software as well as the
maintenance of the same is available in the organization here we are utilizing the resources
which are available already.
 EconomicalFeasibility:
Development of this application is highly economically feasible .The
organization needed not spend much m one for the development of the systemalready
available. The only thing is to be done is making an environment for the development with an
effective supervision. I f we are doing so , we can attain the maximum usability of the
corresponding resources .Even after the development , the organization will not be in a
condition to invest more in the organization .Therefore , the systemis economically feasible.
3. Modules:
The software Library Management System has four main modules.
1. Insertion to Database Module – User friendly input screen
2. Extracting from Database module – Attractive Output Screen
3. Report Generation module – borrowed book list & Available book list
4. Search Facility system – search for books and members
4. SYSTEM REQUIREMENTS SPECIFICATION:
INTRODUCTION:
The library management software systemprovides wide range of advantages over manual
library management system. Data addition and maintenance is easier. Tracing the books with
I.D number and book shelf is not time consuming. A back up database can be maintained in

case of emergency or data loss. Hence a library management software systemis useful
software for University library management.
I. PURPOSE:
The purpose of this Software Requirements Specification (SRS) document is to analyze and
elaborate on the high-level needs and features of the Library Management System. It describes
about the operations, performance, and quality assurance requirements of the Library
Management System. It also describes the non-functional requirements including the user
requirements, performance and security issues.
II. SCOPE:
The Online System is developed for the Admin, Librarian and the library Users to access and
search for books in the library catalogue, and to perform appropriate tasks. The features of the
software include the following:
 The systemprovides login facilities for Library/ administrator
 The product enables the registered users to search and check the available status of the
books in the database.
 The librarian and the administrator are allowed to access and update the details of the
Students and the books.
 The librarian can issue books to the users by changing the status of the book specifying
its due date and return date.
 The administrator has privilege like reserving currently unavailable library books and
requesting for new books to be brought into to the library.
III. OVERVIEW:
Section1:

ThisDocumentwill provide the outlineof the requirements,overview of the characteristicsand
constraintsof the system.
Section2:
Section2:
Thissectiondescribesthe functional requirementswhichinclude the input,outputbehaviorof the
system.Itmentionsthe functionalitieswhichthe systemisexpectedtoaccomplishinthe formof use
cases.
Section3:
Thissectiondescribesthe non-functional whichincludesthe operationof asystemratherthanspecific
behaviors.
V. FUNCTIONAL REQUIREMENTS
USE CASE:
 Name of the Use Case:
Login to the Library Management System
Actors:
Librarian
Precondition:
 The Library Management System webpage should exist
 The administrator should have their email id and password to login the website
Post condition:
If the email id and password entered by the user is correct then the administrator can
perform the specific tasks.
Process:

1. The administrator should first enter into the website then the administrator should
enter the email id and password to login the webpage
2. Now the administrator can perform his specific tasks
Alternate Flow:
 If webpage is not found then display the error message
 If the Email id and password entered by the administrator is wrong then admin can’t
log in.
Searching a Library Book
Actors:
Users, administrator
Precondition:
The user should be connected to the library’s website.
Process Flow:
1.User selects the ‘Search by’ option in which user selects one of the following
categories:
• Name
• Author
• Subject
• Book Id
2. User enters the required choice in the ‘Search Box’.
3. Search results will consist of the list of links along with labels consisting of further
details of the book.
4. To check the availability of the book as well as number of copies issued, user selects
the required link.
Alternate flow:
3a.If the entered book choice is not found
3a.1. The system will ask the user to enter another choice.
3a.2.a.The user can request the admin to add the required book providing the
book details and the user will be notified as and when it is available
4a. If the availability of the book is zero.

4a.1.The user has to enter another choice.
4a.2. The user can request the admin to add the required book providing the
book details and the user will be notified as and when it is available.
 Nameof the Use Case:
Book Issue
Actors:
Librarian, users/students
Pre-Condition:
The readers should decide which book they want to take and also check for its
availability.
Post- Condition:
The book will be issued to the user.
Triggers:
The reader indicates that he/she wants to issue the book.
Process Flow:
1. The reader indicates that the selected book has to be issued.
2. The librarian checks if the book is available or not.
3. The librarian selects issue link.
4. The systemasks the librarian to enter the book id, user id number, issue date and
due date.
Alternate Flow:
.If the entered book choice is not found
3a.1. The system will ask the user to enter another choice.
3a.2.a.The user can request the admin to add the required book providing the
book details and the user will be notified as and when it is available
4a. If the availability of the book is zero.
4a.1.The user has to enter another choice.
4a.2. The user can request the admin to add the required book providing the
book details and the user will be notified as and when it is available.

Book Return
Description:
The process of the Library staff checking the returned book , back into the database
and then proceeding the put it back into the proper location on the shelf.
Actors:
Librarian
Precondition:
The user decides to return a library book which has been issued in the user’s name.
Post condition:
Library book have been checked into the database and have been returned to proper
location.
Process Flow:-
1. The reader indicates that the selected book has to be returned.
2. The librarian selects the return link and enters the book id number which is
specified on the issued book.
3. The status of the book is updated as available.
Book (add)
Actors:
Librarian, admin
Pre –condition:
 To add/remove the admin or the librarian should have logged in successfully,
 The book to be added must be a part of the library.
Process Flow:

1. The admin/librarian should search for the book that is to be added.
2. If the book is not available, it can be added to the book database.
3. User provided the following details and the book can be added to the database
• Name
• Author
• Subject
• Book Id
Alternate scenario:
1a.The book that is to be added is already found on search; it should not be added
again.
 Name ofthe Use Case:
User (Add)
Actors:
Librarian, admin
Pre –condition:
To add the admin or the librarian should have successfully logged in
Process Flow:
1. The admin/librarian should search for the user to be added.
2. If the reader is not found, he/she can be added to the user database
Alternate Flow:
1a. If a reader is to be added and on search he/she is already found, then he/she
should not be added again.

DIAGRAMATIC USECASE:
1. Look and feel Requirements:-
(i).The Library Software interface will be the same for students and Staffs, based on Java
Application.
(ii).The students will have a relatively simpler version without add, remove or modify
possibilities compared to the library staff.
(iii).The web interface will provide search request and reserve books online. The application
should work correctly.
2. Usability Requirements:-

(i).Ergonomically and clear interface
(ii).It should help in avoiding mistakes.
(iii).The product should be made by people with no training.
3. Performance Requirements:-
(i).Any interface between User and Library Software should have a maximum response time of
10 secs
(ii).The response should be fast enough to avoid users’ response collisions.
(iii).It should be available for use at 24x7 throughout the year.
4. Maintainability and portability Requirements:-
(i).Changes like addition or editing student’s information in Database or the change in
password should be verified time to time.
5. Security Requirements:-
(i).The LMS should provide databases’ modification only for librarians and system
administrator after authorization procedures.
(ii).Access to the LMS is permitted only for all students and staff.
6. Legal Requirements:-
(i). Personal information should be protected.
(ii).The LMS should comply with quality assurance standards.
5. Existing System:
System Analysis is a detailed study of the various operations performed by a systemand their
relationships within and outside of the system. Here the key question is- what all problems exist
in the present system? What must be done to solve the problem? Analysis begins when a user
or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions handled by
the present system. The commonly used tools in the systemare Data Flow Diagram, interviews,

etc. Training, experience and common sense are required for collection of relevant information
needed to develop the system. The success of the system depends largely on how clearly the
problem is defined, thoroughly investigated and properly carried out through the choice of
solution. A good analysis model should provide not only the mechanisms of problem
understanding but also the frame work of the solution. Thus it should be studied thoroughly by
collecting data about the system. Then the proposed systemshould be analyzed thoroughly in
accordance with the needs.
System analysis can be categorized into four parts.
1. System planning and initial investigation
2. Information Gathering
3. Applying analysis tools for structured analysis
4. Feasibility study ü Cost/ Benefit analysis.
In our existing systemall the transaction of books are done manually, so taking more time for a
transaction like borrowing a book or returning a book and also for searching of members and
books. Another major disadvantage is that to preparing the list of books borrowed and the
available books in the library will take more time, currently it is doing as a one day process for
verifying all records. So after conducting the feasibility study we decided to make the manual
Library management systemto be computerized.
6. PROPOSED SYSTEM:
Proposed system is an automated Library Management System. Through our software user can
add members, add books, search members, search books, update information, edit
information, borrow and return books in quick time. Our proposed system has the following
advantages.
1. User friendly interface
2. Fast access to database
3. Less error
4. More Storage Capacity
5. Search facility
6. Look and Feel Environment
7. Quick transaction

All the manual difficulties in managing the Library have been rectified by implementing
computerization.
7. TECHNOLOGY USED:
 Front End: HTML, CSS, JAVA Script
 Back End: My SQL Server, PHP
I. HARDWARE CONFIGURATION (Minimum):
 Processor: Pentium III 630MHz
 RAM : 128MB
 Hard Disk : 20GB
 Monitor : 15” Color monitor
 Key Board : 122 Keys
II. SOFTWARE CONFIGURATION:
 Operating System: Windows XP and above.
 Language: Java 2 Runtime Environment
 Database: MS Access2007.
8. Software Life Cycle Model:
There are various models like Waterfall, Spiral, Evolutionary, Prototype, 4GT models.
• The model that is used in our project is RAD model.

Reasons and Features:
 Reusability: RAD models are particularly useful when we want project with large
amount of code reusability.
• Modularization: Our project is divided in many modules and RAD supports
modularization.
• Parallel Programing: The functions are developed in parallel as if they were mini
projects.
• Cost: RAD supports projects with less cost. Since the software used is free and cost is
not a major issue.
• Time: Supports projects with small duration. As we need to complete the project within
4 months.
• Small Projects: Mainly used in small projects.
• RAD is especially well suited developing software that is driven by user interface
requirements.
 RAD model allows quick development and hence quick reviewing. As this is our first
attempt at creating software, quick initial reviews would help in avoiding/detecting
critical mistakes.
9. Cost Estimation:
• For an initial estimation of project size, we used an Estimated Function Point Count. The
expected processes and files are listed and categorized by programming language and
component type:
External Input (EI),
External Output (EO),
External Inquiry (EQ),
External Interface File (EIF)

• Since this is an initial estimation before formal specification
All files are considered to have low complexity
Processes are assumed to be of average complexity
• When the VAF is multiplied with the UAF, we are given the Function Points (FP)
• Size, as measured in Source Lines of Code (SLOC), was then calculated with median
Function Point Gearing Factors
Internal Logical files : Administration data ,User accounts (SQL) .
• External inquiry :
Home page, Account page , Administration page, Search page , Updation of
students , Updating of books ,Information page ,Login (HTML) ,Issuing of books(PHP) .
• External Interface : Web resources .(SQL)
• External output : Logout . (PHP)
• External Input: Add, Delete .(PHP)
Unadjusted function points
The net total is 32+19+13= 64

Calculating TdoI:
Total DoI = 46
GSC DoI GSC DoI
Data
Communications 1 Online update 2
Distributed Functions 4 Complex Processing 3
Performance 5 Reusability 3
Heavily used Config 2 Installation Ease 5
Transaction rate 1 Operational Ease 5
Online data entry 3 Multiple Sites/
Portability
5
End User Efficiency 5 Ease of Change 3
• VAF= 0.65+0.01*(TDol).
= 0.65+0.01(46) =1.11
• Adjusted Function point
For
HTML : 32*1.11=35.52
PHP : 13* 1.11=14.43
SQL : 26*1.11 = 28.86
• The Language factor for

HTML = 58
SQL=37
PHP =53
Calculating SLOC:
• HTML : 35.52*58 = 2060.16
• SQL : 28.86*37 = 1067.82
• PHP : 14.43*53 = 764.79
• Therefore the total SLOC is 3892.77
Effort Estimation using COCOMO:
We use the Basic Model Effort Equation:
Effort=A*(SLoC)Exponent
A is a constant that depends on the developmental mode.Its values are:
Organic = 3.2
Semi-Detached = 2.8
Embedded = 3
SLoC = Source Lines of Code in 1000s.
Exponent is a factor that is also constant for a given mode.
Organic = 1.05
Semi - Detached = 1.12
Embedded = 1.20
Estimation of Effort in Person Months:
Our project comes under the Organic mode.
So, using the formula:

Effort=A*(KSLoC)Exponent
Where,
A = 3.2
KSLoC =3.892
Exp = 1.05
We get Effort = 3.2*(3.892)1.05 = 13.33=13 Person Months
Estimation of Schedule in Calendar months:
Development Time (D) = cb(Effort Applied)db
Here for a organic project:
Cb = 2.5
db = 0.38
Calculating we get
D = 2.5 * (13)0.35
= 5.05 Calendar Months
Average Cost:
• Hardware Cost : 20000/-
• Software cost : Free
• Employee Cost : 20000/-
• Total cost = 40000/-
• Actual Cost = Effort*40000 = 13 * 40000 = 5,20,000 /-

11. System design.
In design phase the important lies on quality which makes this phase an integral part of the
software development .During this phase the software specifications are transformed into
design models that describe the details of the data structures, Interface and design components
Data design: Data design is the process of designing data for the system .Transforms the
information domain model into data structures required to implement the software
Design concept :
Abstraction: Showing the important part and hiding the unnecessary part of the system
Refinement: It is the process of elaboration where the designer provides successively
more detail for each design component. So we have provided all the basic details of the
designing used in the system development.
Modularity: It is a single attribute of software that allows a program to be intellectually
manageable. In our LMS we have divide the whole systeminto several modules, this
reduces chances of errors as different modules are developed and tested separately.
Software Architecture: Architecture is the structure of program components which
describe the interaction between this product as well as the data structure. It provides
the conceptual integrity for a system.
Control hierarchy – The structure of the program elaborates the organization of the
program mechanism in modules & their sub-modules and display relationship between
them this implies a hierarchy of control. In LMS we have divide the systeminto modules
like issue return, login and registration ETC.
Information hiding – It means information within one module is inaccessible to the
other module means intentionally hiding the secret part. In our system we implemented
it like one student can’t view the details of others.

Architectural design :
The main purpose that this architectural design serves is to determine the structure of
the software. It is like designing a framework for the systemand so that’s why we need
to analyse this and then begin with the design. A good architecture can help ensure that
a system will satisfy key requirements in areas such as performance, reliability,
portability, scalability. The used architecture in our case is layered architecture as
security is critical element rather than all.

11. E-R Diagram:
Itis clear that the physicalobjects from the previous section– the member, books,
library – correspond to entities in the Entity-Relationship model, and the
operations to be done on thoseentities – holds, checkouts, and so on –
correspond to relationships. However, a good design will minimize redundancy
and attempt to store all the required information in as small a spaceas possible.

System Design : Input design
Input design is a process of converting user oriented input to a computer based format .
The main objectives take into consideration are :
1) Produce cost effective method of input .
2) Achieve highest possible level of accuracy .
3) Ensure that the input is acceptable and is understood .
Goal when designing input data :
1) Make entry easy ,logical free and free from errors if possible
2) The entering data operators need to know the allocated space for each field
3) The format in which data fields are entered should be given in the input form
Since the data entry is onine here it makes use of processor that accepts the commands and
data from keyboard
Input types can be characterized as
1) External
2) Internal
3) Operational
4) Computerized
5) Input files can exist document form before being input to the computer.
6) Input design is rather complex since it involves procedures for capturing data
And as well as inputting it to the computer

Output design :
Various types of outputs are
• External outputs
• Internal outputs
• Operational outputs
• Interactive outputs
• Turn around outputs
All screens are informative and interactive in such a way that the user can full fill his
requirements through asking queries
Database design :
The general theme behind a database is to handle information as an integrated whole.A
database is a collection of interrelated data stored with minimum redundancy to serve
many users quickly and effectively. After designing input and output, the analyst must
concentrate on database design or how data should be organized around user
requirements. The general objective is to make information access, easy quick,
inexpensive and flexible for other users.
During database design the following objectives are concerned:-
1) Controlled Redundancy
2) Data independence
3) Accurate and integrating
4) More information at low cost
5) Recovery from failure
6) Privacy and security
7) Performance
8) Ease of learning and use TABLES USED

Data tables
In general all servers contains databases which stores data of the projects.
Each database will have specific tables which store relevant data tables project data on to the
user interface. Because database had already linked to the user interface where one can access
the tables.
Tables in our database are:

Programming environment:
It describes the bunch Software’s used for developing a particular system. The whole topic
is categorized into two parts Front-end Scripting, & Backend Programming. Tools Used to
develop this system are the following:
Adobe dream viewer: Used for developing the design & building the code of the
application. Front end of the program is done using HTML and CSS. The backend
programming is done using PHP and MYSQL.
Code snapshots:

12. SOFTWARE TESTING:
Is the menu bar displayed in the appropriate contested some systemrelated features included
either in menus or tools? Do pull –Down menu operation and Tool-bars work properly? Are all
menu function and pull down sub function properly listed? Is it possible to invoke each menu
function using a logical assumption that if all parts of the systemare correct, the goal will be
successfully achieved? In adequate testing or non-testing will leads to errors that may appear
few months later.
This creates two problems
1. Time delay between the cause and appearance of the problem.
2. The effect of the system errors on files and records within the system.
The purpose of the systemtesting is to consider all the likely variations to which it will be
suggested and push the systems to limits.
The testing process focuses on the logical intervals of the software ensuring that all statements
have been tested and on functional interval is conducting tests to uncover errors and ensure
that defined input will produce actual results that agree with the required results. Program
level testing, modules level testing integrated and carried out.

There are two major type of testing they are
1) White Box Testing.
2) Black Box Testing.
White box Testing:
White box Testing sometimes called “Glass box testing” is a test case design uses the
control structure of the procedural design to drive test case. Using white box testing methods,
the following tests were made on the system:
 All independentpathswithinamodule have been exercisedonce inoursystem, ensuringthat
case wasselectedandexecutedcheckedall case structures.The bugsthatwere prevailingin
some part of the code where fixed.
 All logical decisionswere checkedforthe truthandfalsityof the values.
Black box Testing:
Black box testing focuses on the functional requirements of the software. Black box testing
enables software engineering to derive a set of input conditions that will fully exercise all
functional requirements for a program. Black box testing is not an alternative to white box
testing rather it is complementary approach that is likely to uncover a different class of errors
that white box methods like
1) Interface errors
2) Performance in data structure
3) Performance errors
4) Initializing and termination errors
Test Cases in Project:

13. SYSTEM IMPLEMENTATION:
Implementation is the stage in the project where the theoretical design is turned into a working
system. The implementation phase constructs, installs and operates the new system. The most
crucial stage in achieving a new successful systemis that it will work efficiently and effectively.
There are several activities involved while implementing a new project they are:
• End user training
• End user Education
• Training on the application software
• System Design
• Parallel Run and To New System
• Post implementation Review
End user Training:
The successful implementation of the new system will be purely based upon the involvement of
the officers working in that department. The officers will be imparted the necessary training on
the new technology.
End User Education:
The education of the end user start after the implementation and testing is over. When the
system is found to be more difficult to understand and complex, more effort is put to educate
the end used to make them aware of the system, giving them lectures about the new system
and providing them necessary documents and materials about how the systemcan do this.

Training of applicationsoftware:
After providing the necessary basic training on the computer awareness, the users will have to
be trained upon the new systemsuch as the screen flows and screen design type of help on the
screen, type of errors while entering the data, the corresponding validation check at each entry
and the way to correct the data entered. It should then cover information needed by the
specific user or group to use the system.
Post ImplementationView:
We are planning a method to know the states of the past implementation process. For that
regular meeting will be arranged by the concerned members about the implementation
problem and success.
14. FUTURE SCOPE:
FUTURE SCOPE OF APPLICATION:
This application can be easily implemented under various situations. We can add new features
as and when we require. Reusability is possible as and when require in this application. There is
flexibility in all the modules.
SOFTWARE SCOPE:
• Extensibility: This software is extendable in ways that its original developers may not expect.
The following principles enhance extensibility like hide data structure, avoid traversing multiple
links or methods, avoid case statements on object type and distinguish public and private
operations.
• Reusability: Reusability is possible as and when require in this application. We can update it
next version. Reusable software reduces design, coding and testing cost by amortizing effort
over several designs. Reducing the amount of code also simplifies understanding, which
increases the likelihood that the code is correct. We follow up both types of reusability:

Sharing of newly written code within a project and reuse of previously written code on new
projects. Online Library Management System
• Understandability: A method is understandable if someone other than the creator of the
method can understand the code (as well as the creator after a time lapse). We use the
method, which small and coherent helps to accomplish this.
• Cost-effectiveness: Its cost is under the budget and make within given time period. It is
desirable to aimfor a system with a minimum cost subject to the condition that it must satisfy
the entire requirement.
Scope of this document is to put down the requirements, clearly identifying the information
needed by the user, the source of the information and outputs expected from the system.
Online Library Management System
CONCLUSION:
Our project is only a humble venture to satisfy the needs in a library. Several user friendly
coding have also adopted. This package shall prove to be a powerful package in satisfying all the
requirements of the organization.
The objective of software planning is to provide a frame work that enables the manger to make
reasonable estimates made within a limited time frame at the beginning of the software project
and should be updated regularly as the project progresses.

DOCUMENTATION

In this document

More Related Content

What's hot

Similar to DOCUMENTATION

DOCUMENTATION