Computerized Daily Operational Library

Management System for Readerware

Proposal, Technical Project

Dream Team

Mr. Wimalasiri Peiris

Version 1

01/08/2021

This proposal is submitted to the Information Technology

department in partial fulfillment for the PPA module in the
Diploma in Information Technology program.
DECLARATION
We hereby declare that the project work entitled “Computerized daily operational
library management system for Readerware”, submitted to the SLIIT Academy (Pvt.)
Ltd. a subsidiary of Sri Lanka Institute of Information Technology is a record of an
original work done by us, under the guidance of our Supervisor “Mr. Roshan
Jayawardana”. This project work is submitted in the partial fulfillment of the
requirement for the award of the Diploma in Information Technology. The Results
embodied in this report have not been submitted to any other University or Institution
for the award of any degree or diploma. Information derived from the published or
unpublished work of others has been acknowledged in the text and a list of references
is given.

Project ID:

Group Members:

Student ID Student Name Signature

IT20755942 M.K.M.Sharaf -
IT19017952 K.W.O.Y.Wiyangoda -
IT18094350 K.D.P.M.Chandrathilaka -
IT20751814 M.F.F Shahani -
IT20758530 L.M.Uzair -

Date of Submission: 01/08/2021

Name of Supervisor: Roshan Jayawardana

…………………………….…
Signature of the Supervisor

i
Contents
DECLARATION ............................................................................................................ i

LIST OF TABLES ........................................................................................................ iv

LIST OF FIGURES ...................................................................................................... iv

1 INTRODUCTION ................................................................................................. 1

1.1 BACKGROUND OF THE CLIENT/ PROJECT ........................................... 1

1.2 PROBLEM STATEMENT ............................................................................. 1

1.3 NEEDS STATEMENT ................................................................................... 2

1.4 SOLUTION AND OBJECTIVES ................................................................... 2

2 PROPOSED TECHNICAL APPROACH ............................................................. 3

2.1 DEVELOPMENT METHODOLOGY ........................................................... 3

2.2 REQUIREMENT GATHERING .................................................................... 4

2.3 ARCHITECTURE DIAGRAM ...................................................................... 5

2.3.1 AS IS SYSTEM ....................................................................................... 5

2.3.2 TO BE SYSTEM ..................................................................................... 6

2.4 FUNCTIONAL REQUIREMENTS ............................................................... 6

2.5 NON-FUNCTIONAL REQUIREMENTS ..................................................... 7

2.6 IMPLEMENTATION AND DEVELOPMENT REQUIREMENTS. ............ 8

2.7 RUNNING ENVIRONMENT REQUIREMENTS ........................................ 9

2.8 QUALITY ASSURANCE PLAN ................................................................... 9

3 EXPECTED PROJECT RESULTS ..................................................................... 10

3.1 DELIVERABLES ......................................................................................... 10

3.2 MEASURES OF SUCCESS ......................................................................... 10

4 BUDGET ............................................................................................................. 12

5 ROLES AND RESPONSIBILITIES ................................................................... 13

6 SCHEDULE ......................................................................................................... 15

7 REFERENCES .................................................................................................... 16

ii
8 APPENDICES ..................................................................................................... 17

iii
LIST OF TABLES
Table 3.2.1: Roles and responsibilities of the project. ................................................. 13

LIST OF FIGURES
Figure 2.1.1: Agile development methodology [1] ........................................................ 4
Figure 2.3.1: AS IS System............................................................................................ 5
Figure 2.3.2: TO - BE System ....................................................................................... 6

iv
1 INTRODUCTION

This is the project proposal of the “Computerized Daily Operational Library

Management System for Readerware”. Human existence has been revolutionized by
information technology, which has made life easier through a variety of uses. Many
tools, technologies, and systems have been developed and invented as a result of the
rapid changes in the use of information technology. This project is concerned with
developing Readerware Library Management system in order to make library
management more efficient and easier to handle. As the project goal, the
computerized daily operational library management system become more efficient,
user-friendly & easier to handle with its reliable system components. The proposal
will provide an idea about the functions, structure and the design of the system which
being developed by the 5 members of our team.

1.1 BACKGROUND OF THE CLIENT/ PROJECT

Readerware library was opened by Mr. Wimalasiri Peiris in the early 2000s. It is
currently located in Panadura, also it is one of the main libraries in the city with a
wide range of books collection. Readerware is a successful & famous library in the
city, librarian identified a big problem which is Readerware doesn't have a
computerized management system with the modern technological advancements.
Librarian and assistants has managed to run the library since the start of the library by
the manual management system. Now this library is famous, and its operations
became more complicated to handle. Hence, a computerized management system is a
must-have option.

