PPHP EQUIPMENT MANAGEMENT SYSTEM NUR NABILAH BINTI …

PPHP EQUIPMENT MANAGEMENT

SYSTEM

NUR NABILAH BINTI AZMAN

BACHELOR OF COMPUTER SCIENCE

(INTERNET COMPUTING)

UNIVERSITI SULTAN ZAINAL ABIDIN

2018

PPHP EQUIPMENT MANAGEMENT SYSTEM

NUR NABILAH BINTI AZMAN

Bachelor of Computer Science (Internet Computing) with Honours

Faculty of Informatics and Computing

Universiti Sultan Zainal Abidin, Terengganu, Malaysia

AUGUST 2018

i

CONFIRMATION

This report PPHP Equipment Management System was prepared and submitted by Nur

Nabilah Binti Azman (Matric Number : 040806) and has be found satisfactory in term

of scope, quality and presentation as a partial as fulfilment in the requirement of the

Bachelor of Degree in Science Computer (Internet Computing) with Honours in

Universiti Sultan Zainal Abidin.

Signature: ……………………………………….

Supervisor Name : Puan Norkhairani Binti Abdul Rawi

Date :

ii

DECLARATION

The thesis is submitted as a partial of fulfilment for the award of Bachelor of Degree

in Science Computer (Internet Computing) with Honours at Universiti Sultan Zainal

Abidin. The works is the result of my own research. This thesis is based on my original

work with the help of information from sources that are fully reference. I declare my

work is never produced by any of other bachelor student in Universiti Sultan Zainal

Abidin.

Signature : …………………………………

Name : Nur Nabilah Binti Azman

Matric Number : BTCL15040806

Date :

iii

ACKNOWLEDGEMENT

First of all, I would like to thank to Allah S.W.T for helping me to complete

the final project and the project report. I am grateful because I can finish this report in

time that had been provided. I would like to thank to my lecturers especially my

supervisor, Puan Norkhairani Binti Abdul Rawi for helping me to solve the problem

and complete the final project report. She has provided ideas and guidance in

completing the final project and also report. I also would like to thank to my family,

especially my parents that always support and give courage to complete the final

project. Last, not forgetting our lecturers of Faculty of Informatics and friends that

help and sharing the ideas and concept in preparing the final project and also report.

iv

ABSTRACT

Pusat Pembangunan Holistik Pelajar (PPHP) is an organization in UniSZA that

provide some aid to the student. PPHP are provide the equipment that the student can

use for certain event. Currently, in order to reserves the equipment, UniSZA's students

still need to go to PPHP to make a manual reservation. Examples of equipment that

the student can reserve are wireless microphones, DSLR cameras, video recorders and

others. But in such a way that it would make the students difficult to reserves the

equipment because of the possibility that the equipment that already been reserved by

other students is highest. This system will enable the students to identify the

availability of equipment they need before they can make any booking. In addition,

this system will provide confirmation the return of equipment. The main objectives of

the development of this system are to facilitate students to book the necessary

equipment via online and provide the right platform to book. The standard for this

system is the integration via the Internet, so the student can access the system easily.

This system will be developed as a web-based platform and it will be created by using

server-side scriptings such as PHP with Apache Web Server and PHPMyAdmin as a

database for the system. The target users of this system are UniSZA's students and

administrator. This report explains the background project, the methodology that will

be used is priority-based algorithm.

v

ABSTRAK

Pusat Pembangunan Holistik Pelajar (PPHP) adalah sebuah organisasi di UniSZA

yang memberikan bantuan kepada pelajar. PPHP menyediakan peralatan yang

boleh digunakan pelajar untuk acara tertentu. Pada masa ini, untuk menempah

peralatan, pelajar UniSZA masih perlu pergi ke PPHP untuk membuat tempahan

manual. Contoh peralatan yang boleh ditempah oleh pelajar adalah mikrofon tanpa

wayar, kamera DSLR, perakam video dan lain-lain. Tetapi ia akan memberi

kesukaran kepada pelajar untuk menempah peralatan itu kerana kemungkinan

peralatan yang telah disediakan oleh pelajar lain adalah sangat tinggi. Sistem ini

akan membolehkan pelajar mengenal pasti ketersediaan peralatan yang mereka

perlukan sebelum mereka boleh membuat tempahan. Di samping itu, sistem ini akan

memberikan pengesahan pemulangan peralatan. Objektif utama pembangunan

sistem ini adalah untuk memudahkan para pelajar untuk menempah peralatan yang

diperlukan melalui talian dan menyediakan platform yang sesuai untuk ditempah.

Standard untuk sistem ini adalah integrasi melalui Internet, oleh itu pelajar dapat

mengakses sistem dengan mudah. Sistem ini akan dibangunkan sebagai platform

berasaskan web dan ia akan diwujudkan dengan menggunakan bahasa yang telah

ditetapkan seperti PHP dengan Apache Web Server dan PHPMyAdmin sebagai

pangkalan data untuk sistem ini. Pengguna sasaran sistem ini adalah pelajar dan

pentadbir UniSZA. Laporan ini menerangkan projek latar belakang, metodologi

yang akan digunakan adalah algoritma berasakan keutamaan.

