PROJECT

ON
LIBRARY MANAGEMENT SYESTEM
BY

Amit Kumar
Roll no.-130
Prn no.-1714110442

Under the Supervision of

Prof. Mr. SHASHANK JOSHI SIR

Bharati Vidyapeeth

(Deemed To Be University)

College Of Engineering,Pune

Department of Computer Engineering

1
ACKNOWLEDGEMENT

I would like to express my special thanks of gratitude to my teacher Mr.

SHASHANK JOSHI SIR ,who gave me the golden opportunity to do this wonderful
project of FSE on “LIBRARY MANAGEMENT SYSTEM “ ,who also helped me in
completing my project . I came to know about so many new things and I am really
thankful to them.

Name of student
Amit Kumar
PRN NO. 1714110442
ROLL NO.-130
BTECH SEM-IV

2
CERTIFICATE
This is to certify that the project titled LIBRARY MANAGEMENT SYSTEM
submitted by AMIT KUMAR (Roll number 130 of Computer Department Sem-iv)
has been prepared under my/our supervision for the partial fulfillment of the
requirements for B.TECH degree in Bharati Vidyapeeth (deemed to be
university)College of Engineering pune .

Dept. of Computer Engineering, BVUCOEP

(Internal Supervisor)
Countersigned by
………………………………………….
Name of Head-SHASHANK JOSHI SIR

3
CONTENTS :-

1. INFORMATION GATHERING 5-8

2. SDLC Model 9-15

3. Software Requirement Specifications 16-26

4. RISK MANAGEMENT: IT’S IMPLICATIONS 27-38

5. System Analysis 39-41

6. System Design 42-48

 DFD( Data Flow Diagram)

7. Software Architecture Document 49-53

8. UML Design for Library Management System 54-77

9. Software Design Model 78-81

10. System Testing 82-83

11. Conclusion and Future scope 84

12. REFRENCES 85
4
 1. INFORMATION GATHERING

DESCRIPTION OF THE PROJECT

A library is organized for use and maintained by a public body, an institution, a corporation, or a
private individual. Public and institutional collections and services may be intended for use by
people who choose not to—or cannot afford to—purchase an extensive collection themselves, who
need material no individual can reasonably be expected to have, or who require professional
assistance with their research. In addition to providing materials, libraries also provide the
services of librarians who are experts at finding and organizing information and at interpreting
information needs. Libraries often provide quiet areas for studying, and they also often offer
common areas to facilitate group study and collaboration. Libraries often provide public facilities
for access to their electronic resources and the Internet.

This software project is a library management software system with all the basic as well as some
innovative features for managing a library. It consists of a large database of various books available
in the library. It also lists various books issued to respective readers. The system keeps track of all
the books readily available and also the books that have been issued to various readers for the
time period for which the books have been issued. The system also handles books database. If the
reader needs a book, he can order the book request for home delivery by just submitting an online
form. Readers usually tend to forget the date to return their library books, so this system even
calculates fine depending on the expiry date. Thus this innovative library management system
provides enhanced library functionality for this modern world.

Objectives of Library Management System (LMS)

a) To build a system that can receive input and generate automatically output in easy way and
short time.

b) To build a monitoring system that is able to monitor and manage all library operations
efficiently.

c) Give an opportunity to librarians to reduce mistakes that always happen during manual method.

5
d) To store properly the library items in order to maintain their security.

e) To enter and preserve details of the various issues and keep a track on their returns.

This system basically has four types of modules that handle daily activities for the library :

a) Manage Account module

b) Search Record Module

c) Book Borrowing System Module

d) Report Generator Module

By using library management system, the operation of borrowing and managing inventories is
paperless. This system provides a user-friendly data entry with dropdown button menu, list box
and checkbox in purpose to make the input entry easier to understand and use. It is also created
to ensure that the library items are stored properly in order to maintain their security.

This system will store all the books and members information that consist book numbers, book
titles, author names and racks to the system database. It also provides search function to help
students find the book by number of book. Search function will search through the books database
to look for the book and view where the book is situated.

For the administrator user, only librarians have access to view or edit data from the system
databases. Administrator user will handle administrative functions such as create new LMS user
account and decide the number of days allowed for the borrowed books. Users need to enter
correct password and user id before they can access to this function. From here, they can add,
delete or update the book and borrower database

FEATURES OF THE SYSTEM

 Admin login: The system will be under sole control of the admin. Admin can add
or remove books from the system and also maintains records of the book available
and issued in the library. The admin can even update the books details if required.

6
  User login: User has to first create an account in the system to gain access. User
can explore and search for the books he wants. He can place order for the books.
 Tracking the user record: The system can track the period for which the book has
been issued to user and calculates fine if the book is not returned on time.
 Quantity Update- The quantity is updated by the system depending on the
quantity ordered.
 Fine calculation: If the user is unable to return the book, the system automatically
calculates the fine that the user has to pay for subsequent days.
 View date info- The user can view the date when he has issued the book as well
as the expiry date of the book and can view fine to be paid that is calculated by
the system.
 Online search and order form: The user may order the book online. The system
provides a search option where user can order online.
 Credit card payment: User can make payment via credit card.

Advantages:

 The system excludes the use of paper work by managing all the records
electronically.
 Administrator doesn't have to keep a manual track of the users
 Also the system calculates the fine levied on user so admin just have to create bill
and not manually calculate.
 Admin can keep updating the system by providing the new books arrival in library
and their availability thus user need not to go to library for issuing purpose. He
may order it online through this system.
 Thus, it saves human efforts and resources.
7
Disadvantages:

 User cannot view the book in person.

 There is no human interaction if users have some enquiry.

Applications:

 This system can be used in public libraries.

 It can also be implemented in the library of schools, colleges, institutes, and
organizations.

8
 2. SDLC Model :-