1.2 PROBLEM STATEMENT

Many libraries run by a committee of volunteers. These individuals maintain track of

employees/staff members, books, and students/borrowers, as well as manually
inspecting and recording provided books. All these things have to be carried out
manually and if the library is very large, proper record-keeping will become a major
problem as manual record keeping has never been a reliable method because people
tend to forget things.
1
Other problems of the existing system are:

• Fast report generation is not possible.

• Information about issues/returns of the books is not properly maintained.
• Tracing a book is difficult.

On the borrower’s point of view, in manual system borrower can’t find a book exactly
at once as they are not ordered well. Sometimes user might be searching for a book
that is not available in the library in such situations people get annoyed or depressed.
Therefore, there should be a reliable way to manage the library system.

Many library systems run by a group of people manually. Many personnel are
involved in the process of maintaining the library, such as keeping records about the
books and students (borrowers), manually checking the books, keeping records on
provided books, and so on. All of this must be done manually, and if the library is
vast, content management might be a challenge. Keeping a large number of
maintenance employees, on the other hand, might be costly and inefficient for a
library. Manual record keeping is also unreliable due to people's proclivity for
forgetting things.

1.3 NEEDS STATEMENT

The main drawback is the current library management system is not working in a
proper way. The library management system needs to be computerized to reduce
human errors and to increase the efficiency. The main focus of this project is to lessen
human effort and encourage efficient record keeping. Our team suggested to
implement a computer-based system and convert their existing manual system to the
computer based one, which will satisfy client’s needs and increase security at the
same time.

1.4 SOLUTION AND OBJECTIVES

A library management system offers many features which make the
functioning of the library easy and efficient. This helps the librarian to search for a
book easily in the library, keep records safely and in an efficient manner, etc.

2
Some key features of a library management system are discussed further in detail
below.

▪ Tracking of book

It is critical for the library to keep track of the books that have been provided, as
well as for students to check the availability of the books. The barcode integration
in the library management system keeps track of the book's state.

▪ Records

Librarian or administrator can generate the reports from the online portal. This
helps to understand the overall functioning of the library.

▪ Issue and return details

The library management system can track all the issued books and keeps the
record of returned book and renewal details of the books. Since all the process
works on the barcode, this makes easy for the users to reserve or return book
easily.

Main objectives of the project.

• Develop a library management system to computerize all sorts of management

functions
• Provide a quality and efficient service to customers by ensuring proper time
management.
• Reduce the workload and stress handled by librarian/Admin.

2 PROPOSED TECHNICAL APPROACH

Computerized Daily Operation Library Management System for Readerware is a
system developed to maintain most of the work done currently manually such as
member details, book details, employee/staff details and supplier details management.

2.1 DEVELOPMENT METHODOLOGY

Agile methodology promotes continuous iteration of development and
testing throughout the software development life cycle of the project. Unlike in
waterfall model, in this model, both development and testing activities are done

3
concurrently. This development methodology is one of the simplest and most
effective processes to turn a vision for a business need into software solutions.
Moreover, this development methodology encourages flexible responses to change.
Since new changes in requirements are always welcome by agile methodology it was
concluded by us that Agile is the most suitable development methodology which we
can use to implement the project. Moreover, since this methodology releases a
working software frequently it will be possible to get the idea of the owner before the
completion of the project. So, if he is dissatisfied or is in the need of changing
anything it will be possible to alter that feature easily.

Figure 2:1: Agile development methodology [1]

2.2 REQUIREMENT GATHERING

A few actions have to be taken in order to get the right concept about the system and
discover the current system's flaws. Members of dream team thoroughly watched the
current manual system and interviews will be conducted with the client to obtain
requirements.

INTRERVIEWS

Some key information has been acquired from the system's end users. Obtaining input
from those who engage with the system is the most effective technique to acquire
requirements and identify system flaws. Each and every person in that library area
was interviewed by the development team.

4
Furthermore, the organization's administrators were interviewed, and their views and
proposals will be recorded. Also, our team was given questionnaires to fill out so that
their thoughts can be heard. In the appendices, you'll find a sample of the
questionnaire.

QUESTIONNAIRES

Questionnaires will be provided to some members in order to get their opinions

understood.

2.3 ARCHITECTURE DIAGRAM

2.3.1 AS IS SYSTEM
Currently the client keeps records of all the member details, staff details, book details
& supplier details as written documents.

Figure 2:2: AS IS System