vi

TABLE OF CONTENT

CHAPTER TITLE PAGE

CONFIRMATION i

DECLARATION ii

ACKNOWLEDGEMENT iii

ABSTRACT iv

ABSTRAK v

TABLE OF CONTENT vi - ix

LIST OF FIGURES x – xi

LIST OF TABLES xii

LIST OF SCREENSHOTS xiii

LIST OF ABBREVIATIONS / TERMS / SYMBOLS xiv

1 INTRODUCTION

1.1 BACKGROUND 1

1.2 PROBLEM STATEMENT 2

1.3 OBJECTIVE 2 - 3

1.4 SCOPE 3

1.5 LIMITATION OF WORK 3

vii

2 LITERATURE REVIEW

2.1 INTRODUCTION 4

2.2 SYSTEM ANALYSIS 5 - 7

2.3 EXISTING SYSTEM 8

2.4 RELATED TECHNIQUE, TOOLS AND

TECHNOLOGY

9 - 10

2.5 EXPECTED RESULT 10

2.6 CONCLUSION 10

3 METHODOLOGY

3.1 INTRODUCTION 11

3.2 PROJECT METHODOLOYG

3.2.1 PHASE 1 REQUIREMENT 12

3.2.2 PHASE 2 DESIGN 12

3.2.3 PHASE 3 IMPLEMENTATION 12

3.2.4 PHASE 4 TESTING 12

3.2.5 PHASE 5 DEPLOYMENT 13

3.3 SYSTEM REQUIREMENT

viii

3.3.1 SOFTWARE REQUIREMENT 13 - 14

3.3.2 HARDWARE REQUIREMENT 14

3.4 FRAMEWORK AND DESIGN 15

3.5 CONTEXT DIAGRAM 16

3.6 ENTITY RELATIONSHIP DIAGRAM (ERD) 17

3.7 DATA FLOW DIAGRAM (DFD)

3.7.1 DFD LEVEL 0 18 – 20

3.7.2 DFD LEVEL 1 PROCESS 1 20 – 21

3.7.3 DFD LEVEL 1 PROCESS 2 22 – 23

3.7.4 DFD LEVEL 1 PROCESS 4 23

3.8 DATA DICTIONARY 24 - 26

3.9 SCREENSHOT OF INTERFACE 27 - 29

3.10 CONCLUSION 29

4 IMPLEMENTATION AND TESTING

4.1 INTRODUCTION 30

4.2 SCREENSHOT OF INTERFACE 31 – 37

4.3 DATABASE DESIGN 38 - 40

4.4 TESTING

ix

4.4.1 INTRODUCTION 41

4.4.2 TEST CASE 41 – 49

4.5 CONCLUSION 49

5 DISCUSSION AND CONCLUSION

5.1 INTRODUCTION 50

5.2 PROJECT CONTRIBUTION 51

5.3 PROJECT CONSTRAINT 51

5.4 FUTURE WORK 51

5.5 CONCLUSION 51

REFERENCES 52

APPENDIX 53

GANTT CHART 54 - 55

x

LIST OF FIGURES PAGE

Figure 1 : PPHP Management 8

Figure 2 : PPHP Roles 8

Figure 3 : Priority-Based Algorithm 10

Figure 4 : Framework Of PPHP Equipment Management System 16

Figure 5 : Context Diagram 17

Figure 6 : Entity Relationship Diagram 18

Figure 7 : DFD Level 0 19

Figure 8 : DFD Level 1 Process 1 21



Figure 14 : Homepage of PPHP Equipment Management System 31

Figure 15 : Registration Page for Student 31

Figure 16 : Student Login 32

Figure 17 : List of Equipment 32

Figure 18 : Reservation Form 33

Figure 19 : Reservation Status 33

Figure 20 : Return or Damage Process 34

Figure 21 : Student Report 34

xi

Figure 22 : Admin Login 35

Figure 23 : Add Equipment 35

Figure 24 : Approval or Rejection 36

Figure 25 : Damage Process 36

Figure 26 : Report 37

Figure 27 : PPHP Equipment Management System Database 38

Figure 28 : Admin_Login Table 38

Figure 29 : Equipment Table 39

Figure 30 : Reserve Table 39

Figure 31 : user_detail Table 40

xii

LIST OF TABLES PAGE

Table 1 : List of Journal and article 5 - 7

Table 2 : Software Requirement 13 - 14

Table 3 : Hardware Requirement 14

Table 4 : Details of student’s table 24

Table 5 : Details of admin’s table 25

Table 6 : Details of equipment’s table 25

Table 7 : Details of reservation’s table 26

Table 8 : User registration 41 - 42

Table 9 : user login 42

Table 10 : Equipment list 42

Table 11 : Reservation Form 43

Table 12 : View Reservation Application 44

Table 13 : Return and Damage Equipment 45

Table 14 : Student report 46

Table 15 : Admin Login 46 - 47

Table 16 : Approval or Rejection 47 - 48

Table 17 : Damage Equipment 48

Table 18 : Report 49

xiii

LIST OF SCREENSHOTS PAGE

Figure 11 : Student Login 27

