surau ar-raudhah assets management system …

SURAU AR-RAUDHAH ASSETS MANAGEMENT SYSTEM

(USING WEIGHTED SUM MODEL)

MARIYAM JAMIELAH JAINUDIN

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE DEVELOPMENT) WITH HONOURS

FACULTY OF INFORMATICS AND COMPUTING

UNIVERSITI SULTAN ZAINAL ABIDIN

2019

i

DECLARATION

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

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

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

Abidin or other institutions.

_____________________________

Name : Mariyam Jamielah Jainudin

Date : ……………………………

ii

ENDORSEMENT

This is to confirm that:

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

___________________________________

Name : Dr. Ahmad Nazari bin Mohd Rose

Date : …………………………………...

iii

DEDICATION

First of all, I express my gratitude to Allah SWT for the health and strength

that He gave to His servant to complete this final year project, Surau Ar-Raudhah

Assets Management System (using Weighted Sum Model). Peace and blessings be

upon to the Prophet Muhammad SAW.

This study is wholeheartedly dedicated to my beloved parents, who have been

my source of inspiration and strength when we thought of giving up, who continually

provide their moral, spiritual, emotional, and financial support.

To my supervisor, Dr. Ahmad Nazari bin Ahmad Rose for his advices,

guidance and support toward this project. Also, thanks to all the panels and lecturers

for their attention and opinions on my project especially En. Mohd Khalid bin Awang,

Dr. Mumtazimah binti Mohamad and Prof. Dr. Mohd Nordin bin Abd Rahman.

And lastly to my sisters, friends and classmates who shared their words of

advice and encouragement to finish this project.

iv

ABSTRACT

Surau Ar-Raudhah Assets Management System is introduced to help JaPSAR

in managing Surau’s lend transaction. Surau has been the main place to borrow tools

for any occasions or programs. There have been some problems existed such as

missing and damages of assets. Using Weighted Sum Model (WSM), the system will

provide a solution if there are two or more association make lend transaction at the

same time. This will ensure borrower is prioritized based on their lend history. With

this system, it eases the lend transaction and produces a lend system for both

JaPSAR(admin) and borrower(user). This system is 70% successfully developed on

the given dateline and has met the system objectives and requirements.

v

ABSTRAK

Sistem Pengurusan Aset Surau Ar-Raudhah diperkenalkan untuk membantu

JaPSAR menguruskan pinjaman barang Surau. Surau adalah tempat utama bagi

persatuan-persatuan lain untuk meminjam barang-barang yang biasanya digunakan

dalam program-program atau majlis-majlis. Namun, barang-barang Surau

kebanyakannya hilang atau rosak selepas barang dikembalikan. Menggunakan

Weighted Sum Model (WSM), sistem ini akan memberi keputusan jika terdapat dua

atau lebih persatuan membuat permohonan pinjaman pada masa yang sama. Ini bagi

memastikan peminjam akan diberi keutamaan berdasarkan rekod pinjaman mereka.

Dengan sistem ini, ia memudahkan proses pinjaman barang dan menghasilkan satu

sistem untuk JaPSAR(admin) dan peminjam(pengguna). Sistem ini berjaya

dibangunkan sebanyak 70% dalam masa yang telah ditetapkan dan dapat mencapai

objektif dan keperluan sistem.

vi

CONTENTS

Page

DECLARATION i

ENDORSEMENT ii

DEDICATION iii

ABSTRACT iv

ABSTRAK v

CONTENTS vi

LIST OF FIGURES x

LIST OF TABLES xii

LIST OF ABBREVIATIONS xiv

LIST OF APPENDICES vi

CHAPTER 1 INTRODUCTION

1.1 Introduction 1

1.2 Problem Statement 2

1.3 Objectives 3

1.4 Scope of the User 3

1.4.1 Admin 4

1.4.2 User (Borrower) 4

1.5 Scope of the System 4

1.6 Limitation of Works 5

1.7 Expected Outcome 6

1.8 Chapter Summary 6

vii

CHAPTER 2 LITERATURE REVIEW

2.1 Introduction 7

2.2 Multi-Criteria Decision Making 7

2.3 MCDM Method Explanation 8

2.4 Research on Weighted Sum Model 9

2.4.1 Application of Weight Sum Model

(WSM) In Determining Special Allocation

Funds Recipients

9

2.4.2 Comparison of Weighted Sum Model

and Multi Attribute Decision Making

Weighted Product Methods in Selecting the

Best Elementary School in Indonesia

10

2.5 Comparison of SDLC Methodologies 11


CHAPTER 3 METHODOLOGY

3.1 Introduction 14

3.2 Agile Model 15

3.2.1 Basic Stages of Agile Model 17

3.2.2 Advantages and Disadvantages of Agile

Model

19

3.3 System Requirements 20

3.3.1 Software 20

3.3.2 Hardware 21

viii

3.4 Framework and Design 22

3.4.1 Context Diagram 23

3.4.2 Data Flow Diagram 24

3.4.3 Entity Relationship Diagram 25

3.4.4 Framework Design 26

3.4.5 Algorithm (Weighted Sum Model) 27


CHAPTER 4 IMPLEMENTATION AND RESULT

4.1 Introduction 32

4.2 Implementation and Output 33

4.2.1 Database Design 33

4.2.2 Interface Design 37

4.2.2.1 User Interface (Borrower) 37

4.2.2.2 Admin Interface 45

4.3 Testing 55

4.3.1 Types of Testing 55

4.3.2 Test Cases 55

4.3.2.1 User Test Case 56

4.3.2.2 Admin Test Case 61


CHAPTER 5 CONCLUSION

5.1 Introduction 68

5.2 Project Contribution 68

ix

5.3 Limitation 69

5.4 Recommendations 69

5.5 Summary 70

REFERENCES 71

x

LIST OF FIGURES

FIGURE TITLE PAGE

3.1 Type of SDLC Model 15

3.2 Agile Model 15

3.3 Graphical Illustrations of the Agile Model 17

3.4 Context Diagram 23

3.5 Data Flow Diagram Level 0 24

3.6 Entity Relationship Diagram 25

3.7 Framework Design 26

4.1 Sams Database 33

4.2 Table Admin 33

4.3 Table Assets 34

4.4 Table Asset_Defect 34

4.5 Table Asset_Lend 35

4.6 Table Borrower 35

4.7 Table Fine 36

4.8 Table Lend 36

4.9 Login Page Interface for User 37

4.10 Alert Message for Wrong Username or Password 37

4.11 Homepage Interface for User 38

4.12 Pinjaman Button Dropdown 38

4.13 Profil Button Dropdown 39

4.14 Senarai Aset Interface 39

4.15 Permohonan Pinjaman Aset Interface 1 40

xi

4.16 Permohonan Pinjaman Aset Interface 2 40

