LI

B
1|Page

Library
Management
System
Documentation
2|Page

Contents
Introduction................................................................................................................................................................................. 3
System Analysis....................................................................................................................................................................... 5
Feasibility Analysis...................................................................................................................................................................5
HARDWARE CONFIGURATION.................................................................................................................................................7
SOFTWARE CONFIGURATION..................................................................................................................................................7
Requirements............................................................................................................................................................................... 8
FUNCTIONALREQUIREMENT...................................................................................................................................................8
Non-Functional Requirements..............................................................................................................................................10
External Interface Requirements..........................................................................................................................................11
Software Design:........................................................................................................................................................................ 11
Use Case Diagram.................................................................................................................................................................. 12
Data Flow Diagram................................................................................................................................................................ 13
Software Interface:................................................................................................................................................................14
SYSTEM IMPLEMENTATION........................................................................................................................................................19
White Box Testing Or Glass testing:......................................................................................................................................20
Black box testing:................................................................................................................................................................... 22
Maintenance:............................................................................................................................................................................. 23
3|Page

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 c++, which mainly focuses on basic operations
in a library like adding new books, and updating new information, searching books
and members and facility to borrow and return books.

“Library Management System” is a windows application written for 64-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.
The report generation facility of library system helps to get a good idea of which are
the books borrowed by the members, makes users possible to generate reports.

The software Library Management System has four main modules.

Insertion to Database Module – User friendly inputscreen

Extracting from Database module – Attractive OutputScreen
Report Generation module – borrowed book list & Available booklist
Search Facility system – search for books andmembers

PURPOSE

The purpose of the project is to maintain the details of books and library members of
different libraries. The main purpose of this project is to maintain an easy circulation
system between clients and the libraries, to issue books, also to search and reserve
any book from different available libraries and to maintain details about the user).
4|Page

SCOPE

The ILM System provides information's like details of the books, insertion of new books, deletion
of lost books, limitation on issuing books, fine on keeping a book more than one month from the
issueddate.
It is easy to manage books in the library.

Also, user can provide feedback for adding some new books to thelibrary.
5|Page

System Analysis

No Existing System
There is no existing system in the school.

Proposed System

Proposed system is an automated Library Management System. Through our software

user can add books, search members, search books, update information, edit
information, borrow and return books in quick time. Our proposed system has the
following advantages.

 User friendlyinterface
 Fast access todata
 Lesserror
 More StorageCapacity
 Searchfacility
 Look and FeelEnvironment
 Quicktransaction

All the manual difficulties in managing the Library have been rectified by
implementing computerization.

Feasibility Analysis

Whatever we think need not be feasible. It is wise to think about the

6|Page

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

Technical Feasibility:

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 with us
here we are utilizing the resources which are available already.

Economic Feasibility

Development of this application is highly economically feasible. The

organization needed not spend much money one for the development of the
system already available. The only thing is to be done is making an environment
for the development with an effective supervision. If 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 system is economicallyfeasible.
7|Page

HARDWARE CONFIGURATION

Processor : which run dev c++

RAM : 128MB
HardDisk : 20mb
KeyBoard : 122Keys

SOFTWARE CONFIGURATION

OperatingSystem : WindowsNT,

Language : Dev C++

Compiler : Dev C++ compiler

Database : Binary file

8|Page

Requirements
FUNCTIONALREQUIREMENT

R.1: Users
Description:First the user will have to select the user type. There are two different type ofusers.
The librarian:The librarian will have to access to control book incoming and outgoing.
student: The user has to provide select as a student.

R.1.1: Login
Input: To login as a librarian you have to put password in it.As a student you have to select
student option.
Output: User will be able to use the features ofsoftware.

R.2: Manage books byuser.

R.2.1: Booksissued.
Description: List of books will be displaced along with data ofreturn