5
2.3.2 TO BE SYSTEM
After all, with requirements we gathered we are willing to create the software
application to fulfill the client’s needs. The above diagram shows how will it be
implemented and handled using the computerized library management system.

Figure 2:3: TO - BE System

2.4 FUNCTIONAL REQUIREMENTS

The functional requirement specification involves the behavior of the inputs

and outputs that the system can perform. Here are some of the functional requirements
that the system which our team is going to fulfill.

 User Login (Librarian/admin)

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 their 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
access
to.
-The user must be able to logout after they finished using system.

6
 Register New Staff/Employees and Members

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

 Billing Function

 Register New Book

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.
-System must be able to not allow two books having same book id.

 Search Book

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 entered
- System must be able to show the filtered book in table view

2.5 NON-FUNCTIONAL REQUIREMENTS

 Product Requirement
 Efficiency
When a library management system will be implemented librarian and user can
easily access library as searching and book transaction will be very faster.

 Reliability
The system should accurately perform member registration, member validation,
report generation, book transaction and search

7
 Usability
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.
 Security
System should be secure against unauthorized access

 Performance
The system should have fast responses from task started to task finished.

 Maintainability
The system should be easy to maintain.

2.6 IMPLEMENTATION AND DEVELOPMENT

REQUIREMENTS.
Since this is a computerized library management system, a database will be
used to store data. It will be developed using the Agile methodology and also the
implementation will be done using Development Tools/ Languages and Libraries.

Front End: - ASP.NET 2.0 with C# ASP.NET is a web application framework

developed and marketed by Microsoft to allow programmers to build dynamic
websites, web applications and web services. It was first released in January 2002
with version 1.0 of the .NET Framework and is the successor to Microsoft’s Active
Server Pages (ASP) technology.ASP.NET is built on the Common Language Runtime
(CLR), allowing programmers to write ASP.NET code using any supported .NET
Language.

C# is a strongly typed object-oriented language designed to give the optimum blend

to simplicity, expressiveness, and performance. The .NET platform is centered around
a Common Language Runtime (similar to a JVM) and a set of libraries which can be
exploited by a wide variety of languages which are able to work together by all
compiling to an intermediate language(IL). C# and .NET are a little symbiotic: some
features of C# are those to work well with .NET, and some features of .NET are there
to work well with C# (though .NET aims to work well with many languages).

Back End: - Microsoft SQL Server 2005 Microsoft SQL Server is a relational model
database server produced by MICROSOFT. Its primary query languages are T-SQL

8
and ANSI SQL.SQL Server allows multiple clients to use the same database
concurrently. As such, it needs to control concurrent access to shared data, to ensure
integrity- when multiple clients update the same data, or clients attempt to read that is
in the process of being changed by another client.

2.7 RUNNING ENVIRONMENT REQUIREMENTS

 Processor: Intel Core processor or better performance.

 A device that is capable of running the software application using the
minimum windows 7, 8 or 10 operating system.
(Operating System: Windows Vista, Windows7,8,10, Ubuntu, Macintosh)
 Memory: 2gb RAM or more.
 Hard disk space: Minimum 3 GB for database usage (Maximize with the
usage).

2.8 QUALITY ASSURANCE PLAN

The quality assurance plan was designed with the purpose of fulfilling the client’s
demands and the project meets the quality that the project’s scope demands and
achieve the quality of the industry of industry standards.

REQUIREMENT TESTING

• This Library management system software will be used by the administrator of

the library. The software will 100 percentage fulfill the requirements of the
client. And we will add more features to the final software to be an UpToDate
software.

DESIGN TESTING

• The design of the software will be reviewed by all the developers in our team
to give to the client an almost perfectly designed software.

FUNCTIONALITY TESTING

• Defect tracking – while we develop the software, we’ll give our full effort to
identify the bugs and we build a report about the bugs and fix them.

9
 • Alpha testing – testing the project during the development and fixing the bugs
as much as possible.
• Beta testing – giving this project to trusted people and other developers to use
the management system. And ask them to report the problems and bugs they
find when they are using the software or giving the software to the actual
client to test it to find any improvements that he needs and find any final bugs
before finalizing the software and officially give them to the client.

3 EXPECTED PROJECT RESULTS

3.1 DELIVERABLES
• Research on 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.

• Algorithmic cost modeling

▪ A model based on historical cost information that relates some
software Metric to the project is used. After computerized
system is implemented less human force will be required to
maintain the library thus reducing the overall cost.

• Create quality management with efficiency