Figure 12 : List Of Equipment 28

Figure 13 : Reservation Form 29

xiv

LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram

DFD Data Flow Diagram

ERD Entity Relationship Diagram

1

CHAPTER 1

INTRODUCTION

1.1 BACKGROUND

UniSZA are provided the system where the students and staffs can reserve the

equipment that they need for events. The system that is going to develop is PPHP

management system. But PPHP management still using manual method to reserve the

equipment. The students or staffs need to fill the form to reserve the equipment for the

event. Then, they need to wait the approval for their application.

PPHP management system is a system that will help the students and staffs to

reserve the equipment for certain event. From this system, the user can make

reservation via online and they did not have to fill the form. It will display the

availability of the equipment that they need and it will ease the users to make sure that

the equipment they want to reserve is available or not.

The admin will decide whether the student application should be approved or

reject based on certain criteria. Then, admin will make the verification of the return of

equipment when the students return the equipment to PPHP management. This will

make the process of equipment reservation efficiently.

2

1.2 PROBLEM STATEMENT

PPHP Management system are located at Kampus Gong Badak and it has few

problem that had been figured :

1.2.1 Lack of Time and Transportation

Some of the students did not have transportation to go to PPHP that are located

at Kampus Gong Badak. Besides, the student did not have enough time to go there due

to the class schedule.

1.2.2 Lack of Equipment Details

Students did not know whether the equipment that they want to reserve are

available or not. The equipment may be not available at day the student want to reserve.

1.2.3 Keep Manually

Admin had to keep the information manually and the information might be

redundant. Admin also need to track the equipment manually whether the equipment

had been return or not.

Based on the problem stated above, there are a few solution that will solve this

problem and it will be mention at next section.

1.3 OBJECTIVE

Based on the problem statement that are listed above, the main objective of PPHP

Equipment Management System is to provide the online reservation system that will

make it easier for student to reserve the equipment. The objective of this system are:

i. To design the PPHP Equipment Management System

3

ii. To develop the system based on priority-based algorithm

iii. To test the system that will be develop

1.4 SCOPE

For this system, only two (2) scopes that will be covered :

1.4.1 Student

For student scope, the student can make the reservation of the equipment. The

purpose of this system is to provide a platform for student from Kampus Besut to

reserve the equipment at Kampus Gong Badak for certain event. The student also can

view the equipment that had been reserved for confirmation

1.4.2 Admin

For admin scope, the admin can create, read, update and delete the equipment

details. Admin will approve or reject the student application based on condition

that will be stated next chapter. Then, admin also will verify whether the

equipment that had been reserved is already return or not.

1.5 LIMITATION OF WORK

The limitation of work for this system is the time consume to complete the

system might be insufficient. Then, this system only can be viewed as a web-based

system and cannot be develop as mobile application. If the user want to reserve the

equipment, he or she must apply it in online mode and it cannot be apply in offline

mode.

4

CHAPTER 2

LITERATURE REVIEW

2.1 INTRODUCTION

An online management system has become very important in developing

technology for administration, documentation, tracking, reporting and delivery of

educational courses or training programs. They help the instructor deliver material to

the students, help admin to keep all the information and document organized. Some

companies try to manually manage their equipment, implementing paper-based

systems with high administrative costs and even higher chances of important

documents being defaced, lost or simply misplaced. In web-based technology, it can

view in computer and smartphone and it offer user-friendly online system. For this

system, the literature review involved studies of:

i. Gathering journal and article

ii. Review the similarity of the system available

Based on method above, it will be list in next section which is system analysis and

existing system.

5

2.2 SYSTEM ANALYSIS

Author’s

Name

Title Year Summary Objective Techniques

Thean,

Looi Kim

A Tool for the

Automation of

Membership Services

and Equipment

Management

(AMEMS)

2008 The typical usage on AMEMS will be on

membership registration and equipment

check in and check out process. Built in

with customization capability, AMEMS

allows staff members to create team

equipment and decide the pricing on

memberships to support the ever changing

events in UWL. Apart from this, staff

members can now print out receipts and

store the receipt for each membership for

to computerize the

current manual process

in order to make the

registration and

equipment checkout

processes fast and

accurate

-

6

record keeping in digital format.

Ronald

M.

Ramsaran

Development of a

Mobile Equipment

Management System

2000 A prototype Mobile Equipment

Management System (MEMS) has been

developed including hardware integration

and software development. The prototype

system not only demonstrates how new

and existing technologies can be integrated

to achieve new applications but also can

create efficiencies in collecting, processing,

distributing and storing pertinent

information of mobile equipment.

Investigate the theory on

satellite navigation and

positioning techniques

using GNSS to determine

the best-suited

positioning technique for

a Mobile Equipment

Management System.

Satellite

navigation

and

positioning

techniques

Davis, JR.

et

al.(2003)

Equipment

Management System

2003 The system incorporates a tagging device

to attach identification tags to each piece of

equipment. A reading device such as a

scanner, is used to read the identification

to organize and Store

information and

information is stored in

equipment management

-

7

tags and this information is ultimately

relayed to an equipment Server. An

input device is used to input information to

the equipment server. The equipment

server runs the equipment management