R.2.2: Search
Input: Enter the name of author's name, book name, id of the books to beissued.
Output: List of books related to thekeyword.
Input:select the book userwants.
Processing: if selected book is available then book will be issued else error will bedisplayed.
9|Page

Manage book bylibrarian

Update details ofbooks

Addbooks
Input: Enter the details of the books such as names, author, edition,quantity.
Output:Book added

Removebooks
Input: Enter the name of the book and quantity ofbooks.
Output: Update the list of the booksavailable.

Issuesbook
State: Searched the book user wants to issues.

Return
Input; Return the book to thelibrary.
Output: The issued list will be updated and the returned book will be listedout.

Fine
Input: check for the fines.
Output: Details about fines on different books issued by theuser.
Processing: The fine will be calculated, if it crossed the date of return and the user didnot
renewed if then fine will be applied by Rs 10 perday.
10 | P a g e

Non-Functional Requirements

UsabilityRequirement

The instruction is written so no worries about the confusion it is just a simple system with less and
clear options so no special training is required to use this system. The system is user friendly
which makes the system easy.

AvailabilityRequirement

The system is available 100% for the user and is available whenever the library is open and
authorized person is there.

EfficiencyRequirement

Less chances of damage because bin files are used which only computer can understand the data
and no one can change it.

Accuracy
The system should accurately provide real time information taking into consideration various
concurrency issues. The system shall provide 100% access reliability.

PerformanceRequirement

The information is refreshed depending upon whether some updates have occurred or not in the
application. The system shall respond to the member in not less than two seconds from the time
of the request submittal. The system shall be allowed to take more time when doing large
processing jobs. Responses to view information shall take no longer than 5 seconds to appear on
the screen.

ReliabilityRequirement
11 | P a g e

The system has to be 100% reliable due to the importance of data and the damages that can be
caused by incorrect or incomplete data. The system will run as the library is open.

External Interface Requirements

First there will be a welcome page to ask the user to select the user option
If the user is a student he will be then shift to menu where he can look book list and can search
the book.
If the user is librarian then a menu will be appearing with list of book search and the librarian can
modify the information, issue the book, and can change the password.

Software Design:

System design is the process of defining the architecture, components, modules, interfaces and

data for a system to satisfy specified requirements. Normally, the design proceeds in two stages:

• Physical design (High level & low level)

• Database design

• Physical Design

The physical design is a graphical representation of a system showing the system’s internal and

external entities and the flow of data into and out of these entities. An internal entity is an entity

within the system that transforms data. To represent the physical design of the system, we use

diagrams like data flow diagrams, use case diagrams, etc.

 12 | P a g e

Use Case Diagram

Primary Actor: Student
Secondary Actor: Librarian

include LMS
pass
Login

List of Book

Search book

Add, Delete, and

Student
issue book
Librarian

Change
password
13 | P a g e

Data Flow Diagram

Context:

System Output
User

Level 1:

List of book

Add book

Book

Search

Modify

Delete
14 | P a g e
Borrow book

Borrow

Return book

Issue

Librarian

Return book

Change password

Software Interface:
Welcome Page
15 | P a g e

As a Student:

Book List Branches:

As a Librarian Password:
16 | P a g e

As a librarian login:

INPUT DESIGN

Input design is the process of converting user-oriented input to a

computer-based format. Input design is a part of overall system design, which
requires very careful attention. Often the collection of input data is the most
expensive part of the system. The main objectives of the input design are…

Produce cost effective method ofinputAchieve highest possible level ofaccuracy

1.Ensure that the input is acceptable to and understood by thestaff.

Input Data

The goal of designing input data is to make enter easy, logical and free
from errors as possible. The entering data entry operators need to know the
allocated space for each field; field sequence and which must match with that in
the source document. The format in which the data fields are entered should be
given in the input form. Here data entry is online; it makes use of processor that
accepts commands and data from the operator through a key board. The input
required is analyzed by the processor. It is then accepted or rejected. Input
stages include the followingprocesses
17 | P a g e

 DataRecording
 DataTranscription
 DataConversion
 DataVerification
 DataControl
 DataTransmission
 DataCorrection

