Library Management System.

TESIS" APPROVAL STATUS FORM
JUDUL: LIBRARY MANAGEMENT SYSTEM
SESI PENGAJIAN: 2004/2005
Saya

MOHD F AIRUZ ANWAR BIN MAHADI

mengaku membenarkan tesis (PSM/Saijana/Doktor Falsafah) ini disimpan di
Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat
kegunaan seperti berikut:
1. Tesis adalah hakmilik Kolej Universiti Teknikal Kebangsaan Malaysia.
2. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan
membuat salinan untuk tujuan pengajian sahaja.
3. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan
membuat salinan tesis ini sebagai bahan pertukaran antara institusi pengajian
tinggi.
4. ** Sila tandakan (/)
SULIT

(Mengandungi maklumat yang berdaijah
keselamatan atau kepentingan Malaysia seperti

yang termaktub di dalam AKTA RAHSIA
RASMI 1972)

TERHAD

(Mengandungi maklumat TERHAD yang telah
ditentukan oleh organisasilbadan di mana
penyelidikan dijalankan)

TIDAK TERHAD

(TANDAT
GAN PENULIS)
Mohd Fairuz Anwar Bin Mahadi
Alamat: L-1-8, Blok K
Taman Setapak Indah,
53300 Setapak, Kuala Lumpur.

Tarikh :


CATATAN:

2

'f-1 3/2 Oo f