program.

databases.

Table 1 : List of Journal and article

8

2.3 EXISTING SYSTEM

PPH Management UMT

Universiti Malaysia Terengganu (UMT) has its own PPH Management. The

Sports and Welfare Club was established and the main objective is providing sports

facilities and recreation. In this system, the user can view the background and objective

of the system. This system did not provided the user to fill the username and password.

Figure 1 : PPHP Management

Figure 2 : PPHP Roles

9

2.4 RELATED TECHNIQUES

For this system, the technique that will use is priority-based algorithm. Priority-

based scheduling has two type, preemptive and non-preemptive. Non-preemptive

algorithms designed so that once a process enters the running state, it cannot be

preempted until it completes its allotted time, whereas the preemptive scheduling is

based on priority where a scheduler may preempt a low priority running process

anytime when a high priority process enters into a ready state. There are six processes

scheduling algorithm which is :

• First-Come, First-Served (FCFS) Scheduling

• Shortest-Job-Next (SJN) Scheduling

• Priority Scheduling

• Shortest Remaining Time

• Round Robin(RR) Scheduling

• Multiple-Level Queues Scheduling

For this system, scheduling process that will be used are Priority Scheduling. This

process is non-preemptive algorithm and it is the most common scheduling algorithm.

Each process will be assigned a priority and the highest priority will be executed first.

10

Figure 3 : Priority-Based Algorithm

2.5 EXPECTED RESULT

The expected result for this system is it will be a web-based system and the

student can use this system to make reservation. The user also need to apply it in online

mode and connected to the Internet. Next, the students especially from Kampus Besut

can apply the reservation via online and they did not have to go to Kampus Gong

Badak. The information of the equipment will not be redundant and the admin did not

have to keep it manually.

2.6 CONCLUSION

Overall of this chapter, the article or requirement that are researched will give

impact for this system. Based on the research that had been studied, it can be the

references for this project. The requirement that had been collected can be use when

the system will develop and we get the requirement to develop the system.

11

CHAPTER 3

METHODOLOGY

3.1 INTRODUCTION

Methodology is important in system development because it is used to plan,

structure and control the process of developing the system. In this chapter, it will be

cover the detail in explaining of methodology that will be used to develop this system

and to make it complete and working well. There are three types of methodologies of

system development which is traditional, contemporary and radical. In traditional

methodology, the common methodology is System Development Life Cycle (SDLC).

In SDLC, there are few types of method which is waterfall model, spiral development,

V-shaped model, evolutionary prototyping model, iterative and incremental method

and last is agile development. Waterfall model has been chosen to develop this system.

12

3.2 PROJECT METHODOLOGY

Based on Waterfall method, there are six phase of software development which

is the first phase is requirement, next is design, implementation, testing and

deployment.

3.2.1 Phase 1: Requirement

In this phase, the abstract and the project to be chosen is discussed with the

supervisor. The project that has been chosen is PPHP Equipment Management System

and Priority-based Technique. Next, based on user requirement, start writing the

proposal and state the problem statement, objectives and scope.

3.2.2 Phase 2: Design

In design phase, start design context diagram (CD), Entity Relationship

Diagram (ERD), Data Flow Diagram (DFD), interface and database. ERD will show

the relationship between database entities with the system. Meanwhile, DFD is a

graphical representation of the way of data through an information system.

3.2.3 Phase 3: Implementation

The system that will be developed is a web-based system and internet browser

and server are used to run the system. PPHP Equipment Management System are

developed using PHP as a server scripting language. The database that will be used is

PHPMyAdmin and XAMPP as the web browser.

3.2.4 Phase 4: Testing

This system will be test in every level to ensure that the system functionally

working and meet its requirement. If there is any error occur, design activity will be

performed again.

13

3.2.5 Phase 5: Deployment

When the system is ready, it is stated that the system has meet all the objectives

in the project for satisfactory result. If the system is free from bug, the user can use

this system.

3.3 SYSTEM REQUIREMENT

During the development process, there are 2 types of system requirements that

have to be fulfilled which is software requirement and hardware requirements.

3.3.1 Software Requirement

Software requirement is a tool that will be used to make a report and develop

the system. Software that are needed during this project development is shown below:

NO SOFTWARE DESCRIPTION

1 Microsoft Office

• Microsoft Word 2016

• Microsoft Power Point 2016

Tools for creating, editing and view the

document and slide

2 Web Browser

• Google Chrome

• Mozilla Firefox

Web browser used to gather the

information and detail about the project

3 Local Web Server

• XAMPP

• PHPMyAdmin

Act as platform to run this system

4 Open Source

• Windows 10

Use to develop the project

14

5 Data Storage

• Dropbox

Use to keep the project as a backup

Table 2 : Software Requirement

3.3.2 Hardware Requirement

Hardware requirement is a device that will be used in this project. Hardware

that are needed during this project development is shown below:

NO HARDWARE DESCRIPTION

1 Laptop OS : Windows 10

Processor : Intel Core i5

RAM: 4GB

Function : to develop the system

2 Printer Name : HP Deskjet 2520hc

Function : submission of abstract and the report

3 Pendrive Name : Sandisk FlashDrive(8GB)

