APPOINTMENT CONSULTATION SYSTEM

MUHAMMAD FATIHIE BIN MAT HUSSIEN

BACHELOR OF COMPUTER SCIENCE (SOFTWARE

DEVELOPMENT) WITH HONOURS FACULTY OF

INFORMATICS AND COMPUTING UNIVERSITY SULTAN

ZAINAL ABIDIN

2020

APPOINTMENT CONSULTATION SYSTEM

MUHAMMAD FATIHIE BIN MAT HUSSIEN

BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT)

WITH

HONOURS FACULTY OF INFORMATICS AND COMPUTING

UNIVERSITY

SULTAN ZAINAL ABIDIN

JULY 2020

i

DECLARATION

I hereby declare that I am the sole author for this work except for quotations and

citations, which have been duly acknowledged. I certify that it has not been previously or

concurrently submitted for any other degree at University Sultan Zainal Abidin or any

other institutions.

Signature: _________________________________

Name: Muhammad Fatihie Bin Mat Hussien

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

ii

CONFIRMATION

This is to confirm that the project title Appointment Consultation System was prepared

and submitted by Muhammad Fatihie Bin Mat Hussien (BTAL 17046434) and has found

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

Bachelor of Computer Science (Software Development) requirement under Universiti

Sultan Zainal Abidin (UniSZA). The research conducted and the report writing was under

my supervision.

Signature: ________________________________

Supervisor: Dr. Mumtazimah Binti Mohamad

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

iii

DEDICATION

Praised be to Allah, the Most Gracious and the Most Merciful for blessing me and giving

me the opportunity to undergo and complete my final year project, an system of

Appointment Consultation System. This project could not be finished without the support,

encouragement and cooperation of my supervisor, my family, friends and everyone

surrounds me. Thus, I would like to thank a lot to my supervisor, Dr Mumtazimah Binti

Mohamad, who has always guiding me and giving ideas in developing this project

successfully. Lastly, bunch of thanks to everyone who directly or indirectly involved in

the process of making the system and documentation.

Thank you.

iv

ABSTRACT

The Appointment Consultation system for universities is a web based system developed

with the aim of making it easier for students to register online by using this system. This

means that students do not need to go to the office earlier to register. This will make it

easier for students to enroll even wherever students are regardless of time. Furthermore,

this system also has several functions, among them is to make it easier for students to

book the remaining appointment dates online. Students can choose the dates displayed to

book for follow-up negotiations. Another function is, students can see the history of their

previous appointment recorded by the lecturer. The expected result of this project is that

this system allows students to use this system wherever they are regardless of time. In the

meantime, it will reduce congestion in the waiting room in the office. And it will also

reduce the waiting time for students in the office. In conclusion, technology is now more

sophisticated and it will benefit many consumers. The wise consumer will use technology

to the best of his or her convenience.

v

ABSTRAK

Sistem Appointment Consultation untuk universiti ialah sebuah sistem web based yang

dibangunkan dengan tujuan untuk memudahkan pelajar mendaftarkan diri secara atas

talian dengan menggunakan sistem ini. Maknanya, pelajar tidak perlu ke klinik lebih awal

untuk mendaftar. Hal ini akan memudahkan pelajar untuk mendaftar walaupun di mana

sahaja pelajar berada tanpa mengira masa. Tambahan pula, sistem ini juga mempunyai

beberapa fungsi antaranya ialah untuk memudahkan pelajar menempah tarikh

appointment yang masih ada secara atas talian. Pelajar boleh memilih tarikh-tarikh yang

dipaparkan untuk ditempah untuk mendapatkan rundingan susulan. Fungsi yang lain pula

ialah, pelajar boleh melihat sejarah rawatan mereka yang terdahulu yang direkod oleh

pensyarah. Hasil dijangka daripada projek ini adalah sistem ini membolehkan pelajar

untuk menggunakan sistem ini di mana sahaja mereka berada tanpa mengira masa. Dalam

pada itu, ia akan mengurangkan kesesakan di ruangan menunggu di pejabat. Dan ia nya

juga akan mengurangkan masa menunggu pelajar di pejabat. Kesimpulannya, teknologi

sekarang semakin canggih dan ia akan memberi banyak manfaat kepada pengguna.

Pengguna yang bijak akan menggunakan teknologi dengan sebaiknya untuk kemudahan

dirinya.

vi

TABLE OF CONTENT

DECLARATION I

CONFIRMATION II

DEDICATION III

ABSTRACT IV

ABSTRAK V

TABLE OF CONTENT VI

CHAPTER 1 1

1.1 Background 1

1.1.1 Management of appointment 2

1.1.2 Uncoordinated Schedule 3

1.1.3 Motivation 3

1.2 Objectives 3

1.3 Scope 4

1.3.1 Administrator: 4

1.3.2 Lecturer 4

1.3.3 Student 4

vii

1.4 Project Schedule 5

1.5 Limitation 7

1.6 Expected Result 7

2 CHAPTER 2 8

2.1 Introduction 8

2.2 Related work 9

2.3 Existing System 16

2.3.1 Web Modeling Language (WebML) in a Student Appoinment Management

System (SAMS). (Nasir, Hamid & Hassan, 2009) 16

2.3.2 Lecture Planning With Lecturers Based on Android Application(Nursyahira

Binti Mohd Yazid & Noorfa Haszlinna Mustaffa, 2017) 17

2.3.3 Managing a mixed-registration-type appointment system in outpatient clinics.

(Su & Shih 2003). 18

2.3.4 Outpatient Appointment Scheduling In A Multi Facility System. (Cayirli, Veral

& Rosen, 2006) 18

2.3.5 Conceptual Design Of Web-Based Appointment Management System using

Object WebML. (Lu, K. M., & Ab Hamid, 2007). 19

2.4 Review of Comparison 20

2.5 Summary 21

viii

3 CHAPTER 3 22

3.1 Introduction 22

3.2 Project Methodology 22

3.2.1 Planning 23

3.2.2 Requirements 23

3.2.3 Analysis and Design 24

3.2.4 Implementation and Deployment 24

3.2.5 Testing 24

3.2.6 Evaluation 24

3.3 Software and Hardware Requirement 25

3.3.1 Software 25

3.3.2 Hardware 26

3.4 Framework Design 26