The software development life cycle (SDLC) is a framework defining tasks performed at each step
in the software development process. SDLC is a structure followed by a development team within
the software organization. It consists of a detailed plan describing how to develop, maintain and
replace specific software. The life cycle defines a methodology for improving the quality of
software and the overall development process.

The software development life cycle is also known as the software development process.

An effective System Development Life Cycle (SDLC) should result in a high quality system that
meets customer expectations, reaches completion within time and cost evaluations, and works
effectively and efficiently in the current and planned Information Technology infrastructure.

System Development Life Cycle (SDLC) is a conceptual model which includes policies and
procedures for developing or altering systems throughout their life cycles.
9
SDLC is used by analysts to develop an information system. SDLC includes the following activities
−

 Requirements

 Design

 Implementation

 Testing

 Deployment

 Operations

 Maintenance

Phases of SDLC:-
Systems Development Life Cycle is a systematic approach which explicitly breaks down the work
into phases that are required to implement either new or modified Information System.

Feasibility Study or Planning:-

 Define the problem and scope of existing system.

 Overview the new system and determine its objectives.

10
  Confirm project feasibility and produce the project Schedule.

 During this phase, threats, constraints, integration and security of system are also
considered.

 A feasibility report for the entire project is created at the end of this phase.

Analysis and Specification:-

 Gather, analyze, and validate the information.

 Define the requirements and prototypes for new system.

 Evaluate the alternatives and prioritize the requirements.

 Examine the information needs of end-user and enhances the system goal.

 A Software Requirement Specification (SRS) document, which specifies the software,

hardware, functional, and network requirements of the system is prepared at the end of
this phase.

System Design:-
 Includes the design of application, network, databases, user interfaces, and system
interfaces.

 Transform the SRS document into logical structure, which contains detailed and complete
set of specifications that can be implemented in a programming language.

 Create a contingency, training, maintenance, and operation plan.

 Review the proposed design. Ensure that the final design must meet the requirements
stated in SRS document.

 Finally, prepare a design document which will be used during next phases.

Implementation:-
 Implement the design into source code through coding.

 Combine all the modules together into training environment that detects errors and
defects.
11
  A test report which contains errors is prepared through test plan that includes test related
tasks such as test case generation, testing criteria, and resource allocation for testing.

 Integrate the information system into its environment and install the new system.

Maintenance/Support:-
 Include all the activities such as phone support or physical on-site support for users that is
required once the system is installing.

 Implement the changes that software might undergo over a period of time, or implement
any new requirements after the software is deployed at the customer location.

 It also includes handling the residual errors and resolve any issues that may exist in the
system even after the testing phase.

 Maintenance and support may be needed for a longer time for large systems and for a short
time for smaller systems.=

OperatingEnvironment:-
• Operating System : Microsoft Windows
• Network connection that connects user’s computer to local intranet server
• Database: MS-Access
• Hardware: P4 processor, Mouse, Keyboard and Monitor.

Waterfall Model

The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each
phase must be completed fully before the next phase can begin. This type of software
development model is basically used for the project which is small and there are no uncertain
requirements.

At the end of each phase, a review takes place to determine if the project is on the right path and
whether or not to continue or discard the project.

12
In this model software testing starts only after the development is complete. In waterfall model
phases do not overlap.

Diagram of Waterfall model

SOFTWARE PROCESS MODEL

(Linear Sequential Model)

A process model for software engineering is chosen based upon:-

 Nature of the Project.

 Methods and Tools to be used.
 Control and desired deliverables.
The process model, we have chosen to develop this software is a Linear Sequential Model Linear
Sequential Model suggests a systematic, sequential approach to software development that begins
at the system level and progresses through analysis, design, coding, testing and support.

Linear Sequential Model approach has the following phases:-

Software requirements analysis

In this, software engineer understand the nature of a program to be built, he must understand the
information domain for the software as well as required function, behaviour, performance and
interface. Requirements for both the system and the software are documented and reviewed with
the customer.

13
Design

It has four distinct attributes of a program: data structure, software architecture, interface
representations and procedural detail. It is documented and becomes part of the software.

Code generation

Design must be translated into a machine readable form which is done by code generation.

Testing

It focuses on the logical internals of the software, ensuring that all the statements have been tested,
and on the functional externals; that is conducting test to uncover errors and ensure that defined
input will produce actual results.

The Software model used is LINEAR SEQUENTIAL MODEL because of the following reasons:-

 Project being small demands a systematic and sequential approach to software development
i.e. system engineering, software requirement analysis, design, code generation, testing and
support occur in sequence.

 All requirements for the project have been explicitly stated at the beginning. There is very little
scope of customers’ deviation from current requirements, coding and testing after detailed
analysis is much easy.

 Structure is less complex and less innovative with less need of iteration.

14
Support
This is a phase when software will undoubtedly undergo change after it is delivered to the
customer. Change will occur because errors have been encountered, because the software must be
adapted to accommodate changes in its external environment, or because the customer requires
functional or performance enhancements. Software support/maintenance reapplies each of the
preceding phases to an existing program rather than a new one.

15
3. Software Requirement Specification(SRS)

Product Description

Library Management System is a computerized system which can 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 time-saving.
Problem Statement
The problem occurred before having computerized system includes:

 File lost
When no computerizes system is implemented, the file always lost because of
human and environment. Sometimes librarian didn’t keep the record to its original
place because of a lot member queue up to borrow books. After that the file was
missing due to messy environment.

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

PROBLEM STATEMENT:
The problem occurred before having computerized system includes:
 File lost
When computerized system is not implemented file is always lost because of
16
 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.1 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.
 Option of online Notice board
Librarian will be able to provide a detailed description of workshops going in the

17
 college as well as in nearby colleges
 Lecture Notes
Teacher have a facility to upload lectures notes in a pdf file having size not more
than 10mb.

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

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

