Project Report

On
“Online Library Management System”

GAM-IT-P-2018-0007 W. P. Chathuri Imasha

 Online Library Management System

Contents

Software Development Life Cycle (SDLC)........................................................................................ 3

Introduction............................................................................................................................................... 4
Situation ................................................................................................................................................. 4
Solution................................................................................................................................................... 4
Feasibility Study....................................................................................................................................... 5
1. Technical feasibility: ................................................................................................................... 5
2. Operational feasibility: ............................................................................................................... 5
3. Economic feasibility: .................................................................................................................. 5
4. Social feasibility ........................................................................................................................... 5
System Analysis ....................................................................................................................................... 6
1. System Objective: ....................................................................................................................... 7
2. System Boundary: ....................................................................................................................... 7
3. System Importance:.................................................................................................................... 7
4. Nature of the System: ................................................................................................................. 7
5. Role of the System as an Interface: ....................................................................................... 7
6. User Participation: ...................................................................................................................... 7
7. Required Resources:.................................................................................................................. 7
System Design .......................................................................................................................................... 8
Software Requirement Specification ............................................................................................ 8
Hardware Requirement Specification........................................................................................... 9
Software Model Followed .................................................................................................................... 10
Linear Sequential Modal .................................................................................................................. 10
Modules .................................................................................................................................................... 12
Testing Procedure ................................................................................................................................ 14
Implementation and Maintenance .................................................................................................... 15

2
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Software Development Life Cycle (SDLC)

3
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Introduction

Situation
Gone are the days when the librarian had to have his library log updated manually with
help of his assistants. The tedious process of updating the log, manually, after every
transaction is dying out in most of the libraries. This is with the advent of computerization
in this field too.
Then came spreadsheets which used to run for pages. Even then it was the duty of the
librarian/administrator to enter all details manually in the spreadsheet. She/he had to
keep track of all items in the library and update the corresponding records. The person
borrowing the book had to get his verification card and get it updated every time he
borrows/returns an item from/to library. Even this work of verifying the person and
updating the card falls on the librarian or his assistant. Every now and then the librarian
has to keep track of all the books and other items by checking the stocks.
Solution
This solution is developed using .NET technology which improves the accuracy of the
information by leaps and bounds. This solution helps the administrator accomplish his
tasks at ease. This solution is an online library management system which lets users sign-
up to the library initially and then sign-in every time they want to find some item in the
library. The user can also maintain and edit his profile details.
It also lets administrators manage the library from their desktop. They can monitor any
item, its stock and other related information. A user can sign-in and search for items,
borrow or reserve items if they are present in the library. If not, user can request the
librarian/administrator to get the book by furnishing all the details. As soon as a user
reserves a book the library database gets updated automatically. This improves accuracy
and leaves no user fooled about the status of availability of an item. All details of the user
are stored in the database which eases pressure on the administrator about defaulters.
Defaulters can be blocked/removed from the library, by the administrator.
The user need not visit the library every time to find an item; instead he/she can search
items from his/her own PC/laptop. Reports can also be generated for individual items or
for number of defaulters and the number of transactions for an item or by a user. They
can also be generated in graphical form.
An advantage of this solution is that a web browser which supports .net framework is
enough to view the user interface. This interface can be seen in any such system and hence
makes it portable too.

4
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Feasibility Study

Feasibility is a determination of whether or not a project is worth doing. Feasibility Study

is performed for determining the feasibility of a project. The content and
recommendations of such a study will be used as a sound basis for deciding to proceed,
postpone, or cancel the project.
In the conduct of feasibility study, we will usually consider following inter-related type of
feasibility. They are:

1. Technical feasibility:
We concern here with specifying Equipment and software that will satisfy the user
requirement. It will run on any platform (machine), since the C# is considered platform
independent. It will run with minimum system requirements and with minimum system
resources acquired during run. It will need a web server, to which it gets from the internet,
at run time. Expandability will be maintained in the new system. New modules can be
added later on the application, if required in the future.

2. Operational feasibility:
The system will be easy to use as user interface is GUI based. The system is easy to use so
no any special skills will be required to use the system. New user will find it easy to use.
So the project will be operationally feasible.

