WEB INFORMATION MANAGEMENT: FACULTY WEBSITE

NAJAH FASIHAH BINTI MOHD ZAINUDDIN

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE DEVELOPMENT)

UNIVERSITI SULTAN ZAINAL ABIDIN

2019

ii

DECLARATION

I hereby declare that the report of the project titled Web Information Management:

Faculty Website is based on my own investigations and based on information

from sources that stated. This dissertation is submitted to the Faculty Informatics

and Computing, Universiti Sultan Zainal Abidin as partial fulfilment of the

requirements for the Bachelor of Computer Science (Software Development) with

Honour. I also declare that this thesis has been composed solely by me and it has

not been previously submitted for any other degree at Universiti Sultan Zainal

Abidin.

_____________________________________

Name : Najah Fasihah binti Mohd Zainuddin

Date : ............................................................

iii

CONFIRMATION

I have read this report and in my point of view, this project report was prepared

and submitted by Najah Fasihah binti Mohd Zainuddin (BTAL16044445) and had

been satisfactory in scope, quality, and presentation as partial fulfilment of the

condition and requirements to be awarded as Bachelor of Computer Science

(Software Development) with Honour.

I also confirm that the research conducted and the writing of this report was under

my supervision.

_____________________________________

Name : Prof Dr.Mohd Nordin bin Abd Rahman

Date : ............................................................

iv

DEDICATION

In the name of Allah SWT, Most Gracious, Most Merciful

First of all, thanks to Allah Almighty for giving me strength and provided me with

good health throughout this project. This final year project, Android Based Real

Time Parcel Management and Tracking System with Integrated GPS is dedicated

to my beloved mother and father who is giving me a lot of moral support to

complete this project. Also, to my supervisor, Prof Dr. Mohd Nordin bin Abd

Rahman that always support me and guides me to complete my final year project.

Last but not least, my sincere thank you goes to all lecturers and Bachelor of

Computer Science (Software Development) group members who always help me

in many ways to complete this project.

v

ABSTRACT

Universiti Sultan Zainal Abidin (UniSZA) is the 18th public institution of higher learning,

located in the state of Terengganu, Malaysia. The university has four campuses and has a

total of 12 different faculties. The current website of faculty does not provide a platform

that allows user to search information about different faculty on a single webpage. This is

because each faculty has their own difference websites. To find out the information on

different faculties, users need to access each related faculty website one by one. This

causes users to take a long time to get the information they need. The project of Web

Information Management: Faculty Websites proposes a web service that will integrate all

the faculty websites available at UniSZA to help users to minimize their time in searching

the information about the faculty. The use of JSON techniques is one of the alternative

methods works as syntax for storing and exchanging data of the websites. Three processes

involved; read data from source data, convert into JSON format and read the JSON

format.

vi

ABSTRAK

Universiti Sultan Zainal Abidin (UniSZA) adalah institusi pengajian tinggi awam ke-18 yang

terletak di negeri Terengganu, Malaysia. Universiti ini mempunyai empat buah kampus dan

mempunyai 12 buah fakulti keseluruhannya. Laman web fakulti UniSZA yang sedia ada tidak

menyediakan platform yang membolehkan pengguna mencari maklumat mengenai fakulti yang

berbeza pada satu halaman web tunggal. Hal ini adalah kerana penggunaan laman web yang

berbeza-beza bagi setiap fakulti. Oleh hal yang demikian, untuk mengetahui maklumat mengenai

beberapa fakulti yang berbeza, pengguna perlu mengakses setiap laman web fakulti yang berkait

satu persatu. Hal ini boleh memakan masa yang lama bagi pengguna mendapatkan maklumat

yang mereka perlukan. Projek Pengurusan Maklumat Web: Laman web Fakulti mencadangkan

perkhidmatan web yang akan mengintegrasikan semua laman web fakulti yang terdapat di

UniSZA untuk membantu pengguna meminimumkan masa mereka dalam mencari maklumat

yang diperlukan. Penggunaan teknik JSON adalah salah satu kaedah alternatif yang berfungsi

sebagai sintaks untuk menyimpan dan menukar data dari laman web. Tiga proses yang terlibat;

baca data dari data sumber, tukar ke format JSON dan kemudian baca kemabali format JSON

tersebut.

vii

TABLE OF CONTENT

ABSTRACT ...................................................................................................................................... v

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

CHAPTER 1 .................................................................................................................................... 1

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

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