Function : For transferring the data and system backup

Table 3 : Hardware Requirement

15

3.4 FRAMEWORK AND DESIGN

Figure 4 : Framework Of PPHP Equipment Management System

Figure 4 shows the framework of PPHP Equipment Management System.

Based on this figure, it will show the flow of the system. Firstly, student need to login

to the system and the student will proceed to equipment reservation. Student need to

check whether the equipment that are needed are available or not. If it is available, it

will proceed to reserve equipment. The detail of reservation will be insert to database.

Next, admin need to login to the system. Then, if there is any reservation

application, admin will make approval or rejection based on condition that will be

listed. Then, the approval status notification will be send to the student that make

application.

16

3.5 CONTEXT DIAGRAM

Figure 5 : Context Diagram

3.5.1 Student

Figure above show the context diagram of the system. Based on the diagram,

student need to register first if they not registered yet. Next, student can make a

reservation based on the equipment that are available.

3.5.2 Admin

For admin, he/she need to login to the system and admin can view the

equipment detail either the admin want to update the equipment status, delete the

equipment that not provided anymore or view the status of equipment.

Based on context diagram above, entity relationship diagram will be develop based on

context diagram in next section.

17

3.6 Entity Relationship Diagram (ERD)

Figure 6 : Entity Relationship Diagram

Based on figure above, the relationship between user which is student will

make a reservation that have the details which is date reserve, date return, reserve item,

equipment detail, reserve id as a primary key and equipment id as a foreign key from

table Equipment. Then, reservation will have equipment that has the detail about

equipment id as a primary key, equipment status and equipment name. Reservation

will have an approval. Admin will manage the equipment and student information.

Damage table for the equipment that already damage and not available to reserve. The

attribute damage id which is the primary key, damage equipment and damage quantity.

18

3.7 DATA FLOW DIAGRAM

3.7.1 Data Flow Diagram Level 0

Figure 7 : DFD Level 0

Figure above shows the entity relationship diagram of the system. Based

on the ERD above, the flow of the system will be shown and there are 6 databases for

this data flow diagram. For this system, there are 5 processes which is student profile,

reservation application, reservation approval, return of equipment and the last process

is report process. For this system, there are only two (2) scopes; student and admin.

19

3.7.1.1 Student Profile

In this process, the student will log in to the system by using matric

number and password. If that student’s detail did not have in UniSZA’s student

database, he or she need to register first.

3.7.1.2 Reservation Application

In reservation application process, the student can make the reservation

by fill the form of reservation. When the application is already formed, the detail will

be directed to reservation detail database. Then, the applicant need to wait for a while

for availability process.

3.7.1.3 Reservation Approval

At this process, admin will make the verification whether the reservation

is fulfill the condition that had been stated or not. Then, admin will approve or reject

the application. The reservation detail will be taken from reservation detail database.

Then, if the application is approved, it will insert into on reserve detail database.

3.7.1.4 Return of Equipment

When the student returned the equipment, the equipment will be checked

first. It is to make sure that the equipment returned in good condition. If the equipment

is damage, the equipment detail will be in damage database and the applicant need to

pay the fine that will be stated. But if the equipment is in good condition, it will be

insert into return detail database.

20

3.7.1.5 Report

Based on return detail, admin will print out the report of reservation and

it will be given to the student. The detail about the report will be keep in report database

for references.

3.7.2 Data Flow Diagram Level 1 Process 1

Figure 8 : DFD Level 1 Process 1

3.7.2.1 Register Process

Figure 8 shows the dfd level 1 for process 1 which is student profile. If

the student not registered yet, he or she need to register first. Then, the data will be

insert to UniSZA’s student database. It will set as student UniSZA. This process only

for student that not registered yet. In register form, there are some details that will

verify that the student is UniSZA student and it will not duplicate with other student

which is matric number.

21

3.7.2.2 Login

When the student log in to the system, it need to insert the input that are

required which is matric number and password. Then, the data will be compared with

the database in UniSZA’s student. This is to make sure that the input that had been

insert are similar with data in UniSZA student database.

3.7.2.3 Denial Process

If the data that had been insert are wrong, it will give the feedback to the

student that the input had been insert are wrong and not match with the detail in

database.

22



3.7.3.1 Reserve Equipment Process

Figure 9 shows the data flow diagram level 1 for process reservation

application. Based on the diagram above, student will make a reservation by fill the

detail that required for reserve an equipment.

3.7.3.2 Equipment Status Process

Then, student can view the status of the equipment whether the equipment

is already reserved or not. In this process, student will know the equipment that they

want to reserve is available or not.

23

3.7.3.3 Reservation Submission Process

If the equipment available, admin will approve the process. But if the

equipment are not available, it will reject the process. Admin will notify the approval

or rejection of the reservation.



3.7.4.1 Return Process

Figure 10 shows the DFD level 1 process 4 which is return of equipment.

If student return the equipment in good condition, the data will be insert to return

equipment.

3.7.4.1 Damage Process

But if the equipment that had been return are damage or lose, the student

will need to pay the damage and it will insert to damage detail. There are a few steps

for the equipment that student need to follow. The details of the equipment that already

