1.

0 Introduction

Now, in our society all over the world technology is the most important advancement, a necessity
in bringing about progress as we move along in this computerized world. These changes in effect make
man’s life easier and more convenient. The relationship between the library and computer is constantly
changing that the use of computer contributes to the way man learns and communicates. It is easy in
this world to strive for changes and since library is different from any firm and institution, considering to
perform a given task will be efficient.

Librarians have the responsibility not only to know about the ways in which libraries will be managed
using techniques of computerized, but also to be aware of the change that computerized can bring to
the library services in the near future. Traditionally, library system are implemented manually. Forms
are given to librarian and they fll them of using pens. Afterwards, the school administrators process
them manually and compiled on large bulky file cabinet. Indeed, the manual library system is very
costly, time consuming and hard task.

1.1 Background of the Study

(History of school blah blah.... )

The Process of borrowing books is that the students will sign in the log form then search for
the book they want to borrow. The students will present the library card and the librarian will give a
request form to fill up and sign the book card and the library card of the students.

The library provides a card catalog for the student to use it for searching the books they need.
But most of them are having hard time and sometimes they don’t know how to use the card catalog.
The result is they’re going to ask the librarian about the book, which might disturb the librarian from
more important work for that day. The transaction done in (name of school) library includes borrowing
and returning of books, the current transaction require a lot of things such as a borrower’s card, book
cards and log books.
It is also done manually by writing dates, student name, books they borrowed and other
relevant data. Sometimes mistakes occur on their manual transaction. Although the current system
provides reports will take a lot of time. For example, in making an inventory report for books, it takes a
lot of time to check for each book cards to see which book is still out in the circulation. Also, they refer
to logbook to confirm for the transaction.

1.2 Statement of Objectives

1.2.1 General Objective

 To Design, Develop and implement a Computerized library system for (name of

school)
 To Develop computerized library system that will store the students records such
as students basic information, books record, and list of borrowers returned books,
borrowed books.
[Which one ?]

1.2.2 Specific Objectives

 To Develop a module that will make inquiry of availability of books becomes faster.
 To Develop a module that will improve the transaction of borrowing and returning
of books
 To Develop a module that will lesser time in making important library related
reports.
 To print out reports immediately.
 1.3 Significance of the Study
The study can help lessen problems that are presently encountered by the said school.

For the school ( and The people behind the management of the library system particularly
the librarian), this would help in minimizing the loss of the book records being encountered in the
existing library. Creating reports would be easier for the librarian. For the students and teachers,
this would save time in verifying whether the book is available or not. They can easily find the books
that they are looking for without going through the traditional way of searching a library material.
Convenience is more visible for it is not time-consuming, resulting to a number of accomplished
works. The computerized library system would improve the monitoring capacities of those who
maintain the library which is the librarian. It would be easier to determine whether a particular book
is on shelf or not. In addition, they can easily identify when the borrowed material will be returned
and if a borrower has failed to return the book on its due date. Furthermore, the librarian would be
much guided when it comes to recognizing new inventory books, letting them arrange it promptly
and accordingly.

For The Researchers to enhance and likewise develop their skills and talents in analyzing
system needs designing a computerized system and as a programmer developing a software.

1.4 Scope and Limitations of the Study

Scope

The proposed computerized Library system has a scope of following features such as:
The Transaction
This will be used in all book transactions, The transaction includes Borrowing and returning
of books. This form can view all the list of books borrowed and returned by the Students or Faculty.
The system can add, edit, delete, and update, some of the features in the system are Generating
reports. The system provides printable copies of all data and records that the library processes in
their system. The Generation of reports includes Borrower’s report. This report shows the list of
students or Faculty who borrows the books.
The generation of reports also includes book reports. This Report also includes book
reports. This report shows the Master list of books, Damaged books, Reading books, and
reference. The Generation of reports also includes Penalty reports. This Report shows the penalty
of students.

Limitation

The computerized Library system does not provide book reservation. The Library does not
accept reservation of books from borrowers for there are possibilities that the borrowers may not
borrow the book.

2.0 Methodology of the Study

Model Faculty user Interface system – lets the administrator to modify book information and logs
borrowed and returned books directly from Database. By this they can easily monitor books that are going
out and going in.

Student User Interface??

3.0 Data Gathering Procedures and Output

4.0 The Existing System
4.1 Company Background
4.2 Description of the System
4.3 Data Flow Diagram
 4.4 Data Dictionary
4.5 Problem Areas
5.0 The Proposed System
5.1 System Overview
5.2 Process Specification
5.2.1 Data Flow Diagram
5.2.2 Data Dictionary
5.3 Data Specifications
5.3.1 Entity Relationship Diagram
5.3.2 Tables/ Files Layout
5.4 Screen Layout/ Specifications
5.5 Report/ Form Specifications
5.6 Program/ Module Specifications
6.0 System Coding (Prototype)
6.1 Programming Language
6.2 Special Purpose Language Tools
7.0 System Testing Plan
7.1 Testing Stages
7.2 Testing Schedules
8.0 System Implementation Plan
8.1 Resource Requirements
8.1.1 Hardware Requirements
8.1.2 Software Requirements
8.1.3 Human Resource Requirements
8.2 Implementation Plan
8.2.1 Site Preparation
8.2.2 Personnel Training
8.2.3 System Conversion
8.2.4 Data Conversion
8.2.5 Implementation Schedule
9.0 System Maintenance Plan

Appendices
Bibliography
Resource Persons
Curriculum Vitae