Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
PUSAT KESIHATAN UNISZA (PKU) MANAGEMENT
SYSTEM
NURUL FATIN SHAFIQAH BINTI MOHD SHAFEE
BACHELOR OF COMPUTER SCIENCE
(INTERNET COMPUTING) WITH HONOURS
UNIVERSITI SULTAN ZAINAL ABIDIN
2018
PUSAT KESIHATAN UNISZA (PKU) MANAGEMENT SYSTEM
NURUL FATIN SHAFIQAH BINTI MOHD SHAFEE
Bachelor of Computer Science (Internet Computing) with Honours
Faculty of Informatics and Computing
Universiti Sultan Zainal Abidin, Terengganu, Malaysia
AUGUST 2018
i
DECLARATION
I hereby declare that Pusat Kesihatan UniSZA (PKU) Management System report is
based on my original work except for quotations and citations, which have been duly
acknowledged. I also declare that it has not been previously or concurrently submitted
for Bachelor of Computer Science (Internet Computing) at Universiti Sultan Zainal
Abidin (UniSZA).
Name : Nurul Fatin Shafiqah Binti Mohd Shafee
Date : 8th August 2018
ii
CONFIRMATION
This is to confirm that:
This project entitled Pusat Kesihatan UniSZA (PKU) Management System using
mobile computing technique was prepared and submitted by Nurul Fatin Shafiqah Binti
Mohd Shafee, matric number BTCL15039861 has been found satisfactory in terms of
scope, quality and presentation as a partial fulfilment of the requirement for a Bachelor
of Computer Science (Internet Computing) in Universiti Sultan Zainal Abidin
(UniSZA).
Supervisor : Mrs. Maizan Binti Mat Amin
Date : 8th August 2018
iii
ACKNOWLEDGEMENT
In the name of Allah, the Most Gracious and the Most Merciful for giving me this
kind of opportunity to complete this final year project entities “Pusat Kesihatan UniSZA
(PKU) Management System”. This project was prepared for Faculty of Informatics and
Computing, Universiti Sultan Zainal Abidin (UniSZA) to complete undergraduate
program in Bachelor of Computer Science (Internet Computing).
I would like to express my gratitude to my supervisor, Mrs. Maizan Binti Mat Amin,
lecturer of Faculty of Informatics and Computing who had guided and give valuable
information during development of this project.
I also want to express my gratitude towards my parent, family, friend and all the
lecturer of Faculty of Informatics and Computing for their help and encouragement
during this whole semester and for those who has involve during this project
development.
iv
ABSTRACT
Pusat Kesihatan UniSZA (PKU) is a health centre for all UniSZA students. Basically
this health centre is for the early treatment such as fever, stomach ache, small wound
and etc. Besides, students also can take the medicine that they need with consultation
from the medical assistant. Currently, the students need to fill in the form every time
they have to meet the medical assistant or take the medicine. Other than that, all the
details of medicine for the students are manually written and the medical assistant need
to check the file for the previous details of the student that came to the health centre.
Thus, PKU Management System is proposed to overcome these problems. For
student, they needs to register their details in the system and when visiting the PKU
they just need to give their matric number. Thus, this system helps them from re-written
their details when visiting the health centre. For the medical assistant, after registered
into the system, they only need to enter the student′s matric number and fill in the details
of their medicine and health. Besides, they can review the details from the system. This
system is more systematic to the assistant medical and student.
v
ABSTRAK
Pusat Kesihatan UniSZa adalah sebuah pusat kesihatan yang dikhaskan kepada
pelajar Universiti Sultan Zainal Abidin. Secara amnya, pusat kesihatan ini memberikan
khidmat rawatan awal kepada pelajar sebagai contohnya demam, luka kecil, sakit perut
dll. Selain itu, pelajar juga boleh mendapatkan ubat dengan nasihat pembantu medikal.
Penggunaan kertas setiap kali mengisi borang perjumpaan menyebabkan sistem pusat
kesihatan ini tidak teratur dan berkemungkinan borang tersebut utuk hilang dan
berlebihan.
Oleh itu, Sistem Pengurusan Pusat Kesihatan UniSZA dicadangkan bagi mengatasi
masalah tersebut. Dengan adanya sistem ini, pelajar tidak perlu mengisi borang setiap
kali mereka ingin berjumpa pembantu medikal. Pembantu medikal juga hanya perlu
mengisi butiran keihatan pelajar terus ke dalam sistem dengan memasukkan nombor
matrik pelajar.Pelajar juga boleh melihat semula butiran di dalam sistem. Sistem ini
membantu pusat kesihatan lebih teratur dan sistematik.
vi
CONTENTS
PAGE
DECLARATION i
CONFIRMATION ii
ACKNOWLEDGEMENT iii
ABSTRACT iv
ABSTRAK v
CONTENTS vi
LIST OF TABLES ix
LIST OF FIGURES x
LIST OF ABBREVIATIONS xi
CHAPTER I INTRODUCTION
1.1 Project Background 1
1.2 Problem statement 2
1.3 Objectives 2
1.4
1.5
Scopes
Limitation of Works
2
3
1.6 Expected Result 3
1.7 Activities 4
CHAPTER II LITERATURE REVIEW
2.1 Introduction 5
2.2 Management Information System 5
2.3 Mobile Computing 6
2.4 Cordova Apache 6
2.5 Android
2.6 Research of Studies 7
2.7 Application on PKU Management System
2.7.1 Hospital Management System 10
2.7.2 SoftClinic 11
2.7.3 Dr. Pad Management Application 13
2.8 Summary 14
vii
CHAPTER III
METHODOLOGY
3.1 Introduction 15
3.2 System Development Life Cycle (SDLC) 15
3.3 Waterfall Model 15
3.4 Framework and Design
3.4.1 Framework 19
3.4.2 Context Diagram 20
3.4.3 Data Flow Diagram Level 0 21
3.4.4 Data Flow Diagram Level 1 23
3.4.5 Entity Relationship Diagram (ERD) 28
3.5 Data Decomposition 30
3.6 Data Dictionary 34
3.7 Software and Hardware Requirement 37
3.8 Summary 38
CHAPTER IV IMPLEMENTATION DAN RESULT
4.1 Introduction 39
4.2 Graphical User Interface Module
4.2.1 Student – Register and Login 40
4.2.2 Student – Appointment 41
4.2 4.2.3 Student – Profile and Treatment Report 42
4.2.4 Medical Assistant – Login and Profile 43
4.2.5 Medical Assistant – Approve Appointment 44
4.2.6 Medical Assistant – Treatment Details 45
4.2.7 Admin – Login 46
4.2.8 Admin – Manage User 46
4.2.9 Admin – Add Medicine 48
4.3 Implementation of Mobile Computing (Coding) 49
4.4 Test Case
4.4.1 Authentication 51
4.4.2 Make an appointment (Student) 52
viii
4.4.3 Update Profile (Student) 52
4.4.4 Cancel Appointment (Student) 53
4.4.5 Approve Appointment (Medical Assistant) 53
4.4.6 Add Treatment Details (Medical Assistant) 54
4.4.7 Add Medical Assistant and Medicine
(Admin)
54
4.4.8 Update Profile (Admin) 55
4.4.9 Delete (Admin) 55
4.5 Summary 56
CHAPTER V CONCLUSION
5.1 Introduction 57
5.2 Project Constraint 57
5.3 Result Discussion 57
5.4 Future Works 58
5.5 Summary 58
REFERENCES 59
ix
LIST OF TABLES
TABLE TITLE PAGE
2.1 Description on method in PKU Management System 7
3.1 Details of admin table in PKU Management System 34
3.2 Details of student table in PKU Management System 34
3.3 Details of medical assistant table in PKU Management
System
35
3.4 Details of appointment table in PKU Management System 35
3.5 Details of medicine table in PKU Management System 36
3.6 Details of treatment table in PKU Management System 36
3.7 Lists of Software Requirement 37
3.8 Lists of Hardware Requirement 38
4.1 Test Case for Authentication 51
4.2 Test Case Success Add Appointment 52
4.3 Test Case Success Update Profile 52
4.4 Test Case Success Delete Appointment 53
4.5 Test Case Success Approve Appointment 53
4.6 Test Case Success Add Treatment Details 54
4.7 Test Case Success Add 54
4.8 Test Case Success Update Profile 55
4.9 Test Case Success Delete 55
x
LIST OF FIGURES
FIGURE TITLE PAGE
2.1 Appointment page of HMS 10
2.2 HMS’s patient registration form 11
2.3 Appointment page of SoftClinic 12
2.4 SoftClinic’s patient details form 12
2.5 Appointment and patient details pages of Dr.Pad 13
3.1 Model of Waterfall 16
3.2 Framework of PKU Management System 19
3.3 Context Diagram of PKU Management System 20
3.4 DFD Level 0 of PKU Management System 22
3.5 Data Flow Diagram Level 1 (Admin) 24
3.6 Data Flow Diagram Level 1 (Student) 25
3.7 Data Flow Diagram Level 1 (Medical Assistant) 27
3.8 ERD of PKU Management System 29
3.9 Data Decomposition of PKU Management System 30
3.10 Data Decomposition of Admin 31
3.11 Data Decomposition of Student 32
3.12 Data Decomposition of Medical Assistant 33
4.1 Register and Log In (Student) 40
4.2 Appointment (Student) 41
4.3 Profile and Treatment Record (Student) 42
4.4 Log In and Profile (MA) 43
4.5 Approve Appointment (MA) 44
4.6 Treatment Details (MA) 45
4.7 Log In (Admin) 46
4.8 Medical Assistant Record (Admin) 46
4.9 Student Record (Admin) 47
4.10 Treatment Record (Admin) 47
4.11 Medicine Record (Admin) 48
4.12 Command to create an APK for PKU Management System 49
4.13 Command to create an APK for PKU Management System 49
4.14 IP Address for connection 50
4.15 Code to build an APK 50
4.16 Code to build an APK 50
xi
LIST OF ABBREVIATIONS / TERMS / SYMBOLS
CD Context Diagram
DFD Data Flow Diagram
ERD Entity Relationship Diagram
PKU Pusat Kesihatan UniSZA
MA Medical Assistant
MIS Management Information System
SDLC System Development Life Cycle
1
CHAPTER I
INTRODUCTION
1.1 Project Background
Health centres are community-based and patient-directed organizations that
deliver comprehensive, culturally competent, high-quality primary health care
services. Health centres also often integrate access to pharmacy, mental health,
substance abuse and oral health services in areas where economic, geographic, or
cultural barriers limit access to affordable health care services. Pusat Kesihatan
UniSZA (PKU) is a health centre for all UniSZA students. This health centre is for
the early treatment for the students such as fever, stomach ache, small wound and
etc. Besides, students also can take the medicine that they need with consultation
from the medical assistant. Currently, the students need to fill in the form every time
they need to meet the medical assistant for consultation or any treatment. Other than
that, all the records of medicine for the students are manually written and the medical
assistant need to check the file for the previous records of the student that came to
the health centre. A system is needed for a systematic management.
PKU Management System is proposed to overcome the problems. For student,
they needs to register their details in the system and when visiting the PKU they just
need to give their matric number. Thus, this system helps them from re-written their
details when visiting the health centre. For the medical assistant, after registered into
the system, they only need to enter the student’s matric number and fill in the details
of their medicine and health. Besides, they can review the details from the system.
This system is more systematic to the assistant medical and student.
2
1.2 Problem Statement
There are several problems that lead to develop this system
1. Student need to fill in the form every time they need to meet the medical
assistant, thus it leads to data redundancy.
2. Medical assistant need to manually write the student’s record and need to
check the file for the previous records of the student that came to the health
center.
1.3 Objectives
1. To design a health center management system for UniSZA.
2. To implement the technique of mobile computing in the system.
3. To test the functionality of the system.
1.4 Scopes
1.4.1 Admin
Admin can manage students and medical assistant records. Admin need to
add and update the medicine details in the system.
1.4.2 Students
Students are able to register to the system. After being registered, they
can proceed to log in into the system and fill in the form that provided.
Besides, student can make an appointment before visiting health centre.
PKU Management System will manage the student’s details with their
medical details after visiting the health centre. Students can view their
medical details.
3
1.4.3 Medical Assistants (MA)
Medical assistant will use the system to view a student details. MA need
to log into the system. After logging in, MA can fill in the student’s
treatment records and choose the suitable medicine. MA will be approved
the appointment based on their free schedules. The records can be
retrieve which is help the MA to view the previous student’s record.
1.5 Limitation of work
1. This system only available for students and medical assistants in Unisza
Besut.
2. This system only manage the students, medical assistants, and the health
records of the student.
1.6 Expected Result
This system is expected to be able to help the student from fill in their details every
time that they need to get a treatment to register in a system and just give the matric
number to medical assistant. The redundancy of records can be reduced with this
management system. Besides, the system can be accessed by using mobile
application. It also can help medical assistants to retrieve the previous records of the
student from this system.
4
1.7 Activities
Week
Task Name
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Project Title
Discussion With
Supervisor
Abstract And
Title Submission
Analyser And
Determine The Of
Objective
Analyser Problem
Statement &
Literature Review
Proposal
Presentation
Proposal
Correction
Designation Of
Framework &
Functional
Design
Documentation
Presentation FYP
Report
Submission
5
CHAPTER II
LITERATURE REVIEW
2.1 Introduction
This chapter discusses the literature for the Pusat Kesihatan UniSZA (PKU)
Management System to be developed. In this chapter it will be described how this
project relates to existing research, techniques, and related technology. Thus, based
on the reviews and evaluation from the existing system, it will be a guidelines in
developing the system. There are many system have been develop for health centre
or hospital that provided the records of the patients, medicine and payment details
after visiting the hospital or getting a treatment.
2.2 Management Information System.
Management information system, or MIS, broadly refers to a computer-based
system that provides managers with the tools to organize, evaluate and efficiently
manage departments within an organization. In order to provide past, present and
prediction information, a management information system can include software that
helps in decision making, data resources such as databases, the hardware resources
of a system, decision support systems, people management and project management
applications, and any computerized processes that enable the department to run
efficiently.
6
2.3 Mobile Computing
Based on an article by A.Scherchen (2017),mobile computing is the advances in
wireless networking have prompted a new concept of computing, called mobile
computing in which users carrying portable devices have access to a shared
infrastructure, independent of their physical location. This provides flexible
communication between people and (ideally) continuous access to networked
services. Mobile computing is revolutionizing the way computers are used and in
the coming years this will become even more perceptible although many of the
devices themselves will become smaller or even invisible (such as sensors) to users.
2.4 Cordova Apache
Apache Cordova is an open-source mobile development framework. It allows
you to use standard web technologies - HTML5, CSS3, and JavaScript for cross-
platform development. Applications execute within wrappers targeted to each
platform, and rely on standards-compliant API bindings to access each device's
capabilities such as sensors, data, network status, etc.
2.5 Android
Android is a popular, Linux-based mobile phone operating system developed by
Google. The Android operating system (OS) powers phones, watches, and even car
stereos. Android is a widely-adopted open-source project. Google actively develops
the Android platform but gives a portion of it for free to hardware manufacturers and
phone carriers who want to use Android on their devices. Google only charges
manufacturers if they also install the Google apps portion of the OS.
7
2.6 Research of Studies
Table 2.1: Description on method used in PKU Management System
TITLE AUTHOR/
YEAR
OBJECTIVES SUMMARY TECHNIQUE/
METHOD
Mobile
computing
acceptance
factors in the
healthcare
industry: A
structural
equation
model
Jen-Her Wu,
Shu-Ching
Wang, Li-
Min Lin
January,
2007
A revised
technology
acceptance model
to examine what
determines
mobile healthcare
systems (MHS)
acceptance by
healthcare
professionals
In this journal,
further study is
needed to
explore extra
significant
antecedents of
new IT/IS
acceptance for
mobile
healthcare.
Mobile
computing
Mobile
healthcare
information
managemen
t utilizing
Cloud
Computing
and Android
OS
Thomas
Pliakas,
2010
-To develop the
availability of e-
health
applications and
medical
information
anywhere and
anytime and the
invisibility of
computing
In this article, by
using mobile
application can
provides the
management of
patients health
records and it
can be updated,
retrieved the
Cloud
computing,
Android
operating
system
8
- To utilize cloud
computing and
Android operating
system in mobile
healthcare
information
management
system
data using cloud
computing
Mobile
Application
Web service
Performanc
e Analysis:
Restful
Services
with JSON
and XML
Carlos
Rodrigues,
José
Afonso,
Paulo Tomé
2011
To show how
restful Web
services,
combined with
JSON, may help
developers to fill
this gap while
keeping security,
stability and speed
In this paper, it
will shows how
the restful Web
services
combined with
JSON may help
the
communication
between the
mobile
application and
the pre-existing
background
system become
stable , secure
and light way.
JSON, XML
9
The
developmen
t of hybrid
mobile
applications
with Apache
Cordova
Heitkötter,
H.,
Hanschke,
S., &
Majchrzak,
T. A.
2012, April
Apache Cordova
tools that we used
to develop cross-
platform or hybrid
applications.
In this paper,
Apache
Cordova are
used to build
hybrid
application.
Hybrid
applications or
cross-platform
application are a
flexible solution
for the rapid
development of
smart devices.
Apache
Cordova
10
2.7 Application on PKU Management System
2.7.1 Hospital Management System
A hospital management system (HMS) is a computer or web based system
that facilitates managing the functioning of the hospital or any medical set
up. This system or software will help in making the whole functioning
paperless. It integrates all the information regarding patients, doctors, staff,
hospital administrative details etc. into one software. It has sections for
various professionals that make up a hospital.
Not only for the doctors and patients, this system also manage the functioning
of the hospital or any medical set up which is the occupancy, staff, supplies
control, billing, laboratory and employees. A Web based HMS can be used
for providing online services to patients, appointments and obtaining
opinions of consultants sitting away from the hospital set up.
Figure 2.1: Appointment page of HMS
11
Figure 2.2: HMS’s patient registration form
2.7.2 SoftClinic
SoftClinic is world best EHR & HMS (Hospital Management System) with
all required features to run a practice or hospital smoothly and hassle free.
SoftClinic has become preferred choice for respective physicians, clinics,
hospital and nursing homes. Currently there are more than a million patients
registered on SoftClinic in over 30 countries. Having various integrated
modules like pharmacy, laboratory, human resources and financial
accounting, it has everything a physician needs. This system has appointment
management, charting and patient portal features. Besides, this system can
be access by using mobile phone and personal computer.
12
Figure 2.3: Appointment page of SoftClinic
Figure 2.4: SoftClinic’s patient details
13
2.7.3 Dr.Pad Management Application
By using Dr.Pad management app, user can manage patient records such as
personal information, medical reports, medication, visit history, clinical
notes, patient history, and other notes. Appointments for patients can be
easily handled using Dr.Pad app. User just log in through Google, Facebook
or Twitter account, then user can save their data in a secure cloud. There are
two type of features which the free features and paid features. For the free
features, user can create and keep track of patient's appointments, visit
history, and medical records. SMS and/or email prescription, appointment
reminder, and visit history to a patient.
Figure 2.5: Appointment and patient details page of Dr.Pad
14
2.8 Summary
The idea of proposing Pusat Kesihatan UniSZA (PKU) Management System is
based on the previous research materials includes articles, journals, papers and
existing systems. Based on the research, the existing systems are very helpful to
develop the PKU management system better.
15
CHAPTER III
METHODOLOGY
3.1 Introduction
This chapter covers the details explanation of methodology used in this system.
A methodology is a model, which employ for the design, planning, implementation
and achievement of the project objectives. Common methodologies include
Waterfall, Spiral Development, Rapid Application Development (RAD) and Agile
Software Development. Hence, this project will adapt the use of waterfall model as
a software development life cycle (SDLC).
3.2 System Development Life Cycle (SDLC)
The systems development life cycle (SDLC) is a conceptual model used in
project management that describes the stages involved in an information system
development project, from an initial feasibility study through maintenance of the
completed application. The life cycle defines a methodology for improving the
quality of software and the overall development process.
3.3 Waterfall Model
Waterfall model is a sequential design process which the progress is seen as
flowing steadily downwards through the phases. In a waterfall model, each phase
must be completed before the next phase can begin and there is no overlapping in t
the phases. In waterfall model, there are generally five phases involved, which are
analysis, design, implementation, testing and maintenance.
16
Figure 3.1 Model of Waterfall
Requirement Analysis
All possible requirements of the system to be developed are captured in this
phase and documented in a requirement specification document.
In this phase, the system requirements have been collected and analyzed. The
problems statements, objectives and scope of the project have been defined.
The requirement have been specified based on the scope and user which is
students and medical assistant.
17
Design
The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture.
Design phase is important because it shows the detailed of the system and its
functionality. For example, Context Diagram (CD), Data Flow Diagram
(DFD) and Entity Relationship Diagram (ERD). A DFD shows the
movement of the data between processes, entities and data store. The
database and interface design also have been designed.
Implementation
With inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit
Testing.
Codes have been written according to specification, requirements and
diagrams design in previous phase. By using PHP and Xampp Server the
codes are written. In this phase the JSON are used for storing and exchanging
data.
18
Verification/Testing
All the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is tested
for any faults and failures.
For PKU Management System, testing is vital to ensure the functionality.
Intention of testing is to detect an error so that all the error can be corrected.
This process helps in discovering vulnerabilities that are not discovered in
the previous phase.
Deployment of system
Once the functional and non-functional testing is done; the product is
deployed in the customer environment or released into the market.
Maintenance
There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
This phase is needs to maintain the system and make a changes if needed
until the project is completely better.
19
3.4 Framework and Design
3.4.1 Framework
Figure 3.2 shows the framework for PKU Management System. In order to
access the system, student will be needed to register first before proceeding
into the login page and accessing system. After succeed logging in, the
students can access their user interface and make an appointment. The
appointment details will be in the database and the medical assistant will
make the confirmation of the appointment. The medical assistant will update
the treatment details of the students and choose the right medicine. Admin
will be add the medicine in the system. Besides, student can review the
treatment information after the medical assistant update in the system.
Figure 3.2: Framework of PKU Management System
20
3.4.2 Context Diagram
Figure 3.3 shows the Context Diagram for PKU Management System. Since
PKU Management System involve three actor which the Admin, Student and
Medical Assistant, the context diagram will explain more about the flow
between the three actors and what they are capable to do with their own
authorization.
Figure 3.3: Context Diagram of PKU Management System
21
3.4.3 Data Flow Diagram Level 0
Figure 3.4 show an in-depth processes flow of the system based on context
diagram that had been explained before. This is where the details of
functionality will be stretch out for better understand what the system do.
There are ten process involve in PKU Management System which is
Registration, Login, Make appointment, Approve appointment, Manage
student, Manage medical assistant, Manage treatment record, Manage
medicine, Manage user and Manage report. There are five data store involved
which are Student, Medical assistant, Appointment, Treatment and
Medicine.
22
Figure 3.4: DFD Level 0 of PKU Management System
23
3.4.3 Data Flow Diagram Level 1
Below are Data Flow Diagram Level 1 involved in this system. This include
the Admin, Student and Medical assistant.
3.4.3.1 Admin
Figure 3.5 shows the DFD level 1 of Admin. In DFD level 0, admin were
involve in four processes including manage medicine (process 8.0), manage
user (process 9.0) and manage report (process 10.0). In DFD level 1, the
process of managing medicine (process 8.0) is divided into two sub processes
which is add medicine (process 8.1) and delete medicine (process 8.2).
Besides, the process of managing user (process 9.0) only has one sub process
which is delete user (process 9.1). The process of managing report (process
9.0) also has one sub process which is view report (process 10.1).
24
Figure 3.5: Data Flow Diagram Level 1 (Admin)
25
3.4.3.2 Student
Figure 3.6 shows the DFD level 1 of Student. In DFD level 0, student
were involve in three processes including register student (process 1.0), login
(process 2.0), make appointment (process 3.0) and manage student (process
5.0). In DFD level 1, the process of managing student (process 5.0) is divided
into three sub processes which is edit profile (process 5.1), view profile
(process 5.2) and view treatment record (process 5.3).
Figure 3.6: Data Flow Diagram Level 1 (Student)
26
3.4.3.3 Medical Assistant
Figure 3.7 shows the DFD level 1 of Medical Assistant. In DFD level 0,
medical assistant were involve in three processes including approve
appointment (process 4.0), manage medical assistant (process 6.0), and
manage treatment records (process 7.0). In DFD level 1, the process of
managing medical assistant (process 6.0) is divided into two sub processes
which is edit profile (process 6.1) and view profile (process 6.2). Moreover,
the process of managing treatment records (process 7.0) is divided into four
sub processes which are add treatment records (process 7.1), edit treatment
records (process 7.2), view medicine (process 7.3) and choose medicine
(process 7.4).
27
Figure 3.7: Data Flow Diagram Level 1 (Medical Assistant)
28
3.4.4 Entity Relationship Diagram (ERD)
Figure 3.8 shows the tables and their relationship one to another. All tables
are normalized to a satisfactory level as shown below. There are three entity
consist of Admin, Student and Medical assistant.
29
Figure 3.8: ERD of PKU Management System
30
3.5 Data Decomposition
3.5.1 System as general
Figure 3.9 below shows that the PKU Management System are open for
student and medical assistant in UniSZA use. First, user need to register as
the system user. After being confirm as a user then they need to login. In this
system, there are three types of user which is Admin, Student and Medical
Assistant and then each of the user will be directed to their own homepage.
Figure 3.9: Data decomposition of PKU Management System
31
3.5.2 Admin
Figure 3.10 below shows the data decomposition of an Admin. The admin
will be able to approve the appointment, manage medicine, manage user and
manage report.
Figure 3.10: Data decomposition of Admin
32
3.5.3 Student
Figure 3.11 shows the data decomposition of Student. For student, there are
three main functionality that they can do including manage profile, make an
appointment and logout.
Figure 3.11: Data decomposition for Student
33
3.5.4 Medical Assistant
Figure 3.12 below shows the data decomposition of a Medical
Assistant. For medical assistant, they also have three main functionality
including manage profile, manage treatment record and logout.
Figure 3.12: Data decomposition of Medical Assistant
34
3.6 Data Dictionary
A database is a collection of information that is organized so that it can be easily be
access, manage and update. There are six table involve in this PKU Management
System. Each attributes displayed in ERD will be describe in this section.
3.6.1 Table Admin
Table 3.1 shows the attributes in Table Admin.
Table 3.1: Details of admin table in PKU Management System
Column Types Null Default Description
id varchar(10) no none Primary key
email varchar(50) no none
password varchar(20) no none
3.6.2 Table Student
Table 3.2 shows the attributes in Table Student
Table 3.2: Details of student table in PKU Management System
Column Types Null Default Description
matricNo varchar(10) no none Primary key
fullName varchar(50) no none
faculty varchar(4) no none
email varchar(20) no none
password varchar(15) no none
confirmPassword varchar(15) no none
35
3.6.3 Table Medical Assistant
Table 3.3 shows the attributes in Table Medical Assistant.
Table 3.3: Details of medical assistant table in PKU Management System
Column Types Null Default Description
maName varchar(10) no none
staffID varchar(50) no none Primary key
email varchar(20) no none
password varchar(15) no none
confirm
password
varchar(15) no none
3.6.4 Appointment
Table 3.4 shows the attributes in Table Appointment.
Table 3.4: Details of appointment table in PKU Management System
Column Types Null Default Description
id varchar(10) no none Primary key
matricNo varchar(10) no none Foreign Key
appointDate date no none
appointTime time no none
status varchar(10) no none
36
3.6.5 Medicine
Table 3.5 shows the attributes in Table Medicine.
Table 3.5: Details of medicine table in PKU Management System
Column Types Null Default Description
medID varchar(10) no none Primary key
medName varchar(20) no none
3.6.6 Treatment
Table 3.6 shows the attributes in Table Treatment.
Table 3.6: Details of treatment table in PKU Management System
Column Types Null Default Description
id varchar(10) no none Primary key
matricNo varchar(10) no none Foreign key
treatDetails varchar(50) no no
medName varchar(20) no no
37
3.7 Software and Hardware Requirement
Project requirement consists of two parts which are software requirement and
hardware requirement. All those requirement are very important in order to develop
successful application.
3.6.1 Software Requirement
Table 3.7 shows the listed type of software needed.
Table 3.7: Lists of Software Requirement
NO SOFTWARE PURPOSE
1. Notepad ++ To code the system and connection to the
database
2. XAMPP Local server used in the system
3. HTML,PHP Programming language used
4. PhpMyAdmin Software used for database
5. Cordova Apache and
Android Studio
Used to build an APK for mobile
application
6. Microsoft Word and
Power Point (2013)
Use for documentation and presentation.
7. Google Chrome Browser to run the localhost and also for
searching information.
38
3.6.2 Hardware Requirement
Table 3.8 shows the listed type of hardware used.
Table 3.8: Lists of Hardware Requirement
NO HARDWARE PURPOSE
1. Laptop ASUS
2. Processor AMD A4-5100 APU with Radeon ™ HD
Graphics @ 1.55 GHz
3. Memory 6.00 GB RAM
4. Operating System Windows 8
5. System Type 64-bit Operaing System
6. Mobile Phone Galaxy 5s
7. Google Chrome Browser to run the localhost and also for
searching information.
3.7 Summary
In this chapter, the explanation is all about how the system is designed which
includes CD, DFD and ERD. Besides, the explanation of relationship that related
between tables also being explained on this system.
39
CHAPTER IV
IMPLEMENTATION
4.1 Introduction
Implementation method is a systematic structured approach to integrate software
based service or component into workflow of an organizational structure or an
individual end-user. This phase should be done before a system is fully utilized. PKU
Management System may be customized to meet functional requirement and the
whole system is tested before being approve, signed off and becoming a fully
operational production system.
40
4.2 Graphical User Interface Module
4.2.1 Student – Register and Login
Figure 4.1 shows that the registration and log in part for student in the system.
Figure 4.1: Register and Log In (Student) Interfaces
41
4.2.2 Student – Appointment
Figure 4.2 shows the appointment interface. Student can make an
appointment by fill in the form.
Figure 4.1: Appointment (Student) Interface
42
4.2.3 Student – Profile and Treatment Report
Figure 4.3 shows the profile of the student. Student can update their data by
clicking the pencil icon. Thus, student can view the treatment records after
visiting the healthcare centre.
Figure 4.3: Profile and Treatment Record (Student) Interfaces
43
4.2.4 Medical Assistant – Login and Profile
Figure 4.4 shows the log in session for MA. MA had been registered by
Admin and the Staff ID and password are given to log in the system. The profile of
MA shows the full name, staff ID and email.
Figure 4.4: Log In and Profile (MA) Interfaces
44
4.2.5 Medical Assistant – Approve Appointment
Figure 4.5 shows the appointment of the students. There are two icons that
which are approve and reject the appointment. Medical assistant will update the
status appointment by clicking the icon.
Figure 4.5: Approve Appointment (MA) Interface
45
4.2.6 Medical Assistant – Treatment Details
Figure 4.6 shows that the treatment details form. MA need to fill in the form
and choose the medicine when the student visiting the healthcare centre. This details
will be updated to the student.
Figure 4.6: Treatment Details (MA) Interface
46
4.2.7 Admin – Login
Figure 4.7 shows the login session of the admin in the system.
Figure 4.7: Log in (Admin) Interface
4.2.8 Admin – Manage User
Figure 4.8, Figure 4.9 and Figure 4.10 shows the records of the students,
medical assistants and treatment.
Figure 4.8: Medical Assistant Record (Admin) Interface
47
Figure 4.9: Student Record (Admin) Interface
Figure 4.10: Treatment Record (Admin) Interface
48
4.2.9 Admin – Add Medicine
Figure 4.11 shows the list of the medicine. The medicine will be added by
Admin and was listed in treatment details form.
Figure 4.11: Medicine Record (Admin) Interface
49
4. 3 Implementation of Mobile Computing (Coding)
Figure 4.12 and Figure 4.13 shows the command used to build an APK which is
stand for Android Package Kit. These two figures shows by implement Cordova
Apache, Software Developer's Kit (SDK) in Android Studio, Node.js the APK can
be created.
Figure 4.12: Command to create an APK for PKU Management System
Figure 4.13: Command to create an APK for PKU Management System
50
Figure 4.14 shows the IP Address to make connection between mobile
application and local host. While Figure 4.15 and Figure 4.16 shows the code to
build an APK.
Figure 4.14: IP Address for connection
Figure 4.15: Code to build an APK
Figure 4.16: Code to build an APK
51
4.4 Test Case
A test case is a set of conditions or variables under which a tester will determine
whether a system under test satisfies requirements or works correctly. The process
of developing test cases can also help find problems in the requirement or design of
an application. The test cases below shows several processes of the PKU
Management System that have been tested.
4.4.1 Authentication
Table 4.1 shows the test case for authentication in login page. Student,
medical assistant and admin will directed to their homepage after login session.
Table 4.1 Test Case for Authentication
Steps Procedure Expected Result Pass/Fail
1 Go to login page Preview page loaded Pass
2 Enter incorrect details
or invalid account and
submit
Page will show an error
message
Pass
3 Enter correct details
or valid account and
submit
Redirect to homepage Pass
52
4.4.2 Make an appointment (Student)
Table 4.2 shows the test case for student when make an appointment.
Table 4.2 Test Case Success Add Appointment
Steps Procedure Expected Result Pass/Fail
1 Click appointment on
menu
Page will show a form to
fill
Pass
2 Click submit button New data are added and
directed to appointment
status page
Pass
3 Click cancel button The form will be unfilled Pass
4.4.3 Update Profile (Student)
Table 4.3 shows the test case for student updating the profile.
Table 4.3 Test Case Success Update Profile
Steps Procedure Expected Result Pass/Fail
1 Click pencil icon on
profile page
Page will show a
confirmation message
Pass
2 Click submit button
on confirmation
message
Profile is edited and
redirected to view profile
page
Pass
53
4.4.4 Cancel Appointment (Student)
Table 4.4 shows the test case for student cancelling the appointment.
Table 4.4 Test Case Success Delete Appointment
Steps Procedure Expected Result Pass/Fail
1 Click cancel icon on
appointment status
page
Page will show a
confirmation message
Pass
2 Click yes button on
confirmation message
Page will show an success
message
Pass
3 Click no button on
confirmation message
Redirect to previous page Pass
4.4.5 Approve Appointment (Medical Assistant)
Table 4.5 shows the test case for medical assistant make an approval.
Table 4.5 Test Case Success Approve Appointment
Steps Procedure Expected Result Pass/Fail
1 Click approve
appointment on menu
Preview page loaded Pass
2 Click approve icon Page will show approved
status message
Pass
3 Click reject icon Page will show reject
status message
Pass
54
4.4.6 Add Treatment Details (Medical Assistant)
Table 4.6 shows the test case for MA adding the treatment details
Table 4.6 Test Case Success Add Treatment Details
Steps Procedure Expected Result Pass/Fail
1 Click treatment
details on menu
Preview page loaded Pass
2 Click submit button New data are added and
page will show success
message
Pass
3 Click cancel button The form will be unfilled Pass
4.4.7 Add Medical Assistant and Medicine (Admin)
Table 4.7 shows the test case for Admin adding new medical assistant and
medicine.
Table 4.7 Test Case Success Add
Steps Procedure Expected Result Pass/Fail
1 Click add new
medical assistant or
medicine button
Page will show a form to
fill in
Pass
2 Click add button New data are added and
page will show success
message
Pass
3 Click cancel button The form will be unfilled Pass
55
4.4.8 Update Profile (Admin)
Table 4.8 shows the test case success of update profile for Admin.
Table 4.8 Test Case Success Update Profile
Steps Procedure Expected Result Pass/Fail
1 Click pencil icon on
profile page
Page will show a
confirmation message
Pass
2 Click submit button
on confirmation
message
Profile is edited and
redirected to view profile
page
Pass
4.4.9 Delete (Admin)
Table 4.9 shows the test case of delete for Admin
Table 4.9 Test Case Success Delete
Steps Procedure Expected Result Pass/Fail
1 Click student, medical
assistant or medicine
on menu
Preview page loaded Pass
2 Click delete icon Page will show a
confirmation message
Pass
3 Click yes on
confirmation message
Page will show a success
message
Pass
4 Click no on
confirmation message
Redirect to previous page Pass
56
4.4 Summary
Testing and implementation is an interrelated process where each of
implementation modules need to be tested in order to achieve less error and meets
requirement specified. In general, most of the budget consume on implementation
and testing phase because it is core process to complete the product and able to
deliver all the functionalities smoothly.
57
CHAPTER V
CONCLUSION
5.1 Introduction
This final chapter will focus on achievement of the system, system constraints
and suggestion on improvement for PKU Management System.
5.2 Project Constraint
There are several problems occurred throughout the development of the project.
Since this system are based on healthcare centre, most of the existed system are for
clinical and hospital. Besides, PKU management system is a mobile application and
this system can be accessed by using the same internet network only.
5.3 Result Discussion
Generally, this project has been carried out and follow the objectives that have
been stated in Chapter I. This project is based on management system and mobile
computing implementation. PKU Management System can be accessed by using
mobile phone which is easier for students and medical assistant. This system manage
all the records systematically and can be shown as a report. The result is the system
can be installed in APK format as an application in mobile phone.
58
5.4 Future Works
Although PKU Management System is good enough for student and medical
assistant, future works can be consider to enhance the system even more. The future
works suggested are as below:
I. The appointment listed are based on priority schedulling
II. More medicine can be choosen in treatment details form.
III. Students and medical assistant will be notified for appointment status and
approval.
5.3 Summary
Pusat Kesihatan UniSZA (PKU) Management System have meet its objective to
user to make an online registration and manage the health centre. Thus, this system
help student and medical assistant from fill in the form in the paper, by using this
system it can be written in mobile application view. With this system the health
centre become more systematic.
59
REFERENCES
D. Jaramillo, R. Smart, B. Furht and A. Agarwal, "A secure extensible container
for hybrid mobile applications," 2013 Proceedings of IEEE Southeastcon,
Jacksonville, FL, 2013, pp. 1-5.
G. Wang, "Improving Data Transmission in Web Applications via the Translation
between XML and JSON," 2011 Third International Conference on
Communications and Mobile Computing, Qingdao, 2011, pp. 182-185.
C. Doukas, T. Pliakas and I. Maglogiannis, "Mobile healthcare information
management utilizing Cloud Computing and Android OS," 2010 Annual
International Conference of the IEEE Engineering in Medicine and Biology, Buenos
Aires, 2010, pp. 1037-1040.
Rösler, F., Nitze, A., & Schmietendorf, A. (2014, July). Towards a mobile
application performance benchmark. In International Conference on Internet and
Web Applications and Services (Vol. 9, pp. 55-59).
Latif, M., Lakhrissi, Y., Nfaoui, E. H., & Es-Sbai, N. (2016, March). Cross platform
approach for mobile application development: A survey. In Information Technology
for Organizations Development (IT4OD), 2016 International Conference on (pp. 1-
5). IEEE.
Prof. Madhuri Nitin Badgujar Birla College of Arts, commerce, and Science, Kalyan
(w), “Introduction to Mobile Computing”, Aug 22, 2014
Dinh, H. T., Lee, C., Niyato, D., & Wang, P. (2013). A survey of mobile cloud
computing: architecture, applications, and approaches. Wireless communications
and mobile computing, 13(18), 1587-1611.
Heitkötter, H., Hanschke, S., & Majchrzak, T. A. (2012, April). Evaluating cross-
platform development approaches for mobile applications. In International
Conference on Web Information Systems and Technologies (pp. 120-138). Springer,
Berlin, Heidelberg.
Anderson, R.S., Gestwicki, P.: Hello, worlds: an introduction to mobile application
development for iOS and Android. J. Comput. Sci. Coll. 27, 32–33 (2011).
Barnes, P. M., Bloom, B., & Nahin, R. L. (2008). Complementary and alternative
medicine use among adults and children; United States, 2007.
Apache Cordova (2012), http://incubator.apache.org/cordova/