4.17 Alert Message for Successful Lend Transaction 41

4.18 Status Permohonan Interface 41

4.19 Senarai Aset Permohonan Interface 42

4.20 Profil Pengguna Interface 42

4.21 Alert Message of Successful Update for User Profile 43

4.22 Ubah Kata Laluan Interface 43

4.23 Register Page Interface for User 44

4.24 Login Page Interface for Admin 45

4.25 Homepage Admin Interface 46

4.26 Pengguna Button Dropdown 46

4.27 Permohonan Button Dropdown 47

4.28 Aset Button Dropdown 47

4.29 Laporan Button Dropdown 47

4.30 Rekod Pengguna A-Sar Interface 48

4.31 Rekod Permohonan Aset Interface 49

4.32 Application Details Interface 50

4.33 Update Application Status 50

4.34 Borang Aset Hilang/Rosak Interface 51

4.35 Senarai Aset A-Sar Interface 52

4.36 Tambah Aset Baru A-Sar Interface 52

4.37 Laporan Pinjaman Aset Interface 53

4.38 Laporan Kerosakan Aset Interface 53

4.39 Laporan Kehilangan Aset Interface 54

4.40 Laporan Pinjaman Interface 54

xii

LIST OF TABLES

TABLE TITLE PAGE

2.1 Comparison of Waterfall, Spiral and Agile Model 11

3.1 Advantages and Disadvantages of Agile Model 19

3.2 List of Software 20

3.3 List of Hardware 21

3.4 Algorithm Calculation: Step 4 28

3.5 Algorithm Calculation: Step 5(a) 29

3.6 Algorithm Calculation: Step 5(b) 29



4.1 Test Case Registration 56

4.2 Test Case User Login Fail 57

4.3 Test Case User Login Success 57

4.4 Test Case View List of Assets 58

4.5 Test Case Apply and View Lend Application 58

4.6 Test Case Change Password 59

4.7 Test Case Update User Profile 60

4.8 Test Case Admin Login Fail 61

4.9 Test Case Admin Login Success 62

4.10 Test Case View List of Users 62

4.11 Test Case View and Update Lend Application 63

4.12 Test Case Submit Report of Damage or Missing Asset 64

4.13 Test Case View List of Assets 64

4.14 Test Case Add New Asset 65

xiii

4.15 Test Case Generate Asset Lend Report 66

4.16 Test Case Generate Asset Damage Report 66

4.17 Test Case Generate Asset Missing Report 67

xiv

LIST OF ABBREVIATIONS

AHP Analytic Hierarchy Process

A-Sar Surau Ar-Raudhah Assets Management System

DFD Data Flow Diagram

DM Damage or missing of asset

FYP Final Year Project

JaPSAR Jawatankuasa Pengurusan Surau Ar-Raudhah

LR Damage or missing of asset

MADWMP Multi Attribute Decision Making Weighted Product Methods

MCDM Multi-Criteria Decision Making

SDLC Software Development Life Cycle

SL Satisfactory lend without any problem

TOPSIS Technique for Order of Preference by Similarity

UniSZA Universiti Sultan Zainal Abidin

WSM Weighted Sum Model

xv

LIST OF APPENDICES

APPENDIX TITLE PAGE

A Gantt Chart FYP I 74

B Gantt Chart FYP II 77

1

CHAPTER 1

INTRODUCTION

1.1 Introduction

Kampus Besut is one of the campus in Universiti Sultan Zainal Abidin with only

two faculty. There are many associations in UniSZA Kampus Besut including

Jawatankuasa Pengurusan Surau Ar-Raudhah or known as JaPSAR.

JaPSAR is the responsible association in managing Surau Ar-Raudhah such as

making programs to encourage students come to Surau, provide a duty schedule of

Imam and Bilal and many more. JaPSAR is also responsible in managing Surau assets.

Surau Ar-Raudhah has been the main place for other associations to borrow

tools for any program or occasion. Unfortunately, students take the existing facilities

for granted. There has been some problem after students borrow these assets such as

missing items, damages and many more.

Due to these problems, quantity of assets is reduced by a lot causing JaPSAR to

replace the missing and damage assets even though they are not the one who is

2

responsible of the missing and the damage of assets. This also led JaPSAR to look for

funds to replace the assets.

These problems sometimes cannot be solved by JaPSAR because lack of

information storage and strong agreement between JaPSAR and the borrower. One way

to solve this problem is to have a management system that could manage and store all

the lend transaction.

Thus, the Surau Ar-Raudhah Assets Management System using Weighted Sum

Model has been introduced in order to solve the problem. This system will provide user

categorization using Weighted Sum Model algorithm. Thereby, admin can choose to

prioritize which user, if there is a clash in user’s applications. Also, with this system,

admin could refuse the applications from association that not yet replace the damage

and missing assets.

1.2 Problem Statement

i. The information storage for lend transaction has been done manually by writing

it down on paper.

▪ Some of the transactions might not be written down because of overlooked.

▪ The documents could be missing or damaged.

▪ There is no place to store all the documents and reports.

ii. Giving permissions to the borrower though there have been problems in

previous lend.

▪ The problem association could not be detected causing the same problem to

repeat without taking any actions.

3

▪ There is no action taken to the existing problem such as replace the missing

assets.

iii. There are two or more association make lend transaction on the same time.

▪ There is no rules and criteria in choosing between two associations.

1.3 Objectives

The objectives of developing Surau Ar-Raudhah Assets Management System are:

i. To design a web-based system for Surau Ar-Raudhah Assets Management

System that helps admin to manage their lend transaction.

ii. To develop a system that help admin in categorize type of borrower.

iii. To implement a system that assist admin to make the best and suitable

judgement in letting other associations borrowing the assets using Weighted

Sum Algorithm.

1.4 Scope of the User

The scope of the system means what will be covered in the research project

and who involves in the system. It defines clearly the extent of the content that will be

covered by the whole system. The scope of the study has to be defined at a preliminary

stage and it is very important to do it as early as possible.

The target users are the representative of associations (students) in UniSZA

Kampus Besut and the admin.

4

1.4.1 Admin

i. Register and log in as admin.

ii. Manage user.

iii. Manage assets.

iv. Update lend status.

v. Generate report.

1.4.2 User (Borrower)

i. Register and log in as user.

ii. Apply for lend.

iii. Print lend statement.

1.5 Scope of the System

In this Surau Ar-Raudhah Assets Management System, the user needs to

register and login into the system to make lend transaction. In this system, user can see

the assets provided for lending. To make the lend transaction, the user needs to enter

information needed for lending including lend date, lend time, lend purpose, and stage

of the program either faculty, university or international. Next, user needs to choose the

assets they want to borrow and the asset quantity. Once the lend transaction has been

submitted, user needs to wait for the result whether it is been approved or rejected by

admin.

5