19
 - System must be able to not allow two books having same book id.

SEARCH BOOK

DESCRIPTION OF FEATURE
This feature is found in book maintenance part . we can search book based on book id
, book name , publication or by author name.

Functional requirements
- System must be able to search the database based on select search type
- System must be able to filter book based on keyword enterd
- System must be able to show the filtered book in table view

1.5 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

1.6 EVENT ADDITION

DESCRIPTION OF FEATURE
This feature allows teacher and student to add information about various workshops being
conducted in college and colleges nearby.

20
 functional requirements
-System should be able to add detailed information about events .
-System should be able to display information on notice board available in the homepage
of site

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 EXISTING VS PROPOSED SYSTEM

i. Existing system does not have any facility of teachers login or student
login where as proposed system will have a facility of student login as

21
 well as teacher’s login
ii. Existing system does not have a facility of online reservation of books
whereas proposed system has a facility of online reservation of books
iii. Existing system does not have any facility of online notice board where
description of workshops happening in our college as well as nearby
colleges is being provided.
iv. Existing system does not has any option of lectures notes uploaded by
teachers whereas proposed system will have this facility
v. Existing system does not have any facility to generate student reports as
well book issue reports whereas proposed system provides librarian with
a tool to generate reports
vi. Existing system does not has any facility for book request and
sugeestions where as in proposed system after logging in to their
accounts student can request books as well as provide suggestions to
improve library

22
2.3 EXISTING VS PROPOSED SYSTEM

vii. Existing system does not have any facility of teachers login or student
login where as proposed system will have a facility of student login as
well as teacher’s login
viii. Existing system does not have a facility of online reservation of books
whereas proposed system has a facility of online reservation of books
ix. Existing system does not have any facility of online notice board where
description of workshops happening in our college as well as nearby
colleges is being provided.
x. Existing system does not has any option of lectures notes uploaded by
teachers whereas proposed system will have this facility
xi. Existing system does not have any facility to generate student reports as
well book issue reports whereas proposed system provides librarian with
a tool to generate reports
xii. Existing system does not has any facility for book request and
sugeestions where as in proposed system after logging in to their
accounts student can request books as well as provide suggestions to
improve library

2.4 SOFTWARE TOOLS USED

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

2.4.1 Front end

The front end is designed using of html , Php ,css, Java script
 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

23
 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) 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

24
 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) 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 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 (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
25
 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.
BACK END- The back end is designed using mysql which is used to design
the adatabases

 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 for- profit
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
forsearches), Facebook, Twitter, Flickr, and YouTube.

26
 4.RISK MANAGEMENT: IT’S IMPLICATIONS FOR
LIBRARY MANAGEMENT

Abstract

The development and dissemination of information in various forms

and media on a local, national and international level has envisaged
the librarians to be advocative in all means of information service
provided from their libraries. Higher education is experiencing a
dramatic influx with a new generation of faculty with different sources
of information. This article deals with the definition of risk
management and identification of the various areas of risks in library
environment. The applications of risk management in libraries start
from the collection development, through publishers / vendors for
different types of documents. The different types of risk include:

Assessing the organization

Collection management

Access rights by the users

Scholarly communication

Risks associated with the migration

Consortia

Staff training and recruitment

Preservation

 Use of technology by the students, faculty and

library staff. The strategies for managing the risks are
explained for the following:
By having discussions, group meetings, etc, the information
requirements of users,
27
 faculty and students can be found;

Communicating with other agencies like library schools,

professional associations for finding out the latest syllabus, in
order to develop the content accordingly.
Detailed discussion with publishers / vendors for collection
management covering all aspects of the future needs /demands
/ changes;
For collecting the resources from external sources, resource
sharing and access to the databases along with Internet;
Consortium approach for collection development, content
management, information services and preservation;
Hiring staff with competitive skills and also develop skills for the
existing staff, by providing in-house training; and
Preservation aspect could be resolved by consortia approach by
discussing the formats, storage medium, software availability,
upgradation of hardware, etc.

INTRODUCTION
Libraries in general are experiencing unprecedented demands for change both
in the way they work and the information and materials they provide.
Librarians have tended to greet the need for change with feelings of insecurity
and visions of ongoing chaos. The vitality and relevance of academic libraries
are increasingly at risk. Faculty and students on / off campuses expect more
from the library due to the growth of information available through electronic
resources. As the changes in higher education are moving, librarians are
responding to these systematic changes in the academic environment. Changing
roles for librarians, as collaborators, integrators, instructional designers and
information consultants and models of information delivery necessitated not
only increased relation between faculty-librarian contacts, but also dramatic
changes in the nature of faculty-librarian relationships(5). The need for
understanding of different techniques in procuring content, management of

28
content, rights of access, collection development policies, etc with risk
associated with managing different activities in association with other
librarians, publishers, system specialists, students and faculty and others are
discussed in this article.
DEFINITION
Risk management is the process of measuring or assessing risk and then
developing strategies to manage the risk.
1. AREAS OF RISK MANAGEMENT
The different areas, where risk management can occur in library environment
are:
 Assessing the institution / organizations requirement

 Acquisition / Collection development

 Content development

 Access rights by the users

 Risks associated with migration

 Scholarly communication

 Consortium arrangements

 Staff training and recruitment

 Preservation decisions

 Use of technology by the students, faculty and library staff.

 Security aspects for library materials and staff

 The risk of exposing the items in the collection to theft, mutilation or

accidental loss.
2. RISK MANAGEMENT
Risk management is the sum of all activities directed toward acceptably
accommodating the possibility of failure in a program. Risk management is
based on assessment; every risk management assessment includes a number of

29
 tasks:
(1) identification of concerns,.
(2) identification of risks.
(3) evaluation of the risks as to likelihood and consequences.
(4) assessment of options for accommodating the risks.
(5) prioritization of risk management efforts.
(6) development of risk management plans.