▪ Librarian is able to search record by using few clicks of mouse
and few search
▪ keywords thus saving librarian’s valuable time.

• Create database connecting each librarian and related uses.

• Include more visual effects for library management system.

• Research and create protype of the library management system with user
management and book discovery system.

3.2 MEASURES OF SUCCESS

• Collect data from face-to-face interviews.
• Develop a project plan with replacing the manual library management system
after understanding the client requirements
10
• Develop a database which store all details.
• Present Charter and get approval.
• Create an easy-to-understand user friendly environment.
• Our team developed the plan after understanding the client's requirements and
collected all the data by discussing with the client. Our team is willing to
create an UpToDate library management system with the client requirements.
• These are the tasks this management system will do to improve the growth of
the library.
 The front page will always display the state of the library.
o The available book stock, the borrowed books, best-borrowed
books, the cash flow of the library, Top members and
employees/staff of the library.

11
4 BUDGET

4:1: Total Employee Cost

Element Charges Per Estimated Total Cost (LKR)

Hour (LKR) Number of Hours

Project Manager 800.00 30 24,000.00

03 Full Stack 1800.00 120 (for all 3 72,000.00

Developers developers)

Database 650.00 35 22,750.00

Developer

Front End 600.00 45 27,000.00

Developer

Total Employee Cost 145,750.00

Table 4:2: Total Estimated Cost

Element Total Cost (LKR)

Employee Cost 145,750.00

Hardware Cost 100,000.00

Documentation Cost 2,500.00

Travel Cost 2,500.00

Telephone Cost 500.00

Total Cost 251,250.00

12
5 ROLES AND RESPONSIBILITIES
Table 5:1: Roles and responsibilities of the project.

Role Responsibility Participant(s)

Project Sponsor - -
Project Leader • Assign tasks to the M.K.M. Sharaf
team members.
• Finalize the work of
each task.
• Communicate with
client and the team
members.
Analysis • Talk to the client and M.K.M. Sharaf
gather requirements. K.W.O.Y. Wiyangoda
• Share ideas and create L.M. Uzair
solutions for each M.F.F Shahani
requirement. K.D.P.M. Chandrathilaka
Design • Design the solution for M.K.M. Sharaf
the given requirements K.W.O.Y. Wiyangoda
by the client. L.M. Uzair
• Design interfaces for M.F.F Shahani
each function. K.D.P.M. Chandrathilaka
• Design database
schema.
• Develop the back end
of the particular
function, or application
Implementation • Use a proper M.K.M. Sharaf
programming language K.W.O.Y. Wiyangoda
to develop the software L.M. Uzair
application.
• Develop interfaces.
• Create database.

13
 • Develop each function
and make them all as
fully functional
software application.
• Check capability of the
software application
with hardware.
Testing • Check all the function M.K.M. Sharaf
of the system one by M.F.F Shahani
one. K.D.P.M. Chandrathilaka
• Check the capability of
the system.

14
6 SCHEDULE

Figure 6:1: Gantt Chart

15
7 REFERENCES

https://www.researchgate.net/publication/274311464_College_Library_Management

https://www.academia.edu/33632232/LIBRARY_MANAGEMENT_SYSTEM

https://www.sciencedirect.com/topics/computer-science/library-environment

https://www.sisarcams.com/blog/library-management-system-in-educational-

management-system-erp/

https://www.inettutor.com/source-code/library-management-system-capstone-project/

https://www.academia.edu/18618910/Project_Proposal_for_a_Library_Management_

system

16
8 APPENDICES

1. Based on your complete experience with public library, how likely are
you to recommend it to your family and friends?
a. Very likely
b. Very unlikely

2. How often do you visit public libraries on average?

a. Daily
b. Weekly
c. Monthly
d. Less than once a month
e. Never

3. What drew your attention to the library's services? Choose everything

that applies.
a. Library website
b. Social Media Platform
c. Newspaper
d. Flyers
e. Other

4. Please select your age category.

a. Under 18
b. 18-24
c. 25-34
d. 35-44
e. 45-54
f. 55-64
g. Above 64

5. Please select your highest level of educational qualification

a. High school
b. Some college
c. Trade/vocational/technical
d. Associates
e. Bachelors
f. Masters
g. Professional
17
 h. Doctorate

6. What is your preferred language?

a. English
b. Tamil
c. Sinhala
d. Other

7. What is your employment status?

a. Full-time employment
b. Part-time employment
c. Unemployed
d. Self-employed
e. Homemaker
f. Student
g. Retired

8. How does the library benefit your community?

9. Is there anything else you would like to add to make the library services
better?

18