3.5 Context Diagram 27

3.6 Data Flow Diagram 28

3.6.1 Data Flow Diagram Level 0 28

3.6.2 Data Flow Diagram Level 1 Process 2.0 29

3.6.3 Data Flow Diagram Level 1 Process 3.0 31

3.7 Entity Relationship Diagram (ERD) 33

3.8 Data Dictionary 34

ix

3.9 Summary 37

4 CHAPTER 4 38

4.1 Introduction 38

4.1.1 Deployment/Configuration 38

4.1.2 Interfaces 39

4.2 Testing 51

4.2.1 Types of testing 51

4.2.2 Test Case 52

4.2.3 Results 52

5 CHAPTER 5 54

5.1 Discussion 54

5.2 Limitation 54

5.3 Recommendations 55

5.4 Summary 55

x

LIST OF TABLES

Table 1: Project Gantt Chart ................................................................................................ 6

Table 3. 1 Student Table .................................................................................................... 34

Table 3. 2 Lecturer Table ................................................................................................... 35

Table 3. 3 Admin Table ..................................................................................................... 35

Table 3. 4 Appointment Table ........................................................................................... 36

xi

LIST OF FIGURES

Figure 4. 1 Interface design “Register” .............................................................................. 39

Figure 4. 2 Interface design “Student Login” .................................................................... 40

Figure 4. 3 Interface design “My Profile Student” ............................................................ 40

Figure 4. 4 Interface design “Booking Appointment Date”............................................... 41

Figure 4. 5 Interface design “List All Available Appointment Dates” .............................. 41

Figure 4. 6 Interface design “View All History Appointment Student .............................. 42

Figure 4. 7 Interface design “Lecturer Login” ................................................................... 43

Figure 4. 8 Interface design “My Profile Lecturer” ........................................................... 43

Figure 4. 9 Interface design “List Lecturer Appointment Date”........................................ 44

Figure 4. 10 Interface design “Add Appointment Date” ................................................... 44

Figure 4. 11 Interface design “Manage Appointment Date” ............................................. 45

Figure 4. 12 Interface design “List Appointment Record Student” ................................... 45

Figure 4. 13 Interface design “Add Appointment Student Record1” ................................ 46

Figure 4. 14 Interface design “Follow Up Appointment Date Student .............................. 46

Figure 4. 15 Interface design “Admin Login” ................................................................... 47

Figure 4. 16 Interface design “List All Appointment Date” ............................................. 48

Figure 4. 17 Interface design “List All Lecturer Data”...................................................... 48

Figure 4. 18 Interface design “Edit Lecturer Data Form”.................................................. 49

Figure 4. 19 Interface design “Add New Lecturer Data Form” ......................................... 49

Figure 4. 20 Interface design “List All Student Data” ....................................................... 50

Figure 4. 21 Interface design “Edit Student Data Form” ................................................... 50

xii

Figure 4. 22 Interface design “Add New Student Data” .................................................... 51

xiii

LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram

DFD Data Flow Diagram

ERD Entity Relationship Diagram

FYP Final Year Project

HCI Human Computer Interface

xiv

LIST OF APPENDICES

APPENDIX TITLE PAGE

A Appendix 1 -

B Appendix 2 -

C Appendix 3 -

D Appendix 4 -

1

1 CHAPTER 1

INTRODUCTION

1.1 Background

Great changes take place in every area of life especially in university environment

with the remarkable growth of web technology over the past few decades. It leads to the

evolution of teaching, registration or administration and processes, such as e-learning, e-

library, online portals for administrative systems and so on. However, it is not in the

management of appointments (between lecturers and college students).

There are two common approaches in a university or college. Lecturer to either

place a sign-in sign on their door (manually) or to allow a period of time for students to

book a meeting. This method does not constitute dynamic changes or revocation of

appointments, taking all clamps, managing consultation time, if the lecturer simply

relinquishes consulting time. many students may want to meet at the same time.

Based on the literature review, most of the existing appointment management

systems have been developed using ad-hoc approaches with regard to functionality only (

Karen Ming Lu & Siti Hafizah Ab Hamid, 2009). There is little emphasis on the design

and development process. Only a few design management systems use UML, which is a

widely recognized modeling standard for system design. However, because of its

2

complexity: UML is unable to achieve the goals of web application development. Web

Modeling Language (WebML) defined for Web applications can reduce development

efforts (cost and time) and allow for a more structured development process.

1.2 Problem Statement

1.2.1 Management of appointment

Some lecturers can be very busy or have other duties and responsibilities besides

teaching. This makes it difficult for students to meet them office room. Often, students

will go to the lecturer's room or call to confirm. Lecturers often take a long, long time to

answer to a student call or SMS (Short Message System). Waiting for a long response

from busy lecturers or some students may not be considered valuable. This system will

help reduce student wait time for lecturers because they may know the status of the

lecturer before meeting them.

In addition, students do not have a lecturer's phone number call. When they try to reach

them in the faculty, the lecturers are not in it whether it be for a class, meeting, or

vacation. The disadvantage of some lecturers is that they only place office telephone

connection numbers. This makes it difficult for students to contact the lecturer after office

hours appointments the next day especially for important things.

3

1.2.2 Uncoordinated Schedule

Lecturer tend to have urgent meeting or late notice resulted to manual appointment with

the student left unattended without a substitute date and time. With this system, lecturers

will be able to arrange appointments with students and can also review approved

appointments when they enter the system.

1.2.3 Motivation

Traditionally, before students will meet with lecturers for discussion, they need to go to

the faculty. If not, they should contact the lecturer by phone or send a message. However,

this is expensive for some students. As a result, developing a system or program that

assist a systematic appointment is free and easy for students and lecturers to consider is a

thought that will facilitate communication among them. Building this system can be

challenging and exciting because it requires independent thinking and intuition. In

addition, it helps build social and life skills and combines previous knowledge with the

latest.

1.3 Objectives

Every project developed must have objectives to be implemented in order to solve the

problem stated in the beginning. Thus, there are three objectives stated in this

Appointment Consultation System. The objectives of the project are:

1) To design the lecturer-student appointment system that enables lecturer manage

their slot.

4

2) To develop a system that allows students to make request to have an appointment

with the lecturer after viewing the lecturer’s availability.