3. RISKS AND STRATEGIES FOR RISKS

Assessing the institution / organizations requirement

Academic libraries address their mission to support research and teaching by

building collections and developing services intended to meet the information
needs of their users. If there is a sudden change in administrative / managerial
personnel, and the change in organizations goal and policy issues, may also
pose risks for the libraries in procurement policy and other activities.

Acquisition / Collection management

Librarians try to assure for information supply as per the user demand by
having collection development policy by allocating budgets in institutional
priorities. If the library collections does not meet user needs and expectations,
can lead to a spiral of loss of funding; resulting in a decrease in usefulness,
followed by further erosion of fiscal support and the decline in the quality of the
collection in the short run. Due to this, there is a risk for decline in budget
allotment or the budget allotted may be diverted to other departments (2).
Content Management
For many reasons libraries do not have the same degree of control over the
content in digital resources. Providers of digital information resources are able to
add content or more often, delete content from their products without their
30
customers’ consent. Libraries are frequently notified after the fact or given very
little advance notice of these actions. On occasion, no notification is issued;
libraries and their users simply discover the content change. Unplanned content
changes affect the collection’s reliability and integrity and content removal may
pose risks to the library profession’s commitment. (1)

Access Rights by Users

Legal risks can arise in relation to the access to, use and dissemination of data
and information. These risks increase with on-line material. Proprietary rights
apply to software, databases, written works and other original materials.
Information used, updated and circulated should be accurate, both in order to
avoid the risks of liability for defamation or for illegal content and for any data
protection compliance. Also the risk related to CD-ROM network, like maximum
access, full text download, network licence, etc. are to be considered.

Migration

The following three major categories of risk must be measured when

considering migration as a digital strategy:

 Risks associated with the general collection. These risks include the
presence or absence of institutional support, funding, system hardware
and software, and the staff to manage the archive. These are essential
components of a digital archive. The collection, and the users who use the
collection, will be affected to some degree by a migration of data. Legal and
policy issues associated with digital information will introduce additional
risks.

 Risks associated with the data file format. These include the internal
structural elements of the file that are subject to modification.

 Risks associated with a file format conversion process. The conversion

31
 software may or may not produce the intended result; conversion errors
may be gross or subtle.

4. SCHOLARLY COMMUNICATION

a) Publishing

Scholarly Communication actually encompasses the totality of what occurs

between the creation and consumption of a scholarly work. The risks to it and
the information marketplace begin at the point at which it is documented and
are related to who sells scholarly content, who buys it, and how these
transactions are accomplished. Richard Fyffe (4) notes that librarians must
inform the members of their academic communities about this risk, if they are
to participate in the reform of the scholarly communication process and
maintain their credibility and integrity. Risk and technological changes are
inexorably linked, and librarians as experts, must communicate these risks to
lay persons and develop appropriate risk management strategies like:

1 Encourage and enforce sound scholarly citation and documentation

practices

2 Promote competition among publishers and alternative access to locally

produced content.

3 Cancel individual titles available through aggregated databases judiciously.

4 Become more assertive as negotiators and as customers. Be willing to say

‘‘no’’ when a contract or license is not satisfactory.

b) E-Journals

The content removal by e-journal publishers is copyright-related, which is one

32
of the risks to the libraries by not providing the content without any
interruption. Publishers do not have the rights to republish electronically the
content they originally published in paper. Less frequently, publishers remove
content in response to research errors, plagiarism, and fraud. This practice is
contrary to traditional scholarly communication practice and it violates the
library’s commitment to preserve the historical record with all its flaws.
Disaggregation, or the removal of content from an aggregated database by its
creator or owner, occurs for a variety of reasons—often economic but
sometimes philosophical in nature. This can transform an aggregated database
from a key, to a marginal, resource and, since libraries are rarely compensated
for content removal, it can also pose financial challenges. If the lost content is
an important resource for its users the library may have to resubscribe to it
from another, generally from more expensive source (2).

c) Royalty to authors, publishers and others

The payment to authors, publishers and others who participate in scholarly

publishing is trivial, due to the policy changes in distribution of honorarium and
other mode of payments.

5. CONSORTIA

a) Big Deals

Libraries pursue ‘‘Big Deals’’ i.e., license agreements in which access is gained
to all of a publisher’s output for a price based on current subscriptions—they
acquire more content for less money in the short run, but they risk weakening
‘‘the power of librarians and consumers to influence scholarly communication
systems in the future’’ It is worth noting that the pursuit of more information or
more publications for less money takes place in most consortia purchases,
many of which would not necessarily be considered ‘‘Big Deals.’’

33
 b) License Agreements

Publishers and content providers often require libraries to sign agreements that
restrict the libraries’ ability to use their products for interlibrary loan, as well as
the libraries’ rights to preserve and archive parts of them. Further, by using
digital rights management systems, they enforce use restrictions, such as on
copying and downloading, which are more stringent than those that copyright
law would impose. Also they create digital fences that enclose not only their
works but also large portions of the public domain.

c) Co-ordination

Risk involved for co-coordinating with local, national and international

organizations for forming the consortia are for the material to be procured /
accessed. Each country has a different policy for acquiring
/ accessing to the different types of content and agreements would be a risk, if
there is a change in future policy decision by the Government and also in
continuing the membership (3).

6. PUBLISHER AND VENDOR MERGERS

The librarian is serious and concern about the ownership of content. Publishers
suddenly raise prices due to inflation and thereby threaten one of the
profession’s core values, equal access to information. They can also affect the
usability of digital content due to changes in the interface through which

acquired content is accessed and/or the way acquired and existing content are
merged or juxtaposed(2).