The lend transactions will be managed by admin. If the admin has approved it,

it will appear in the user’s account. Admin will state the time and date for the user to

take and return the borrowed assets. The user can print out the lend statement and view

when they should be taking and returning the assets.

Then, if the assets have been returned by the user, admin will update the lend

status in the system. Admin could choose if the lend has been returned late or any

problem arises such as missing or damage of the assets. Fines will be charged to the

problems committed. The user profile will be used in deciding which user should be

prioritized. Report can be generated by admin according to date entered. Type of report

that can be generated including Lend Report, Damage Asset Report and Missing Asset

Report.

In list of user profile page, admin could view type of user whether user is

excellent, good or poorly. These types are determined by user lend history using

Weighted Sum Model algorithm. Criteria used in WSM algorithm including number of

lend transactions that has been returned late, number of lend transactions that has

damage or missing asset and number of lend transactions with clean records (no

problem occurred).

1.6 Limitation of Works

Limitations of works are the constraints I face while doing this project:

▪ Admin still need to check whether the items have been returned manually.

▪ Communication between borrower and admin happened outside the system.

▪ This system is designed only for students of UniSZA Campus Besut.

6

1.7 Expected Outcome

This project aims to:

▪ Assist the user in making assets lend.

▪ Help admin in managing information of the lend transaction.

▪ Make an information storage for Surau Ar-Raudhah Assets Management

System.

▪ Make sure all the mistakes made by user stored and fines collected from

them.

▪ Prioritized the user when two users make lend for the same assets, date and

time.

▪ Functioning with full functionality and meets the specified user’s

requirement such as making lend assets, user prioritizing and user profiling.

1.8 Chapter Summary

This chapter concluded the introduction of the system including problem

statement, objectives, user scopes, system scopes, limitation of works and expected

outcome of the system. This information is important to clarify the purpose of the

system and targeting the user for this system.

7

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

This chapter is to present knowledge of existing research and debates relevant

to this project. Based on this project, Weighted Sum Model is chosen in deciding which

borrower that should be prioritized. This chapter also cover the research on Multi-

Criteria Decision Making, Weighted Sum Model (WSM) and comparison of algorithm.

2.2 Multi-Criteria Decision Making

Multi-criteria decision making (MCDM) helps people in making decisions

according to their preferences, in cases where there is more than one criterion. MCDM

is a way of dealing with complex problems by breaking the problems into smaller

pieces. It is one of the most widely used decision methodologies in various fields such

as energy and environment, business, economy, production and so on.

8

In making a decision, there are sometimes choices that do matter in making a

better decision. It is with this situation that the tools and methods could be use in making

the right decision. With MCDM, it helps the decision makers organise and synthesize

such information in a way which leads them to making decision with confidence and

more comfortable by all the criteria or factors have properly been taken into account.

[1]

Some of known Multi-criteria decision making (MCDM) methods are including

Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS), Simple

Additive Weighting (SAW), Analytic Hierarchy Process (AHP) and Weighted Sum

Model (WSM). [2]

2.3 MCDM Method Explanation

Some of Multi-Criteria Decision Making (MCDM) methods are including

Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS), Analytic

Hierarchy Process (AHP) and Weighted Sum Model (WSM).

▪ Weighted Sum Model (WSM)

The Weighted Sum Model is the simplest Multi-Criteria Decision

Analysis method for estimating number of alternatives using a number

of decision criteria.

9

▪ Technique for Order of Preference by Similarity to Ideal Solution

(TOPSIS)

TOPSIS is choosing the shortest geometric distance from the positive

ideal solution (PIS) and the longest geometric distance from the negative

ideal solution (NIS).

▪ Analytic Hierarchy Process (AHP)

AHP is a tool for making complex decision and may help the decision

make to set priorities and make the best decision. It reduces the complex

decisions and synthesize the results. [5]

2.4 Research on Weighted Sum Model

A few researches of journals that explain the application of Weighted Sum

Model (WSM) in determining funds recipients and the comparison of WSM and Multi

Attribute Decision Making Weighted Product (MADMWP).

2.4.1 Application of Weight Sum Model (WSM) In Determining Special

Allocation Funds Recipients [3]

The aim of this journal is to explain the application of Weighted Sum

Model (WSM) in determining Special Allocation Funds Recipients. Using

Decision Support System (DSS) application, it allows the decision maker to

make generate decisions in favour of the Special Allocation Fund beneficiary.

10

Using WSM as the MCDM method, clarifies that even a simple method

is able to generate ranking from the proposer alternatives in a special

allocation fund. WSM has a good results accuracy and has a set of alternative

options based on several decision-making criteria.

To be concluded, implementation of WSM can produce results that can

be used as a recommendation in giving special allocation fund. Also, WSM is

easy and very simple method but can give better decision.

2.4.2 Comparison of Weighted Sum Model and Multi Attribute Decision

Making Weighted Product Methods in Selecting the Best Elementary

School in Indonesia [4]

This journal compares the result of WSM and MADMWP in selecting the best

elementary school. The purpose of this selection program is to encourage the

development of the growth and to improve the quality of primary school.

The difference of MADWMP with WSM is it uses multiplication

instead of adding the usual in mathematical operations.

Conclusion from this comparison, these two methods can be used in

selection of the best elementary school system. WSM showed higher accuracy

than MADMWP. Thus, WSM is more suitable to be implemented in this

system.

11

2.5 Comparison of SDLC Methodologies

Table 2.1 shows the comparison between three methodologies in SDLC with

their advantages and disadvantages.

Model Waterfall Model Spiral Model Agile Model

Definition

The development

process moving step

by step through the

phases from the

requirement analysis

to maintenance phase.

A combined

architecture of the

Iterative and Waterfall

SDLC models and

prototyping by stages.

It is a risk-driven

software development

process model.

The requirements and

solutions evolve

through the

collaborative efforts of

the development team

and their customer (end

users).

Advantages

• Simple to use

and

understand.

• Development

stages proceed

one by one.

• Easy to

determine the

key points in

the

• The phase can

be finished

early to control

threats if exist.

• The process is

precisely

documented yet

scalable to the

changes.

• Can make

changes and

• Project is

divided by short

and transparent

iterations.

• Risks are

minimized

thanks to the

flexible change

process.

12

development

cycle.

new

functionality

even at the late

stages.

• First product

version is

released early.

Disadvantages

• The software

is ready only

after the last

stage is over.

• High risks

uncertainty.

• The progress

of the stage is

hard to

measure while

it is still in

development.

• The risk control

demands

involvement of

highly-skilled

professionals.

• Big number of

the intermediate

stages requires

excessive

documentation.

• Can be quite

expensive.

• Difficulties in

measuring the

final cost

because of

permanent

changes.

• New

requirements

may conflict

with the existing

architecture.

• The project may

exceed expected

time because of

the corrections

and changes