3) To test the system by eliminating the possibility of reiteration of the same time

slot with other students or in case lecturer is not available because of other

meetings or university’s activities.

1.4 Scope

The scope of the Appointment Consultation System is for the use of the Faculty

Informatics and Computer by Sultan Zainal Abidin University students. The development

of the system will help the admin and lecture-student to manage their appointment. The

followings are the user’s scope for the proposed system:

1.4.1 Administrator:

• Manage faculty record and lecturers that exist in the system

• Manage important updates

• Manage database

1.4.2 Lecturer

• Manage Profile and account

• Manage table and time slot

• View requests by students either to reject or accept

1.4.3 Student

• Check date and time slot before proceeding with the appointment process.

• Make booking and check the appointment request status

5

• View the record of the sent appointment request

1.5 Project Schedule

Project schedule is one of the import documents before developing the system. It

comprises of activities in timeline and summary elements of the project. It acts as a

project guideline to finish the project on time.

6

Table 1: Project Gantt Chart

ACTIVITY /

WEEK

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

Initiating

Discuss for the

topic with

supervisor

Project title

proposal

Planning

Proposal writing –

introduction

Proposal writing –

literature review

Proposal progress

presentation

Propose solution

methodology

Proof of concept

Analysis and

design

Design system

model

Design database

Design interface

Drafting report of

proposal

Final presentation

Final report

submission

7

1.6 Limitation

This system is only activated in campus activities only, the appointment of the most

involved consultants.

1.7 Expected Result

The development of Appointment Consultation System is intended to allow the student to

make an appointment to meet with the lecturer at the appropriate time without interfering

with any other activities. In addition, to ensure that all records of the students and

lecturers are kept in a more organized and effective manner.

8

2 CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

In this chapter, discussions on past research and developed systems related to the

proposed project. Previous research can serve as a general description and may broaden

the topic. In this literature review, relevant research or systems are presented in the table

to facilitate understanding. The research is then described in paragraphs for more

information on components and details. Comparison between existing systems and the

systems to be developed makes for more ideas so improvements can be made to the

systems to be developed.

Appointments are times that are devoted to things like doctor visits, business matters, and

much like booking. The recipient notification agent receives the message notification on

behalf of the recipient. Getting the system with many free participants for behavior is a

big challenge. Nowadays, people use computer systems on it organization. The reason is

to reduce human workload and at the same time, it will require less staff or employees to

operate in various systems within the organization. Organizations may need only one

worker per system. In addition, technology helps people to save time by using electronic

systems instead of manually recording data. For this reason, an online appointment

system is built in some organizations to make meetings and appointments more

convenient. The online appointment system is a paperless electronic application designed

9

with high flexibility and ease of use, implemented for organizations such as faculty,

administration, hospitals, clinics, and other business organizations to handle meetings

with customers or customers more effectively. There are many types of online

appointment systems that exist today. This system is usually built to avoid repeating the

same time slot for different users.

2.2 Related work

Most appointment systems have a variety of methods and approaches in developing

systems to meet the demands of consumers. There are 5 systems that have been used as a

reference to view and select the appropriate techniques for this system. Table 2.1

describes the related works for appointment system and its technique

10

Table 2. 1 Shows a review on comparison existing systems

Author Title Method Problem Statement Advantages Disadvantages

Syi Su,

Chung-

Liang Shih

(2003)

Managing a

mixed-

registration-

type

appointment

system in

outpatient

clinics

process-

based

simulation

This study proposes a better

scheduling philosophy by

showing how a simulation

model can be applied to

outpatient clinics that provide

registration for both the

scheduled and walk-in

patients, and recommends the

best feasible solution to this

kind of system

• Study the behavior

of a system without

building it.

• Results are accurate

in general, compared

to analytical model.

• Help to find un-

expected

phenomenon,

behavior of the

system.

• Easy to perform

• Expensive to

build a

simulation

model.

• Expensive to

conduct

simulation.

• Sometimes it is

difficult to

interpret the

simulation

11

``What-If'' analysis

results.

Karen

Ming Lu,

Siti

Hafizah

Ab Hamid

(2007)

Conceptual

Design Of

Web-Based

Appointment

Management

System

using Object

WebML

Web

Modeling

Language

(WebML)

A web based appointment

management system is to

utilize the web technology to

manage the appointment

online. Through there are

some web based supports in

the form of static web pages

showing lecturers’ available

time for consultation

The WebML addresses the

high-level, platform-

independent specification

and targets websites that

require advanced features

like multidevice access,

one-to-one personalization

and evolution management.

WebML has support for

both modeling web

application design and

html forms.

S. J.

Mason, R.

R. Hill, L.

Mönch, O.

Outpatient

Appointment

Scheduling

In A Multi

appointment

rule

(ARULE)

-patient

The ARULE establishes the

appointment interval and

block size

12

Rose, T.

Jefferson,

J. W.

Fowler eds

(2008)

Facility

System

sequence

(PSEQ)

-PSEQ determines the way

patients are arranged or

assigned to each block

based on patient type.

MHNM,

N., Hamid,

S. R., &

Hassan, H.

(2009).

Modeling

Language

(WebML) in

a Student

Appoinment

Management

System

(SAMS)

Web

Modeling

Language

(WebML)

- NET four

architecture

This study presents the

application of Web Modeling

Language (WebML) in a

Student Appoinment

Management System (SAMS)

to help students and lecturers

arrange meetings in an

effective and efficient way in a

university or college

environment

-The WebML addresses the

high-level, platform-

independent specification

and targets websites that

require advanced features

like multidevice access,

one-to-one personalization

and evolution management.

-By using a four-tier

approach, it can integrate

WebML does not

support use cases. Two

features with UML

found very useful when

developing web

applications, use cases

and class diagrams. The

use cases are useful

when you want to see

the interaction between

13

existing databases and

applications with new

functionality for seamless

business-to-business

integration

i. units of computation

(database queries or external

interactions) ii. links

between pages and units of

computation iii. creation of

entities and relationships

instances

the application and the

user

Nursyahira

Binti

Lecture

Planning

UML Appointment planning and

location tracking between

• UML is a most useful

method of visualization and

• UML has not ability to

model the html forms.

14

Mohd

Yazid,

Noorfa

Haszlinna

