TEXTBOOK LOAN MANAGEMENT SYSTEM USING SIMPLE RULE …

i

TEXTBOOK LOAN MANAGEMENT SYSTEM USING SIMPLE RULE

BASED DECISION TREE

NUR FARAH AZLIN BINTI TUSRI

BACHELOR OF COMPUTER SCIENCE

(SOFFTWARE DEVELOPMENT) WITH HONOURS

UNIVERSITI SULTAN ZAINAL ABIDIN

2019

`````

`````

`````

ii

DECLARATION

I hereby declare that the report is based on my original work except for quotations and

citations, which have been duly acknowledged. I also declare that is has not been

previously or concurrently submitted for any other degree at Universiti Sultan Zainal

Abidin or other institutions.

Name: Nur Farah Azlin Binti Tusri

Date:

iii

CONFIRMATION

This is to confirm that:

This research conducted and writing of this report was under my supervision.

Name: Dr Wan Suryani binti Wan Awang

Date:

iv

DEDICATION

In the name of Allah of the most Gracious and the most Merciful

Firstly, Alhamdulillah, all thanks for Allah for giving me the chance, strength and

ability to complete this final year project in time. Without His permission, I would not

able to complete and handle this project properly. I would like to express my gratitude

to those who have helped me whether directly or indirectly. Special thanks to my

dedicated supervisor, Dr Wan Suryani binti Wan Awang for her guidance, ideas,

comments and encouragement throughout the whole process in completing this final

year project in time that had led me to produce project with good quality. My personal

gratitude goes to my parents and all my family member for all of the moral supports

and understanding that they gave to me. Finally, I would like to this chance and

opportunity to thanks my friends who always willing to help and support me through

this journey to done this project. May Allah S.W.T repays them with great reward for

their generosity.

v

ABSTRACT

This final year project was conducted at Sekolah Menengah Kebangsaan

(SMK) Tembila, Besut, Terengganu. The aim of this study is to computerized

Textbook Loan Management System (TLMS) or better known as “Skim Pinjaman

Buku Teks” (SPBT) from existing manual system. The main problems of manual

system as pointed out by the teacher in charge include the inefficiency of recording

the students’ data manually and keeping track the lost textbooks. In addition, the

teacher must counter check the quantity of the textbooks received from suppliers with

the quantity of textbooks distributed to the students. Sometimes, a few textbooks are

damaged or missing, which is difficult for a teacher to find who is the borrower. This

system can also help a staff to record all the students and textbook information more

efficiently. It can reduce their burden to check the quantity of the textbook if it still

available, damaged or missing. It can create a systematic and efficient SPBT

management based on ICT and establish a system that can assist in the monitoring and

coordination of SPBT management. In realizing this problem, simple rule-based

decision tree is proposed in this final year project.

vi

ABSTRAK

Projek tahun akhir ini telah dijalankan di Sekolah Menengah Kebangsaan

(SMK) Tembila, Besut, Terengganu. Tujuan kajian ini adalah untuk Sistem

Pengurusan Pinjaman Buku Teks (TLMS) berkomputer atau lebih dikenali sebagai

"Skim Pinjaman Buku Teks" (SPBT) daripada sistem manual sedia yang ada.

Masalah utama sistem manual seperti yang ditunjukkan oleh guru yang

bertanggungjawab termasuk ketidakcekapan untuk merekodkan data pelajar secara

manual dan menjejaki buku teks yang hilang. Di samping itu, guru mesti mengecilkan

kuantiti buku teks yang diterima daripada pembekal dengan jumlah buku teks yang

diedarkan kepada pelajar. Kadang-kadang, beberapa buku teks rosak atau hilang,

sukar bagi guru untuk mencari siapa peminjam. Sistem ini juga boleh membantu

kakitangan untuk merekodkan semua maklumat pelajar dan buku teks dengan lebih

cekap. Ini dapat mengurangkan beban mereka untuk memeriksa kuantiti buku teks jika

masih tersedia, rosak atau hilang. Ia boleh mewujudkan pengurusan SPBT yang

sistematik dan cekap berdasarkan ICT dan mewujudkan satu sistem yang boleh

membantu dalam pemantauan dan penyelarasan pengurusan SPBT. Dalam menyedari

masalah ini, pokok keputusan berasaskan peraturan mudah dicadangkan dalam

projek akhir tahun ini.

vii

TABLE OF CONTENTS

Contents Pages

DECLARATION ....................................................................................................................... ii

CONFIRMATION .................................................................................................................... iii

DEDICATION .......................................................................................................................... iv

ABSTACT ................................................................................................................................. v

ABSTRAK ................................................................................................................................ vi

TABLE OF CONTENTS ......................................................................................................... vii

LIST OF TABLES .................................................................................................................... ix

LIST OF FIGURES ................................................................................................................... x

LIST OF ABBREVIATIONS / TERMS / SYMBOLS ............................................................ xii

LIST OF APPENDICES ......................................................................................................... xiii

CHAPTER I ............................................................................................................................... 1

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

1.1 Background ............................................................................................................ 1

1.2 Problem Statement ................................................................................................. 2

1.3 Objectives............................................................................................................... 3

1.4 Scope ...................................................................................................................... 3

1.5 Limitation Of Work ............................................................................................... 4

CHAPTER II .............................................................................................................................. 5

LITERATURE REVIEW ...................................................................................................... 5

2.1 Introduction .................................................................................................................. 5

2.2 The Comparison Of The Research ............................................................................... 6

2.3 Research Technique ................................................................................................... 16

2.4 Chapter Summary ...................................................................................................... 16

CHAPTER III .......................................................................................................................... 17

METHODOLOGY .............................................................................................................. 17

3.1 Introduction ................................................................................................................ 17

3.2 Project Methodology .................................................................................................. 17

3.3 System Requirement .................................................................................................. 21

3.4 Framework ................................................................................................................. 23

viii

3.5 Context Diagram ........................................................................................................ 24

3.6 DFD Level 0............................................................................................................... 25

3.7 DFD Level 1............................................................................................................... 28

3.8 Entity Relation Diagram ............................................................................................ 34

3.9 Database Design ......................................................................................................... 35

3.10 Data Dictionary ........................................................................................................ 36

CHAPTER IV .......................................................................................................................... 45

IMPLEMENTATION AND TESTING ........................................................................... 45

4.1 Introduction ................................................................................................................ 45

4.2 Interface Design ......................................................................................................... 46

4.2 Test Cases .................................................................................................................. 57

CHAPTER V ........................................................................................................................... 62

CONCLUSION .................................................................................................................... 62

5.1 Introduction ................................................................................................................ 62

5.2 Project Contribution ................................................................................................... 62

5.3 Project Constraints And Limitation ........................................................................... 63

5.4 Future Works.............................................................................................................. 63

5.5 Conclusion ................................................................................................................. 64

REFERENCES ........................................................................................................................ 65

APPENDIX A: GANTT CHART FYP 1................................................................................. 66

APPENDIX A: GANTT CHART FYP 2................................................................................. 67

ix

LIST OF TABLES

Table 2.1 Table Comparison of Research ................................................................................ 11

Table 3.1 Table Admin ............................................................................................................ 36

Table 3.2: Table Buku .............................................................................................................. 37

Table 3.3: Table Form .............................................................................................................. 38

Table 3.4: Table Guru Kelas .................................................................................................... 38

Table 3.5: Table Kelas ............................................................................................................. 39

Table 3.6: Table Pelajar ........................................................................................................... 39

Table 3.7: Table Pembekal....................................................................................................... 40

Table 3.8: Table Pembekal Buku ............................................................................................. 41

Table 3.9: Table Staff SPBT .................................................................................................... 42

Table 3.10: Table Pelajar Buku ............................................................................................... 43

Table 3.11: Table User ............................................................................................................. 44

Table 4.1: Test Case Register for the user ............................................................................... 57

Table 4.2: Test Case Update for the user ................................................................................. 58

Table 4.3: Test Case Add Student ............................................................................................ 58

Table 4.4: Test Case Update Student ....................................................................................... 59

Table 4.5: Test Case Delete Student ........................................................................................ 59

Table 4.6: Test Case Add Student Borrow Textbook .............................................................. 60

Table 4.7: Test Case Add Staff ................................................................................................ 61

Table 4.8: Test Case Delete Student ........................................................................................ 61

x

LIST OF FIGURES

Figure 3.1 Iterative and Incremental Development Model ...................................................... 18

Figure 3.2 Framework for Textbook Loan Management System ............................................ 23

Figure 3.3 Context Diagram for Textbook Loan Management System ................................... 24

Figure 3.3 Context Diagram for Textbook Loan Management System ................................... 25

Figure 3.4 DFD Level 0 for Textbook Loan Management System ......................................... 28

Figure 3.5 DFD Level 1 for Manage User (for staff)............................................................... 29

Figure 3.6 DFD Level 0 for Manage User (for admin) ............................................................ 30

Figure 3.7 DFD Level 1 for Manage Student (for staff) .......................................................... 31

Figure 3.8 DFD Level 1 for Manage Book (for staff) ............................................................. 32

Figure 3.9 DFD Level 1 for Manage Supplier (for staff)......................................................... 33

Figure 3.10 DFD Level 1 for Manage Order (for staff) ........................................................... 34

Figure 3.11 ERD for Textbook Loan Management System .................................................... 34

Figure 3.12 Database in Textbook Loan Management System ............................................... 35

Figure 4.1 Homepage Interface ................................................................................................ 46

Figure 4.2 Homepage Contact Us ............................................................................................ 46

Figure 4.3 Login Page .............................................................................................................. 47

Figure 4.4 Register page .......................................................................................................... 47

Figure 4.5 Login Page the staff ................................................................................................ 48

Figure 4.6 Homepage the Staff ................................................................................................ 48

Figure 4.7 Profile staff information page ................................................................................. 49

Figure 4.8 Student information page ....................................................................................... 49

Figure 4.9 Textbook information page .................................................................................... 50

Figure 4.10 Supplier information page .................................................................................... 50

Figure 4.11 Teacher information page ..................................................................................... 51

Figure 4.12 Student borrow textbook information page .......................................................... 51

Figure 4.13 Display record of the student borrow textbook page ............................................ 52

Figure 4.14 Change Password Page ......................................................................................... 53

xi

Figure 4.15 Page after successfully Change Password ............................................................ 53

Figure 4.16 Record all the student Page .................................................................................. 54

Figure 4.17 Record all the student borrow textbook in form 2 Page ....................................... 54

Figure 4.18 Login page the admin ........................................................................................... 55

Figure 4.19 Homepage the admin ............................................................................................ 55

Figure 4.20 Add or delete the staff .......................................................................................... 56

Figure 4.21 Record all the student Page .................................................................................. 56

xii

LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram

DFD Data Flow Diagram

ERD Entity Relationship Diagram

xiii

LIST OF APPENDICES

APPENDIX TITLE PAGE

A Appendix 1 66

B Appendix 2 67

1

CHAPTER I

INTRODUCTION

1.1 Background

The Textbook Loan Scheme Program (SPBT) was first implemented in 1975.

SPBT is a textbook loan program for eligible students in all government schools and

government aid schools. The SPBT program was originally intended to alleviate the

financial burden incurred by poor parents or guardians and ensure that pupils from

underserved families do not drop out of their schooling. However, beginning 2008, the

Malaysian government has provided textbooks loans to all students who attend school

at government schools regardless of their family's financial status. Hence, this

situation makes the responsibility of the SPBT unit be more weighted to ensure that

each book is processed and distributed to all students at SMK Tembila.

Based on my observation and interview from En Adanan Bin Mohd Zin, the

SPBT coordinator teacher at SMK Tembila, there was a problem when that school

was still using manually to get and fill the information of students who had borrowed

textbooks. Mostly, staff of SPBT will provide logbooks for students and students will

write the details of the textbooks they have borrowed. To avoid that situation, we have

come out with a system that offers a management for the textbook supervisors to

manage the textbook without using manually. This proposed system will help the

textbook supervisors to standardize the management and implementation of SPBT in

2

SMK Tembila throughout the direction of excellence and commitment of

administrators and teachers in the management and implementation of SPBT. This

project is useful to save user’s time in management of SPBT with only simple click of

a mouse.

Textbook Loan (SPBT) Management System is able to problems such as time

constraints and reduced workload. This system will use Intelligent Decision Support

System Technique because it provides the simplest and most understandable way of

expressing knowledge. As for the conclusion, Textbook Loan (SPBT) Management

System will be a good solution in solving real life problems and makes the user life

easier and simpler.

1.2 Problem Statement

There are some problems faced by the staff SPBT who intended to manage the

textbook. Firstly, it becomes harder and takes time for the staff SPBT to key-in the

data of the students that borrows the textbooks because the staff SPBT works only 8

hours, so they do not have enough time to record all information of student that

borrowed textbook so it will take a few days to complete key-in all the information

data of students. Next, the staff SPBT must check the quantity of textbooks whether

adequate or not. The staff SPBT must know how much total textbook in each subject,

so they do not have to count and check each of the subject textbook whether adequate

or not. Lastly, sometimes the textbook are damage or missing the then staff SPBT

cannot know who was student that borrows. It because sometimes the student do not

returning of textbook or textbook was damage, so the staff SPBT did not know student

who responsible to textbook.

3

1.3 Objectives

The objectives of Textbook Loan (SBPT) Management System are:

i. To design a system for staff SPBT manage the data information of student

who borrowed the textbook

ii. To develop and implement an intelligent support system to evaluate the

textbook when accessing this system

iii. To evaluate the performance and usefulness of an intelligent decision

support system based on textbook information

1.4 Scope

There are main actors which are the staff SPBT and admin

1.4.1 Scopes of the User

i) Admin

Able to log in as admin

Able to manage profile and update details or password

Able to view all the report

Able to manage security and maintenance of the system

4

ii) Staff SPBT

Able to register and log into management system

Able to update profile and change password

Able to manage details of textbooks, supplier and student

Able to generates and view reports

1.5 Limitation Of Works

This system only can access by admin and the staff SPBT who work at SMK

Tembila. This system will only manage distribution textbook to the student that had

borrowed.

5

CHAPTER II

LITERATURE REVIEW

2.1 Introduction

This chapter will continue with the discussion and the idea from previous

research. In general, literature review refers to survey books, scholarly articles, and

any other sources relevant to a particular issue, area of research or theory and by so

doing, provides a description, summary and critical evaluation of these works in

relation to the research problem being investigated. This literature review contains the

general description of the existing system and making comparison between existing

systems.

6

2.2 The Comparison Of The Research

1) Book Inventory System Using RFID

In the research paper, the system that is being developed is known as “Book

Inventory System Using RFID.” Radio-frequency identification (RFID) is a

technology uses communication via electromagnetic waves to exchange data

between a terminal and an object such as a product, animal, or person for the

purpose of identification and tracking. This technology has slowly begun to

replace the traditional barcodes on library items (books, CD’s, DVDs, etc). The

RFID tag can contain identifying information, such as a book’s title or material

type, without having to be pointed to a separate database. In this project, RFID

technology will help the management of the library and also the customer for

library in order to manage the inventory and all the transaction process happen

every day. In this technologies also reduce time and increase the efficiency.

Therefore, it will make the data of the library can be view and manage more

systematically by the administrator or staff.

7

2) Automatic Creation of Stock Trading Rules Basis of Decision Trees

In the research paper, the system that is being developed is known as

“Automatic Creation of Stock Trading Rules Basis of Decision Trees”. This

conceptual paper discusses the main task of any trader is the selection of profitable

strategies for trading a financial instrument. One of the simplest ways to represent

trading rules of binary decision trees based on the comparison of current values of

technical indicators with some absolute values. This approach simplifies the

creation trading system but their validity is limited to short-term intervals of trade.

This paper represents an approach for generating more universal trade rules in the

form of binary decision tree based on the comparison of the current values of

technical indicators with relative levels.

8

3) Implementation of an Intelligent Library System Based on WSN and

RFID


“Implementation of an Intelligent Library System Based on WSN and RFID”. In

this research paper, to improve the intelligent of the library, on the basis of manual

and information management, new technologies were combined to design RFID

wireless network with WSN consisting of nodes. The intelligent library system

based on WSN and RFID used advanced RFID and ZigBee technology for the

optimization and integration of literature resources, service process and

management mode of the library. The result showed that the intelligent library

system based on WSN and RFID could basically realize the intelligent library

management. To sum up, the system creates a random library service and

management system at anytime and anywhere.

9

4) Fault Diagnosis of Water Quality Monitoring Devices Based on Multiclass

Support Vector Machines and Rule-Based Decision Tress

In the research paper, the system that is being developed is known as “Fault

Diagnosis of Water Quality Monitoring Devices Based on Multiclass Support

Vector Machines and Rule-Based Decision Tress”. This conceptual paper

discusses preventing faults of sensors, wireless transmitters, and getaways are

essential for water quality management in intensive aquaculture. It remains a

challenging task to achieve high fault diagnostic accuracy of water quality

monitoring and controlling devices. This paper proposes a hybrid water quality

monitoring device fault diagnosis model based on multiclass support vector

(MSVM) in combination with rule-based decision tree (RBDT). In the modelling

process, an RBDT is used to diagnose the getaway fault and wireless transmitter

fault at the same time as a feature selection tool to reduce the number of features.

RBDT-MSVM was tested and compared with other algorithms by applying it to

diagnose faults of water quality monitoring devices in river crab culture ponds.

The diagnostic results indicate that the model has great potential for fault

diagnosis of online water quality devices.

10

5) Enhancing Cooperative Loan Scheme Through Automated Loan

Management System.


“Enhancing Cooperative Loan Scheme Through Automated Loan Management

System”. This research paper, it involves utilization of computing or electronic

devices to undertake the tasks that are being handled by people. It is a pertinent

factor in a profitable and soundly run financial institution. Financial transactions

through manual system of operation are prone to errors and unimagined

complexities, making it so difficult a task maintaining all entries of users account,

search records of activities, handle loan deduction errors and generate reports. The

system essentially manages both short-term and long-term loans, and keeps track

of cash inflow and outflow of a cooperative society among others. It utilized SQL

Server database architecture at the back end and Visual Basic.Net framework at

the front end. This makes it user-friendly and highly interactive. The Object

Modelling Technique (OMT) is adopted for the analysis and design of the Loan

Software. A pragmatic system bundles with several competent capabilities to

eliminate data inconsistency and redundancy as well as ensuring data integrity and

security, with guaranteed fast retrieval response time.

11

Author/Year Research Name System Description Methodology

Nurul Nadia Binti

Mat Jalaluddin,

Universiti Malaysia

Pahang / 2011

Book Inventory

System Using

RFID

-RFID technology will

help the management of

the library and also the

customer for library in

order to manage the

inventory and all the

transaction process

happen every day.

-Reduce time and

increase the efficiency. -

It will make the data of

the library can be view

and manage more

systematically by the

administrator or staff.

- RFID

12

Dmitry Iskrich,

Dmitry Grigoriev,

St. Petersburg State

University St.

Petersburg, Russia /

2013

Automatic

Creation of

Stock Trading

Rules Basis of

Decision Trees

-One of the simplest

ways to represent

trading rules of binary

decision trees based on

the comparison of

current values of

technical indicators

with some absolute

values.

-This paper represents

an approach for

generating more

universal trade rules in

the form of binary

decision tree based on

the comparison of the

current values of

technical indicators

with relative levels.

-Decision Trees

13

Mbam B.C.E. and

Igboji, Kingsley O,

Department of

Computer Sciencem

Ebonyi State

University –

Avakaliki /2013

Enhancing

Cooperative

Loan Scheme

Through

Automated Loan

Management

System

-Financial transactions

through manual system

of operation are prone

to errors and

unimagined

complexities, making it

so difficult a task

maintaining all entries

of users account, search

records of activities,

handle loan deduction

errors and generate

reports.

-The system essentially

manages both short-

term and long-term

loans, and keeps track

of cash inflow and

outflow of a cooperative

society among others.

The Object

Modeling

Technique (OMT)

14

Shiangyin Liu,

Longqom Xu,

Qiucheng Li,

Xuehua Zhao,

Daoliang Li, College

of Information

Science and

Technology,

Zhongkai University

and Engineering,

Guangzhou, China /

2017

Fault Diagnosis

of Water Quality

Monitoring

Devices Based

on Multiclass

Support Vector

Machines and

Rule-Based

Decision Tress

-Hybrid water quality

monitoring device fault

diagnosis model based

on multiclass support

vector (MSVM) in

combination with rule-

based decision tree

(RBDT).

-RBDT is used to

diagnose the getaway

fault and wireless

transmitter fault at the

same time as a feature

selection tool to reduce

the number of features.

-RBDT-MSVM was

tested and compared

with other algorithms

by applying it to

diagnose faults of water

quality monitoring

devices in river crab

culture ponds

-Multiclass

Support Vector

Machines

-Rule-Based

Decision Tress

15

Table 2.1: The comparison of research

Yuping Gao, North

China Electric

Power University,

Baoding, China /

2018

Implementation

of an Intelligent

Library System

Based on WSN

and RFID

-To improve the

intelligent of the

library, on the basis of

manual and

information

management, new

technologies were

combined to design

RFID wireless network

with WSN consisting of

nodes.

-Wireless Sensor

Network

-RFID

16

2.3 Research Technique

Rule based decision tree methods handle manipulations in the data through the

rules induced from the data not the decision tree itself. RBDT methods create

decisions tree from rules, they could be used also to create decision tree from

examples by considering each examples as a rule. Data-based decision tree methods

create decision tree from data only. It to represent trading rules is binary decision trees

based on the comparison of current values of technical indicators with some absolute

values [2]. Thus, to generate a decision tree for problems where rules are provided, e.g.

by an expert, and no data is available, rule-based decision tree methods are the only

applicable solution. RBDT is used to diagnose the gateway fault and wireless

transmitter fault at the same time as a feature selection tool to reduce the number of

features [4]. The method‘s goal is to create on-demand a short and accurate decision

tree from a stable or dynamically changing set of rules. The rules used by RBDT

could be generated either by an expert or induced directly from a rule induction

method or indirectly by extracting them from a decision tree.

2.4 Chapter Summary

In this chapter, technique to be used is studied and few collection of literature

review has been done. By this, knowledge have been gain to help to develop a good

and functioning system. By literature review also helps to gain knowledge about

techniques and past systems that has been used in previous research. In the phase, we

will know that Rule Based Decision Tree (RBDT) is the best practice way to be

implemented in Textbook Loan (SPBT) Management System.

17

CHAPTER III

METHODOLOGY

3.1 Introduction

In this chapter, it will be discussed about the methodology that used to develop

this system. Hence, the System Development Life Cycle (SDLC) will be used which

its Interactive and Incremental Model that is used for step in SPBT Loan Management

System. It will explain more details of each phase involve in this project development

based on the system requirements.

3.2 Project Methodology

Iterative and Incremental Process Model has been chosen as a methodology to

develop this application in order to achieve the objectives of the project to solve the

problem in managing textbook among the supervisor textbook. The phases of this

methodology are Planning, System Analysis and Requirement, System Design,

Implementation, Testing and Deployment. The project will be started with an initial

planning and ended with deployment phase.

18

Figure 3.1 Iterative and Incremental Development Model

This model is chose because it is a method of software development that

begins with planning and continues through iterative development cycles involving

user requirement and incremental addition of features concluding with the deployment

of completed system at the end of each cycle. Hence, if the system is having some

error, the developer able to fix the error with this cyclic model based on the allocated

time given.

19

3.2.1 Planning Phase

The requirement will be planned to complete the project based on the time

givens. The phase started with brainstorming of any ideas with the supervisor in which

the abstract of the project that contained title, problem, technique and the solution of

the project problem. The proposed title that has been approved by the faculty was a

management system called SPBT Loan Management System.

3.2.2 Requirement Analysis Phase

In this phase, the detailed of introduction has been decided in which project

title, problem statement, objectives and scope of project. The survey of daily expenses

among the students and employee generally were conducted for better understanding

of the proposed system to be developed rather than the current or existing system. The

objectives of this project have been determined after the survey is done. The

requirements are discovered in order to build the better system to the user.

3.2.3 Design Phase

The required design was developed based on the requirement that has been

analysed from the Requirement Analysis Phase previously. The certain diagrams such

as Context Diagram (CD), Entity Relational Diagram (ERD), Data Flow Diagram

(DFD) Level 0 and Framework were built as a guideline while developing this system.

Then, the interface of this application will be sketched roughly, for example Mock Up.

20

3.2.4 Implementation Phase

In this phase, SPBT Management System is implemented into the coding

based on the sub-module of the system requirements. This project is developed using

PHP, Notepad and Xampp will be used as a local host server.

3.2.5 Testing Phase

Once the coding is implemented, the module is tested through unit testing to

test the single part of the module in this application. In order to ensure the process of

the system can be worked correctly, testing needs to be done. If the system is having

some errors, the error must be fixed and testing the system again so that the first

version of this system can be released.

3.2.6 Deployment Phase

The users are able to try this application after it has been released. Then, from

user requirement or review, the developer will be know if this application has met the

objectives of SPBT Management System that stated in Introduction of this project.

21

3.3 System Requirement

The stated requirements below required in order to develop this system properly such

as software and hardware requirement.

3.3.1 Software Requirement

1. Microsoft Word 2010

Software for writing project and report of project

2. Dropbox

Tool for cloud storage of back up data

3. Jing

Tool for screen shot the image to be used in this report

4. Xampp Control Panel v3.2.1

Tool for open source of web server

5. Notepad++

Tool for develop PHP

6. PHP

Language used to develop the system

7. Google Chrome

Used to do research on the project and to run the project

8. Lucid Chart Diagram Software

Used to draw CD and DFD model

22

3.3.2 Hardware Requirement

1. Laptop

The laptop used was Lenovo 100-14IBD with Intel(R) Core(TM) i3-5005U

CPU @ 2.00GHz 2.00 GHz. 6.00 GB RAM, 64-bit operating system, x64-

based processor and Edition Windows 10 Home Single Language

2. Pendrive

The Pendrive user Data Traveler USB 32GB

3. Printer

The printer used was Epson L-210 to print out several documents such as

proposal and report of project.

23

3.4 Framework

Figure 3.2 Framework for Textbook Loan Management System

Framework is basically a board overview or outline of interlinked items which

supports a particular approach to a specific objectives, and serves as a guide that can

be modified as required by adding or deleting items.

24

3.5 Context Diagram

Figure 3.3 Context Diagram for Textbook Loan Management System

Description:

Based on the figure 3.4 above, there are three actors in this Textbook Loan (SPBT)

Management System which are ADMIN, STAFF SBPT and SUPPLIER. The context

diagram above display the flow between three actors and what are they involved in

system based on their roles. Staff SBPT is able to insert their own details during

registration and login. They have to insert student detail, book details and supplier

details. Then, they can generate all the report detail by the system. Other than that,

Supplier will take order detail from the staff SPBT and then payment detail will

display after payment have pay. Meanwhile, Admin will be able to manage their

profile and view all the report that system will display and also user’s information.

25

3.6 DFD Level 0

Figure 3.4 DFD Level 0 for Textbook Loan Management System

26

Description:

The DFD has three entries which are ADMIN, STAFF SPBT and SUPPLIER. There

are six processes involved in the system which are MANAGE USER, MANAGE

STUDENT, MANAGE BOOK, MANAGE SUPPLIER, MANAGE ORDER, and

GENERATE REPORT. There are six data stores created in the system which are

STAFF RECORD, ADMIN RECORD, STUDENT RECORD, BOOK RECORD,

SUPPLIER RECORD, and ORDER RECORD. The flow of the system is like below.

1. STAFF SPBT input STAFF DETAILS into MANAGE USER process which

outputs STAFF DETAILS into STAFF data store.

2. STAFF SPBT input STUDENT DETAILS into MANAGE STUDENT process

which outputs STUDENT DETAILS into STUDENT data store.

3. STAFF SPBT input BOOK DETAILS into MANAGE BOOK process which

outputs BOOK DETAILS into BOOK data store.

4. STAFF SPBT input SUPPLIER DETAILS into MANAGE SUPPLIER

process which outputs SUPPLIER DETAILS into SUPPLIER data store.

5. ADMIN input ADMIN DETAILS into MANAGE USER process which

outputs ADMIN DETAILS into ADMIN data store.

6. SUPPLIER input SUPPLIER DETAILS into MANAGE ORDER process

which outputs ORDER DETAILS into ORDER data store.

7. When STAFF SPBT wants to view reports, STAFF INFO, ADMIN INFO,

STUDENT INFO, BOOK INFO, SUPPLIER INFO, and ORDER INFO are

taken from STAFF, ADMIN, STUDENT, BOOK, SUPPLIER and ORDER

RECORDS data stores respectively into REPORT process which outputs

REPORT to STAFF.

27

8. When ADMIN wants to view reports, STAFF INFO, ADMIN INFO,

STUDENT INFO, BOOK INFO, SUPPLIER INFO, and ORDER INFO are

taken from STAFF, ADMIN, STUDENT, BOOK, SUPPLIER and ORDER

RECORDS data stores respectively into REPORT process which outputs

REPORT to ADMIN.

28

3.7 DFD Level 1

3.7.1 Manage User

3.7.1.1 Manage User (for staff)

Figure 3.5 DFD Level 1 for Manage User (for staff)

Description:

1. STAFF SPBT input STAFF DETAILS into REGISTER process which output

STAFF DETAILS into STAFF data store

2. STAFF SPBT input STAFF DETAILS into LOGIN process which output

STAFF DETAILS into STAFF data store

3. STAFF SPBT input STAFF DETAILS into UPDATE PROFILE process

which STAFF DETAILS into STAFF data store

29

3.7.1.2 Manage User (for admin)

Figure 3.6 DFD Level 1 for Manage User (for admin)

Description:

1. ADMIN input ADMIN DETAILS into LOGIN process which output ADMIN

DETAILS into ADMIN data store.

2. ADMIN input ADMIN DETAILS into UPDATE PROFILE process output

ADMIN DETAILS into ADMIN data store.

30

3.7.2 Manage Student

Figure 3.7 DFD Level 1 for Manage Student (for staff)

Description:

1. STAFF SPBT input STUDENT DETAILS into ADD STUDENT process

which output STUDENT DETAILS into STUDENT data store.

2. STAFF SPBT input STUDENT DETAILS into UPDATE STUDENT process


3. STAFF SPBT input STUDENT DETAILS into DELETE STUDENT process


31

3.7.3 Manage Book

Figure 3.8 DFD Level 1 for Manage Book (for staff)

Description:

1. STAFF SPBT input BOOK DETAILS into ADD BOOK process which output

BOOK DETAILS into BOOK data store.

2. STAFF SPBT input BOOK DETAILS into UPDATE BOOK process which

output BOOK DETAILS into BOOK data store.

3. STAFF SPBT input BOOK DETAILS into DELETE BOOK process which

output BOOK DETAILS into BOOK data store.

32

3.7.4 Manage Supplier

Figure 3.9 DFD Level 1 for Manage Supplier (for staff)

Description:

1. STAFF SPBT input SUPPLIER DETAILS into ADD SUPPLIER process

which output SUPPLIER DETAILS into SUPPLIER data store.

2. STAFF SPBT input SUPPLIER DETAILS into UPDATE SUPPLIER process


3. STAFF SPBT input SUPPLIER DETAILS into DELETE SUPPLIER process


33

3.7.5 Manage Order

Figure 3.10 DFD Level 1 for Manage Order (for supplier)

Description:

1. SUPPLIER input ORDER DETAILS into VIEW ORDER process which

output ORDER DETAILS into ORDER data store.

2. SUPPLIER input ORDER DETAILS into UPDATE ORDER process which

output ORDER DETAILS into ORDER data store.

34

3.8 Entity Relation Diagram

Figure 3.11 ERD for Textbook Loan Management System

An entity relational diagram (ERD), also known as an entity relational model, is

a graphical representation of an information system that shows the relationship

among people, objects, places, concepts or events within that system.

35

3.9 DATABASE DESIGN

Database is a structured set of data held in a computer, especially one that is

accessible in various ways. So basically, database is needed to hold all the data

needed in the system.

Figure 3.12 Table in Textbook Loan Management System Database

There are eleven tables in database which are Admin, Buku, Form, GuruKelas, Kelas,

Pelajar, PelajarBuku, Pembekal, PembekalBuku, StaffSPBT and User. For each table,

there are attributes at every column.

36

3.10 Data Dictionary

3.10.1 Table Admin

NO ATTRIBUTES DESCRIPTION TYPE LENGTH REMARK

1 AdminID Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NamaAdmin The attribute for

admin’s name

VARCHAR 100 -

3 Password The attribute for

admin’s

password

VARCHAR 12 -

Table 3.1: Table Admin

37

3.10.2 Table Buku


1 NoSiriBuku Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NamaBuku The name of the

book

VARCHAR 100 -

3 HargaBuku Represents of the

price of the book

VARCHAR 20 -

4 Penerbit The name of the

publisher book

VARCHAR 120 -

5 BilanganBuku The quantity of

the book

INT 11 -

Table 3.2: Table Buku

38

3.10.3 Table Form


1 FormID Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NameForm Represents of the

name of form

VARCHAR 100

3 JumlahBuku Represents of the

total of the book

that every form

must have

INT 11 -

Table 3.3: Table Form

3.10.4 Table GuruKelas


1 ICNoGuru Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NamaGuru Represents the

name of the

teacher

VARCHAR 100 -

3 KelasID Represents the

Kelas ID who

teacher manage

student

VARCHAR 12 FOREIGN

KEY

Table 3.4: Table GuruKelas

39

3.10.5 Table Kelas



unique id

VARCHAR 12 PRIMARY

KEY

2 NamaKelas The name of the

class

VARCHAR 100 -

Table 3.5: Table Kelas

3.10.6 Table Pelajar


1 ICNumber Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NamaPelajar Represents the

student’s name

VARCHAR 100 -

3 NoPhone Represents the

student’s phone

number

VARCHAR 12 -

4 Email Represents the

student’s email

VARCHAR 20 -

5 Alamat Represents the

student’s address

VARCHAR 11 -

Table 3.6: Table Pelajar

40

3.10.7 Table Pembekal


1 PembekalID Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NamaPembekal The name of the

supplier

VARCHAR 100 -

3 NoPhone Represents of the

supplier’s phone

number

VARCHAR 12 -

4 Email Represents of the

supplier’s email

VARCHAR 20 -

5 Alamat Represents of the

supplier’s

address

VARCHAR 120 -

6 Penerbitan Represents of the

supplier’s

publishing

VARCHAR 100 -

Table 3.7: Table Pembekal

41

3.10.8 Table PembekalBuku


1 NoSiriBuku Represents the

No Siri Book that

supply by the

supplier

VARCHAR 12 PRIMARY

KEY

2 PembekalID Represents the

supplier ID who

supply the book

VARCHAR 12 FOREIGN

KEY

3 NoInvoice Represents of the

invoice of the

supplier

VARCHAR 20 -

4 JumlahBayaran Represents of the

amount of the

book that have

paid

VARCHAR 20 -

5 Tarikh Represents of the

date of the

invoice

VARCHAR 20 -

Table 3.8: Table PembekalBuku

42

3.10.9 Table Staff SPBT


1 StaffID Represents the

unique id

VARCHAR 12 PRIMARY

KEY

2 NamaStaff The attribute for

staff’s name

VARCHAR 100 -

3 NoPhone Represents the

staff’s phone

number

VARCHAR 12 -

4 Email Represents the

staff’s email

VARCHAR 100 -

5 Alamat Represents the

staff’s address

VARCHAR 100 -


staff’s password

VARCHAR 12 -

Table 3.9: Table Staff SPBT

43

3.10.10 Table PelajarBuku


1 ICNumber Represents the ic

number of student

VARCHAR 12 FOREIGN

KEY

2 NamaPelajar The attribute for

student’s name

VARCHAR 100 -

3 Tahun Represents the

year

VARCHAR 10 -


unique id

VARCHAR 12 FOREIGN

KEY

5 ICNoGuru Represents the

unique ic number

teacher

VARCHAR 12 FOREIGN

KEY

6 NamaGuru The attribute for

teacher’s name

VARCHAR 100 -

7 TarikhPinjaman Represents the

date of borrowed

DATE - -

8 TarikhPulangan Represents the

date of returned

DATE - -

9 Aliran Represents the

stream of class

VARCHAR 50 -

10 JudulBuku Represents the

textbook

VARCHAR 150 -

Table 3.10: Table Pelajar Buku

44

3.10.11 Table User


1 StaffID Represents the

unique id

VARCHAR 12 PRIMARY

KEY


admin’s name

VARCHAR 12 -

Table 3.11: Table User

45

CHAPTER IV

IMPLEMENTATION AND TESTING

4.1 Introduction

In this chapter, the implementation and testing of the system will be described.

During implementation, the system is developed. Projects developers begin building

and coding the software. While in testing, this phase includes detection of errors on

the system. Also, in this chapter, interface of the system will assist user to understand

the systems.

46

4.2 Interface Design

4.2.1 Main Page

Figure 4.1: Homepage interface

This interface is the public homepage on which user does not login first to view the

system.

Figure 4.2: Homepage Contact Us

This interface is the user can view the location, phone number, fax, email and web of

SMK Tembila.

47

Figure 4.3: Login Page

This interface is the user login into the system. There are two users in this system,

which are Admin and Staff. For Admin, they need to enter adminID while Staff needs

to enter staffID. Both are also required to enter password as well. If not the member,

admin needs to register the staff to sign up as a new member.

Figure 4.4: Register page when staff registered by admin

This interface is the user login into the system when the user already registered by the

admin.

48

4.2.2 User Page

Figure 4.5: Login page the staff

This interface is the user login into the system. The staff needs to enter staffID and

password correctly.

Figure 4.6: Homepage the staff

This interface is homepage of when staff successfully entered the staffD and

password.

49

Figure 4.7: Profile staff information page

This interface is the user can manage their profile. The staff can update their

information only.

Figure 4.8: Student information page

This interface is the information of students. The staff can add, update and delete

information of students.

50

Figure 4.9: Textbook information page

This interface is the information of textbooks. The staff can add, update and delete

information of textbooks.

Figure 4.10: Supplier’s information page

This interface is the information of suppliers. The staff can add, update and delete

information of suppliers.

51

Figure 4.11: Teacher’s information page

This interface is the information of teachers. The staff can add, update and delete

information of teachers.

Figure 4.12: Student borrow textbook information page

This interface is information of student’s borrowed the textbook. The user must select

the textbook that student had borrowed. It must contain the identification number of

student, name student, year, class, identification card number of teacher, date borrow,

date return, stream of the class and textbook.

52

Figure 4.13: Display record of the student had borrowed textbook page

This interface is the display all the record of the student’s borrowed textbook. The

staff can update and delete the record of the student borrowed textbook.

53

Figure 4.14: Change Password Page

Figure 4.15: Page after Successfully Change Password

Both on figure 4.14 and figure 4.15 shows change password pages where the staff can

do.

54

Figure 4.16: Record all the student page

This interface is the display all the record of student in SMK Tembila.

Figure 4.17: Record all the student had borrowed textbook in Form 2 page

This interface is the display of record the all student in form 2 that had borrowed

textbook at SMK Tembila.

55

4.2.3 Admin Page

Figure 4.18: Login page the admin

This interface is the user login into the system. The admin needs to enter adminID and

password correctly.

Figure 4.19: Homepage the admin

This interface is homepage of when staff successfully entered the adminID and

password.

56

Figure 4.20: Add or delete the staff

This interface is the admin register (add) or delete staff from the system. The admin

must register the staff before the staff login into the system.

Figure 4.21: Record all the student page

This interface is the display all the record of student in SMK Tembila. The admin can

generate all the record of the system.

57

4.2 Test Cases

A test case is a set a conditions in which a tester determine whether a system under

test satisfies requirements or works correctly. The process of developing test cases can

also help to find problems in the requirements or design of an application. The tables

below show the test cases for several processes of the system.

4.2.1 Test Cases For User

Step Procedure Expected Result Pass/Fail

1 Clik “Daftar” to register Application form Pass

2 Enter the following details:

1. StaffID : TM003

2. Password: 12345

3. Re-type Password:

12345

Pass

3 Clik “Submit” button Message preview successful

or failure

Pass

Table 4.1: Test case register for the user

58


1 Click “Find” StaffID Pass

2 Pick one attribute to be updated

1. Example: Alamat:

Kuala Lumpur

Pass

3 Click “Submit” button Message preview successful

or failure

Pass

Table 4.2: Test case update for the user


1 Click “Pelajar” Application form Pass


1. ICNo: 0102526116490

2. NamaPelajar: Farisha

Ariana Binti Md Abbas

3. NoPhone: 0193928573

4. Email:

[email protected]

m

5. Alamat: Gong Medang

Pass

3 Click “Add” button Message preview

successful or failure

Pass

Table 4.3: Test case add student

59


1 Click “Find” ICNo

Example: 950120018026

Form of details of the IC

Number of student

Pass

2 Pick one attribute to be

updated

1. Example: Alamat:

Kuala Lumpur

Pass

3 Click “Update” button Message preview successful or

failure

Pass

Table 4.4: Test case update student


1 Click “Find” ICNo

Example: 950120018026

Form of details of the IC

Number of student

Pass

2 Click “Delete” button ICNo deleted Pass

Table 4.5: Test case delete student

60


1 Click “Pinjaman Buku Teks” Application form Pass


1. ICNo: 0102526116490

2. NamaPelajar: Nur Farisha Ariana

Binti Md Abbas

3. Tahun: 2019

4. Kelas: 2JYA

5. ICNoGuru: 830424125895

6. NamaGuru: Ahmad Bin Aziz

7. TarikhPinjaman: 05/01/2019

8. TarikhPulangan: 27/09/2019

9. Aliran: Menengah Rendah

10. JudulBuku:BM,BI,MM,SN,SEJ,PM,

PSK,GEO,PJK,KH (ERT),PI

3 Click “Submit” button Message preview successful

or failure

Pass

Table 4.6: Test case add student borrow textbook

61

4.2.2 Test Cases For Admin


1 Click “Staff” Application form Pass


1. StaffID: TM003

2. NamaStaff: Nazirah Nasir

3. NoPhone: 0122839201

4. Email:

[email protected]

5. Alamat: Batu Rakit, Kuala

Terengganu

Pass

3 Click “Add” button Message preview

successful or failure

Pass

Table 4.7: Test case add staff


1 Click “Find” StaffID

Example: TM002

Form of details of the staff

id of the staff

Pass

2 Click “Delete” button StaffID deleted Pass

Table 4.8: Test case delete student

62

CHAPTER V

CONCLUSION

5.1 Introduction

This chapter focused on project contribution, constrains of the project, the

conclusion and also future works that can be gained from this project. From this

project, we can find out how to improve the system.

5.2 Project Contribution

The contribution of this system for the staff is to manage their textbook in

efficient ways. They are able to track each of textbook. In addition, it will easier for

them in response to the system. This system is able to summarize each record of

student, textbook, supplier, and teacher by the user or staff. Last but not least, this

system is secure since user need to register an account of Textbook Loan Management

System and login successfully in order to use it.

63

5.3 Project Constraints And Limitation

In the process of developing the project and preparation of fully functioning

system, there are a few limitation of work that cause the constraints and difficulties to

the developer.

For this system, the limitations of the work is that the simple rule based

decision tree in this system does not implemented well due to limited characteristic to

be chosen from. Other than that, the user must know what kind type of textbook that

student had borrowed. They need to check and count the amount of textbook by class.

5.4 Future Works

In future, there are few things need to be improved on this system in order to

make this system more usable to the user or staff. One of them is the staff able to view

status of textbook by selecting date, month and year. The system would able more

completed if it able to prevent the record of textbook that has exceed the class limit

from the entered into the system. Also, this system needs to have more validation.

64

5.5 Conclusion

Textbook Loan Management System was implemented using the simple rule

based decision tree technique. As the technique is to find the goal first before anything

else, it proves that this method is the most suitable in order to develop this system.

This system will help users to achieve their goals, as in this system which is

textbooks. So when the users had information of the students had borrower the

textbook, the textbook loan management system will know that the current class of the

student. However, this system only functioning in selecting, so the users need to

select the textbook by themselves.

Textbook Loan Management System managed the textbook loan management

at SMK Tembila. Other than that, implementation of this system can helped the staff

SPBT to manage the textbook more systematically and efficiently at the SMK

Tembila.

65

REFERENCES

1. NURUL NADIA BINTI MAT JALALUDDIN. 2011. Book Inventory System

Using RFID. Universiti Malaysia Pahang

2. Iskrich, D., & Grigoriev, D. (2017). Automatic Creation of Stock Trading

Rules on the Basis of Decision Trees. In Second Conference on Software

Engineering and Information Management (SEIM-2017)(full papers) (p. 25).

3. Gao, Y. (2018). Implementation of an Intelligent Library System Based on

WSN and RFID. International Journal of Online Engineering (iJOE), 14(05),

211-224.

4. Liu, S., Xu, L., Li, Q., Zhao, X., & Li, D. (2018). Fault Diagnosis of Water

Quality Monitoring Devices Based on Multiclass Support Vector Machines

and Rule-Based Decision Trees. IEEE Access, 6, 22184-22195.

5. Mbam, B. C. E., & Igboji, K. O. (2013). Enhancing Cooperative Loan Scheme

Through Automated Loan Management System. West African Journal of

Industrial and Academic Research, 6(1), 144-153.

66

APPENDIX A: GANTT CHART FYP 1

Task Name Week

2

Week

3

Week

4-5

Week

5-6

Week

7

Week 8-

10

Week 11-

12

Week 13-

14

Initial Phase

Coordinator

Briefing

Topic

Discussion

Topic

Register

Planning

Phase

Gather

Information

Proposal

Writing

Proposal

Progress

Presentation

and

Evaluation

Correction

Proposal and

System

Methodology

Requirement

Phase

Determine

System

Requirement

Analysis

Existing

System

Progress

Proposal

Analysis and

Design

Design

Context

Diagram

Design Entity

Relational

Diagram

Design Data

Flow

Diagram

Design

Framework

67

APPENDIX B: GANTT CHART FYP 2

ACTIVITY WEEK 1 2 3 4 5 6 7 8 9 10

Decision Project

Project Development

Project Development and

Testing

Documentation and Report

Project Progress Presentation

and Evaluation

Project Presentation and

Evaluation

Final Submission of Project

Report

Documents

TEXTBOOK LOAN MANAGEMENT SYSTEM USING SIMPLE RULE …