1.2 Problem Statement ..................................................................................................... 3

1.3 Objectives .................................................................................................................... 2

1.4 Scope ............................................................................................................................ 2

1.5 Limitation of work ..................................................................................................... 3

1.6 Expected Result .......................................................................................................... 3

1.7 Conclusion................................................................................................................... 3

CHAPTER 2 .................................................................................................................................... 4

LITERATURE REVIEW ............................................................................................................ 4

2.1 Introduction .................................................................................................................... 4

2.2 Technique ........................................................................................................................ 5

2.3 Summaries from the articles ..................................................................................... 9

2.4 Summary ................................................................................................................... 10

CHAPTER 3 .................................................................................................................................. 11

METHODOLOGY ........................................................................................................................ 11

3.1 Introduction .............................................................................................................. 11

3.2 System Development Life Cycle (SDLC) ............................................................... 12

3.3 System Development Life Cycle (V- Model) .......................................................... 13

3.4 System Requirement ................................................................................................ 18

3.5 System Design ........................................................................................................... 19

3.6 Summary ................................................................................................................... 33

3.7 References ................................................................................................................. 34

3.8 Appendix ................................................................................................................... 35

viii

LIST OF TABLES

TABLE TITLE

2.1 Comparison between JSON and XML

2.2 Summaries of Articles

3.1 SuperAdmin

3.2 Admin

3.3 Faculty

3.4 Programme

3.5 Lecturer

3.6 Staff

ix

LIST OF FIGURES

FIGURE TITILE

3.1 Software Development Life Cycle Phase

3.2 V Model

3.3 Framework

3.4 Context Diagram

3.5 Data Flow Diagram Level 0

3.6 Data Flow Diagram Level 1: Manage Admin

3.7 Data Flow Diagram Level 1: Manage Faculty

3.8 Data Flow Diagram Level 1: Manage Data

3.9 Entity Relationship Diagram

3.10 Gantt Chart

x

LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram

DFD Data Flow Diagram

ERD Entity Relationship Diagram

FYP Final Year Project

PK Primary Key

FK Foreign Key

SDLC System Development Life Cycle

1

CHAPTER 1

INTRODUCTION

1.1 Project Background

Universiti Sultan Zainal Abidin (UniSZA) is the 18th public institution of

higher learning, located in the state of Terengganu, Malaysia.The University has

four campuses namely Gong Badak Campus, Medical Campus, Tembila Campus

and the latest is UniSZA International Campus (UIC) in Kuala Lumpur City. The

university has 12 faculties located in different campuses which offer programs in

diploma, bachelor’s and master’s level as well as doctor of philosophy.

The webpage mining services is a web services that provides the main

information on all the twelve faculties available at UniSZA to users on one

webpage. This system provides the ability to store the database of multi website.

It allows user to get information faster and easily without having to direct access

to the entire faculty website. Users enables

2

1.2 Problem Statement

The current website can be time consuming to find the information needed as

each faculty has their own website.

It does not provide a website that allows users to get information of different

faculty on a single website.

1.3 Objectives

There are three objectives that have been identified in this project. The objectives

are as follows:

To design a website that can give convenience to the user to minimize

their time in finding the information about the faculty at UniSZA.

To develop a website that will integrate information from different

faculty websites.

To test the functionality of a website that allows user to search

information about the faculties.

1.4 Scope

In order to achieve the objective of this project, there are several scopes have been

outlined. This scope shows about the user who will use this system and how it can

be established later.

1.4.1 Main user

3

For this system, admin is responsibility person that can control and

manage this system. While the user can search the information about the

faculties provided.

1.5 Limitation of work

This system does not provide all faculty-related information but only provides

information on programs, lecturers and staff for each faculty.

1.6 Expected Result

The users will be able to search information about the twelve faculties available at

UniSZA on a single website without having to direct access to each faculty

website.

1.7 Conclusion

As a conclusion, chapter 1 explains about the overview of this system, problem

statement, objectives of the project, scopes, limitation of work and lastly expected

result.

4

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

Along with the rapid development of technology, a lot of efforts have been

made to ensure that the technology used in Malaysia is in line with the

development of the world. Regardless of the Government or Non-Government

Organization, they are trying to replace the latest technologies with more

sophisticated, fast and easy-to-use technology.

As we know, the review of the literature is important before develop new

technologies because it identifies the methods used in previous research on the