Mustaffa.

(2017)

with

Lecturers

Based on

Android

Application

lecturers and students are

common

set via a simple ordering

system. The system resulted in

an appointment

it takes a long time for

lecturers to respond to it

student.

documenting software

systems design. UML uses

object-oriented design

concepts and it is

independent of specific

programming language.

• The UML uses set of

symbols to represent

graphically the various

components and

relationships within the

system and UML can be

used for business processing

modeling and requirements

modeling, it mainly is used

Another feature missing

was the ability to model

the design of the web

application, which is

what the pages contain

and how they are

connected to each other.

• UML is a huge and

partly difficult modeling

language, consisting of

many different diagrams

that make modeling of

web application time

consumable for its

implementation in an

15

to support object oriented

system analysis and to

develop the object models

organization

16

2.3 Existing System

One of the major causes of overlap or collision with other events at the same time is the

lack of a well-planned appointment system. A conceptual framework is provided to

address the existing system of appointments and to explain their work. The variables that

play a role in the appointment system are discussed. All the different appointments

systems can be tailored to suit the needs of the situation.

2.3.1 Web Modeling Language (WebML) in a Student Appoinment Management

System (SAMS). (Nasir, Hamid & Hassan, 2009)

This study presents the Web Modeling Language (WebML) application in the

Student Appointment Management System (SAMS) to help students and faculty

manage meetings effectively and efficiently in a university or college

environment. WebML is well designed for web applications and. The NET four-

level budget offers maximum functionality and flexibility in a heterogeneous web-

based environment. Each WebML element is modified according to the Hypertext

model known as the SAMS site view which is believed to work well in

implementing the appointment management system and changing the traditional

management approach to current web technologies. Comparisons with existing

systems are presented based on three common attributes of quality for web

applications: usability, performance, and workability. The usefulness of SAMS

was measured using the Question-Metrics-Salary (GQM) approach in the

questionnaire to gather 011 users' opinions, especially the interface while the

maintenance of the system was measured using complex cyclomatic techniques.

From the survey, it is evident that SAMS meets the requirements of use as the

17

results show that 67% of lecturers and 75% of students are satisfied with the

system as a whole.

2.3.2 Lecture Planning With Lecturers Based on Android Application(Nursyahira Binti

Mohd Yazid & Noorfa Haszlinna Mustaffa, 2017)

This project involves the development of a prototype of an appointment planning

system with lecturers as a form of the smartphone application. The system

developed takes into account the physical and technical features that enable it to

work well with smartphones. With this system, it will enable lecturers to inform

students of the time available to plan appointments. The method implemented in

this project uses a scheduled calendar system. At the end of this project, students

will be able to know how much time the lecturer has before making an

appointment. Appointment Planning System is a system that provides convenience

to lecturers and students quickly determine the appropriate meeting time. Planning

appointments and tracking of locations between lecturers and students is common

is set via a simple ordering system. This system produces long appointments for

lecturers to respond to students. With this location planning and location tracking

system, lecturers and students can make appointments faster and more effective.

Students will only have to wait for notification from the lecturer if the

appointment is approved by the lecturer. In addition, it will also allow students to

know how much time the lecturer has before making an appointment with the

lecturer. This methodology uses the Unified Modeling Language (UML) to

analyze and design systems. The design and development phase will only stop

when system testing is performed.

18

2.3.3 Managing a mixed-registration-type appointment system in outpatient clinics. (Su

& Shih 2003).

Improving the use of outpatient resources can significantly improve the efficiency

of healthcare organizations. A large number of patient walk-ins (72% in our

study) to outpatient services are a universal feature of healthcare organizations. As

a result, scheduling becomes very complex and important. Choosing the right

scheduling alternative, healthcare organizations can improve the efficiency of

outpatient surgery. This study used simulation methods to analyze several

scheduling solutions and found that setting an appropriate arrival time interval for

registered patients had a significant impact on the problems faced by outpatients.

Using robust simulation models, the effects of various scheduling policies on

patient delivery time and time were reported. In conclusion, the findings of this

study can be used for any outpatient clinic with mixed (inbound and scheduled)

enrollment types, especially for high percentages the patient is walking.

2.3.4 Outpatient Appointment Scheduling In A Multi Facility System. (Cayirli, Veral &

Rosen, 2006)

This study evaluates appointment systems used in hospitals by incorporating

appointment rules and patient characteristics. Using an experiment unit at an

internal medicine department of a large outpatient ward in Nagoya university

hospital, a number of prevailing assumptions were relaxed, and twenty-five

appointment systems were developed combining five appointment rules with five

patient sequences.

19

These appointment systems were evaluated under two different environments

namely no-show and patient punctuality, with each of the two-levels totaling one-

hundred different environments. A best appointment system is capable of

identifying the problems in terms of both patients waiting time and doctor idle

time.

This study investigated two decision factors, namely the appointment rule

(ARULE) and patient sequence (PSEQ). The ARULE establishes the appointment

interval and block size whereas the PSEQ determines the way patients are

arranged or assigned to each block based on patient type.

2.3.5 Conceptual Design Of Web-Based Appointment Management System using

Object WebML. (Lu, K. M., & Ab Hamid, 2007).

The rapid growth and spread of the Web is fueling a new generation of applications

growing in size and complexity. The development of such applications is a hybrid

between the development of traditional Information Systems and the authors of

Hypermedia. It challenges existing tools and approaches to software production. At

this time, the development of web applications is quite volatile and often the ad hoc

process lacks systematic techniques and methodologies. As a result, many

companies today face severe problems in the management and maintenance of web

applications. In response to this, the project is to use Web Modeling Language

(WebML) that is defined for web applications and. The four-level architecture is

clean to the management of appointment management in the university / college

environment. A web-based appointment management system called WBAMS is

20

designed and implemented to enable students and faculty to organize meetings

effectively and efficiently.

2.4 Review of Comparison

There is many collection management software available in the market today. To find a

comparison between the existing system and the new system, research has been done.

There are several types of comparative research. Each research uses its own approach to

make their research more relevant. As for the Student Appointment Management System

(SAMS), WebML is well designed for web applications and. BEL level BEL offers

maximum functionality and flexibility in a heterogeneous web-based environment. Each

WebML element is modified according to the Hypertext model known as the SAMS