damage will be remove from equipment reservation detail.

24

3.8 DATA DICTIONARY

Data dictionary is a set of files that will contain a database’s metadata. It

will contains the records about other objects in database. Based on this system, it has

four(4) databases which is Admin, Reserve, Equipment, and user_detail.

3.8.1 User Detail

Table 4 shows the attributes in user detail’s Table. In this table, it will

keep student data which is matric_no, name, password, gender and course. These data

for student’s login. For this table, the primary key is matric_no.

Attribute Name Data Type Size Remark

Matric_no Varchar 20 Primary Key(PK)

Name Varchar 100 Null

Password Varchar 20 Null

Gender Varchar 100 Null

Course Varchar 100 Null

Table 4 : Details of student’s table

25

3.8.2 Admin

Table 5 shows the attributes in Admin’s Table. In admin table, it will keep

admin data which is admin_id and password. For this table, the primary key is

admin_id.


Admin_id Varchar 20 Primary Key(PK)

Password Varchar 20 Null

Table 5 : Details of admin’s table

3.8.3 Equipment

Table 6 shows the attributes in Equipment’s Table. For equipment’s table,

it will keep equip_id, equipment_name, status and equip_quantity. The details of

equipment will be keep in this table. The primary key for this table is equip_id.


Equip_id Varchar 20 Primary Key(PK)

Equipment_Name Varchar 100 Null

Status Varchar 10 Null

Equip_quantity Varchar 100 Null

Table 6 : Details of equipment’s table

26

3.8.4 Reservation

Table 7 shows the attributes in Reservation’s Table. When student make

reservation, the detail will be insert in this table. The detail for this table is reserve_id,

matric_no, Book_type, date_reserve, date_return, reserve_quantity, time_reserve,

time_return, id_equip and Status. Reserve_id remark as primary key, meanwhile

id_student is a foreign key from user detail table and id_equip is a foreign key from

equipment table.


Reserve_id Varchar 100 Primary Key(PK)

Matric_no Varchar 100 Foreign Key (FK)

Book_Type Varchar 100 Null

Date_reserve Date None Null

Date_return Date None Null

Reserve_quantity Varchar 100 Null

Time_reserve Time None Null

Time_return Time None Null

Id_Equip Varchar 100 Foreign Key (FK)

Status Int 100 Null

Table 7 : Details of reservation’s table

27

3.9 SCREENSHOT OF INTERFACE

Figure 11 : Student Login

Figure 11 show the interface of student login page. In his page, student

must login to the system by insert matric number and password that inserted in

login database. For example, the matric number that had been registered is 010101

and the password is 12345. The system will compare with data in login database

whether it is same or not.

28

Figure 12 : List Of Equipment

Figure 12 shows the list of equipment that student can reserve. It will show

the table that have details of number, equipment id, equipment name and the action

is reserve. When the student click button reserve, it will directed to the next page

for reservation detail.

29

Figure 13 : Reservation Form

Figure 13 shows the reservation form. In this page, the student need to fill

in a few details for reservation. The student need to fill the date reserve and also

date returned.

3.10 CONCLUSION

PPHP Equipment Management System is a system that will help the

students from Kampus Besut to reserve the equipment for certain event. Based on this

sytem, the students will know the availability of the equipment that they want to

reserve. Priority-based algorithm are used to develop this system and when the student

want to reserve the equipment, it will update the priority based on type of booking.

Context diagram, entity relationship diagram (ERD) and data flow diagram(DFD) are

needed to develop the system. Based on that, the system can be developed step by step

and the method are very important. If the system that needed to be developed did not

have method, it will be a problem if there is an error while develop the system.

30

CHAPTER 4

IMPLEMENTATION AND TESTING

4.1 INTRODUCTION

This chapter will explain the process during implementation phase. It will

explain the construction of the actual project result. It involves the developing of

system interfaces, and databases that are required. In implementation phase, the project

visible to users or outsiders. In next section, it will provide the interfaces of the system

that had been developed.

31

4.2 SCREENSHOT OF INTERFACE

4.2.1 Homepage PPHP Equipment Management System for Student

Figure 14 : Homepage of PPHP Equipment Management System

Figure 14 display about the homepage of system for student and admin. There

are eight menus which are Home, About Us, List of Equipment, Login, Register,

Report and Contact Us.

4.2.2 Registration for Student

Figure 15 : Registration Page for Student

32

Figure 15 shows the interface of registration for student. To proceed to the next

process, student need to register.

4.2.3 Student Login

Figure 16 : Student Login

When the student are already registered, it will directed to login page. Student

need to login the system to proceed to the next page which is list of equipment that can

be reserved.

4.2.4 List of Equipment

Figure 17 : List of Equipment

33

Figure 17 shows the list of equipment. Based on this list, the student can make

the reservation by click on button “Reserve”. Then, it will directed to the next page in

next section.

4.2.5 Reservation Form

Figure 18 : Reservation Form

Based on figure above, it shows the form that the student need to fill in before

the reservation process complete. After the student fill the form, they have to wait for

admin to approve or reject the reservation application.

4.2.6 Reservation Status

Figure 19 : Reservation Status