topics and also provides comparisons for your own research findings. To have a

further understanding about this project, a few researches on existing system

were made.

5

2.2 Technique

1. JSON Technique

JSON is designed to be a data exchange language which is human readable and

easy for computers to parse and use. In reality, there are a lot of systems that using

JSON approach and also XML language. JSON is known as JavaScript Object

Notation that represent simple data structures and recently all of the modern

browsers can support the JSON.

JSON is used for transmitting the data over a network connection that link

between the server and the web application. Then this technique is an alternative

way rather than XML technique and by using this JSON, data source will be

integrate into one application.

Meaning that, all the data sources have own database, so to create one application

that has many database, it easy to use JSON because it allows the different

database to access the data sources from other application. Then it also provides a

better and good performance for database integration collection.

6

2. XML technique

XML is known as eXtensible Markup Language and not tied to any programming

language because it can use to construct other language for defining new

document formats for the World Wide Web (www). This XML make use of

elements and attributes to describe data and in XML, each element contains

number of attributes.

It differences with the JSON because the data that get from the database is

converting into XML format then it will load and give the customer as HTML

format. XML also can create human-readable structure of data and as self-

describing documents that can conform to a set of rules.

In other word, XML is a platform-independent complex and more complex rather

than JSON in integrate of the database. Then for querying in XML may present

issues because parsing XML can be costly in term of parsing time.

7

3. Differences between JSON and XML approach

Technique Speed Fetch data

from server

Verbose Array

of

Usage

Coding

XML Slower Use XMLHttp

Request to

fetch data

from server

More

verbose

Not

include

array

<players>

<player>

<firstName>Safee

</firstName>

<lastName>Sali

</lastName></player>

<player>

<firstName>Sapiq

</firstName>

<lastName>Rahim

</lastName></player>

</players>

JSON Faster Can fetch data

from server

with and

without

XMLHttp

Request in

AJAX, it also

uses

JSONRequest.

Not

verbose

Include

an

array

{“players”:[

{“firstName”:”Safee”,

“lastName”: “Sali”}

{“firstName”:”Sapiq”,

“lastName”:

“Rahim”}

]}

Table 2.1: Differences between JSON and XML

8

4. Advantage of JSON

There are four (4) advantages of JSON. Firstly, JSON has a smaller message size.

Besides, JSON is more structural information in the document. It can easily

distinguish between the numbers 1 and the string “1” as a number, strings (and

Booleans) are represented differently in JSON. It can also distinguish between

single items and collections of size one by using JSON arrays. Next, JSON can

easily represent a null value and the last, JSON is more compact and can be easily

loaded in JavaScript

9

2.3 Summaries from the articles

Title/Author/Year System Strength Weakness

A comprehensive

analysis of XML

and JSON web

technologies

- Zia Ul Haq,

Gul Faraz

Khan, Tazar

Hussain

- 2015

Using the

HTML,

JavaScript, ASP,

JSP, XML,

JSON and etc on

web

technologies to

represent the

information on

the internet.

- The ultimate

compression

ratio, with a

tiny

negligible

performance

overhead

- A minified

JSON message

is a better

alternative to

using traditional

XML messages,

or specialized

XML

compression.

Automated web

usage data mining

and

recommendation

system using K-

Nearest

Neighbor(KNN)

classification

method

- D.A.

Adeniyi, Z.

Wei, Y.

Yongquan

- 2014

Using the

HTML,

JavaScript, RSS,

KNN

- Automaticall

y discover

and extract

useful

information

from a

particular

web site

- Identify

visitors click

stream data

matching it

to a

particular

user group

- RSS is

essentially just

plain-text XML

A web service

based on RESTful

API and JSON

Schema/JSON

Meta Schema to

construct

knowledge graphs

- Adam

Agocs

- 2018

Using the

HTML,

JavaScript,

RESTful API,

JSON

- Be able to

create the

elements of

knowledge

graph(s) and

validate the

uploaded

data together

with the

elements

- Development of

the validation

code required

for JSON-LD

would call for a

substantial

amount of work

in comparison

with the gain in

expressiveness

Table 2.2:Summaries of Articles

10

2.4 Summary

As the summary of this chapter 2, it shows that the Literature Review is giving a

good effect about the research. From that, we can know more knowledge about the

research that we search for.

In the other word, review is look again at what others have done in areas that are

similar, though not necessary identical to, one’s own area of investigation and it can show

how others have handled methodological and design issues in studies similar.