One of the aims of the system analyst must be to select data capture
method and devices, which reduce the number of stages so as to reduce both
the changes of errors and the cost. Input types, can be characterizedas.

• External
• Internal
• Operational
• Computerized
• Interactive

Input files can exist in document form before being input to the
computer. Input design is rather complex since it involves procedures for
capturing data as well as inputting it to the computer.

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provide a permanent copy of these result for latter
consultation. Computer output is the most important and direct source of information to the
users. Designing computer output should proceed in an organized well throughout the manner.
The right output must be available for the people who find the system easy to use. The outputs
have been defined during the logical design stage. If not, they should define at
thebeginningoftheoutputdesigningtermsoftypesofoutputconnect,format,responseetc,
18 | P a g e

Various types of outputs are

Externaloutputs
Internaloutputs
Operationaloutputs
Interactiveoutputs
Turn aroundoutputs

All screens are informative and interactive in such a way that the user can full fill his requirements
through asking queries.
19 | P a g e

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 system is that it will work efficiently andeffectively.

• There are several activities involved while implementing a new project they areEnd
usertraining
• End userEducation
• Training on the applicationsoftware
• SystemDesign
• Parallel Run and To NewSystem
• Post implementationReview

End user Training:

The successful implementation of the new system will purely upon the involvement
of the officers working in that department. The officers will be imparted the
necessary training on the newtechnology.
End UserEducation:

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 system can dothis.
20 | P a g e

Training of application software:

After providing the necessary basic training on the computer awareness,

the users will have to be trained upon the new system such 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 thesystem.

Post Implementation View:

The department is planning a method to know the states of the past
implementation process. For that regular meeting will be arranged by the
concerned officers about the implementation problem and success

White Box Testing Or Glass testing:

White box 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 where made on the system A) All
independent paths within a module have been exercised once. In our system,
ensuring that case was selected and executed checked all case structures. The bugs
that were prevailing in some part of the code wherefixed

b)All logical decisions were checked for the truth and falsity of thevalues.
 21 | P a g e

Basic path Testing:

Flow Graph Notation

Welcome Student menu Go back

Select user

Librarian
Search book Select branch Enter name id
Enter Password author

While not
ture
Not found Show book
List of book

Librarian

menu
Select branch

Add book Delete book

Modify book

Enter name id Select book

author
Select book

Not found delete

Not found edit

22 | P a g e

There is a lot more steps in the White box testing.

Black box testing:

Black box testing focuses on the functional requirements of the
software. This is black box testing enables the 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 methodslike.

1)Interfaceerrors

2)Performance in datastructure

3)Performanceerrors

4)Initializing and terminationerrors

The test was perfectly fine but there was one subject missing so we added as in
maintenance.
23 | P a g e

Maintenance:

projectmaintenance is a matter of practicing some very simple values throughout

the course of your project. It means being very intentional about tracking your
progress toward milestones and goals, instead of assuming everything will
happen as planned.

Maintenance form

The project LibraryManagementSystem (LMS) is for computerizing the working in

a library. It is a great improvement over the manual system. The computerization

of the system has speed up the process. In the current system, the front office

managing is very slow. The library managing system was thoroughly checked and

tested with dummy data and thus is found to be very reliable. The software takes

care of all the requirements of an average Library and is capable to provide easy

and effective storage of information related to books that come up to the Library.

Corrective:
There was one subject missing as we added that subject at the deployment time
and it was an important subject therefore it must be added.

Perfective approach:
24 | P a g e

The stack holder said that it would be much better if the software become more
have a graphical user interface so we will try to make the software perfect and
give it graphical user interface.

Adaptive:
The software should need to be adaptive if the want any new subject to be
added to the software

Preventive approach:
We will make our code perfect that next time such mistake can be overcome.