. . . . . _/, ,__3-+-(_..?-tJO
_ 'f_,______
Tarikh : _ 0#

** Jika tesis ini SULIT atau TERHAD, sila lampirkan surat daripada
pihak berkuasa.
" Tesis dimaksudkan sebagai Laporan Projek Saijana Muda (PSM)

LffiRARY MANAGEMENT SYSTEM

MOHD FAIRUZ ANWAR BIN MAHADI

This report is submitted in partial fulfillment ofthe requirements for the
Bachelor oflnformation and Communication Technology (Software

Development).

FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY
KOLEJ UNIVERSITI TEKNIKAL KEBANGSAAN MALAYSIA
2005

11

ADMISSION

I admitted that this project title name of

LffiRARY MANAGEMENT SYSTEM

is written by me and is my own effort and that no part has been plagiarized without
citations.

STUDENT
: (MOHD


SUPERVISOR

faセ@

Date : 2
AR BIN MAHADI)

4ID/0 !;"
I

111

DEDICATION

Specially dedicated to
My beloved one and family members who have
encouraged, guided and inspired me during the long hours ofwriting.

lV


ACKNOWLEDGEMENTS

The main objective of this Project Sarjana Muda 2 is to gain first-hand experience of
project working as an engineering professional, including the technical application
of engineering methods. This is for students to provide themselves to faces these new
challenges and to ensure that they abide by the rules and regulation ofKUTKM and
the project criteria. This is KUTKM students will undergo the Project Sarjana Muda
2 successfully, effectively and to the best oftheir ability while maintaining the good
name and reputation ofKUTKM.
I'm would like to express my appreciation to the many people who have contributed
to the successful completion ofthis Project Sarjana Muda 2. Most especially, I would
like to thank my faculty supervisor Puan Wahidah Binti Md. Syah for supervise me
during my Project Sarjana Muda 2 and En Mohd Faizal as my panel.
Special thank you goes to Hajah Norasiken Bte Bakar the supervisor before I'm
switch to Puan Wahidah Binti Md. Syah who was trained me to do a proposal and a
lot ofvaluable experience work and give me some experience to handling some
business work project.

v


ABSTRACT

The title of this thesis is "Library Management System". The main purpose of
LMS to manage library daily operation efficiently. This system basically has four
type of module that handles daily activity for the library. The four modules is User
Manage Account module, Search record module, Book borrowing system module
and Report Generator module. The library system is focusing to solve two major
problem in case of the number of hours the library can get from the librarian and the
average time in order to process a case of the new books. By using this system, the
operation of borrowing and managing inventories is paperless. The processes of
searching for books become much easier with just a help of mouse click. This library
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. This
library system also created to ensure that the library items store properly in order to
maintain their security. Library Management System version 1.0 will be fully
operated into Sekolah Menengah Kebangsaan Ayer Keroh's library once completely
constructed.

Vl


ABSTRAK

Tesis yang bertajuk "Library Management System" ini dibangunkan untuk
menguruskan operasi harian perpustakaan dengan lebih efisien dan teratur. Sistem ini
secara asasnya mengandungi empat modul yang merangkumi operasi pengurusan
perpustakaan. Empat modul yang digambarkan ialah Pengurusan Akaun Pengguna,
Carian rekod, Sistem Pinjaman buku dan Penghasilan laporan. Pembangunan sistem
ini bertujuan untuk menyelesaikan dua permasalahan yang dihadapi oleh sistem
secara manual iaitu jangkamasa yang mampu diperuntuk oleh pustakawan dan masa
yang mencukupi untuk memproses kemasukan buku-buku baru. Dengan sistem ini,
proses pinjaman buku dan pegurusan perkakasan perpustakaan tidak bergantung
kepada kertas lagi. Sistem ini berciri mesra pengguna di mana proses memasukkan
data adalah ringkas dan mudah difahami. Sistem ini juga dibangunkan bagi tujuan
penyimpanan data yang tersusun dan terlindung. Apabila telah siap dibangunkan
sepenuhnya, sistem ini akan mula beroperasi di perpustakaan Sekolah Menengah
AyerKeroh.

Vll

TABLE OF CONTENT


TITLE

PAGE

PROJECT TITLE
ADMISSION

11

DEDICATION

111

ACKNOWLEDGEMENT

lV

ABSTRACT


v

ABSTRAK

Vl

TABLE OF CONTENT

Vll

LIST OF TABLES

X1

LIST OF FIGURES

Xlll

LIST OF ABBREVIATION


XV

CHAPTER I- INTRODUCTION
1.1

Preamble/Overview

1

1.2

Problem Statements

3

1.2.1 Problem Analysis

3

1.2.2


Methods of Solution

3

1.3

Objectives

4

1.4

Scopes

5

1.5

Contributions

5

1.6

Expected Output

6

1.7

Conclusion

7

Vlll

CHAPTER II - LITERATURE REVIEW
2.1

Introduction

8

2.2

Fact and Finding

9

2.2.1

Project Theory

10

2.2.2

Previous System Study

12

2.3

Conclusion

15

CHAPTER ill- PROJECT PLANNING AND METHODOLOGY
3.1

Introduction

16

3.2

High-Level Project Requirement

17

3.2.1

Project Facilities Requirement

17

3.2.2

Software Requirement

18

3.2.3

Hardware Requirement

19

System Development Approach

20

3.3.1 Waterfall Model

22

3.3.2

25

3.3

3.4

Justification of Methodology Selection

26

Conclusion

CHAPTER IV - ANALYSIS
4.1

Introduction

27

4.2

Analysis of Current System

28

4.2.1

Business Process

28

4.2.2

Problem Analysis

29

4.2.3

Problem Statements

29

4.3

Analysis ofTo Be System

30

4. 3.1

Functional Requirement

31

4.3.1.1

System Requirement Specification

31

4.3.1.1.1

User Interface

32

4.3.1.1.2

Data Entry

33

4.3.1.1.3

Report Generator

34

4.3.1.1.4

Performance Requirements

35

4.3.1.1.5

Security Requirements

35

lX

4.3.1.1.6
4.3.1 .2
4.3.2

4.4

Reliability

Data Flow Diagram Analysis (Level 0)

35
36

Technical Requirement

42

4.3.2.1

Software Requirements

42

4.3.2.2

Hardware Requirements

44

4.3 .2.3

Implementation Requirements

46

Conclusion

47

CHAPTER V- DESIGN
5. 1

Introduction

48

5.2

Preliminary/High-Level Design

49

5.2.1 Raw Input/Data

50

5.2.2

System Architecture

53

5.2.3

User Interface Design

56

5.2.4

Database Design

58

5.3

5.4

Detailed Design

60

5.3.1

Software Specification

61

5.3.2

Physical Database Design

78

Conclusion

79

CHAPTER VI- IMPLEMENTATION
6. 1

Introduction

80

6.2

Software Development Environment Setup

81

6.3

Software And Hardware Configuration Management

87

6.4

Implementation Status

88

6.5

Conclusion

90

CHAPTER VII - TESTING
7.1

Introduction

91

7.2

Test Plan

92

7.2.1

Test Organization

92

7.2.2

Test Environment

93

X

7.2.3 Test Schedule

93

Test Strategy

94

7.3. 1 Tests Cases

95

Test Design

96

7.4.1 Test Description

96

7.4.2 Test Data

101

7.5

Test Case Results

103

7.6

Conclusion

104

7.3
7.4

CHAPTER VIII- PROJECT CONCLUSION

8.1

Observation on Weaknesses and Strengths

105

8.1.1

105

Strengths

8.1.2 Weaknesses

106

8.2

Propositions for Improvement

106

8.3

Conclusion

107

BffiLIOGRAPHY

108

ATIACHMENTS

109

APPENDIX A- FIGURES

110

APPENDIX B - TABLES

115

APPENDIX C- LMS USER GUIDE

120

APPENDIX D- GANTT CHART

128

Xl

LIST OF TABLES

NO.

DESCRIPTION

PAGE

Table 3-1

Project Facility Specifications

17

Table 3-2

Software Requirement and Function

18

Table 3-3

Language Used and Function

18

Table 3-4

Complete of Personal Computer

19

Table 3-5

Other Computer Accessories and Functions

19

Table 4-1

Description of Data Flow Diagram Level 0

37

Table 4-2

Library User Account Manage System Diagram

38

Analysis
Table 4-3

Search book record Diagram Analysis

39

Table 4-4

Book borrowing system Diagram Analysis

40

Table 4-5

Report Generator

41

Table 4-6

Software Requirement and Description

42

Table 4-7

Language Requirement and Description

43

Table 4-8

Requirement for Personal Computer

44

Table 4-9

Other Accessories

45

Table 4-10

Implementation Requirement Specification

46

Table 5-l

Observation Specification

50

Table 5-2

Research Specification

50

Table 5-3

Login System Specification

51

Table 5-4

Search record system Specification

51

Table 5-5

Book Borrowing System Specifications

52

Table 5-6

Report Generator Specification

52

Table B-1

Data input design

116

Table B-2

Output design

117

Table B-3

Description of Relationship 1

118

Table B-4

Description of Relationship 2

118

Table B-5

Description of Relationship 3

118

Xll

Table B-6

Description of Relationship 4

119

Table B-7

Description of Relationship 5

119

Table B-8

Description of Relationship 6

119

Table 5-7

Description of Data Flow Diagram Level 0

68

Table 6-1

Activity Status

88

Table 6-2

Module Implementation Status

89

Table 7-1

Test Organization

92

Table 7-2

Test Schedule Specification

94

Table 7-3

Units Testing

96

Table 7-4

Integration Testing

97

Table 7-5

System Testing - Linkage Between Forms

98

Table 7-6

System Testing- Linkage Between Forms

99

Table 7-7

System performance testing

100

Table 7-8

Login Test Data

101

Table 7-9

Change Password

101

Table 7-10

Input Members Record

102

Table 7-11

Input Book Record

102

Table 7-12

Test Summary Report

103

Xlll

LIST OF FIGURES

NO.

DESCRIPTION

PAGE

Figure 3-1

Waterfall Model

22

Figure 3-2

Requirement Engineering Process

23

Figure 3-3

Typical Phase Design

24

Figure 4-1

Data Flow Diagram Level 0

36

Figure 5-l

Package Diagram for Architecture

54

Figure 5-2

System navigation

57

Figure A-1

ERD for Library Management System

111

Figure A-2

Relationship 1 Diagram

112

Figure A-3

Relationship 2 Diagram

112

Figure A-4

Relationship 3 Diagram

113

Figure A-5

Relationship 4 Diagram

113

Figure A-6

Relationship 5 Diagram

114

Figure A-7

Relationship 6 Diagram

114

Figure 5-3

Flowchart Diagram for Login Function

62

Figure 5-4

Flowchart Diagram for Search Book Record System

63

Figure 5-5

Flowchart Diagram for Book Borrowing System

64

Figure 5-6

Flowchart Diagram for Report Generator

65

Figure 5-7

Context Diagram for Library Management System

66

Figure 5-8

DFD Level 0 for Library Management System

67

Figure 5-9

DFD Level 1.0 -Login Process for Library User

69

Account Manage System
Figure 5-10

DFD Level 2.0 - Login Process for Library User

70

Account Manage System
Figure 5-11

DFD Level 2.0 - Add new user

71

Figure 5-12

DFD Level 2.0 - Edit user profile

72

Figure 5-13

DFD Level 1.0 - Search record module

73

Figure 5-14

DFD Level2.0 - Search record module

74

XIV

Figure 5-15

DFD Level 2.0 - Search Borrowed record

75

Figure 5-16

DFD Level 1.0 - Book borrowing module

75

Figure 5-17

DFD Level 2.0 - Book borrowing module

76

Figure 5-18

DFD Level 1.0 - Report generator module

77

Figure 5-19

DFD Level 2.0 - Report generator module

78

Figure 6-1

Software Development Environment Setup

81

Architecture
Figure 6-2

Select SETUP.exe from the installation folder

84

Figure 6-3

Click OK to proceed

85

Figure 6-4

Begin Installation

85

Figure 6-5

Defme System Name

86

Figure 6-6

Installation in Progress

86

Figure 6-7

Architecture layout of LMS

87

XV

LIST OF ABBREVIATIONS

KUTKM

Kolej Universiti Teknikal Kebangsaan Malaysia

FTMK

Faculty of Information Communication Technology

PSM

Projek Srujana Muda

CD-ROM

Compact Disk-Read Only Memory

DFD

Data Flow Diagram

ERD

Entity Relationship Diagram

ICT

Information Communication Technology

AUT

Application Under Test

GUI

Graphic User Interface

JAD

Joint Application Development

RAD

Rapid Application Development

LMS

Library Management System

SDLC

System Development Life Cycle

CPU

Centre Processor Unit

DBMS

Database Management System

ODBMS

Object Database Management System

SQL

Structured Query Language

CHAPTER I

INTRODUCTION

1.1

Preamble/Overview

The Library management system version 1.0 (LMS) is design to provide one
systematic system for librarians to manage booklist, inventory and borrowing process.
Basically the system will be created using the Visual Basic and the system database
will be build by Microsoft Access. The system is build for Sekolah Menengah
Kebangsaan Ayer Keroh's library.
The Library management system version 1.0 provides two types of application
method for different user, regular user and administrator user. For regular user, they
only can access the booklist function and book searching function. Only administrator
is allowed to access to the restricted function such as create new user account.
The Library management system will store all the books and members
information that consist book number, book title, author name and racks to the system
database. The system also provides search function to help students fmd 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 create new LMS user account and
decide the number of days allowed for the borrowed books. User needs to enter
correct password and user id before user can access this function. From here, user can
add, delete or update the book and borrower database.

2
Since the amount of students/borrowers and books is increasing, it is necessary
to prepare a space to store them. After a long time, the record book will be stockpiled.
It needs well organized and it is hard to find the record in short time because they

need to find it one by one. This will cost extra time and is not efficient at all.
Based on present method, librarian needs to record the entire booklist and
borrower list manually using a logbook. This manual system is currently misspend
time and might cause mistakes while recording process. The library's inventory such
as books is always changes within certain time because of additional or lost of those
inventories. With the present manually system, the monitoring process for this
inventory become complicated. For example, if one over hundreds of books is lost,
they need to check one by one of novel name through list of hundreds from logbook
to search for the lost book data.
With the Library Management System Version 1.0, librarians are able to
monitor and manage library's inventory much easier and more efficient. There is large
amount of database to support the future needs and will give added advantages to the
all library operations.

3

1.2

Problem Statement

Basically, problem statement often have two elements which is the problem
itself, stated clearly and with enough contextual detail to establish why it is important
and the method of solving the problem, often stated as a claim or a working thesis.

1.2.1

Problem Analysis

There are some problems in previous system operation, which can be state in
the documentation. There are: i)