11

CHAPTER 3

METHODOLOGY

3.1 Introduction

This chapter discusses the methodology that was used during the system

development project. The flow of the project will discuss briefly to give more

understanding of design and develop of this project. There are many method can be used

for developing this project. One of the methodologies that suitable for this project is

System Development Life Cycle (SDLC). In this methodology is based on phases for

each development process.

12

3.2 System Development Life Cycle (SDLC)

System Development Life Cycle(SDLC) contain of detailed plan describing to develop a

system or web services, maintain and replace specific software. This methodology is for

improving the quality of software and the overall development process which have a

beginning of the operation and end of the operation. SDLC consists of six phases which is

Planning, Analysis, Design, Implementation, Testing and Integration and maintenance.

Figure 3.1: SDLC Phase

13

3.3 System Development Life Cycle (V- Model)

Figure 3.2 show the V- model that is chosen in in developing this project. The V-Shaped

model focused on the importance of testing during all stages of development. Each phase

in V-Shaped model has to be evaluated by the client with review and verified by specific

deliverable before proceeding to the next phase. Furthermore, this model has a number of

advantages such as earlier receipt user feedback, earlier review and evaluation of

requirements which helps in developing additional requirements and upfront monitoring

of quality. This is one of the few available ways to generate a quality software product.

Figure 3.2: SDLC (V-Model)

Requirement Analysis

System Design System testing

User Acceptance

Testing

Architectural Design

Module Design

Integration Testing

Coding

Unit Testing

Verification and

Validation

14

3.3.1 Verification Phases

3.3.1.1 Requirements analysis

In this phase, the requirements of the proposed system are collected by analyzing user

requirements. This phase is concerned about creating an ideal system to implement it.

Usually, the users are interviewed and a document called the user requirements document

is generated. The user requirements document will typically describe the system’s

functional, physical, interface, performance, data, and security requirements as expected

by the user. It is a way that business analysts use to communicate their understanding of

the system to the users. The users carefully review this document as this document will be

the guideline for the system designers to design the system. The user acceptance tests are

designed in this phase.

3.3.1.2 System Design

System engineers analyze and understand the proposed system business by reviewing

user requirements documents. They figure out possibilities and techniques by which the

user requirements can be implemented. If any of the requirements are not feasible, the

user is informed of the issue. A resolution is found and the user requirement document is

edited accordingly.

15

The software specification document which serves as a blueprint for the development

phase is generated. This document contains the general system organization, menu

structures, data structures etc. It may also hold example business scenarios, sample

windows, reports for the better understanding. Other technical documentation like entity

diagrams, data dictionary will also be produced in this phase. The documents for system

testing are prepared in this phase.

3.3.1.3 Architecture Design

This phase can also be called as high-level design. The baseline in selecting the

architecture is that it should realize all which typically consists of the list of modules,

brief functionality of each module, their interface relationships, dependencies, database

tables, architecture diagrams, technology details etc. The integration testing design is

carried out in this phase.

16

3.3.1.4 Module Design

This phase can also be called as low-level design. The designed system is broken up in to

smaller units or modules and each of them is explained so that the programmer can start

coding directly. The low level design document or program specifications will contain a

detailed functional logic of the module, in pseudo code - database tables, with all

elements, including their type and size - all interface details with complete API

references- all dependency issues- error message listings- complete input and outputs for

a module.

3.3.2 Validation phases

In the V-model, each stage of verification phase has a corresponding stage in the

validation phase. The following are the typical phases of validation in the V-Model.

3.3.2.1 Unit testing

In the V-Model, Unit Test Plans (UTPs) are developed during module design phase.

These UTPs are executed to eliminate bugs at code level or unit level. A unit is the

smallest entity which can independently exist, e.g. a program module. Unit testing

verifies that the smallest entity can function correctly when isolated from the rest of the

codes/units.

17

3.3.2.2 Integration Testing

Integration Test Plans are developed during the Architectural Design Phase. These tests

verify that units created and tested independently can coexist and communicate among

themselves. Test results are shared with customer's team.

3.2.2.3 System testing

System Tests Plans are developed during System Design Phase. Unlike Unit and

Integration Test Plans, System Test Plans are composed by client's business team. System

Test ensures that the expectations of the develop application are met. The whole

application is tested for its functionality, interdependency and communication. System

Testing verifies that the functional and non-functional requirements have been met. Load