website which is believed to work well in implementing system management

appointments and transforming traditional management approaches to current web

technologies.

For the Lecture Design With Lecturers Based on Android Application, the methods

implemented in this project use the system calendar table. At the end of this project,

students will be able to know how much time the lecturer has before making an

appointment. With location planning and location tracking systems, lecturers and students

can make appointments faster and more effectively. In addition, it will also allow students

to know how much time the lecturer has before making an appointment with the lecturer.

Uses Integrated Modeling Language (UML) to analyze and design systems. The design

and development phase will only stop once the test system is run. To manage a mixed

enrollment system in the outpatient clinic, this study uses simulation methods to analyze

several scheduling solutions and finds that determining the appropriate time interval for a

21

registered patient has a significant impact on the problem arising. Using robust simulation

models, the effects of various scheduling policies on patient delivery time and time were

reported.

Besides, for Design Concepts Web-based Design Management System, This project uses

Web M0deling Language (WebML) which is defined for web applications and. The four-

level architecture is clean to the management of appointment management in the

university/college environment. A web-based appointment management system called

WBAMS is designed and implemented to enable students and faculty to organize

meetings effectively and efficiently. To improve information management, the

Appointment Consultation System uses a WebML approach to make the system easy to

arrange meetings in an effective and efficient way in a university or college environment.

2.5 Summary

In this phase it will deliver the information about the study on the past research, current

application or system, and article on the website. This study is more to focus to do the

development and guide to the successful project, to come out with the new system will

benefits to all user.

22

3 CHAPTER 3

METHODOLOGY

3.1 Introduction

This chapter will discuss the methodology in this project. There is a detailed system

requirements description of each phase involved in the project.

3.2 Project Methodology

The methodology that is use to develop the system is Iterative Model. The iterative

model is a particular implementation of a software development life cycle (SDLC) that

focuses on an initial, simplified implementation, which then progressively gains more

complexity and a broader feature set until the final system is complete. There are 5 phases

in this methodology that is planning, analysis and design, implementation, testing and

evaluation. The details of these phases are described in Figure 3.1:

Figure 3. 1 Iterative Model

23

3.2.1 Planning

In this phase, the requirement needed to develop the system is identified. The meeting

with the supervisor is held to discuss the system that will be developed. Result for the

meeting, the system decided to develop is an system that is used to manage appointment

between students and lecturers at University known as Appointment Consultation System.

The requirement that needed to develop the system is identified. The schedule to develop

this application is set into a Gant chart to ensure that the proposed system is successfully

completed within the schedule by make research, observing and interview.

3.2.2 Requirements

All of the systems available for the specific techniques collected have been analyzed,

summarized and complied with to identify any requirements needed for the application.

Different techniques in multi-criteria decision methods have been observed. Previous

research and articles related to specific techniques focused on their advantages and

disadvantages for implementing appropriate techniques in the system. Web Modeling

Language (WebML) is selected for the techniques that will be implemented in the system

as it is best suited for positioning based on the criteria that will be displayed in the

system. From research, there are many local systems related to appointment consultation

to facilitate business between the two parties.

24

3.2.3 Analysis and Design

In this phase, the details study of requirements for the application such as from the users,

journals, internet and many more are conducted. There might be a change in requirement

while in this phase to follow the requirement that are gathered. The activities for high-

level and low-level design are started in this phase.

3.2.4 Implementation and Deployment

In this phase, the design is translated into coding. To develop this application, the

programming language that has been used is PHP and the server used is Wamp Server.

The database also designed in MySQL. Computer programs are written using a

conventional programming language or an application generator.

3.2.5 Testing

During this phase the developed system is tested. The separated modules are combined

and brought together then tested as the complete system. The system needs to be tested in

order to detected errors. It is also being tested to make sure the function is working such

as are the interface work and operate according to the what user requires. The system

wills also being demonstrated to the user.

3.2.6 Evaluation

In the testing phase, the system is demonstrated to the user. In this phase, based on

customer feedback the result from the testing is being evaluated. The error and bugs are

25

detected, and then the repair and modifications are made accordingly. There might be

some feature that is removed from the early planning phases.

3.3 Software and Hardware Requirement

The requirement of hardware and software are the most important part of the successful

of the project. The project cannot be completed without software and hardware

requirement. The consumption of these facilities depends on what already provided or

what they have been used before. These are the details of the requirements for the

Appointment Consultation System:

3.3.1 Software

Software requirement of this project are:

a) Notepad++

This software is a text-editor and even a source code editor for the Microsoft

Windows. It supports code folding and syntax highlighting for many

programming, scripting and markup languages which make it the popular source

code editors in the world.

b) Wamp Server MySQL

This software is a Windows web development environment to create the web

application with Apache2, MySQL database and PHP. It allows easily manage of

database via PhpMyAdmin.

c) Microsoft Project 2007

26

This software is used for develop the Gantt Chart. As a project management tool

that assists the project managers in managing project schedules, resources

assignments, tracking progress, allocating the project budget, tracking the labor

effort and generating various reports related to project.

d) Microsoft Vision 2007

This software is used for make the report of this system and creates diagrams for

this system. Go from complicated text and tables that are hard to understand to

Visio diagrams that communicate information at a glance.

3.3.2 Hardware

Hardware requirement of this project is Laptop Asus with processor Intel® Core i5-

8300H CPU @ 2.30GHz and with memory (RAM) 4.00 GB

3.4 Framework Design

In general, a framework design is a real or conceptual structure intended to serve as a

support or guide for the building of something that expands the structure into something

useful. Figure 3.2 shows that students can book appointments, and view lecturer

vacancies. Lecturers can manage profiles, and approve bookings. Admins can monitor the

system, manage staff, manage data information.

27

Figure 3. 2 Framework Design

3.5 Context Diagram

Figure 3.3 shows the Context Diagram for this system. This system involves three main

entities which are admin, student and lecturer. Students can check the date and time of

slots, make reservations and check the status of appointments, and view records. While

lecturers can manage profile accounts, schedules and time slots, and view requests by

students. As administrators can manage faculty records and lecturers and manage

databases.

Figure 3. 3 Context Diagram

28

3.6 Data Flow Diagram

3.6.1 Data Flow Diagram Level 0