The number of hours the library can get from the librarian:
The librarian have a limited hours to complete manage all the library
jobs such as take care of the arrangement and maintenance oflibrary items.

ii)

The average time in order to process a case of the new books:
The librarian need to misspend time in proper to manage of the book
items along with the details like the title of the book, the publisher's and
author's name, edition and whether that book is available for issue purpose.

1.2.2

Methods of Solutions

There are several types of solution for the problem statement above after the
problems have been analysed in previous phase of development. All the
specifications have referred to the problem statement below: i)

The number of hours the library can get from the volunteers/librarian
Major categories are created to define specified task is conducted by
chosen volunteers and the related items are kept into them so that the required
item can be made available any time with ease. Plus quick processing of
library monitoring status such as producing report for each activities and task.

4

ii)

The average time in order to process a case of the new books
With the help of reports like the stock-in-hand of the items existing in
the library and subscription details report, the operation of process a case of
new books become faster and easier.

1.3

Objectives

The main objectives of Library Management System are:
i)

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

ii)

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

iii)

Give an opportunity to librarians to reduce the time spends and mistake that
always happens during manual method.

iv)

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

v)

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

vi)

To maintain the suppliers and publishers details so that the order can be placed
on time.

vii)

To maintain the record of the subscribed items.

5

1.4