and performance testing, stress testing, regression testing, etc., are subsets of system

testing.

3.3.2.4 User acceptance testing

User Acceptance Test (UAT) Plans are developed during the Requirements Analysis

phase. Test Plans are composed by business users. UAT is performed in a user

environment that resembles the production environment, using realistic data. UAT

verifies that delivered system meets user's requirement and system is ready for use in real

time.

18

3.4 System Requirement

The requirement of the software and hardware for developing this project

is needed in order to develop system successfully.

3.4.1 Hardware Requirement

i. Acer’s Laptop

ii. Pendrive: used to backup data and small storage in order to transfer

the file

iii. Printer

3.4.2 Software Requirement

i. Eclipse

ii. Xampp: as the platform for testing the database of the system.

iii. MySQL

iv. Drop box: used to share and backup data.

v. Google Chrome

vi. Microsoft Word

vii. Microsoft Power Point

19

3.5 System Design

3.5.1 Framework

A framework is conceptual structure to serve as a guide for the building of

something that expands the structure into something useful. A framework is for a

set of function within a system and how they related to each other, and how

communication should be standardized at some level of a network.

Figure 3.3: Framework

Convert to

20

3.5.2 Process Model

3.5.2.1 Context Diagram

Context diagram is a high level view of a system, and a diagram that

defines the boundary between the system, or part of a system, and its environment,

showing the entities that interact with it.

Based on figure 3.4, there are two entities that interact with the system

which are Admin and User. Firstly, user is one of the important user in this system

because of the requirement that needed. Second is the admin that more to update

the information and control this system properly.

Figure 3.4: Context Diagram

21

3.5.2.2 Data flow diagram

A data flow diagram (DFD) is a graphical representation of the flow

of data through an information system and it is another way of showing the

information flow of the process. DFD consist of four major components; entities,

processes, data stores and data flows. DFD are important to reveals relationship

between component in the system and for modelling a system’s high level detail

by showing how input is being transformed to output result through sequence of

functional transformations.

Figure 3.5 shows the DFD level 0 which is the main data process of this

system that involves six processes which are login, manage admin, manage

faculty, data verification, search info and lastly generate report.

22

Faculties’

information

Faculties’

information

manage data

login

admin details

admin

faculty info

Admin details

Login

authentication

Login

authentication

login

faculty info

report

Verify data

Faculties’

information

admin details

JSON

Figure 3.5: Data Flow Diagram (DFD) level 0

2.0

Manage admin

faculties 3.0

Manage faculty

5.0

Search info

USER

Search info

D2

D3

6.0

Generate Report

ADMIN

1.0

Login D1 S_admin

SUPER ADMIN

4.0

Data Verification

23

admin details

admin details

admin details

3.2.1.1 Data Flow Diagram (DFD) level 1

3.2.1.1.1 Manage Admin

Figure 3.6 shows the DFD level 1 for manage admin. In this process, only

super admin will be able to use this function. There are four processes which

are add data, update data, view data and delete data. While there are one data

store involved to this function which is admin.

Figure 3.6: DFD level 1 for manage admin

2.4

Delete admin admin details

2.2

Update admin

Super Admin admin details

2.1

Add admin

2.3

View admin

admin details

admin details

admin details

Admin D4

24

admin details

admin details

3.2.1.1.2 Manage Faculty

Figure 3.7 shows the DFD level 1 for manage faculty. In this process, only

admin will be able to use this function. There are four processes which are add

data, update data and delete data. While there are one data store involved to

this function which is faculty.

Figure 3.7: DFD level 1 for manage faculty

3.3

Delete data

admin details admin details

3.2

Update data

Admin

admin details

3.1

Add data

admin details

admin details

faculty D3

25

JSON

3.2.1.1.3 Data verification

Figure 3.8 shows the DFD level 1 for data verification. In this process,

only admin will be able to use this function. There are two processes which

are add and update data. All the information stored in JSON format.

Figure 3.8: DFD level 1 for data verification

Faculties’ data

3.3

Delete data

3.2

Update data Admin

Faculties’ data Faculties’

information

Faculties’ information

26

3.2.2 Data Model

3.2.2.1 Entity Relationship Diagram (ERD)

An entity relationship model, also called an entity-relationship (ER) diagram, is a

graphical representation of entities and their relationships to each other. An entity is a

piece of data-an object or concept about which data is stored. ERD show how data will

be represented and organized in the various components of the final database.