7. PRESERVATION
34
Preservation of information in all formats is increasingly an emphasis of libraries
and allow for ongoing use. It should evolve as a distributed system by interacting
with large national coordinating organizations; preservation guidelines should
follow the data processing and filtering at all levels. The lack of any long- term
technical solution to the problem of digital preservation limits to the efficacy of
critical problems with substantial new investments, with allocating new
responsibilities and assessing costs for a nonexistent process is one of the risks
to the librarians (7).

Staff Training and Recruitment

The staffs who are already working are to be retrained to update their
knowledge and may have to recruit new entrants with better / higher
qualifications. The risk involved here is the willingness to attend the training
and risk of taking new staff, by thinking that they will be better than the existing
ones.

Use of Technology

For accessing the organization, the proper use of website, by having sufficient
connectivity and systems is one of the risks. People may have different type of
system, and if there is a change in software and formats for access, download
there is a risk. The type of users also suddenly changes, in case the organization
introduces new courses, the need for updating or modifying the content on the
website is one of the risks.

8. STRATEGIES FOR MANAGING RISK

The strategies for managing the risks are explained for the following:

35
 By having discussions, group meetings, etc, the information requirements
of users, faculty and students can be found;

 Communicating with other agencies like library schools, professional

associations for finding out the latest syllabus, in order to develop the
content accordingly.

 Detailed discussion with publishers / vendors for collection management

covering all aspects of the future needs /demands / changes;

 For collecting the resources from external sources, resource sharing and
access to the databases along with Internet;

 Consortial approach for collection development, content management,

information services and preservation;

 Developing own collections by e-print archives and arrange for access to

open access materials
/ freely available resources;

 Hiring staff with competitive skills and also develop skills for the existing
staff, by providing in- house training; and

 Preservation aspect could be resolved by local, national or consortial

approach by discussing the formats, storage medium, software availability,
upgradation of hardware, etc.

36
 CONCLUSION

Risk, while connoting serious consequences, collection managers must work

knowledgeably to manage the risk mentioned. They must continue to communicate with
their constituents about their needs, but these conversations should be expanded in
scope, on changing expectations as well as convey information about changes in
scholarly communication, the information marketplace and risks to professional and
societal values. They should be more proactive consumers, conveying to their publishers
and content providers concerns about privacy, collection stability and reliability, and
access. Further, collection managers must be prepared to discontinue purchasing or
subscribing to the information resources offered by publishers and content providers
who, over the long term, do not address these concerns. Finally, collections managers need
to play an active role in local and national efforts to encourage competition and create
alternative access to information.

Risk Mitigation Plan

All risk analysis activities presented to this point have a single goal-to assist the project team in developing
a strategy for dealing with risk.

Issues:

 Risk avoidance
 Risk monitoring
 Risk management and contingency planning

Steps taken are:

 Meet with current staff and check cause for problems

 Mitigate causes which are under control before project starts
 Presume turnover will occur develop plans
 Conduct peer reviews
RISK STRATEGIES
37
Reactive

A Reactive Strategy monitors the risk project for likely risk and set aside resources to deal with them,
should they become actual problems. Software team does nothing about risks until something goes wrong.

Proactive

A Proactive strategy begins long before technical work is initiated. Potential risks are identified, their
probability impact is assessed, and they are ranked by importance.

38
5. System Analysis

Current problems

A number of problems have been identified with the current system, including:

• The catalogue is often out-of-date; updating is tedious and only takes place when the staff have
time.

• The processes for recording loans, returns and recalls are time consuming.

• Searching through the catalogue, borrower and loan records is often long and laborious. Both
borrowers and library staff find this very annoying.

• Fines have to be calculated manually. This takes time and is error prone, resulting in arguments
between borrowers and staff.

• Finding out whether a book is actually available for loan is tedious, and often only possible by
looking for it on the shelve.

.• A later enhancement will be the inclusion of ordering of books.

• Online lectures video tutorials can be added by teachers.

• Online assignments submission facility.

• A feature Of group chat where students can discuss various issues of engineering can be added
to this project.
39
• Data encryption can be added
According to the current situation of small and medium-sized library carried out feasibility
analysis and the actual demand. The library's basic business processes are described. Combining
with the knowledge of library and database technology to design each module. The system using
the Windows XP/Windows 6.0 as system platform, using Visual basic 6.0 as a front-end application
development tools, Microsoft SQL Server 2000 as the background database. Through to the small
and medium-sized books management system management system requirements analysis,
functional module division, database model analysis, designed the database structure and
application. Due to the use of computer management, improved the traditional manual
management way, improve the management level.
ANALYSIS MODEL
Software analysis and design includes all activities, which help the transformation of requirement
specification into implementation. Requirement specifications specify all functional and non-
functional expectations from the software. These requirement specifications come in the shape
of human readable and understandable documents, to which a computer has nothing to do.

Software analysis and design is the intermediate stage, which helps human-readable
requirements to be transformed into actual code.

Let us see few analysis and design tools used by software designers:

 Data Flow Diagram

Data flow diagram is graphical representation of flow of data in an information system. It is
capable of depicting incoming data flow, outgoing data flow and stored data. The DFD does not
mention anything about how data flows through the system. There is a prominent difference
between DFD and Flowchart. The flowchart depicts flow of control in program modules. DFDs
depict flow of data in the system at various levels. DFD does not contain any control or branch
elements.
Types of DFD
Data Flow Diagrams are either Logical or Physical.

 Logical DFD - This type of DFD concentrates on the system process, and flow of data in
the system.For example in a Banking software system, how data is moved between
different entities.
40
  Physical DFD - This type of DFD shows how the data flow is actually implemented in the
system. It is more specific and close to the implementation.

DFD Components
DFD can represent Source, destination, storage and flow of data using the following set of
components -

 Entities - Entities are source and destination of information data. Entities are represented
by a rectangles with their respective names.
 Process - Activities and action taken on the data are represented by Circle or Round-