Project Scopes
It is necessary to defme a scope when built up a project and following is the

scope of Library Management System version 1.0.
This system is build for Sekolah Menengah Kebangsaan Ayer Keroh's library,
so the system will store information of all books and records of borrower. However
only the librarians who have specified access such administrator can handle
administrative functions of this library system. This can avoid unauthorized user to
enter the restricted area of this system especially system databases.
Basically this system got four major functions; there is Library User Account
Manage System, Search Record, Book Borrowing System and Report Generator.
From all of four functions mentioned, The Library User Account Manage System can
only be access by LMS administrator.
Library Management System version 1.0 will be fully operated into Sekolah
Menengah Kebangsaan Ayer Keroh's library once completely constructed. The
interface and database will only design in single language, which is English.

1.5

Contributions
Using this system, the operation of borrowing and managing inventories is

paperless. It means we do not need to use any paper for the system and logbook is no
longer will be library database. It will reduce the usage of papers.
It is more efficient and makes the process of searching for books become

easier. These because what they need to do is just insert information of book such
book' s id and system will find and views the book item such author, category and
publisher. The system will also view rack that the book are situated.
The process of keeping borrower information and books inventory become
more sophisticated. Each operation for both functions is handle by the system to

6
define the period of time for borrowing, penalty calculation for late return book and
total of books that still remain every week for inventory check.
The system is easy to use. User just need to insert input and click some button
to get output for all functions provided by Library Management System Version 1.0.
The interface design of the system is attractive. 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. The time of loading is fast. So, the users do
not need waiting for a long time to get result from the system.