along the project

development.

Table 2.1 Comparison of Waterfall, Spiral and Agile Model

13

2.6 Chapter Summary

This chapter discussed about collection of literature reviews that had been

reviewed during the feasibility studies. The literature review helps developer to identify

which algorithm is suited for development of this system. Also, research on SDLC

methodologies is also done in this chapter. Furthermore, it also can gain understanding

about the development process of the system.

14

CHAPTER 3

METHODOLOGY

3.1 Introduction

In this chapter, it will discuss regarding to the methodology used to develop this

system. Out of many types Software Development Life Cycle (SDLC), the chosen

methodology is Agile Model because the development can be divided into parts and the

phase is repeated in each part. This allow the developer to make improvement from time

to time if there are any changes made. The method chosen and its development phase

will also be explained more in this chapter.

SDLC have been created by universities, experts and standards organizations

such as Waterfall Model, Spiral Model, Agile Model, Top-Down Model, Bottom-Up

Model, and Rapid Application Development (RAD) Model.

15

Figure 3.1 Type of SDLC Model

3.2 Agile Model

Figure 3.2 Agile Model

Agile software development is an approach to software while requirements and

solutions develop through the combine efforts of the development teams and their

customers as the end user. It supports adjustable planning, advancement development,

Waterfall Spiral Agile

Top-Down Bottom-UpRapid Application

Development (RAD)

16

early delivery, and continual development. Also, it is flexible and rapid response to

changes.

Agile Methods break the product into small parts that can be called as

replication. After every development of replication, the customer is able to see the result

and understand if he is satisfied or not. This is one of the advantages of the Agile

software development life cycle model. [6]

17

Figure 3.3 Graphical Illustrations of the Agile Model

3.2.1 Basic Stages of Agile Model

a) Stage 1: Planning and Requirement Analysis

In this stage, planning and requirement analysis is discussed. The

objective of the project is to built a lend system for Surau Ar-Raudhah.

The title of this project is selected, Surau Ar-Raudhah Assets

Management System (Using Weighted Sum Model). The abstract was

constructed with all the information gathered. Then, the requirement

analysis is also conducted in this stage. The risk that may exist is when

to make decision and giving the lend permission between two or more

18

associations for one lend transaction. Once the risk is identified, a plan

is finalized to overcome the risk.

b) Stage 2: Designing Project Architecture

In this second phase, the project architecture is designed. Here are

defined the limitations and milestones. The limitations of this project are

listed including there is still communications exist outside the system

between the admin and the user. This project is aimed to finish in the

third week of April.

c) Stage 3: Development and Programming

In the third phase, the development and programming of the project

is conducted. Surau Ar-Raudhah Assets Management System will be

developed. It will combine all the modules to become a complete system.

d) Stage 4: Testing

The testing phase involves the debugging process. All the code flaws

missed during the development are detected and fixed. Any

improvements are listed and be implemented to the system.

These stages are repeated until user is satisfied with the end product of the

system.

19

3.2.2 Advantages and Disadvantages of Agile Model

Advantages Disadvantages

• Functionality can be developed

rapidly and demonstrated.

• Not suitable for handling

complex dependencies.

• Suitable for fixed or changing

requirements.

• More risk of sustainability,

maintainability, and extensibility.

• Gives flexibility to developers.

• There is very high individual

dependency, since there is

minimum documentation

generated.

• Minimal rules, documentation

easily employed.

• Strict delivery management

determine the scope,

functionality to be delivered, and

adjustments to meet the

deadlines.

Table 3.1 Advantages and Disadvantages of Agile Model

20

3.3 System Requirements

System requirement is a very essential part to develop a system. They are the

software and the hardware that built up the system from scratch into a complete system.

Thus, Surau Ar-Raudhah Assets Management System deployed several software and

hardware when developing the system as listed below.

3.3.1 Software

Software Description

XAMPP Server, MySQL

Localhost to create database for this

system.

Notepad++

Platform used to write coding to be run

into localhost.

Dropbox

Cloud storage software which is used to

back up all the coding and report.

WiFi UniSZA

Internet connection used to search

information and coding-solve

alternatives.

ClickCharts Diagram Flowchart

Software

Software to draw diagram including

DFD and Context Diagram.

MySQL Workbench

Design the real ERD by importing table

from MySQL database.

21

Microsoft Office

Software to write report for references

and slides for presentation.

Google

Platform to search for information,

images and references.

Snipping tool

Used to cut and create image from the

MySQL Workbench to cut Entity

Relationship Diagram.

Table 3.2 List of Software

3.3.2 Hardware

Hardware Description

Laptop Acer Windows 10

Laptop used in developing the system

with RAM 4.0 GB, 64-bit operating

system and write report using Microsoft

Office.

Printer

Hardware used to print the hard copy of

related information and the report of this

system.

Table 3.3 List of Hardware

22

3.4 Framework and Design

This section discussed about the framework and design used in developing this

project. Project modelling has been used in order to define and analyse the data required

in this project.

Context Diagram, Data Flow Diagram, and Entity Relationship Diagram are

used in order to explain the project modelling. These diagrams also will represent the

framework of the system. Algorithm for method used in this system is also represent in

this chapter.

In conclusion, this section will explain more about how the system is designed

and modelled.

23

3.4.1 Context Diagram

Diagram below shows the context diagram that displays all the function

of the system.

Figure 3.4 Context Diagram

Figure 3.4 shows the context diagram that includes the two main entities

and their main process in this system. The borrower will input the lend detail

based on the assets that they want to borrow. Then borrower can view the lend

status if it is approved or rejected. The borrower could also print lend statement

if the transaction approved. Admin will be able to update and view assets

information in the system. The lend status will be updated by admin based on

the assets whether it has been returned back, missing or returned late. Also,

admin could generate lend report by the end of the month.

24

3.4.2 Data Flow Diagram

Diagram below shows the Data Flow Diagram (DFD) Level 0 of the system.

Figure 3.5 Data Flow Diagram Level 0

Figure 3.5 shows Diagram (DFD) Level 0. DFD is an expansion from

Context Diagram. In DFD, all the processes are connected with an entity and

saved in data store. All users in the system need to login into the system in order

to view, insert, update, delete and create a lend.

25

3.4.3 Entity Relationship Diagram

Figure 3.6 Entity Relationship Diagram

Figure 3.6 above shows the relationship among table. A Borrower can

make one or more than one Lend. But a Lend can only be made by one Borrower.

An Lend can have one or more than one Assets. An Assets can be contained in

one or more than one Lend. An associative created form many to many

relationships. Asset_Lend contain information between Assets and Lend. It

contains asset_name and lend_id as a foreign key. A Fine can have one Lend.

Asset_Defect can have one Asset_Lend. Admin has the access to all tables.

26

3.4.4 Framework Design

Figure 3.7 Framework Design