Based on Figure 19, it shows the reservation status. If the admin not approve

yet the reservation, the status will show as “Pending”. When the admin approved the

application, the status will change to “Reservation Approved”. But if the admin

rejected the application, the status will become “Reservation Rejected”. If the

34

applicant wish to cancel the reservation, the user need to click the button “Cancel

Reserve” to cancel the reservation.

4.2.7 Return Process

Figure 20 : Return or Damage Process

Figure 20 shows the list of equipment that had been reserved by the user. When

the user need to return the equipment, he or she need to click the button “Return”. But

if the equipment is damaged, the user need to click button “Damage”. The status of

reserve will be changed when the user click the button.

4.2.8 Student Report

Figure 21 : Student Report

Figure 21 shows the table of report. In this table, the user can view the

equipment that they reserve, date and time reserved and return and also the status of

application.

35

4.2.9 Admin Login

Figure 22 : Admin Login

Figure 22 shows the admin login page. Admin need to insert Admin_id and

password to log in and proceed to next page.

4.2.10 Add Equipment

Figure 23 : Add Equipment

In this page, admin can add the equipment that will be shown to the users.

Admin need to insert the equipment id, equipment name and the quantity. The details

will be saved in database.

36

4.2.11 Approval or Rejection Reservation Application

Figure 24 : Approval or Rejection

Figure 24 shows the approval or rejection page. Admin will approve the

application when the priority number are number 1. Based on priority, number 1 is the

most important and admin must approve it. If the priority is number 2 or 3, admin must

consider the situation.

4.2.12 Damage Process

Figure 25 : Damage Process

37

Figure 25 shows the damage process. Admin will update the quantity of

damaged equipment and the equipment status will changed to “Damage” status.

4.2.13 Report

Figure 26 : Report

Figure 26 shows the report of the reservation. In this table, it shows the

equipment name, user that reserve it, date and time reserved and returned, quantity of

reserved and the reservation status.

38

4.3 DATABASE DESIGN

Database design is the organisation of data based on a database model. The

data that must be stored and how the data will inter-related will be determine by the

designer. Based on the figure below, it shows the table that will be used in this system.

Figure 27 : PPHP Equipment Management System Database

Based on figure above, it shows the table of database. It consists of

admin_login table, equipment table, reserve table and lastly is user_detail table.

4.3.1 Admin_Login Table

Figure 28 : Admin_Login Table

Figure 28 shows the admin_login table. In this table, it consist of admin_id

which is primary key for this table and password. Both attribute are varchar type. For

39

this table, when admin log in into the system, it will compare with the data in this table.

If the data is same, admin can proceed to the next page.

4.3.2 Equipment Table

Figure 29 : Equipment Table

Figure 29 shows the equipment table. The attribute for this table are equip_id

which is primary key, Status for equipment status which is it has three status ;

Available, Not Available and Damage. Next attribute is Equipment_name and lastly

quantity. Admin will insert the details of equipment and will be saved in this table.

4.3.3 Reserve Table

Figure 30 : Reserve Table

Based on Figure 30, it shows the attribute of reserve table. The attribute that

are listed in this table are Reserve_Id which is primary key, Matric_No and Id_Equip

40

are both foreign key. Next, Book_Type stand for priority which is the user need to fill

the book type with three types ; University, Organization and Student. Next attribute

is Date_reserve, Date_return, time_reserve, time_return, quantity and status. The

status will change from 0 to 1 when the user submit the application.

4.3.4 user_detail Table

Figure 31 : user_detail Table

Based on Figure 31, it shows the user_detail table. In this table, it involved

with user registration and also user log in. in this table, it has id as primary key and id

in auto increment. Next, it has name, no_matric, password, gender and course. For

registration, it will be used all this attribute. But in log in, it will make comparison

with matric_no and password only.

41

4.4 TESTING

4.4.1 INTRODUCTION

This section will discuss the module of testing the system by using Test Case.

The process to be done are using priority based and admin will approve it by view the

priority number. Purpose of testing phase to determine the system are ready for

implementation and if there is an error, it should be fix before the page is loaded.

4.4.2 TEST CASE

The system will be tested by using Test Case. Test Case is a set of conditions

or variable which a tester will determine whether a system under test satisfies the

requirement correctly. This system will be tested within the scope, which is user and

admin.

4.4.2.1 User Registration

Step Procedure Expected Result

1 Go to http://localhost/register.php Registration page appear

2 Enter the detail

Name : Nabilah

Matric Number : 040806

Password : nabilah

Gender : Female

Course : KI

42

3 Click “Register” button Popup message appeared

Table 8 : User registration

4.4.2.2 User Login


1 Go to http://localhost/student_login.php Login page appear.

2 Enter the detail


3 Click “Login” button It will be redirected to

another page.

Table 9 : user login

4.4.2.3 Equipment List


1 Go to http://localhost/list.php Equipment list page

appeared

2 Click “Reserve” button on reservation list It will redirect user to the

form page

Table 10 : Equipment list

43

4.4.2.4 Reservation Form

Step Procedure Expected

Result

1 Go to http://localhost/reserve1.php Reservation

form page

appeared

2 Enter the detail