1.6

Expected Output

Based on the expected end-result for the Library Management System, below
is the summary of expected output for the module exist in Library Management
System:i)

Library User Account Manage System
a) The user with valid user name and password can access the Library
Management System.
b) The system displays the user account information including user id and
password.
c) The system shall give the response for invalid usemame and password.
d) The system allows only administrator to choice actions including removing,
changing and adding user account and account information.

ii)

Search Record
a) The system allows the user typing in search criteria including book id as a key
word for the search criteria.
b) The system display books item such title; author and publisher that are match
the search criteria.
c) The system shall give the response for invalid search criteria.

7
iii)

Book Borrowing System
a) When check out the books, when required by librarians, the system show the
information about books which is borrowed before and not returned yet
including book id and member id.
b) The system allows the user to specify a checking out book using its Id.
c) The system allows the user to specify a checking in book using its Id.
d) The system allows the user to specify that a penalty is paid after book is
consider check out (return).
e) The system commits the check in and check out data to the database as soon as
the data is entered.

iv)

Report Generator
a) The system have a report feature that will allow the user to generate a report
showing the information of all the sign out book in a time period which is the
search criteria input by user. The information includes the number of books,
the time period and the information is grouped by book categories.
b) The system has a report feature that will allow the user to generate a report
showing the information about all the users who have overdue books and
penalty.
c) The system shall generate those reports to the display, a file or a printer that is
linked to the system.

1. 7

Conclusion

As a conclusion, this chapter describes the feasibility study and summary of
analysis about Library Management System. It is including the objectives of project
implementation, scopes of project, the aspect of research, the project contributions
and the expected output. The methodologies of Library Management System to
gathering the collection are from a series of observation and researching. The
observation process enables the identification of safety issues and systemic
deficiencies outside of the formal audit process. The research method can be analysed
from journals, books, experts and Internet resources.

CHAPTER II

LITERATURE REVIEW

2.1

Introduction

The literature study in previous system could give more references in system
development process. All the advantages in the previous system can be implement
during the system development. The characteristic of the previous system such as
interface, module flow, process and security level should be improve and enhance
from the previous system.
The library management feasibility study encompasses all of the research
activities that will discuss in this chapter. In this chapter, there are discussions about
the information that related from library management concepts includes fact-finding,
project theory, previous system study and result from literature study.
Library Management System Version 1.0 is the system that been created and
modified from the problem that occur on current/manual system. Specific researches
need to be form to expel all the weaknesses and strengths of current library systems.
There are four types of source on how to get the evidence for the research pwpose: Systems are created to solve problems. The former case study can think of the
systems approach way of dealing with a problem. The purpose of former case study
implementation is: i)

To understand and defme the different phases of system developments life
cycle

ii)

iii)

To know and studied the components of system analysis
To know the components of system designing