Figure 3.4 shows that administrators, lecturers, and students must sign up to access the

application. The details of the list will be stored in each student, lecturer, and admin desk.

When an administrator registers the details, the data is stored in the store's data store.

Each appointment details will be stored in the appointment data store. Admins can view

reports from individual details, appointment details, and student and lecturer details.

Administrators can also manage users' old records from time to time to keep up to date.

The DFD has two entities which are ADMIN and USER. There are four processes

involved in the system which are MANAGE PROFILE, MANAGE APPOINTMENT,

MANAGE USER, GENERATE REPORT. There are three data stores created in the

system which are STUDENT, LECTURER and APPOINTMENT. The flow of the

system is like below:

1. STUDENT enters student details to MANAGE PROFILE process which outputs

student details into STUDENT data store.

2. STUDENT enters appointment details to MANAGE APPOINTMENT process

which outputs appointment details into APPOINTMENT data store.

3. LECTURER enters lecturer details to MANAGE PROFILE process which output

lecturer details into LECTURER data store.

4. LECTURER enters appointment details to MANAGE APPOINTMENT process

which outputs appointment details into APPOINTMENT data store.

5. ADMIN enters profile lecturer into MANAGE APPOINTMENT process which

output appointment details into APPOINTMENT data store.

29

6. ADMIN enters update user into MANAGE USER process which output update

student and update lecturer into STUDENT and LECTURER data store.

Figure 3. 4 Data Flow Diagram

3.6.2 Data Flow Diagram Level 1 Process 2.0

Based on Figure 3.5, the admin can register the lecturer profile. The lecturer detail will be

stored in a table lecturer and it can appear in the application for the user to view.

Administrators can also update new and old lecturer profiles, erasing lecturer data.

The DFD has ADMIN entity. There are five processes involved in the system which are

REGISTER PROFILE, UPDATE, DELETE, MANAGE APPOINTMENT and

MANAGE USER. There are three data stores created in the system which are

APPOINTMENT, STUDENT and LECTURER. The flow of the system is like below:

30

Description:

1. ADMIN enters lecturer detail into REGISTER PROFILE process which output

lecturer detail into LECTURER data store.

2. ADMIN enters lecturer detail into DELETE process which output lecturer detail

into LECTURER data store.

3. ADMIN enters lecturer detail into UPDATE process which output lecturer detail

into LECTURER data store.

4. ADMIN enters lecturer profile into MANAGE APPOINTMENT process which

output lecturer profile into APPOINTMENT data store.

5. ADMIN enters update user into MANAGE USER process which output update

student and update lecturer into STUDENT and LECTURER data store.

31

Figure 3. 5 Data Flow Digram Level 1 Process 2.0

3.6.3 Data Flow Diagram Level 1 Process 3.0

Based on the number 3.6 students can find a lecturer and then book an appointment.

Details of the appointment will be approved by the lecturer. Then, it will be saved in the

appointment schedule. Administrators can view reports for appointment details.

The DFD has three entities which are STUDENT, LECTURER and ADMIN. There are

four processes involved in the system which are PROCESS, APPOINTMENT,

APPROVAL, MANAGE USER. There are three data stores created in the system which

are STUDENT, LECTURER and APPOINTMENT. The flow of the system is like below:

Description:

32

1. STUDENT enters appointment detail into APPOINTMENT process which output

appointment detail into APPOINTMENT data store.

2. LECTURER enters appointment status info into APPROVAL process which

output appointment status into APPOINTMENT data store.

3. Appointment status is retrieved from APPOINTMENT data store to GENERATE

REPORT process.

4. GENERATE REPORT process sends appointment status to ADMIN.

Figure 3. 6 Data Flow Diagram Level 1 Process 3.0

33

3.7 Entity Relationship Diagram (ERD)

Figure 3.7 shows the ERD which contains four entities which are STUDENT,

APPOINTMENT, LECTURER and ADMIN. This ERD will shows the relationship

between entities. Each entities have their own attributes. For Student entities, it has the

attributes student_id (as primary key), student_name, student_course, student_pnumber,

student_password and student_gender. In addition to Appointment entities, it has the

attributes app_id (as Primary Key), app_date, app_time, app_location, app_category,

student_id and lecturer_id (as Foreign Key). Then, for the Lecturer entity, it has the

lecturer_id attribute (as Primary Key), lecturer_name, lecturer_email, lecturer_pnumber,

lecturer_gender and lecturer_password. Finally, for Admin entities, they have the

Username attribute (as Primary Key) and Password. For the cardinal process, one Student

to many Appointments. Many Appointments to Many Lecturers. One Admin to many

Lecturers. One Admin to One Student.

Figure 3. 7 Entity Relationship Diagram

34

3.8 Data Dictionary

The Data Dictionary is a file or set of files containing the metadata of the database. The

data dictionary contains records of other objects in the database, other data, relationships

with other objects, and such as data ownership. The data dictionary is an important

component of the relational database. For most relational database management systems

(RDBMS), database management system software includes a data dictionary to access

data within a database.

Table 3.1 shows student have 5 attributes with student_id as the primary key. For

student_id and student_pnumber it needs to meet the integer requirements, while for

student_name, student_course, student_gender and student_password it also needs to

meet the varchar requirements

Table 3. 1 Student Table

Name Type Null Comment

student-id Int(100) No Primary Key

student_name Varchar (100) No

student_course Varchar(50) No

student_pnumber Int (15) No

student_password Varchar (15) No

student_gender Varchar(30) No

Table 3.2 show lecturer have 6 attributes with lecturer_id as the primary key. For

lecturer_id and lecture_pnumber it needs to meet the integer requirements, while for

35

lecturer_name, lecturer_address, lecturer_gender and lecturer_password it needs to meet

the varchar requirements as well.

Table 3. 2 Lecturer Table

Name Type Null Comment

lecturer_id Int(100) No Primary Key

lecturer_name Varchar (100) No

lecturer_email Varchar (300) No

lecturer_pnumber Int (15) No

lecturer_gender Varchar(20) No

lecturer-password Varchar(15) No

Table 3.3 shows that admin have 2 attributes with username as primary key. Admins need

to enter a username that has an integer and a password that has varchar requirements.

Table 3. 3 Admin Table

Name Type Null Comment

admin_id Int(100) No Primary Key