Figure 3.7 show the framework of the whole system. This figure explains

all the processes involve in this system in form of diagram. The output from this

system are report and lend statement. As shown in the figure above, the outputs

are stored in database server. Admin will be managing the assets information

and borrower profile. In the lend transaction, admin will be able to view lend

applied by borrower and update the lend status. Borrower will be able to apply

and view the lend transaction. The information from assets, borrower profile and

lend transactions will be used for the report output. The lend statement will use

the information from lend transactions for the borrower to print the output.

27

3.4.5 Algorithm (Weighted Sum Model)

a) STEP 1: Determine the attribute or criteria required.

For this system, Weighted Sum Model is used to categorize the user.

In WSM, criteria are used to help in making the decisions. Based on

Surau Ar-Raudhah Assets Management System, user is categorize

based on three criteria including:

1. Late return of asset (LR): Number of lend transaction that has

been returned late.

2. Damage or missing of asset (DM): Number of lend transaction

that has damage or missing asset.

3. Satisfactory lend without any problem (SL): Number of lend

transaction with clean record (no problem occurred).

b) STEP 2: Clarify the weightage for each criterion.

For each criterion that has been mentioned, it should assign to a

certain value of weightage. The total weightage for the criteria

should be equal to 1:

1. Weightage of late return of asset (LR) = 0.2

2. Weightage of damage or missing of asset (DM) = 0.3

3. Weightage of satisfactory lend without any problem (SL) = 0.5

Total weightage of all criteria = 0.2 + 0.3 + 0.5 = 1

28

c) STEP 3: Count numbers of completed lend transactions for each

user.

For example, we are categorizing five users; User A, B, C, D and E.

Count the numbers of completed lend transactions for each user as

shown below:

▪ Number of lend transactions completed by User A = 10

▪ Number of lend transactions completed by User B = 7

▪ Number of lend transactions completed by User C = 12

▪ Number of lend transactions completed by User D = 3

▪ Number of lend transactions completed by User E = 5

d) STEP 4: Fill in the value for each criterion according to lend history.

Weightage 0.2 0.3 0.5

Attribute or Criteria LR DM SL

User A -3/10 -1/10 6/10

User B -0/7 -0/7 7/7

User C -2/12 -0/12 10/12

User D -0/3 -0/3 3/3

User E -0/5 -1/5 4/5

Table 3.4 Algorithm Calculation: Step 4

In table 3.4, for example user A has 10 numbers of completed lend

transactions. User A has a total of 3 lend transactions that has been

returned late from the actual set time. Thus, in LR criteria for user A is

-3/10. Next, user A has a total of 1 lend transactions that has damage or

return late. Thus, in DM criteria for user A is -1/10. The value for LR

and DM criteria is negative because these criteria will reduce their

29

chance to make lend transaction. Finally, the remain of user A’s lend

lend transaction is add to SL criteria which is 6/10.

e) STEP 5: Multiply each criterion with its weight.



User A -3/10×0.2 -1/10×0.3 6/10×0.5

User B -0/7×0.2 -0/7×0.3 7/7×0.5

User C -2/12×0.2 -0/12×0.3 10/12×0.5

User D -0/3×0.2 -0/3×0.3 3/3×0.5

User E -0/5×0.2 -1/5×0.3 4/5×0.5

Table 3.5 Algorithm Calculation: Step 5(a)

Table 3.5 shows each of the criteria will be multiply with its

predetermined weightage which is 0.2 for LR criteria, 0.3 for DM

criteria and 0.5 for SL criteria.



User A -0.06 -0.03 0.3

User B 0 0 0.5

User C -0.03 0 0.42

User D 0 0 0.5

User E 0 -0.06 0.4

Table 3.6 Algorithm Calculation: Step 5(b)

Table 3.6 shows the amount of each criteria for each user after being

multiply with its weightage. Next, add all criteria for each user.

30

f) STEP 6: Calculate total of all weightage criteria for each user.



User A (-0.06) + -(0.03) + 0.3 = 0.21

User B 0 + 0 + 0.5 = 0.5

User C (-0.03) + 0 + 0.42 = 0.39

User D 0 + 0 + 0.5 = 0.5

User E 0 + (-0.06) + 0.4 = 0.34


In table 3.7, the criteria for each user is added.

g) STEP 7: Categorize the user according to its total weightage.

There are three status for users:

1. Poorly: 0 – 0.167

2. Good: 0.18 – 0.33

3. Excellent: 0.35 – 0.5

Weightage 0.2 0.3 0.5 Status


User A 0.21 Good

User B 0.5 Excellent

User C 0.39 Excellent

User D 0.5 Excellent

User E 0.34 Good


From table 3.8, we can conclude that user B, C and D is categorized as

Excellent. Whereas, user A and E is categorized as Good. These

31

calculations are used in displaying the status of user in Rekod Pengguna

interface.

3.5 Chapter Summary

This chapter explained about the methodology used in this system. Also, the

system requirements for this project including software and hardware. Then, the

framework and design are constructed in the system. These materials are used in

developing the system to make sure the system is designed according to objectives and

requirements of the system that has been mentioned in the planning phase.

32

CHAPTER 4

IMPLEMENTATION AND RESULT

4.1 Introduction

This chapter covers the detail process of implementation. It also discusses about

testing and result. Testing is conducted to test the functionalities of each module in the

system to make sure every module meets their requirements. Verification is done to

verify the Surau Ar-Raudhah Assets Management System is correctly develops and

meet their requirement specification. This process involves testing, integration testing

and system testing. Interfaces of the system is also included in this chapter.

33

4.2 Implementation and Output

4.2.1 Database Design

Figure 4.1 sams Database

Figure 4.1 shows the tables in sams database. There are seven tables which is

table admin, assets, asset_defect, asset_lend, borrower, fine, and lend.

Figure 4.2 Table Admin

Figure 4.2 shows the table admin. Table admin contains admin_id, adminname,

and passcode_a stands for passcode admin. In this table, admin_id is the Primary

Key.

34

Figure 4.3 Table Assets

Figure 4.3 shows the table assets. Table assets contains asset_name,

asset_image, total_quantity, avail_quantity and price. In this table, asset_name

is the Primary Key.

Figure 4.4 Table Asset_Defect

Figure 4.4 shows the table asset_defect. Table asset_defect contains defectId,

asset_lend_id, asset_name, username, defectDate and conditionAsset. In this

table, defectId is the Primary Key and asset_lend_id is a Foreign Key from table

asset_lend.

35

Figure 4.5 Table Asset_Lend

Figure 4.5 shows the table asset_lend. Table asset_lend contains asset_lend_id,

asset_name, quantity, lend_id and asset_lend_status. In this table, asset_lend_id

is the Primary Key. Asset_name is a Foreign Key from table asset and lend_id

is a Foreign Key from table lend.