edged rectangles.
 Data Storage - There are two variants of data storage - it can either be represented as a
rectangle with absence of both smaller sides or as an open-sided rectangle with only one
side missing.
 Data Flow - Movement of data is shown by pointed arrows. Data movement is shown
from the base of arrow as its source towards head of the arrow as destination.

41
6. System Design

TABLE DESIGN

VARIOUS TABELS TO MAINTAIN INFORMATION

BOOK TABLE FOR KEEPING TRACK OF BOOKS

Field Data type Default Key Extra

Code INT(11) Not Null Primary Auto
increment

Bookname VARCHAR(255) Null

Author VARCHAR(255) Null

Publication VARCHAR(255) Null

Subject VARCHAR(255) Null

No of copies INT(10) Null

TEACHER TABLE TO KEEP TEACHER INFORMATION

Field Data Type Default Key Extra

Loginid INT(11) NOT NULL Foreign References

key teacher

Username VARCHAR(255) NULL

Password VARCHAR(255) NULL

42
 Issue table to keep track of books issued

Field Data Type Default Key Extra

bookid INT(11) NOT NULL Foreign key References book

stuid INT(11) NOT NULL Foreign key References

Student

issuedate DATE NULL

returndate DATE NULL

Issue table to keep track of books issued

Field Data Type Default Key Extra

bookid INT(11) NOT NULL Foreign key References

book

stuid INT(11) NOT NULL Foreign key References

Student

issuedate DATE NULL

43
 returndate DATE NULL

STUDENT LOGIN TABLE

Field Data type Default Key Extra

logid INT(11) NOT NULL Foreign key References Student

Username VARCHAR(255) NULL

Password VARCHAR(255) NULL

numbooks INT(1) NULL

EVENT TABLE FOR EVENT INFORMATION

Field Data type Default Key Extra

Name Varchar(255) NULL

Date Date(yyyy/mm/dd) NULL

Time VARCHAR(255) NULL

Mname VARCHAR(255) NULL

Contactno. Int(30) NULL

44
 Email VARCHAR(255) NULL

Venue varchar(255) NULL

TEACHER LOGIN TABLE

Field Data Type Default Key Extra

Loginid INT(11) NOT NULL Foreign References

key teacher

Username VARCHAR(255) NULL

Password VARCHAR(255) NULL

DATA FLOW DIAGRAMS

DATA FLOW DIAGRAM FOR TEACHER LOGIN

TEACHER

DATABASE

45
 ENTER
CHECK
TEACHER
URL

IF VALID

PAGE

After entering to the home page of the website , teacher can choose the TEACHER LOGIN
option where they are asked to enter username & password , and if he/she is a valid user
then a teacher login page will be displayed.

DATA FLOW DIAGRAM FOR STUDENT LOGIN

STUDENT DATABSE

ENTER
CHECK
STUDENT
URL

IF VALID

PAGE

After entering to the home page of the website , student can choose the STUDENT LOGIN option
where they are asked To enter username & password , and if he/sheis a valid user then a student
login page will be displayed.

46
 DATA FLOW DIAGRAM FOR BOOK ISSUE

LOGIN

DATABASE

IF NO.
ENTER IF UPDATE MESSAGE
OF
LOGIN AVBL BOOK
NO. “BOOK
OF
ISSUED

BOOK LOGIN BOOK

DATABASE TABLE DATABASE

It is a 2nd level Data Flow Diagram where after entering STUDENT LOGIN page he/she can
select a book issue option where after entering the book detail, he/she can select the book
issue option and if the maximum no of books issued limit is not crossed then a request
will be sent to the librarian who will approve the book issue.

47
 DATA FLOW DIAGRAM FOR BOOK SEARCH

HOME

BOOK
DATABASE

After the home page login there will be an option of the book search where after entering book
detail like author name, publication, book name ,etc book details will be displayed.

DATA FLOW DIAGRAM FOR ACCOUNT CREATION

ADMIN

ADMIN STUDENT

DATABASE DATABASE

48
7. Software Architecture Document

Introduction
This document provides a comprehensive architectural overview of the system, using a
number of different architectural views to depict different aspects of the system. It is
intended to capture and convey the significant architectural decisions which have been made
on the system.

Scope

This document outlines:

- Detailed use case scenarios of key process flows of the application

- The class model and relationships

- The sequence diagrams which outline key use case scenarios

- The data/object model with relational table design

- User interface style and design

Architectural Representation

This section describes what software architecture is for the current system, and how it is represented.

49
 AddNewStudent
(from csi518team) UpdateDeleteStudent
(from csi518team)

AddBook
(from csi518team)

UpdateDeleteBook
(from csi518team)

SearchBook
(from csi518team)

Librarian
(from csi518team)

CheckInBook
(from csi518team)

CheckOutBook
(from csi518team)

PayLateFee
(from csi518team)
ViewStudentDetails ViewBookDetail
(from csi518team) (from csi518team)

50
 Architectural Goals and Constraints
This section describes the software requirements and objectives that have some significant
impact on the architecture.

The key design goals would be:

- Usability

- Stability

- Platform independence

- 3-Tier design methodologies to enable efficient and responsive system

Use-Case View
This section lists use cases or scenarios from the use-case model which depict significant,
central functionality of the final system, or if they have a large architectural coverage.

Use-Case Realizations
Add New Student:

InsertStudentRecord

ViewStudentDetails VerifyStudent
Librarian

Failure

Update / Delete Student

Failure

ViewStudentDetails VerifyStudent
Librarian

UpdateDeleteStudentRecord

51
Add a Book

Failure

ViewBookDetail
Librarian

AddBookRecord

Update / Delete Book

Failure

ViewBookDetail
Librarian

UpdateDeleteBookRecord

Search Book

ViewBookDetail

Success

EnterSearchParameters DispalySearchResult
Librarian
AddToMyList
<<extends>> Failure