password Varchar(100) No

Table 3.4 shows that booking is a composite table that has 7 attributes with app_id as

primary key and contains 2 foreign key which is student_id from table user and

lecturer_id from table lecturer. For app_id, duration, lecturer_id and student_id need to

36

meet integer requirements, while for app_date, app_time, app_category and app_location

must also meet varchar requirements.

Table 3. 4 Appointment Table

Name Type Null Comment

app_id Int(100) No Primary Key

app_date Varchar (100) No

app_time Varchar (12) No

app_location Varchar(15) No

app_category Varchar (100) No

lecturer_id Int (100) No Foreign Key

reference lecturer

student_id Int (100) No Foreign key

reference student

37

3.9 Summary

For conclusion, in order to develop a successful and complete system for Appointment

Consultation Application, we need to have a better understanding about the flow of the

whole system. The design and modeling which are system framework, context diagram,

DFD, ERD, will make us clear about the system when we have understanding the overall

system.

38

4 CHAPTER 4

IMPLEMENTATION AND RESULT

4.1 Introduction

An implementation and result are to construct the product as design specifications

developed in previous phase, methodically verified to ensure that they are error-free and

fully meet user requirements. Implementation and result should be done before a system

is fully utilized. System implementation consider that the hardware and software system

components are installed, the selected software is configured and tested, the software may

be customized to meet local functional requirement, data mapping, signed off and

becoming a fully operational production system.

4.1.1 Deployment/Configuration

Implementation is the process of carrying out, execution or practice of plan according to

the main objective of the system and achieve user requirement. This project is developed

using PHP language in the whole project. For the server, XAMPP server used to manage

connection between Apache and MySQL. The database used in this system is MySQL.

This is because, MySQL is easy to support browser and also easy to support coding in

PHP. For writing coding, software Notepad++ and Sublime Text 2.0 is used in this

project. For testing, it uses three different browsers to avoid problems not supporting the

39

browser. Among the browsers used is Google Chrome, Mozilla Firefox and Opera. When

the project is developed, the project file will always be updated and stored in Google

Drive Cloud Storage as backup if there is a problem with the computer.

4.1.2 Interfaces

This developed system is a clinic system used by 3 users namely students, lecturers and

admin. Student can set appointment date with a leturer without them having to go the

office. The system has 3 different login, function and dashboards for student, lecturer and

admin.

4.1.2.1 Student Interfaces

In the student’s dashboard, there are 3 main menus that have specific functions namely

Home, Booking Appointment Date and Appointment History. For first-time user, they

need to register in the form register in Figure 4.1 before they can login into this system.

They can register themselves in the form provided or the admin can register.

Figure 4. 1 Interface design “Register”

40

Figure 4.2 shows the student login. Student must use the identification card number as

their username. Student need to fill username and password to enter the system. After

login, the system will continue to the student’s home page, which is displayed My Profile

student.

Figure 4. 2 Interface design “Student Login”

Figure 4.3 shows the profile student. It displays student information such as identity card

number, full name, gender, course and phone number. Student can update all their

information in this menu.

Figure 4. 3 Interface design “My Profile Student”

41

Figure 4.4 shows displays the entire appointment date with the lecturer which is booked

by the student. Students can also check the status of an appointment that has already taken

place.

Figure 4. 4 Interface design “Booking Appointment Date”

Figure 4.5 shows the student can select to booking an available appointment date and can

also cancel the booking date. The student does not need to go the office to make an

appointment date with the lecturer.

Figure 4. 5 Interface design “List All Available Appointment Dates”

42

Figure 4.6 shows displays the all appointment history that the lecturer had insert in during

their previous appointment. This is to facilitate the lecturer to view the previous student’s

progress record as a reference. At the same time, students can also look at their record

information, with the comments provided by the lecturers after the appointment, students

can improve from time to time.

.

Figure 4. 6 Interface design “View All History Appointment Student

4.1.2.2 Lecturer Interfaces

Inside the dashboard lecturer, there are 3 main menu that have certain functions that’s is

My Profile, Add Appointment Date and Manage Appointment. Before the lecturer login,

the admin should register the lecturer first. Lecturer cannot register themselves, only the

admin can register the lecturer. Figure 4.7 shows the lecturer login. Lecturer must use the

identification card number as their username. Lecturer need to fill username and

password to enter the system. After login, the system will continue to go the homepage

lecturer is My Profile lecturer.

43

Figure 4. 7 Interface design “Lecturer Login”

Figure 4.8 show the profile lecturer. It displays a lecturer’s information including identity

card number, full name, gender, address, qualification and telephone number. Lecturer

can also update all their information in this menu.

Figure 4. 8 Interface design “My Profile Lecturer”

44

Figure 4.9 shows display the entire appointment date that has been entered by the lecturer

along with the status of whether the appointment date is still available or has been booked

by the student.

.

Figure 4. 9 Interface design “List Lecturer Appointment Date”

Figure 4.10 shows the lecturer insert appointment date in this system to facilitate the

student to book an appointment date. The lecturer may also delete appointment date if the

date has not been booked by the student.

Figure 4. 10 Interface design “Add Appointment Date”

45

Figure 4.11 shows displays the list student’s booked date of appointment. It has 2

function, lecturer can view the previous appointment records student and lecturer can

insert the student’s appointment record into the system.

Figure 4. 11 Interface design “Manage Appointment Date”

Figure 4.12 shows the lecturer can view the previous appointment records student. This as

a reference to facilitate the lecturers know the progress of the students after the

appointment before.

Figure 4. 12 Interface design “List Appointment Record Student”

46

Figure 4.13 shows when a student makes an appointment with a lecturer, the lecturer can

insert appointment record such as location details, summary and comment into the

system. This will make it easier to review in detail when implemented.

Figure 4. 13 Interface design “Add Appointment Student Record1”

Figure 4.14 shows after appointment data is stored in the system, the lecturer can choose

and insert the date of appointment to follow up the student. This function facilities the

lecturer to book an appointment date with the student and the student does not need to

book appointment date again.

Figure 4. 14 Interface design “Follow Up Appointment Date Student

47

4.1.2.3 Admin Interfaces

In the admin dashboard, there are 4 main menus that have specific functions namely

Home, Manage Appointment, Manage Doctor and Manage Patient. For admins, only one