Figure 4.6 Table Borrower

Figure 4.6 shows the table borrower. Table borrower contains username,

passcode, name, phonenum, faculty and type. In this table, username is the

Primary Key.

36

Figure 4.7 Table Fine

Figure 4.7 shows the table fine. Table fine contains fine_id, lend_id and fine. In

this table, fine_id is the Primary Key and lend_id is a Foreign Key from table

lend.

Figure 4.8 Table Lend

Figure 4.8 shows the table lend. Table lend contain lend_id, username, timenote,

lend_date, lend_time, purpose, loan_status, stage and lend_status. In this table,

lend_id is the Primary Key and username is a Foreign Key from table borrower.

37

4.2.2 Interface Design

4.2.2.1 User Interface (Borrower)

Figure 1.9 Login Page Interface for User

Based on figure 4.9 above, it shows the login page interface for user. User needs

to login and enter their username and password. Then, user needs to click ‘Log

Masuk’ to proceed to another page. If user enters the wrong username or

password, alert message will show saying ‘Nama Pengguna atau Kata Laluan

Tidak Sah’ (as shown in figure 4.10) and needs to re-enter their username and

password.

Figure 4.10 Alert Message for Wrong Username or Password

38

Figure 4.11 Homepage Interface for User

Figure 4.11 shows the homepage interface for user. This page shows Halaman

Utama, Pinjaman, Profil and Log Keluar buttons on the navbar of the page.

Dropdown for Pinjaman button consists of Senarai Aset and Permohonan Baru

options as shown in figure 4.12. Dropdown for Profil button consists of Profil

Pengguna, Ubah Kata Laluan and Status Permohonan options as shown in

figure 4.13.

Figure 4.12 Pinjaman Button Dropdown

39

Figure 4.13 Profil Button Dropdown

Figure 4.14 Senarai Aset Interface

Figure 4.14 shows Senarai Aset interface for user. This page allows user to view

the list of assets in Surau Ar-Raudhah together with the quantity and the price

per unit for each asset.

40

Figure 4.15 Permohonan Pinjaman Aset Interface 1

Figure 4.16 Permohonan Pinjaman Aset Interface 2

Figure 4.15 and 4.16 shows the permohonan pinjaman aset interface. This is

where the user will enter the information needed for apply for lend. The name

and phone number information are retrieved from the borrower database. Other

41

information including date of lend, time, purpose, stage, assets, and asset

quantity needs to be entered by the user. After filling in all the information

needed, user need to click ‘Sahkan’ button. Then, alert message will appear as

shown in figure 4.17.

Figure 4.17 Alert Message for Successful Lend Transaction

After user click the ok button on figure 4.17, it will redirect the borrower

to Status Permohonan page.

Figure 4.18 Status Permohonan Interface

Figure 4.18 shows Status Permohonan interface. Here, the user could

view their lend application whether it has been approved, rejected, or in

process. If the user clicks the link for the application, it will redirect the

user to Senarai Aset Permohonan interface.

42

Figure 4.19 Senarai Aset Permohonan Interface

Figure 4.19 shows senarai aset permohonan interface. User is able to view

assets that they have apply for their lend application on this page.

Figure 4.20 Profil Pengguna Interface

Figure 4.20 shows the profil pengguna interface. Here, user is allowed

to update their information including name, faculty and phone number. The

43

username is retrieved from the borrower table in the database. Once the

‘Kemaskini’ button is clicked, alert message will appear as shown in figure 4.21.

Figure 4.21 Alert Message of Successful Update for User Profile

Figure 4.22 Ubah Kata Laluan Interface

Figure 4.22 is ubah kata laluan interface. User is able to change their

password. Once user clicked ‘Log Keluar’ button, user will be redirect to the

Login Page Interface.

44

Figure 4.23 Register Page Interface for User

In figure 4.23 shows register page interface for user. User needs to register in

order to access the system. Admin will approve user registration. Then, user

can access the system after admin’s approval.

45

4.2.2.2 Admin Interface

Figure 4.24 Login Page Interface for Admin

Figure 4.24 shows login page interface for admin. Admin needs to login

and enter their username and password. Then, admin needs to click ‘Log Masuk’

to proceed to another page. If admin enters the wrong username or password,

alert message will show saying ‘Nama Pengguna atau Kata Laluan Tidak Sah’

(as shown in figure 4.10) and needs to re-enter their username and password.

46

Figure 4.25 Homepage Admin Interface

Figure 4.25 shows homepage admin interface. This page shows Halaman

Utama, Pengguna, Permohonan, Aset, Laporan and Log Keluar buttons on the

navbar of the page. Dropdown for Pengguna button consists of Rekod Pengguna

option as shown in figure 4.26. Dropdown for Permohonan button consists of

Rekod Permohonan and Urus Permohonan options as shown in figure 4.27.

Dropdown for Aset button consists of Rekod Aset and Tambah Aset Baru options

as shown in figure 4.28. Dropdown for Laporan button consists of Laporan

Pinjaman, Laporan Aset Rosak and Laporan Aset Hilang options as shown in

figure 4.29.

Figure 4.26 Pengguna Button Dropdown

47

Figure 4.27 Permohonan Button Dropdown

Figure 4.28 Aset Button Dropdown

Figure 4.29 Laporan Button Dropdown

48

Figure 4.30 Rekod Pengguna A-Sar Interface

Figure 4.30 shows the rekod pengguna A-Sar interface. This page allows

admin to view users profile information including association name, phone

phone number, faculty and type of user. Type of user is divided into

three types which is Excellent, Good and Poorly. Type of user is assigned

according to the calculation of weighted sum model. It is calculated based on

their lend history.

49

Figure 4.31 Rekod Permohonan Aset Interface

Figure 4.31 shows rekod permohonan aset interface. This page allows admin

to view application from users and update the application status. If admin

clicked on the purpose link, it will redirect to page that contains the application

details as shown in figure 4.32. Next, if admin clicked on the ‘Kemaskini

Status’, it will redirect to another page that allows admin to update the

application status (figure 4.33).

50

Figure 4.32 Application Details Interface

Figure 4.32 Application Details Interface. Admin is able to view assets that user

has apply for the lend application on this page.

Figure 4.33 Update Application Status

Figure 4.33 shows Update Application Status. Admin is able to update

application status in this page.

51

Figure 4.34 Borang Aset Hilang/Rosak Interface

Figure 4.34 shows borang aset hilang/rosak interface. Admin can submit any

missing or damage asset in this page. Admin needs to submit association

name, asset name, date of missing or damage asset and choose between

missing or damage.

52

Figure 4.35 Senarai Aset A-Sar Interface

Figure 4.35 shows senarai aset A-Sar interface. This page allows admin to

view list of assets in the system.

Figure 4.36 Tambah Aset Baru A-Sar Interface