ShowMyList CheckInBook

<<extends>>

CheckOutBook

52
Check-In Book
<<extends>>

Success PayLateFee
EnterStudentID
Librarian

Failure

Check-out Book

Success

EnterBookCallNo EnterStudentID
Librarian

Failure

53
 8. UML Design for Library Management System
Use-Case Diagrams for Library Management System

Actors of the Library Management System

 Member
 Administrator
 Librarian
 Guest

Use cases of Library Management System

 Login

 View User Details

 View Books
 View Members
 Reserve Books
 Search Books
 Issue Books
 Return Books
 Add/Remove Books
 Add/Remove Members

54
 Use Case diagram for Library Management System

Login

View User Details

View Books

Reserve Books
Member

Librarian
Search Books

Issue Books

Return Books

View Members Administrator

Guest Add/Remove
Books

Add/Remove
Members

55
 Use Case Scenarios

Use Case: Login

Introduction: To interact with the system, LMS will validate its registration with
this system. It also defines the actions a user can perform in LMS.
Actors: Administrator Librarian Member
Pre- conditions: User must have proper client installed on user terminal.
Post- conditions: System should transfer control to the user main screen to proceed
desired further actions.
Basic Flow: System show login screen Enter user Id & password
Acknowledge the entry.
Alternative Flow: user Id or password is incorrect, user will be prompted a message
regarding the error.
Transfer control back to login screen.
Special Requirements: User should acquire user Id & password before login to the system.
Relationships: The base case includes checking the database case.

56
Use Case: View User Details
Introduction: To see the details of the registered user
& the books currently borrowed from
the library.
Actors: Member

Pre- conditions: User must be logged in to the system.

Post- conditions: View user details.

View books borrowed.

Basic Flow: Enter to the view details page

View user details & books borrowed.
Print details.
Alternative Flow: User does not want to print the details,
user can ignore the step.

Special Requirements:
Relationships: The base case includes checking the
database case.
The base case includes retrieve data case.

57
Use Case: View Books
Introduction: To display the details, when a member,
guest or administrator wants to see the
details on the available books.
Actors: Administrator
guest Member

Pre- conditions: User should have the client interface.

Books should be stored in the database
& available to retrieve.
Post- conditions: User should be displayed all the
available books with the complete
details.
Basic Flow: Identify the user type – member, guest
or administrator
Display the book details
Print the details
Alternative Flow: User does not want to print the details,
user can ignore the step.

Special Requirements:
Relationships: The base case includes checking the
database case.
The base case includes retrieve data
case.

58
Use Case: Reserve Books
Introduction: User can reserve a book by inputting the
relevant details & the librarian can also
reserve a book for a member.
Actors: Librarian
Member

Pre- conditions: User should be logged into the system. User

should have correct book Id.
Books should be available to reserve.
Post- conditions: User should be reserved the book
successfully.
A message should be prompted regarding
reserving.
Database should be updated.
Basic Flow: Member type identified.
Enter book Id & member Id.
Reserve the book.
Update the system.
Alternative Flow: User Id or book Id is incorrect, user will be
prompted a message regarding the error.
Transfer control back to user screen.
The book is already issued a message will
be prompted regarding the error.

Special Requirements: User should acquire book Id to reserve a

book.

59
Relationships: The base case includes checking the
database case.
The base case includesvalidating
reservation case.
The base case includes update database
case.

60
Use Case: Search Books
Introduction: Member or guest can search for a
particular book in the book library by
book name or category.
Actors: Member
Guest

Pre- conditions: Guest & member should available the

client interface of the library.
Members should be logged into the
system.
Book should be available to search.
Post- conditions: The user should be given the results of
the search with full details.

Basic Flow: Member type identified.

Select the search type.
Check the availability. View
the search results.
Alternative Flow: The search is not found a message will be
prompted.
The data entered incorrect, a message
will be prompted.
Special Requirements:
Relationships: The base case includes checking the
database case.
The base case includes retrieving data
case

61
Use Case: Issue Books
Introduction: This use case describes the process of
issuing a certain book for a member by
the librarian.
Actors: Librarian
Member

Pre- conditions: Member should give the member Id to

the librarian.
Books should be available to issue.
Post- conditions: Member should have the issued book.
Confirmation message should
be prompted.
Database should be updated-issued.
Member details should be updated.
Basic Flow: Get the member Id & book Id.
Check the availability.
Check number of books taken.
Issue the book.
Update the system
User Id or book Id is incorrect, user will
be prompted a message regarding the
error.
The given book is already issued prompt
a message regarding that.
User already taken 3 books prompt a
message.
Special Requirements: Borrowed books should be below 3.

Relationships: The base case includes checking the

database case.
The base case includes updating database
case

62
Use Case: Return Books
Introduction: This use case describes the process of
issuing a certain book for a member by
the librarian.
Actors: Librarian
Member

Pre- conditions: Librarian should be logged into the

system.
Member should be borrowed books.
Member should give the member Id to
the librarian.
Post- conditions: Library should have the returned book.
Confirmation message should
be prompted.
Database should be updated-available.
Member details should be updated.
Basic Flow: Get the member Id & book Id.
Check the Id accuracy.
Return the book.
Update the system
User Id or book Id is incorrect, user will
be prompted a message regarding the
error.
Special Requirements:
Relationships: The base case includes checking the
database case.
The base case includes updating database
case

63
Use Case: View Members

Introduction: To display the details, when a member,

guest or administrator wants to see the
details on the registered user.

Actors: Administrator
guest Member

Pre- conditions: User should have the client interface.

Members should be stored in the
database & available to retrieve.

Post- conditions: User should be displayed all the

members with the complete details.

Basic Flow: Identify the user type – member, guest or

administrator
Display the member details
Print the details
Alternative Flow: User does not want to print the details,
user can ignore the step.