admin can login into system. Figure 4.15 shows the admin login.

Figure 4. 15 Interface design “Admin Login”

Figure 4.16 shows displays the entire Appointment Date that has been entered by the

lecturer and also shows status the date is still available or has been booked by student. In

the meantime, the admin can book appointment date for the student, if the student goes

directly to the office. The admin needs to select the student, and select the appointment

date which is still available. In addition, the admin can cancel the booking appointment

date made by the student.

48

Figure 4. 16 Interface design “List All Appointment Date”

Figure 4.17 shows the list all lecturer and overall details of the lecturer. Admin can add a

new lecturer into this system. Admin is also able to update or delete lecturer data if there

are any changes in the university system.

Figure 4. 17 Interface design “List All Lecturer Data”

49

Figure 4.18 shows the edit lecturer data form, if admin want to update the doctor

information. After update, the new data will updated in database. Admin needs to fill in

all the required attributes in the lecturer data accurately so that there is no data

inaccuracy.

Figure 4. 18 Interface design “Edit Lecturer Data Form”

Figure 4.19 shows admin can add a new lecturer into this system. Admin needs to fill in

all the required attributes in the lecturer data accurately so that there is no data

inaccuracy.

Figure 4. 19 Interface design “Add New Lecturer Data Form”

50

Figure 4.20 which shows all student and the overall details of the student. Admin can add

new students into this system, can also update and delete existing student data.

Figure 4. 20 Interface design “List All Student Data”

Figure 4.21 shows the edit student data form if admin want to update the student

information. After update, the new data will update in database. Admin needs to fill in all

the required attributes in the lecturer data accurately so that there is no data inaccuracy.

Figure 4. 21 Interface design “Edit Student Data Form”

51

Figure 4.22 shows admin can add a new student into this system if patient come directly

to the admin at the registration counter. Admin needs to fill in all the required attributes in

the student data accurately so that there is no data inaccuracy.

Figure 4. 22 Interface design “Add New Student Data”

4.2 Testing

There are two types of testing which are user interface and usability testing. User

interface testing defines the emotions of the potential product users. Usability testing is

the expression of the usage. The product form and its appearance are taken into account

during user interface testing. Usability testing is oriented towards the end user.

4.2.1 Types of testing

❖ User interface testing

User Interface testing was created to test and interact with the system to find errors

and bug in this system. The test is done by trying all the buttons in the system to link

the correct page and menu. In the meantime, it tests every page that includes text and

52

design positions, font size and design size so they are organized and consistent with

each other.

❖ Usability Testing

Usability testing is now a key part of any web-based project. It is a method used to

view and evaluate how easy it is to use this system. Tests are done with real users and

small focus groups similar to target audience of this system. It is to measure how this

system can be used and how easy it is to use it.

4.2.2 Test Case

This system is tested repeatedly, especially on interface buttons that are already linked to

on other pages. This is very important to prevent the user from being mistaken on the

system. Additionally, test involving connection to the database are also being tested.

Among them is, entering the data into its example system from registering the student,

after insert fill data in form and the button submit is pressed, the data goes in and stored

into the database. Among other functions tested are display data, update data, insert data

and also delete data.

4.2.3 Results

As a result of the test, there are some errors and bug in the user interface such as non-link

buttons on other pages. After encountering some errors, correction is promptly done and

continues to be tested repeatedly to detect other errors. In addition, there is also a coding

error that causes data from the database to not display on the system screen. Correction

53

takes a while to be repaired because the coding is correct but there are still errors in the

system. After repeated testing, the resulting solution is clear cookies in the browser and

the system can continue to display as usual. In conclusion, if an error on the web system

is not necessarily a problem with coding but a problem with the browser.

54

5 CHAPTER 5

CONCLUSION

5.1 Discussion

Overall, this project has been developed and follow the main objective that have been

explained in Chapter 1.

This system developed to facilitate to register early and fast online before they get

appointment at the office. In addition, this system allows patient to set appointments date

in online with lecturer to get follow-up appointments date and do not need to go to the

office for a date. This will save the time, cost and energy of the student to go to the office.

Now, student can use this system wherever they are, regardless of time.

5.2 Limitation

GUI android application maybe not fit with the size of the device. This is because the

resolutions of each device are different and the possible font size, position and size design

system will be affected.

55

5.3 Recommendations

Among the suggestions for the addition of this system is, for the appointment, the student

can view calendar slots that are free to book for an appointment. Additionally, it can be

improved from a user-friendly standpoint by providing notifications to directors and

students when they have received approval or feedback on appointment booking.

5.4 Summary

As a conclusion, this system can set an appointment date with a lecturer without them

having to go the clinic earlier. This system also hopefully can help the student, lecturer

and admin do their working done smoothly.

56

REFERENCES

1. Schewe, K.D. and B. Thalheim 2005. Conceptual modelling of web information

systems. Data Knowledge Eng.. 54: 147-188

2. F. Huarng, M.H. Lee, Using simulation in outpatient queues: a case study, Int. J.

Health Care Qual. Assur. No. 6 (1996) 21/25

3. Nathalie MoreNo, Piero Fraternali, Antonio Vallecillo, “WebML modelling in

UML,” In Proc. IET Journal , vol. 1, pp. 569 - 576, Mar. 2007.

4. F. Hashimoto, S. Bell, Improving outpatient clinic staffing and scheduling with

computer simulation, J. Gem. Intern. Med. 11 (3) (1996) 182/184.

5. J.S. Rakich, P.J. Kuzdrall, K.A. Klafehn, A.G. Krigline, Simulation in the hospital

setting: implications for managerial decision making and management

development, J. Manage. Dev. 10 (4) (1991) 31/37.

6. -MHNM, N., Hamid, S. R., & Hassan, H. (2009). WebML and .NET architecture

for developing students appointment management system. Journal of Applied

Sciences, 9(8), 1432-1440.

7. -Lu, K. M., & Ab Hamid, S. H. (2007, November). Conceptual Design of Web-

Based Appointment Management System using Object WebML. In 2007 First

IEEE International Symposium

8. -Su, S., & Shih, C. L. (2003). Managing a mixed-registration-type appointment

system in outpatient clinics. International journal of medical informatics, 70(1),

31-40.