3. Economic feasibility:
The procedure is to determine the benefit and savings that are expected from the project
and compare them with the cost. As internet is the cheapest way of communication, we
can perform communication using web. The cost is just the cost of using the internet
based on the channel allocation. So the project will be economically feasible.

4. Social feasibility
The project will be socially feasible as today’s user want quick services in everywhere.
With the help of web based shopping we can make business with others instantaneously
in just seconds, in a large geographical area.

5
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

System Analysis
During the course of fulfilling of the system development, many different situations
arise that must be understood to facilitate the decisions on the approaches, methods,
strategies, technologies and development.

The system to be developed may be either simple or complex, where the complex
systems can be a collection of the other small systems. Such complex integrated system
is developed requiring the operation on the heterogeneous platform of hardware and
software.

It is quite possible that the system developed may require maintenance to have some
additions and modifications. This system may be old in terms of technology, design and
lacks flexibility requiring a higher maintenance cost. The system analysis can be defines
as:

“System analysis is an important activity that takes place when new information systems
are being built or existing ones are changed”.

There are some system elements, given below, which require the system analysis to be
performed:

1. System Objective
2. System Boundary

3. System Importance
4. Nature of the System

5. Role of the System as an Interface

6. User Participation

7. Resources

6
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

1. System Objective:

It’s defining the centralized, single objective of the system. Such objective must be
achieved accurately.

2. System Boundary:

It is necessary to establish the system boundaries that define the scope of the system. It
also helps to identify the inputs and outputs of the system.

3. System Importance:

It is required to see the system importance and its place as the organizational aspects.

4. Nature of the System:

It is to decide whether this particular system will open or closed. On the basis of the
nature, the designer will make the architecture of the system.

5. Role of the System as an Interface:

Sometimes it happens that the system we are going to build plays the role of an interface
among the various other systems. Working as an interface is a very critical task, because
it makes the connectivity among the system.

6. User Participation:

Basically, any new system is to build requires the complete user participation because the
user has to tell its requirements and can see the development of the project.

7. Required Resources:

Resources may be in any of the form like hardware, people and software etc. so, such
resources requirement should be mentioned in the initial phase

7
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

System Design

Software Requirement Specification

Borrowing books, returning books or viewing the available at the Library of the local
University is currently done manually where in the student has to go to the library and
check the available book at the library. Student check the list of books available and
borrow the book if the book is borrow book otherwise it is waste for the student to come
to the library to come to the check for the book if the Student doesn’t get the book.

We have decided to investigate the use of an online library management System. This
system would be used by the members who may be Student or professor of the university
to check the availability of the books or borrow the books and by the librarian to update
the library management system.

The proper of this document is to analyze an elaborate on the high level needs and future
of the online library management system. It focuses on the capabilities and facilities
provide by the library.

Technologies Used
 C#

 ASP.NET 2.0

 Visual Web Developer Express Edition

 SQL Server 2005 Express edition

 Windows XP Professional Edition

All the above listed softwares are either freeware or trial version software. Certain
features which these lacks may be successfully executed using a licensed version
of the same set of softwares. Hence this affects the budget of a solution developer.

8
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Hardware Requirement Specification

Hardware is the back bone of any up and running software. It became more so important
in case of the applications are on a network or the size of the database and system is very
large. Every system demands good hardware to support its functions.

The hardware proposed has been selected keeping in mind the critically of the data to be
maintained and the desired speed of information retrieval. Specification are also be
influenced by the requirement of MIS required at levels and possible queries to be fired
on the machine. The hardware has been sized keeping in view the present growth trend
in terms of increase of workloads and would be sufficient, tentatively, for a period of ten
years.

For the Client Computer:

 CPU – Intel Core 2 Duo E7300

 RAM – 2 GB
 Hard disk – 120 GB
 Operating System – Windows XP with
 Service Pack 3 (CHT)

For The Server:

 CPU – Opteron / Xeon Server CPU