Special Requirements:
Relationships: The base case includes checking the
database case.
The base case includes retrieve data case.

64
 Activity Diagrams for Library Management System

 Activities & Transitions in the Use Cases

Case : Login

 Enter member Id & password.

 Check both fields are filled
 If not prompt a message
 Clear fields
 Else check whether input is correct or not
 If correct display the user interface
 Else prompt an error message
 Clear fields

Case : View member Details

 View details
 Check whether to print details
 If needs, then proceed to print step
 Else exit the window.

Case : View Books

 Check the user type

65
  Proceed to view books page

 Display the book details

 Check whether to print details
 If needs, proceed to print step
 Else exit the window.

Case : Reserve Books

 Check the user type.

 Enter book Id & member Id
 Check both fields are filled
 If not prompt a message
 Else check the member & book Id are correct.

 If correct, reserve the book.

 Confirm reservation.
 Else prompt error message

 Update the database.

Case : Search Books

 Check the user type

 Select the search type
 Enter search data
 If the data incorrect prompt the error message
 Else check the availability
 If available proceed to view books page
 View search results
66
  Else prompt error message

Case : Issue Books

 Get the member Id & book Id

 Check both fields are filled
 If not prompt a message
 Else check the member & book Id are correct.
 If correct, check the availability of the book.
 If not available, prompt error message.
 If available, check number of books taken by the user.
 If less than 3, proceed to “issue book” step
 Else prompt message.
 Proceed to “Update modification” step.

Case : Return Books

 Get the member Id & book Id

 Check both fields are filled
 If not prompt a message
 Else check the member & book Id are correct.
 If correct proceed to “return the book” step
 Else prompt a message regarding error
 Proceed to “Update modifications” step.

Case : View Members

 Check the user type

 Proceed to view members page

67
  Display the member details
 Check whether to print details
 If needs, proceed to print step
 Else exit the window.

Case : Add/Remove books

 Identify the user type

 Check the action
 If “add a book” step, then check the Id number availability.
 If available prompt a message.
 Else proceed to “add details” step
 If “remove book” step, then check the validity of book Id
 If not valid, prompt a message,
 Else proceed to “remove book” step.
 Proceed to “update modifications” step.

Case : Add/Remove Members

 Check the action

 If “add a user” step, check the Id number availability
 If available prompt a message.
 Else proceed to add member step
 If “remove user” step, check the validity of the Id
 If not valid, prompt message
 Else proceed to remove member step
 Proceed to “update modifications” step.

68
 Activity diagrams for the Use Cases

Activity diagram for case : Login

Login

Member Id Password

[Both not filled]

Prompt
error

[Both filled]

[Incorrect inputs]

[Correct inputs] Prompt

error

Display User
interface

69
Activity Diagram for Case : View User Details

View user Details

[Don’t Print]

70
Activity Diagram for Case : View Books

User Type

Guest Membe Administrator

r

View Books Page

Display Results

[Don’t Print]

71
Activity Diagram for Case : Reserve Books

Reserve Books

Member Id Book Id

[Both not filled]

Prompt
error

[Both filled]

[Incorrect inputs]

[Correct inputs]
Prompt
error

Reserve book

Confirm reservation

Update
Database

Activity Diagram for Case : Search Books

72
 User Type

Guest Membe
r

Search Type

By Name By Category

Search Data

73
Activity Diagram for Case : Return Books

Return Books

Member Id Book Id

[Both not filled]

Prompt
error

[Both filled]

[Incorrect inputs]

[Correct inputs]
Prompt
error

Return book

Confirm return

Update
Database

74
Activity Diagram for Case : View Members

User Type

Guest Membe Administrator

r

View Member Page

Display Results

[Don’t Print]

75
 Preferred Action

Add a User Remove a User

[Invalid Id]

[Valid Id] Error message

Error message

Add User Details Remove User

Update Modification

76
 Class Diagram for Library Management System

* * Administrator

1 1

Verifylogin()

ViewBooks()

ViewMembers()
Return() NewBook()
Issue() RemBook()
Log
NewUser()

RemUser()
RemBook() Verifylogin
1
()
*

Member
Books

Guest Verifylogin()

ViewBooks()

Return() MyDetails()
Issue() Search()

Reserve()

Search()

77
9. Software design Model

. MODULE DESCRIPTION

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

Admin Module

78
 The following module contains various facilities like student validation, teacher
registration, book addition, and report generation.

Student Module

The following module contains various facilities like student registration, student
login, online book reservation, and event addition. Any student if at any moment
forgets his password he can retrieve it from forgot password option.

Teacher Module

79
 The following module contains various facilities like teacher login, suggestions, and
event addition. Further any teacher if at any moment forgets his/her password
he/she can retrieve it from ‘forgot password’ option.

Book Module

The following module contains various facilities like add new book and search book. In the ‘add
new book’ section if any new book comes in the library then the librarian can add its specifications.
Similarly if the user wants to search for a specific book then he/she can use search book option to
do it.

80
 Book Transaction Module

The following module contains various facilities like issue book, return book and check
reservation.

Report Module

The following module contains various facilities like student report, teacher report, book
report, and transaction report.

81
10.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
 Student 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
82
 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.
3. Test for teacher login module-

 Test for teacher login form- This form is used for logg in of teacher .In this
we enter the username and password if all these are correct teacher 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.

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.

83
11. 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 in the
online notice board.
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

84
12. REFERENCS

 https://www.academia.edu/10240564/Library_Management_System_I_LIBRA
RY_MANAGEMENT_SYSTEM
 http://soft-project.blogspot.com/2009/01/library-management-system.html
 https://www.scribd.com/document/53130051/library-management-system-
final
 https://www.scribd.com/doc/13850152/Library-Management-System
 https://ieeexplore.ieee.org/document/6405716

85