Id : B008 // Id display and cannot change

Equipment Name : Bola Futsal //Equipment name display and

cannot change

Booking Type : University

Date Reserve : 20/8/2018

Date Return : 27/8/2018

Time Reserve : 12.20 PM

Time Return : 01.30 PM

Quantity : 2

3 Click “Submit” button Popup message

will appear

Table 11 : Reservation Form

44

4.4.2.5 View Reservation Application


1 Go to http://localhost/viewstudent.php Reservation list

page appeared

2 View the detail







Quantity : 2

3 Click “Submit” button Popup message will

appear

Table 12 : View Reservation Application

45

4.4.2.6 Return and Damage Equipment


1 Go to http://localhost/return.php Return equipment

page appeared

2 View the reservation detail







Quantity : 2

Status : Reserve

3 Click “Return” button Popup message about

equipment return will

appear

4 Click “Damage” button Reservation status

will change to

damaged equipment

Table 13 : Return and Damage Equipment

46

4.4.2.7 Student Report


1 Go to http://localhost/report.php Report page appeared

2 View the report detail

Equipment Name : Bola Futsal

User Name : Nabilah





Quantity : 2

Status : Reserve

Table 14 : Student report

4.4.2.8 Admin Login


1 Go to http://localhost/admin_login.php Login page appear.

2 Enter the detail

Admin id : 010101

Password : 123456789

47

3 Click “Login” button It will be redirected to

another page.

Table 15 : Admin Login

4.4.2.9 Admin Approval or Rejection


1 Go to http://localhost/admin_.php Login page appear.

2 View the reservation detail

Equip Id : B008






Quantity : 2

Priority : 1

Admin will approve the

reservation with priority

of 1

3 Click “Approve” button Reservation status will

change from “Pending” to

“Reservation Approved”

4 Click “Reject” button Reservation status will

change from “Pending” to

48

“Reservation Not

Approved”

Table 16 : Approval or Rejection

4.4.2.10 Damage Equipment


1 Go to http://localhost/damage.php Damage page appear.

2 Enter the detail

Id : B008

Name : Bola Futsal

Quantity : 2

Admin need to enter the

quantity of damaged

equipment

3 Click “In Maintenance” button Popup message will

appear

Table 17 : Damage Equipment

49

4.4.2.11 Report

Table 18 : Report

4.5 CONCLUSION

The system had been implemented to help the user to make reservation easily.

The system had been designed to help the system operate better, efficiently and

effectively. Each scope of this system which is user and admin has their own interface.

It will help the admin to keep the data efficiently and there will be no data redundancy.


1 Go to http://localhost/adminreport.php Report page appear.

2 View the detail

Equipment Name : Bola Futsal

User Name : Nabilah





Quantity : 2

Status : Reserve

50

CHAPTER 5

DISCUSSION AND CONCLUSION

5.1 INTRODUCTION

In this chapter, it will present the conclusion, constraint when developed this

system and the future work of the proposed project. Aim for this chapter is to

summarize the project. The constraints when developed this system will be stated in

this chapter. Then, there are several improvements for the future work of this project.

51

5.2 PROJECT CONTRIBUTION

At the end of this project, it can be assumed that the objective of this project is

achieved. This project produces a system that user will know about their reservation

application status. This system will show the list of equipment based on the equipment

status and it also show the status of reservation application to the user.

5.3 PROJECT CONSTRAINT

When the project fully developed, there are a few constraints in this project.

When the user already reserved the equipment, the quantity of equipment will not

reduce in database. Next, when the user returned the equipment, it did not view the

receipt of reservation to the user. The project constraint can be prevented in the future

work in the next section.

5.4 FUTURE WORK

In this section, there are several suggestions to improve the system in the

future. The project constraints that had been mentioned in previous section can be

improve in the future. In the future, this system can be develop in mobile application.

5.5 CONCLUSION

The reservation management are important in UniSZA especially for students

in UniSZA Kampus Besut. This project can help the student in Kampus Besut to make

the reservation application easily and reduced time.

52

REFERENCES

[1] Calgary. Davis Jr, T. L., & Doser, D. E. (2013). U.S. Patent Application No.

13/758,933.

[2] Haupt, R. (1989). A survey of priority rule-based scheduling. Operations-

Research-Spektrum, 11(1), 3-16.

[3] Ramsaran, R. M. (2000). Development of a mobile equipment management system.

[4] Thean, L. K. (2008). A Tool for the Automation of Membership Services and

Equipment Management (Doctoral dissertation, University of Wisconsin--La Crosse).

53

APPENDIX

54

APPENDIX

Gantt Chart

FYP 1

ACTIVITY WEEK

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Topic Discussion

and Determination

Project Title

Proposal

Introduction

Literature Review

Proposal

presentation and

review

Discussion and

correction proposal

Methodology

Proof of concept

Draft Report

Draft submission to

55

FYP 2

Activity Week

1 2 3 4 5 6 7 8

Presentation 1

Documentation

Presentation 2

supervisor

Seminar Presentation

Report correction

Final report

submission

Documents

PPHP EQUIPMENT MANAGEMENT SYSTEM NUR NABILAH BINTI …