(Opteron 2356/Xeon5300)
 RAM – 4 GB
 Hard disk – 30GB(for RAID 5)
 Operating System – Windows Server 2003 Standard
 LAN – at least 100Mbps

9
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Software Model Followed

Linear Sequential Modal

The waterfall model suggests a systematic approach to software development.

That begins at the system level and progress through analysis, design, coding, testing.
The linear sequential model is design for straight-line development. Waterfall approach
assumes that a complete system will be delivered after the linear sequence is completed.
The evolutionary models are iterative. They are characterized in a manner that enables
software engineers to develop increasingly more complete versions of the software.

For most large systems, there is a need to use different approaches for different parts of
the system, so a hybrid model should be used. There is also a need to support process
iteration, where specification is developed in conjunction with the software.

In spiral model or incremental approach, there is not a complete system specification until
the final increment is specified. This requires a new form of contract which large customers
such as government agencies may find difficult to accommodate.

For small systems or for medium-sized system with a fairly short lifetime, the evolutionary
or spiral model is the best approach. However for large longtime system the problem of
evolutionary development become particularly acute. For such system a mixed process
that incorporates the best features of waterfall model and evolutionary models must be
used.

The principal stages of the model are explained as follows:

Requirement analysis and definition: The system services and goals are established by
consultation with system users.

Design Face: It establishes overall system architecture, including data structure,

algorithms and user interface.

Coding: the design must be converted into machine readable form. The code generation
step performs this task.

Testing: Once the code has been generated program testing begins. Testing focuses on
the logical internals of the software, ensuring that all the statements have been tested,
and on functional externals, that is conducting test on uncovered errors.

10
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Requirement
Definition

System and Software

Design

Coding

Testing

Linear Sequential Model

11
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Modules

A module is a logically separable part of a program. It is a program unit that is discrete

and identifiable with respect to compiling and loading. Partitioning a system in two
modules is useful only if the modules are solvable and modifiable. Separately a system is
considered modular if it consists of discrete components such that each component
supports a well-defined abstraction, and if a change to one component has a minimal
impact on other component. Brief description of each of the 3 modules is given below.

a. Administrator Module
b. Librarian Module
c. Student’s Module

Administrator Module:

In this module, all pages which are related to the Administrator means related to security
and maintenance of the portal and department are placed here.

 Creating Librarian Account.

 Modifying, Updating and deleting Librarian Accounts.
 Uploading and Unloading the Notice Board Material.
 Viewing & Updating Library Status.
 Viewing & Updating Students Details and Faculty Details.

Librarian Module:

In this module, all pages which are related to Librarian are placed here. Viewing their
Information and Account.

Adding - Books
News papers
New Student

Viewing - Books
Students Status
Book Status

Issuing - Books
Reference Books
12
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Updating - Books
News papers
New Student

Deleting - Books
News papers
New Student

Student Module:

In this module, all pages which are related to Librarian are placed here. Viewing their
Information and Account.

 Registration
 Search for a book
 View profile
 View Library card Status

13
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Testing Procedure

After completing every part of the software there is the need for software testing to prove
that the module are functioning properly or not and it fulfills all requirement of the user.
For this, the programmer use various type of software testing techniques and strategies.
Software can be tested in one of two ways:

 Black - Box Testing : Knowing the specified function that a product has been
designed to perform, tests can be conducted that demonstrate each function is
fully operational while at the same time searching for errors in each function.

 White - Box Testing : Knowing the internal working of product, tests can be
conducted to ensure that “all gears mesh”, that is internal operations are
performed according to specification and internal component have been
adequately exercised.

14
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Implementation and Maintenance

System Requirements to Run the Software:

To run this project, user must have following tools and environments

Software Requirements:

 Web Designing and Maintaining

 Web browser
 Computer-Based Training
 Multimedia Applications
 Data base server

Hardware Requirements:

 Color monitor for good resolution

 Internet connectivity facility
 Microsoft compatible mouse
 Microsoft compatible keyboard

15
GAM-IT-P-2018-0007 W. P. Chathuri Imasha
 Online Library Management System

Thank You

16
GAM-IT-P-2018-0007 W. P. Chathuri Imasha