Figure3.9 shows the ERD for the faculty website, the entities for the system are SUPER

ADMIN, ADMIN and FACULTY.

27

3.2.2.2 Data dictionary

Database system is used to stores data in systematically and organized so

that it can be easily accessed by an authorized user. There are six tables that are

involved in this system. The following figures show the specification table that

involved in Faculty Website.

Column Type Null Default Comments

S_adminID Varchar(20)PK No

adminID Varchar(20)FK No

Name Varchar(100) No

password Varchar(20) No

Table 3.1: SuperAdmin

Based on the table 3.1, table SuperAdmin has four attributes, which are

S_adminID, adminID, name and password. The primary key in this table is

S_adminID. Every time admin need to access the system, he/she need to enter

S_adminID and password at login interface. The foreign key for this table is

adminID.

28

Column Type Null Default Comments

adminID Varchar(20)PK No

S_adminID Varchar(20)FK No

facultyID Varchar(20)FK No

Name Varchar(100) No

password Varchar(20) No

email Varchar(50) No

datetime Datetime No

Table 3.2: Admin

Based on the table 3.2, table Admin has seven attributes, which are

adminID, S_adminID, facultyID, name, password, email and datetime. The

primary key in this table is adminID. Every time admin need to access the system,

he/she need to enter adminID and password at login interface. The foreign key for

this table is S_adminID and facultyID which is from table SuperAdmin and

faculty.

29

Column Type Null Default Comments

facultyID Varchar(20)PK No

adminID Varchar(20) FK No

F_name Varchar(100) No

F_links Varchar(100) No

noTel Varchar(12) No

Fax Varchar(12) No

Address Varchar(100) No

Table 3.3: faculty

Based on table 3.3, table faculty has seven attributes which are facultyID,

adminID, F_name, F_links, noTel, fax and address. The primary key for this table

is facultyID while the foreign key is adminID from table login.

30

Table 3.4: programme

Based on the table 3.4, table programme has five attributes which are

pprogrammeID, facultyID, programmeName, programmeDetail and

programmeType. The primary key for this table is programmeID and the foreign

key is facultyID from table faculties.

Column Type Null Default Comments

programmeID Varchar(10)PK No

facultyID Varchar(20) FK No

ProgrammeName Varchar(100) No

programmeDetail Varchar(100) No

programmeTtype Varchar(50) No

31

Column Type Null Default Comments

facultyID Varchar(10)PK No

lecID Varchar(20) PK No

lecName Varchar(100) No

lecTel Varchar(12) No

lecEmail Varchar(50) No

lecExpertise Varchar(50) No

lecPosition Varchar(100) No

Table 3.5: lecturer

Based on the table 3.5, table lecturer has seven attributes which are

facultyID, lecID, lecName, lecTel, lecEmail, lecExpertise and lecturerPosition.

The primary key for this table is lecID while the foreign key is facultyID from

table faculty.

32

Column Type Null Default Comments

staffID Varchar(10)PK No

facultyID Varchar(20) FK No

Name Varchar(100) No

Position Varchar(100) No

NoTel Varchar(12) No

Email Varchar(50) No

Table 3.6: staff

Based on the table 3.6, table staff has six attributes which are facultyID,

staffID, Name, NoTel, Email and Position. The primary key for this table is

staffID while the foreign key is facultyID from table faculty.

33

3.6 Summary

As an overall, this chapter gives details about project methodology which is about

the steps using in make sure that the proposed project had been followed the actual

procedure. This process is good in ensuring that the prototype is working properly based

on the requirements. This chapter also gives details about how to model the data that

being used in a project. Starting from the process of identified the related entities that are

involved in this system.

34

3.7 References

1. Haq, Z. U., Khan, G. F., & Hussain, T. (2015). A Comprehensive analysis of

XML and JSON web technologies. New Developments in Circuits, Systems,

Signal Processing, Communications and Computers, 102-109.

2. Adeniyi, D. A., Wei, Z., & Yongquan, Y. (2016). Automated web usage data

mining and recommendation system using K-Nearest Neighbor (KNN)

classification method. Applied Computing and Informatics, 12(1), 90-108.

3. Agocs, A., & Goff, J. M. L. (2018). A web service based on RESTful API and

JSON Schema/JSON Meta Schema to construct knowledge graphs. arXiv preprint

arXiv:1804.03887.

35

3.8 Appendix

Figure 3.10: Gantt chart