Figure 4.36 shows tambah aset baru A-Sar interface. In this page, admin can

add new asset into the system. Admin needs to enter all information needed

including asset name, asset image, quantity and price per unit.

53

Figure 4.37 Laporan Pinjaman Aset Interface

Figure 4.37 shows laporan pinjaman aset interface. Admin needs to insert date

start and date end to generate the report. There are three types of report

including lend asset report, missing asset report and damage asset report. (as

shown in figure 4.38 and 4.39)

Figure 4.38 Laporan Kerosakan Aset Interface

54

Figure 4.39 Laporan Kehilangan Aset Interface

Figure 4.40 Laporan Pinjaman Interface

Figure 4.40 shows laporan pinjaman interface. Admin can generate lend report

according to lend date. In this report shows information including lend date, lend

time, association name and lend purpose.

55

4.3 Testing

4.3.1 Types of Testing

After the system is completed, the software testing take place in order

to get the respective input and output for each process exist in the system.

there are two types of techniques used for testing including black box testing

and white box testing.

▪ Black Box Testing

1. Registration

2. Login

3. CRUD functions

▪ White Box Testing

1. Determine type of user

4.3.2 Test Cases

Test case is a set of conditions under which a tester will determine

whether a system is working as expected and achieve the goals. The process of

developing test cases can help to find problems in the requirement or designs

of the system. The tables show the cases for the process in Surau Ar-Raudhah

Assets Management System.

56

4.3.2.1 User Test Case

Step Procedure Expected Result Pass/Fail

1. Click ‘Daftar Akaun’ on the login

page navbar.

Registration

form

Pass

2. Enter the following details:

▪ Username: kpm_unisza

▪ Phone number:

0138009789

▪ Faculty: -

▪ Name: Kelab Pemikir

Muda UniSZA

▪ Password: pemikir2019

Pass

3. Click ‘Daftar’ button. Message preview

successful or

failure

Pass

Table 4.1 Test Case Registration

57


1. Go to login page Login page Pass



▪ Password: pemikir

Pass

3. Click ‘Log Masuk’ button. Message “Nama

Pengguna dan

Kata Laluan

Tidak Sah!”

Pass

4. Re-enter the correct username

and password.

Login successful

User Homepage

Pass

Table 4.2 Test Case User Login Fail





▪ Password: pemikir2019

Pass

3. Click ‘Log Masuk’ button. Login successful

User Homepage

Pass

Table 4.3 Test Case User Login Success

58


1. Click ‘Senarai Aset’ on the

homepage navbar.

View list of

assets on Senarai

Aset Page

Pass

Table 4.4 Test Case View List of Assets


1. Click ‘Permohonan Baru’ on the

homepage navbar.

Permohonan

Pinjaman Aset

page is loaded

Pass


▪ Lend date: 23/04/2019

▪ Lend time: 08.30 am

▪ Purpose: Usrah Wida’

▪ Stage: University

▪ Assets with quantity:

Cawan (30), Balang Air

(1).

Pass

3. Click ‘Sahkan’ button. Message preview

successful and

redirect to page

status

permohonan

Pass

Table 4.5 Test Case Apply and View Lend Application

59


1. Click ‘Ubah Katalaluan’ on the

homepage navbar.

Ubah Katalaluan

page is loaded

Pass


▪ Current password:

pemikir2019

▪ New password: pemikir

▪ Confirm password:

pemikir

Pass

3. Click ‘Simpan’ button. Message preview

successful or

failure

Pass

Table 4.6 Test Case Change Password

60


1. Click ‘Profil Pengguna’ on the

homepage navbar.

Profil Pengguna

page is loaded

Pass

2. Update the following details:

▪ Name: Kelab Pemikir

Muda UniSZA

▪ Faculty: FIK

▪ Phone number:

0133860614

Pass

3. Click ‘Kemaskini’ button. Message preview

successful or

failure

Pass

Table 4.7 Test Case Update User Profile

61

4.3.2.2 Admin Test Case




▪ Username: umar_96

▪ Password: mukhtar

Pass

3. Click ‘Log Masuk’ button. Message “Nama

Pengguna dan

Kata Laluan

Tidak Sah!”

Pass

4. Re-enter the correct username

and password.

Login successful

Admin

Homepage

Pass

Table 4.8 Test Case Admin Login Fail

62




▪ Username: umar_96

▪ Password: mukhtar

Pass

3. Click ‘Log Masuk’ button. Login successful

Admin

Homepage

Pass

Table 4.9 Test Case Admin Login Success


1. Click ‘Rekod Pengguna’ on the

homepage navbar.

View list of

users on Rekod

Pengguna Page

Pass

Table 4.10 Test Case View List of Users

63


1. Click ‘Rekod Permohonan’ on

the homepage navbar.

View list of

applications on

Rekod

Permohonan

Page

Pass

2. Click ‘Kemaskini Status’ link Rekod

Permohonan

Aset page is

loaded

Pass

3. Update the following details:

▪ Status: Diluluskan/Tidak

Diluluskan/Denda/Selesai

▪ Value: 1 or 0

Pass

4. Click ‘Kemaskini’ button. Message preview

successful or

failure

Pass

Table 4.11 Test Case View and Update Lend Application

64


1. Click ‘Urus Permohonan’ on the

homepage navbar.

Borang Aset

Hilang/Rosak

page is loaded

Pass


▪ User Name: pmfbim

▪ Asset Name: Cawan

▪ Date Damage/Missing:

25/04/2019

▪ Damage/Missing:

Damage

Pass

3. Click ‘Tambah’ button. Message preview

successful or

failure

Pass

Table 4.12 Test Case Submit Report of Damage or Missing Asset


1. Click ‘Rekod Aset’ on the

homepage navbar.

View list of

assets on Rekod

Aset Page

Pass

Table 4.13 Test Case View List of Assets

65


1. Click ‘Tambah Aset Baru’ on the

homepage navbar.

Tambah Aset

Baru A-Sar page

is loaded

Pass


▪ Asset Name: Meja Lipat

▪ Asset Image: Upload an

image

▪ Quantity: 20

▪ Price Per Unit (RM): 40

Pass

3. Click ‘Tambah’ button. Message preview

successful and

redirect to List of

Assets Page

Pass

Table 4.14 Test Case Add New Asset

66


1. Click ‘Laporan Pinjaman’ on the

homepage navbar.

Laporan

Pinjaman Aset

Page is loaded

Pass


▪ Start Date: 01/04/2019

▪ End Date: 30/04/2019

Pass

3. Click ‘Muat Turun Laporan’

button.

Appear asset

lend report in

new tab

Pass

Table 4.15 Test Case Generate Asset Lend Report


1. Click ‘Laporan Aset Rosak’ on


Laporan

Kerosakan Aset

Page is loaded

Pass


▪ Start Date: 01/04/2019

▪ End Date: 30/04/2019

Pass


button.

Appear asset

damage report in

new tab

Pass

Table 4.16 Test Case Generate Asset Damage Report

67


1. Click ‘Laporan Aset Hilang’ on


Laporan

Kehilangan Aset

Page is loaded

Pass


▪ Start Date: 01/04/2019

▪ End Date: 30/04/2019

Pass


button.

Appear asset

missing report in

new tab

Pass

Table 4.17 Test Case Generate Asset Missing Report

4.4 Chapter Summary

This chapter concludes that design and modelling are important for

implementation of the system. Moreover, it is also helping the developer to make sure

the system is developed according to requirement and suitable added value. Next, it also

explains about testing conducted on the system. The testing analysis was performed to

make sure the system achieves its objectives and can operate properly.

68

CHAPTER 5

CONCLUSION

5.1 Introduction

In this chapter, there are three things to be discussed. Including, contribution of

the project from this system, projects limitation and recommendations to improve the

functionality of the system.

5.2 Project Contribution

Surau Ar-Raudhah Assets Management System was developed to help admin in

managing lend transactions more practical. This system also gives some contribution to

the user as well by applying lend applications. Apart from that, this system uses

Weighted Sum Model technique to categorize the users according to predetermined

criteria. Lastly, the system is 70% successfully developed on the given dateline and has

69

met the system objectives and requirements. The system is only 70% developed due to

problems in implementing WSM algorithm in this system.

5.3 Limitation

In general, projects limitation is the constraints of the system. These constraints

must be gone through whether on implementation phase or design phase or any phases

that would affect the project development process. The constraints may be happening

as early as in the planning phase. If there are problems exist in planning phase, it will

affect the other phases ahead. Constraints that can be discovered in this system are there

will be interactions between the admin and the user (borrower) outside of the system in

order for the assets to be claim by the user. Then, admin still needs to check their assets

whether it has been returned or not manually. Lastly, this system is limited to students

of UniSZA Campus Best only because Surau Ar-Raudhah is located there.

5.4 Recommendations

There are many improvements that can be implemented to this system to

increase the functionality of the system. The future works or recommendations that can

be done are generate the report monthly by entering month only, not by date. Next, add

date attributes in assets table to record when it is been submitted by admin and to avoid

error in submitting the same asset on different time. Moreover, changing the one or zero

input for asset condition in the asset damage or missing form because the system should

70

be easy and understandable by the users. Lastly, the report should also be in the form

of graphs and charts.

5.5 Summary

Surau Ar-Raudhah Assets Management System consist of two main users

including user (borrower) and admin. For the user, they are able to apply lend and view

their application status. Then, admin is able to view the applications and the user profile.

Also, admin could generate report and acquire database from the system. This system

can be improved from time to time to make sure it is functional and gives benefits to all

users.

71

REFERENCES

[1] Mardani, A., Jusoh, A., Nor, K., Khalifah, Z., Zakwan, N., & Valipour, A.

(2015). Multiple criteria decision-making techniques and their applications–a

review of the literature from 2000 to 2014. Economic Research-Ekonomska

Istraživanja, 28(1), 516-571.

[2] Belton, V. & Stewart, T. (2002). Multiple Criteria Decision Analysis: An

Integrated Approach. Retrieved from

https://books.google.com.my/books?id=mxNsRnNkL1AC

[3] Handoko, D., Mesran, M., Nasution, S. D., Yuhandri, Y., & Nurdiyanto, H.

(2017). Application Of Weight Sum Model (WSM) In Determining Special

Allocation Funds Recipients. The IJICS (International Journal of Informatics

and Computer Science), 1(2).

[4] Windarto, Agus & Muhammad, Abulwafa. (2017). Comparison of Weighted

Sum Model and Multi Attribute Decision Making Weighted Product Methods

in Selecting the Best Elementary School in Indonesia. International Journal of

Software Engineering and Its Applications. 11. 69-90.

10.14257/ijseia.2017.11.4.06.

[5] Saaty, T. L. (1980). The analytic hierarchy process McGraw-Hill. New

York, 324.

[6] Victor Osetskyi, 2017. SDLC Models Explained: Agile, Waterfall, V-Shaped,

Iterative, Spiral. https://medium.com/existek/sdlc-models-explained-agile-

waterfall-v-shaped-iterative-spiral-e3f012f390c5. Accessed on 29 August

2017.

[7] Sharma, S., Sarkar, D., & Gupta, D. (2012). Agile processes and

methodologies: A conceptual study. International journal on computer science

and Engineering, 4(5), 892.

https://books.google.com.my/books?id=mxNsRnNkL1AC

https://medium.com/@victorosetskyi

https://medium.com/existek/sdlc-models-explained-agile-waterfall-v-shaped-iterative-spiral-e3f012f390c5

https://medium.com/existek/sdlc-models-explained-agile-waterfall-v-shaped-iterative-spiral-e3f012f390c5

72

[8] Mesran, M., Suginam, S., Nasution, S. D., & Siahaan, A. P. U. (2017).

Penerapan Weighted Sum Model (WSM) Dalam Penentuan Peserta Jaminan

Kesehatan Masyarakat. Jurasik (Jurnal Riset Sistem Informasi dan Teknik

Informatika), 2(1), 40-47.

[9] Putra, A. J., Abdillah, L. A., & Yudiastuti, H. (2016). Penentuan sekolah dasar

negeri terbaik kota Palembang dengan metode weighted sum model (WSM)

dan weighted product model (WPM) menggunakan visual basic. net 2015.

[10] Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A

comparative study on SDLC. International Journal of Information

Technology and Business Management, 2(1), 26-30.

73

APPENDIX A

74

GANTT CHART FYP I

No. Task Name Week

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

1. Topic

Discussion &

Determination

2. Project Title

Proposal

3. Proposal

Writing –

Introduction

4. Proposal

Writing –

Literature

Review

5. Proposal

Progress

Presentation

& Evaluation

6. Discussion &

Correction

Proposal &

Proposed

Solution

Methodology

7. Proposed

Solution

Methodology

8. Proof of

Concept

9. Drafting

Report of the

Proposal

10. Submit Draft

of Report to

Supervisor

75

11. Seminar

Presentation

12. Correction

Report

13. Final Report

Submission

76

APPENDIX B

77

GANTT CHART FYP II

No. Task Name Week

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

1. Project

Meeting with

Supervisor

2. Project

Development

3. Proposal

Progress

Presentation &

Evaluation

4. Project

Development

(continued)

5. Project Testing

6. Submit

draft Report

and

Documentation

of the Project

7. Seminar

Presentation

8. Discussion &

Correction

Report

9. Final Thesis

Submission

https://www.kelip.unisza.edu.my/mod/forum/view.php?id=78141

surau ar-raudhah assets management system …

Documents