student lecturer appointment system using …
TRANSCRIPT
STUDENT_LECTURER APPOINTMENT SYSTEM
USING SHORTEST JOB FIRST
NURUL AISHAH BINTI AZIZ
BACHELOR OF COMPUTER SCIENCE
(INTERNET COMPUTING) WITH HONOURS
UNIVERSITI SULTAN ZAINAL ABIDIN
2019
i
DECLARATION
I hereby declare that this report is based on my original work and my own effort except
for quotations and citations with the guidance from my supervisor, which have been
fully acknowledged.
Signature:
Name : Nurul Aishah Binti Aziz
Date :
ii
CONFIRMATION
This is to confirm that the project of Student_Lecturer Appointment System was
prepared by Nurul Aishah Binti Aziz, matric number: BTCL16044074. This project
research have fulfilled the condition to be recognized for the level of bachelor of
Computer Science for Internet Computing. The research conducted and the writing of
this report was under the guidance of my supervision.
Signature:
Supervisor : Dr.Suhailan Bin Safei
Date :
iii
DEDICATION
Alhamdulillah. First and foremost, praised to Allah, the Most Gracious and the Most
Merciful for blessing me and give me the opportunity to undergo and complete my final
year project, Student_Lecturer Appointment System.
I would like to express my gratitude to my supervisor, Dr.Suhailan Bin Safei for his
teaching, kindness, patience, guidance and motivation towards this project.
My gratitude also goes to my family, my beloved mother and father, Fariza Binti Fauzi
and Aziz Bin Ismail. Thank you for supporting me and make me accomplish this
project. I would like to give a special gratitude to all my friends, and roommate, whom
giving me the full support and assisted in completing the project even though they also
busy doing final year project. Thank you for all your support and concern.
Last but not least, thank you to everybody whom have been involved directly or
indirectly in completing this project. All your contribution is very valuable. Thank you
and May Allah blessed you.
iv
ABSTRACT
Student_Lecturer Appointment System was proposed to help UniSZA students and
lecturers to ease the process of making appointment between them. This system helps
to make the system efficient, smooth for the booking appointment process and easy for
the management. This system included notification alert to students and lecturers for
every appointment that has been set that act as reminder if they are forgot the
appointment. Through this systems, all of the students can save their time to book
appointment with lecturer and at the same time, this system also ease the lecturers to set
up an appointment details. The main issues that arises in the main existing system is
that the current system are do not have notification alert and also not efficient. The
implementation of this system is it can simplify the process for application to save time
and more user friendly. The main technique that will be used is shortest job first, in
order to waiting time become short and give chance the other student to make
appointment too.
v
ABSTRAK
Sistem Temu Janji Pelajar_Pensyarah telah dicadangkan untuk membantu pelajar
dan pensyarah UniSZA untuk meringankan proses membuat temu janji di antara
mereka. Sistem ini membantu menjadikan sistem yang lebih cekap, lancar untuk
proses tempahan temu janji dan mudah untuk pengurusan. Sistem ini menyediakan
makluman pemberitahuan kepada pelajar dan pensyarah untuk setiap temu janji
yang telah ditetapkan yang bertindak sebagai peringatan jika mereka lupa tentang
temu janji tersebut. Melalui sistem ini, semua pelajar dapat menjimatkan masa
mereka untuk membuat temu janji dengan pensyarah dan pada masa yang sama,
sistem ini juga memudahkan pensyarah untuk membuat butiran temu janji. Isu-isu
utama yang timbul dalam sistem yang sedia ada ialah sistem semasa tidak
mempunyai pilihan temu janji, tidak mempunyai pemberitahuan dan juga tidak
cekap. Pelaksanaan sistem ini dapat memudahkan proses aplikasi untuk
menjimatkan waktu dan lebih mesra pengguna. Teknik utama yang akan digunakan
adalah “shortest job first”, untuk membuatkan masa menunggu menjadi pendek
dan memberi peluang kepada pelajar lain untuk membuat temu janji juga.
vi
CONTENTS
PAGE
DECLARATION i
CONFIRMATION ii
DEDICATION iii
ABSTRACT Iv
ABSTRAK V
CONTENTS Vi
LIST OF TABLES Vii
LIST OF FIGURES Xvi
LIST OF ABBREVIATIONS Xv
CHAPTER I INTRODUCTION
1.1
Background Project
1
1.2 Problem statement 2
vii
1.3 Objectives 3
1.4
1.5
Project Scopes
Limitation of Works
3
4
1.6 Structure Thesis 5
1.7 Summary 6
CHAPTER II LITERATURE REVIEW
2.1 Introduction 7
2.2 Shortest Job First 7
2.3 Hybrid Application 8
2.4 Existing System 10
2.5 Summary 13
viii
CHAPTER III
METHODOLOGY
3.1 Introduction
14
3.2 Iterative Methodology Model 15
3.2.1 Initial Planning Phase 16
3.2.2 Requirement Phase 16
3.2.3 Analysis and Design Phase 16
3.2.4 Implementation Phase
17
3.2.5 Testing Phase 18
3.2.6 Evaluation Phase 18
3.2.7 Deployment Phase 18
3.3 System Requirement 19
3.3.1 Hardware Requirement 19
3.3.2 Software Requirement 20
ix
3.4 System Design 21
3.4.1 Framework Design 21
3.4.2 Process Model 23
3.4.2.1 Context Diagram 23
3.4.2.2 Data Flow Diagram Level 0 24
3.4.2.3 Data Flow Diagram Level 1 25
3.4.2.3.1 Data Flow Diagram Level 1
(Manage Student)
26
3.4.2.3.2 Data Flow Diagram Level 1
(Manage Lecturer)
27
3.4.2.4 Entity Relationship Diagram 28
3.4.5 Database Schema 29
3.5 Proof of Concept 31
3.6 Technique 32
3.7 Summary 32
x
CHAPTER IV IMPLEMENTATION AND RESULT
4.1 Introduction 33
4.2 Implementation and Output 33
4.3 Interfaces 34
4.3.1 Home Page Interfaces 34
4.3.2 Register Page Interface 35
4.3.3 Login Page Interfaces 35
4.3.4 Lecturer Interfaces 36
4.3.4.1 Profile Page 36
4.3.4.2 Update Profile Page 37
4.3.4.3 Appointment List Page 37
4.3.4.4 Update Appointment List Page 38
4.3.4.5 Status Booked Appointment Page 39
xi
4.3.4.6 Update Status Appointment Page
39
4.3.4.7 Notification Page 40
4.3.5 Student Interfaces 41
4.3.5.1 Profile Page 41
4.3.5.2 Update Profile Page 41
4.3.5.3 Appointment List Page 42
4.3.5.4 Book Appointment Page 43
4.3.5.5 Status Booked Appointment Page 43
4.3.5.6 Notification Page 44
4.4 Test Case 45
4.4.1 Login for Lecturer and Student 45
4.4.2 Register for Lecturer and Student 46
4.4.3 Update Profile for Student and Lecturer 47
4.4.4 Add New appointment in Appointment List
for Lecturer
48
xii
4.4.5 Update Appointment in Appointment List for
Lecturer
49
4.4.6 Delete Appointement in Appointment List
for Lecturer
49
4.4.7 Book Appointment for Student 50
4.4.8 Update Status Booking Appointment for
Lecturer
51
4.4.9 Delete Status Booking Appointment for
Lecturer
51
4.5 Summary 52
CHAPTER V CONCLUSION
5.1 Introduction 53
5.2 Contribution and Achievement 53
5.3 Constraint 54
5.4 Suggestion for improvement in Future 55
xiii
5.4.1 Generate Auto Set Up for Time and Date
based on Lecturer Set Up
55
5.4.2 Generate Auto Booking Without to Wait for
Lecturer Responses
55
5.5 Conclusion 56
REFERENCES 57
APPENDIX 58
xiv
LIST OF TABLES
Table TITLE PAGE
2.1 Existing System on Research Papers 12
3.1 Hardware Requirement 19
3.2 Software Requirement 20
3.3 Users 29
3.4 Student 29
3.5 Lecturer 30
3.6 Appointment 30
3.7 Booking Appointment 31
4.1 Test Case Login 46
4.2 Test Case Register 47
4.3 Test Case Update Profile 47
4.4 Test Case Add New Appointment 48
4.5 Test Case Update Appointment List 49
xv
4.6 Test Case Delete Appointment List 49
4.7 Test Case Book New Appointment 50
4.8 Test Case Update Status Booking Appointment 51
4.9 Test Case Delete Status Booking Appointment 52
xvi
LIST OF FIGURES
FIGURE TITLE PAGE
3.1 Iterative Model 15
3.2 System Framework for System 22
3.3 Context Diagram 23
3.4 Data Flow Diagram Level 0 25
3.5 Data Flow Diagram Level 1 for Manage Student 26
3.6 Data Flow Diagram Level 1 for Manage Lecturer 27
3.7 Entity Relationship Diagram 28
4.1 Home Page 34
4.2 Register Page 35
4.3 Login Page 32
4.4 Profile Page for Lecturer 36
4.5 Update Profile Page for Lecturer 37
4.6 Appointment List Page for Lecturer 37
xvii
4.7 Update Appointment Page for Lecturer 38
4.8 Status Booked Appointment Page for Lecturer 39
4.9 Update Status Appointment Page for Lecturer 39
4.10 Notification Page for Lecturer 40
4.11 Profile Page for Student 41
4.12 Update Profile Page for Student 41
4.13 Appointment List Page for Student 42
4.14 Book New Appointment Page for Student 43
4.15 Status Booked Appointment Page for Student 43
4.16 Notification Page for Student 44
xviii
LIST OF ABBREVIATIONS / TERMS / SYMBOLS
CD Context Diagram
DFD Data Flow Diagram
ERD Entity Relationship Diagram
FYP Final year project
SDLC System Live Development Cycle
UniSZA Universiti Sultan Zainal Abidin
xix
LIST OF APPENDICES
APPENDIX TITLE PAGE
A Gantt Chart of Activities And Milestone for FYP 1 59
B Gantt Chart of Activities And Milestone for FYP 2 60
1
CHAPTER I
INTRODUCTION
1.1 Background Project
Online booking system helps to simplify the booking process and raise the
efficiency in management. Nowadays, an appointment for student and lecturer are
always happen in university real-life. Some student are not confidence and shy to ask
anything in front of people . Through an appointment, the students can ask about their
problems in studies or any else personally without any self-problems. An appointment
with lecturers will help students to understand more about their studies in case they are
asking about studies .
Moreover, the appointment will help and ease the students in their matter with
the lecturers. Student_Lecturer Appointment System will help students and lecturers of
University Sultan Zainal Abidin (UniSZA) in making an appointment process between
them become easily and efficiency. They can book the appointment everywhere and
anytime according the lecturers free time. In the system, notification will be show up
for the confirmation and set-up appointment that act as appointment set-up
2
reminder.The main data in the system is the availability of the appointment . The
student can an appointment refer to the time and that has been set .
1.2 Problem Statement
It is impossible to know and suggest the free time to meet the lecturer if we do
not know the lecturer schedule that sometimes they are busy and not in their room.
Without notification alert about the appointment that have been made ,sometimes
either students or lecturers possible to forget about the appointment.
Currently, system for making appointment between lecturers and students UniSZA has
been existed but the system is unsystematic because the student need to ask the lecturer
personally about their schedule and book manually to their lecturer. Moreover, it always
happened in existing system that the students could not reach the lecturer. Sometimes,
the student need to wait long turn for their appointment even though the student need to
meet the lecturer for the appointment only just a little time.
3
1.3 Objectives
The main objective in this project as follows:
i. To proposed the system that will help the students and lecturers UniSZA to
make the process for making appointment between them become easily.
ii. To design and develop a systematic and user friendly system for students
and lecturers UniSZA to ease them to use it.
iii. To develop and implement the system by using shortest job first.
1.4 Project Scope
The scope of this project consist of two which are students and lecturers.
i. Student:
In the student scope, the students can login the system,view,book or cancel
the booking of the appointment based on the listed availabilities by date and
time. The students also can view the lecturers profile, lecturers list record
and, also the status, details and the approval of the appointment.The student
also can update their profile details.
ii. Lecturer:
In this scope,the lecturer can login and update their profile details in the
system.The lecturers can also view students profile,status and the
4
appointment details.Other than that, the lecturers can view,approve the
appointment even the appointment is accept or reject.Moreover,the lecturer
can update the status of the appointment session.
1.5 Limitation of Works
a. Only for student and lecturer in UniSZA
The students or the lecturers from another institution cannot use this
system. This system is only limited to any students or lecturers in
UniSZA.
b. Must have internet connection
The users need an internet connection when to use this system to make
this system function.
c. Only students can book the appointment
The lecturers cannot book an appointment with the student but only
students can book the appointment.
d. Approval for booking appointment can be approved by lecturer only
After the student make appointment, they need to wait until the lecturer
response either reject or accept.
5
1.6 Structure Thesis
A structure thesis of Student_Lecturer Appointment System project concisely
describing the content in this project for each chapter.
1.6.1 Chapter 1: Introduction
In the first chapter, the contents are consist of project introduction, proposal
background, problem statement, objective, project scope, limitation of work and
Gantt chart.
1.6.2 Chapter 2: Literature Review
Chapter two is about literature review. In this chapter, will be discussing and
analysing the problem towards the existing systems. Shortest Job First method
that will be used in the system will be discussed.
1.6.3 Chapter 3: Methodology
Chapter three will be described the methodology of the research used in the
system. The detailed explanations about every phase are stated.
6
1.6.4 Chapter 4: Design and Project Modelling
Chapter four discuss about design and data modelling comprises of a context
diagram, data flow diagram, framework, and database design. Besides, more
details will be describe about the design of the model.
1.6.5 Chapter 5: Implementation and Results
This chapter consist of the explanation about implementation of this system.
1.6.6 Chapter 6: Conclusion
In chapter six, project achievement, project limitation and some improvements
will be discussed. Finally, the conclusion will be produced.
1.7 Summary
In chapter 1, the purpose of the project of the system is identified to overcome
the problem that occur in the current system. Also, the function and limit of the
project are stated. Besides, the brief about every chapter was stated in this chapter.
7
CHAPTER II
LITERATURE REVIEW
2.1 Introduction
Literature review is made research about the critical points of current knowledge on
a specific topic. The purpose is to justify the choice of research questions, theoretical
or conceptual framework, and the method. In this chapter consist of system review and
method review. System review is about the comparison for the existing system whereas
the method review is study and analyze about the technique and methodology that suited
for the system.
2.2 Shortest Job First
Shortest Job First is an operating system process scheduling algorithm and a
network routing management mechanism that automatically executes queued requests
and processes by the duration for that process to finish the process. With shortest job
first,which process has the shortest duration or time to finish will go first and follow the
second shortest and etc. Shortest Job First provides an efficient, simple ,make waiting
time for other process become short and will make many process can be executed at
that time.
8
Let's take a look at how Shortest Job First process scheduling works. Suppose there
are three processes in a queue: P1, P2 and P3. P1 is placed in the processing register
with 10 minutes for complete processing. The next process, P2, 10 seconds has 20
minutes to finish and P3 has 15 minutes to finish to process is processed. P1 will go
first becasuse it has shortest time to finish, followed by P3 and P2 due to its time to
finish when executes the process.
2.3 Hybrid Application
A hybrid application is an application that will used mobile application and web
based application as platforms to build this system.
A web based application is a software package that can be accessed through
the web browser. The software and database reside on a central server rather than
being installed on the desktop system and is accessed over a network.The
application is built in UniSZA web hosting . It is a client–server computer
program in which the client (including the user interface and client-side logic) runs
in a web browser. Common web applications include webmail, online retail sales,
online auctions, wikis, instant messaging services and many other functions. An
application that is usable only with an active Internet connection and that uses
HTTP as its primary communications protocol. HTML5 introduced explicit
9
language support for making applications that are loaded as web pages, but can store
data locally and continue to function while offline.Web-based applications
are easy to use and can be implemented without interrupting existing work process.
Whether need a content managed solution or an e-commerce system, we can develop a
customized web application that fulfills the requirements. The web based software,
enables to interact with the application and data in a fluid and highly responsive
manner.
A mobile app or mobile application is a computer program of
software application designed to run on a mobile device such as a phone/tablet or
watch. Mobile applications frequently serve to provide users with similar services to
those accessed on PCs. Apps are generally small, individual software units with limited
function. This use of app software was originally popularized by Apple Inc. and its App
Store, which offers thousands of applications for the iPhone, iPad and iPod Touch. A
mobile application also may be known as an app, web app, online app, iPhone app or
smartphone app. A mobile application also useful when the user want to access
anywhere and anytime when they want to use it. For building an mobile application, the
platform to build this system through apache cordova and android studio platform.
10
2.4 Existing System
Existing system is the example of the functional online system that are related to this
system.
Table 2.1: Existing System on Research Papers.
Author/Title/Year Content Advantages
BELLO
Ridwan
Oluwaseun,
OLUGBEBI
Muyiwa,
BABATUNDE
Abdulrauph
Olanrewaju,
BELLO
Bashir
Omolaran,
BELLO Shakirat Iyabo
/Student-Teacher
Online Booking
Appointment System in
Academic
Institutions/2016
The student-teacher web-based
booking appointment system
develped for academic
institutions provided a login
menu and a registration form for
new user.This comprises of an
interface that is user-friendly to
capture password, username and
registration codes, for the student
to log in unto the account. The
appointment’s page create a
platform to book an appointment
with the lecturer with an auto
generated authentication which
also helps prove that the user is
not a robot. In each student’s
account, data relating to the
lecturer and student are inputted
and appointment offered.
minimize time
usage not only for the
students and lecturers
using web based
appointment
11
Alaa Qaffas, Trevor
Barker/Online
Appointment
Management
System/2015
Lecturers can add projects for
students by adding the project
name and description. In
addition, students can select a
lecturer’s name, and then choose
a project from a list of projects
which can be added by the
lecturer. After a student joins a
project, the lecturer has to accept
that student’s decision in order to
allow the student to book an
appointment with them. a new
web application will be
developed. It will be
programmed by ASP.NET with
code behind visual basic. An
online appointment management
system will allow students and
lecturers to interact with each
other in real time.
students and lecturers
who are using the
system will receive
information in
real-time, all
processes are
performed in real-
time which cuts
down
drastically on
mistakes and errors
12
Liliana, Azmi/online
appoinment system for
FSKKP (OASF)/2014
This system is a web-based
platform and will be created
using server side scripting such
as PHP with Apache Web Server,
user side scripting such as HTML
and CSS also MYSQL as a
database for the system. Users
can access to the system
anywhere as long as there is an
internet connection.
Appointments are made based on
the time slots of the lecturer
which can be updated by lecturer
and also administrator. Lecturer
will have to update their
availability because in case they
are on leave or have meetings
The students will check the
lecturer's availably and pick the
time slot they would like to meet
the lecturer. Then, a request will
be submitted and lecturers will be
notified via email. If the lecturer
is not available, the system will
suggest other time slot that the
student can pick.
Facilitate
communication
among lecturer and
student, contact the
lecturers via phone or
through sending
messages(real-time),
able to manage their
appointments with
students and can also
check the approved
appointments
whenever they are
logged in into the
system.
13
2.5 Summary
From this chapter, the main function of the project have been explained
specifically like the function of shortest job first and hybrid application. After that,
the analysis from the past projects that had a similar function are made as a reference
and g guidance about how to develop this project. There are some helpful
information that can be used for the developing phases.
14
CHAPTER III
METHODOLOGY
3.1 Introduction
This chapter will be discuss about the methodology that are being used in this
project. With the methodology, the project will have the guidance to support the system
and to ensure that the project is complete and working well. There are many
methodology recommendation to develop the system like waterfall model, spiral model
and agile model in the System Development Live Cycle (SDLC). These approaches
should be chosen wisely based on the suitability of the system before the beginning of
the development phase as it will become the guidance through the development process.
The methodology of the SDLC proposed in this system is Iterative model.
This chapter also will discuss and explained on the design implementing the system and
proof of concept for this system. The system design will consists of context diagram,
Data Flow Diagram(DFD) Level 0, Data Flow Diagram(DFD) Level 1, Entity
Relationship Diagram(ERD) and data schema.
15
3.2 Iterative Methodology Model
Student_Lecturer Appointment System uses iterative model as the methodology
throughout this project An iterative life cycle model does not attempt to start with a
full specification of requirements. Instead, development begins by specifying and
implementing just part of the software, which can then be reviewed in order to
identify further requirements. This process is then repeated, producing a new version
of the software for each cycle of the model. The advantages using iterative model are;
it generates working software quickly and early during the software life cycle, more
flexible, and less costly to change scope and requirements It also easier to test and
debug during a smaller iteration, easier to manage risk because risky pieces are
identified and handled during its iteration and each iteration is an easily managed
milestone. Moreover, the advantages of the system is adaptive due to the changing of
requirements and technologies.
Figure 3.1: Iterative Model
16
3.2.1 Initial Planning Phase
In the planning phase, the idea of the Student_Lecturer Appointment System is
generated to help the users which is the student and the lecturer to be able to use easily
and for systematic system in the making process of making appointment between them.
The priority queue; shortest job first is capable to solve the issue of the user that are
being treated indifferently. The discussion session about the problem faced in the
system are determined and arranged with the supervisor weekly.
3.2.2 Requirement Phase
During this second stage, the user requirement is analysed in order to properly
generate the models and business logic that will be used in the application. All of the
information are obtained through the research papers and journal of the previous works
and the existing system. The system requirements are identified by direct observation
in the existed booking systems and several research papers. At the end of this phase,
objectives, scope and limitation of works are determined.
3.2.3 Analysis and Design Phase
Once the planning and requirement phase are complete for the cycle, an analysis
is performed to point out the appropriate business logic, database models and to know
any other requirements of this particular stage. Moreover, the design stage also occurs
17
in this phase of iterative model, where the technical requirements are established that
will be utilized in order to meet the need of analysis stage. All the information which is
obtained in the analysis phase is used to design the realistic framework. All of the
information in the previous phases are gathered and transformed into the design which
is follow the identified requirement. Then, there will be Context Diagram (CD), Data
Flow Diagram (DFD) level 1 and level 2 and also the Entity Relationship Diagram
(ERD), data dictionary and interface design of the system. The design for the interface
should cover some of the basic features in Student_Lecturer Appointment System. The
purpose of using these diagram is because to improve the understanding on how the
system will function.
3.2.4 Implementation Phase
This is the third and the most important phase of the iterative model. Here, the
actual implementation and coding process is executed. All planning, specification, and
design documents up to this point are coded and implemented into this initial iteration
of the project.
18
3.2.5 Testing Phase
After the current build iteration is coded and implemented, testing is initiated
in the cycle to identify and locate any potential bugs or issues that may have been in the
software.
3.2.6 Evaluation Phase
The evaluation phase, where the phase that get along with the user, examine the
status of the project and validate whether it is as the user requirements .
3.2.7 Deployment Phase
This phase is the final phase will only achievable as there were no errors or any
improvement to be made as proven during testing and evaluation phase.
19
3.3 System Requirement
In the development of this system, the requirements such as software and hardware
are the most crucial requirement to ensure that the development process flow smoothly.
Below are several requirements that involved during development of this system.
3.3.1 Hardware Requirement
Below are the hardware requirements that are used during development of this system:
Table 3.1 : Hardware Requirement
Hardware Description
Laptop:
Hp
Intel(R)
4GB RAM
Window 10
Develop system, write and modify
documents during process development
this system.
Canon Pixma E560 Print documents
20
3.3.2 Software Requirement
Below are the hardware requirements that are used during development of this system:
Table 3.2 : Software Requirement
Software Description
Microsoft Word 2016
Microsoft Power Point 2016
Tools for create
and modifying documents and prepared
for presentation
E-Draw Max Tools to draw CD, DFD and ERD
Web browser
Web hosting
laravel
Google chrome
MySQL(phpMyAdmin)
Web browser and google chrome are
used to find resources and articles about
system. Web hosting, laravel and
phpMyAdmin(MySQL) are used to
develop system and run using web
hosting.
Cordova
Npm
Node js 8.11.1
Jdk 1.8.1
Tools to convert the system to mobile
applications.
21
3.4 System Design
In the system design, the flow of the system is organized to enable the system
development will progress smoothly. The details of the framework, context diagram,
data flow diagram (DFD) and also the entity relationship diagram (ERD) will be
explained in detailed in this chapter. The way of the system functionality is drawn in
the diagram to make clear the understanding of the each process of the system and
facilitating the interaction between the system designer, programmer and also the end-
users.
3.4.1 Framework Design
The framework are indicating on what kind of programs should be build and
how they would interrelate. In the figure 3.3.1.1, the student can book, view available
time and date appointment that they want to book and also they can cancel boking.
After the student booking the appointment, they can view their own booking details.
The lecturer can approve the appointment either accept or reject. The website and
mobile application of the booking system act as the interface to the user of the system
which retrieves and send the data to the system database through the server.
22
Figure 3.2.: System Framework for System.
23
3.4.2 Process Model
3.4.2.1 Context Diagram
From the context diagram in Figure 3.4.2.1.1, there are two entities involved in
the Student_Lecturer Appointment System which are student and lecturer. The data
flow coming from the student shows that the student provides to the system for the
process of registering, login, and book/cancel. The booking detail, and booking
confirmation, will be given to the student. The student can check the available time and
date. For the lecturer, the data flow in and out are the same as the student but the lecturer
cannot book appointment with the student only can view and approve the appointment.
Figure 3.3: Context Diagram
24
3.4.2.2 Data Flow Diagram Level 0
From the data flow diagram level 0 below, it show ten process and ten data store
in the system. There are two entities which are student and lecturer are involved in the
system. The student entity are involved in manage student process, register user
process, login process, manage booking appointment process, and manage live
conference process. The lecturer entity are involved in manage lecturer process, manage
live conference process, login process ,register user process and manage appointment
process and manage status appointment process.
The data store that involved within the process are, data store D1 of register file,
data store D2 of login file, data store D3 of student file, data store D4 of lecturer file,
data store D5 of time slot file, data store D6 of booking file, data store D7 of status file,
data store D8 of appointment file, data store D9 of notification file and data store D10
of live conference history file.
In the register user process, student and lecturer will provide the registration
details and will be stored in data store D1. For login process, the student and lecturer
provide the login details and stored in D2. In the manage student process, student was
involved that student will provided profile details and the data were sent to D3. In the
manage lecturer process, lecturer was involved that student will provided profile details
and the data were sent to D4 . In the manage appointment process, lecturer was involved
that lecturer will provided time slot details and the data were sent to D5.In manage
booking appointment process, student is involved .The student will provided booking
appointment details and the data will go to D6. In manage status appointment process
25
the lecturer will give appointment approval details and the data will go to D7. For
manage booked appointment process and manage notification, there will be nobody
involved just the system.
Figure 3.4.: Data Flow Diagram Level 0
26
3.4.2.3 Data Flow Diagram Level 1
3.4.2.3.1 Manage Student
Based on the data flow diagram level 1 for manage student process in Figure
3.4.2.3.1.1, one entities are involved which are student. There are view/read, and update
profile student. The data will be stored in data store D3 of student file.
Figure 3.5: Data Flow Diagram Level 1 for Manage Student
27
3.4.2.3.2 Manage Lecturer
Based on the above data flow diagram level 1 for manage lecturer process, one
entities are involved which are lecturer. There are view/read, and update profile lecturer.
The data will be stored in data store D4 of lecturer file.
Figure 3.6: Data Flow Diagram Level 1 for Manage Lecturer
28
3.4.2.4 Entity Relationship Diagram(ERD)
The figure 3.7 below shows an entity relationship diagram (ERD) for
Student_Lecturer Appointment system. There are student, lecturer, appointment,
appointment notification and time slot/free time schedule entity. They are connected to
each other.
Figure 3.7: Entity Relationship Diagram (ERD)
29
3.4.2.5 Database Schema
In this section, the basic structure of the table composing the database for the project
are shown .
a) Table Name : Users
Table 3.3: Users
Table 3.3 shows the database of users. This table keeps the information about user that
use this system. It shows all attributes involves in that table and id is the primary key in
that table.
b) Table Name : Student
Table 3.4: Student
30
Table 3.4 shows the database of student. This table keeps the personal data about the
student personal details. It shows all attributes involves in that table and studentID is
the primary key in that table.
c) Table Name : Lecturer
Table 3.5 : Lecturer
Table 3.5 above shows the database of lecturer. This table keeps the personal data about
the lecturer personal details. It shows all attributes involves in that table and lecturerID
is the primary key in that table.
e) Table Name: Appointment
Table 3.6 : Appointment
Table 3.6 above shows the database of appointment. This table keeps the information
details about appointment that has been created by lecturer. It shows all attributes
involves in that table and appointmentID is the primary key in that table.
31
f) Table Name: Booking Appointment
Table 3.7 : Booking Appointment
Table 3.7 shows the database of booking appointment. This table keeps the information
details about booking appointment that has been booked by student. It shows all
attributes involves in that table and id is the primary key in that table.
3.5 Proof of Concept
In Student_Lecturer Appointment System, the concept that are used are priority;
shortest job first and k-means clustering. From the explanation from chapter 2, the
priority concept are used to the student . The concept are applied in the booking process.
From the normal basic of the booking system which are shortest job first which means
whom are duration of appointment is shortest can have the appointment first.
In this case the priority have took place beside shortest job first. The priority were
given to the user whom have the highest priority over the normal user. For example, if
32
there are two student want to book appointment at the same time and date, the priority
were given to the student whom has the shortest time and then the other student.
3.6 Technique
In this system the techniques will be used are shortest job first. Shortest job first will
used when the lecturer to determine whose appointment will go first to make waiting
for other student become short and make the other students chance to make appointment
that day become successful and achieve. Through this techniques many appointment
can be made at that day.
3.7 Summary
From this chapter, the framework, context diagram (CD), data flow diagram (DFD)
level 0 and level 1, entity relationship diagram (ERD) and data schema has been
presented. The framework and context diagram will be the general function while the
details are on data flow diagram level 0 and level 1.
33
CHAPTER IV
IMPLEMENTATION AND RESULT
4.1 Introduction
This chapter consists of two sections which is implementation and testing. The
implementation section discuss on how the system has been developed, flow of the
system along with the interfaces of the system. The testing section which will discuss
the analysis of testing that has been conducted for evaluating the functionality of this
system. Test cases which test and show the system functionality module by module to
ensure all module fully works and function. Test cases also show the result or expected
output after the testing.
4.2 Implementation and Output
The implementation of Student_Lecturer Appointment System can be started when the
design phase is complete. During this stage, a step-by-step development and installation
of the project would be performed. Once the system has been completed and tested, it
can be used by the user.
34
4.3 Interfaces
This section will describe about the interface in the system. The system interface is the
interaction between the user and the system so that the user can make the choice on the
interface and the system will process it. The system has two user which are student and
lecturer. There are interfaces for student and lecturer.
4.3.1 Home Page Interface
Figure 4.1: Home Page
Figure 4.1 above shows the home page of this system either for student or lecturer. In
this interface consists two menu, login and register.
35
4.3.2 Register Page Interface
Figure 4.2: Register Page
Figure 4.2 above shows the register interfaces for both user either student or lecturer.
They need to fill the all information that shown in the interface to register .
4.3.3 Login Page Interface
Figure 4.3: Login Page
36
Figure 4.3 above shows the login interfaces for both user either student or lecturer. They
need to fill the email address and password that has been created when register process.
4.3.4 Lecturer Interfaces
4.3.4.1 Profile Page
Figure 4.4: Profile Page for Lecturer
Figure 4.4 above shows the profile interfaces for lecturer. It shows all information about
lecturer’s personal data.
37
4.3.4.2 Update Profile Page
Figure 4.5: Update Profile Page for Lecturer
Figure 4.5 above shows the update profile interfaces for lecturer. It retrieve the data
based on lecturerID and the lecturer can modify it.
4.3.4.3 Appointment List Page
Figure 4.6: Appointment List Page for Lecturer
38
Figure 4.6 above shows the appointment list page interfaces for lecturer. It shows all
appointment that has been created by the lecturer.
4.3.4.4 Update Appointment List Page
Figure 4.7: Update Appointment Page for Lecturer
Figure 4.7 above shows the update appointment list interfaces for lecturer. It will show
when you click update button for any appointment.
39
4.3.4.5 Status Booked Appointment Page
Figure 4.8: Status Booked Appointment Page for Lecturer
Figure 4.8 above is the status booked appointment interfaces that shows all appointment
that has been booked by student. It consists of update and delete button for any
modification for any appointment.
4.3.4.6 Update Status Appointment Page
Figure 4.9: Update Status Appointment Page for Lecturer
40
Figure 4.9 above shows the interface will out when you click update button to modify
the status of any appointment . The lecturer may update the status of the appointment
either reject or accept and maybe the lecturer add some comments.
4.3.4.7 Notification Page
Figure 4.10: Notification Page for Lecturer
Figure 4.10 above shows the notification interface is for lecturer and it shows the details
for appointment every time new appointment book and the appointment has been set .
41
4.3.5 Student Interfaces
4.3.5.1 Profile Page
Figure 4.11: Profile Page for Student
Figure 4.11 above shows the profile interfaces for student. It shows all information
about student personal data.
4.3.5.2 Update Profile Page
Figure 4.12: Update Profile Page for Student
42
Figure 4.12 above shows the update profile interfaces for student. It retrieve the data
based on studentID and the student can modify it.
4.3.5.3 Appointment List Page
Figure 4.13: Appointment List Page for Student
Figure 4.13 above shows the appointment list page interfaces for student. It shows all
appointment details that has been created by the lecturer and the student can book based
on the list .
43
4.3.5.4 Book Appointment Page
Figure 4.14: Book New Appointment Page for Student
Figure 4.14 above shows the form for student to book new appointment. It shows all
appointment details that student need to filled up before click the button to book.
4.3.5.5 Status Booked Appointment Page
Figure 4.15 : Status Booked Appointment Page for student
44
Figure 4.15 above shows the status of the appointment that student booked either reject
or accept.
4.3.5.6 Notification Page
Figure 4.16: Notification Page for Student
Figure 4.16 above shows the notification interface for student and it shows the details
for appointment either any appointment that has been accepted or rejected and the
appointment has been set .
45
4.4 Test Case
Test Case is a set of actions executed to verify a particular feature or functionality of
the system if its meets the expected results. Moreover, test case also test the correct
behaviour of a functionality of a system. There are the steps, test and expected results
or output in a test case.
4.4.1 Login for Lecturer and Student
Table 4.1: Test Case Login
Test Cases Table : Login to the system
Pre-conditions
The username and password must exist in the database.
Step Test Step Test Result
1. Login Page. Go to:
http://cloud.myfik.net/aishah/OnlineAppointmentSy
stem/
View login page of the
system
2. The users enter the following details:
Test data:
Lecturer
Email : [email protected]
Password : abc
46
Student
Email : [email protected]
Password : aiziey255
3. User click login button Login page loaded and
login successful.
4. User click logout button Logout successful.
4.4.2 Register for Lecturer and Student
Table 4.2: Test Case Register
Test Cases Table : Register new account
Step Test Step Test Result
1. Register Page View register page of the system
2. The user choose and click to register
button at the home page.
Test data:
Register new user/account
The page will redirect to register
form page.
3. The users enter the following details:
Test data:
Lecturer
Username : Fariza
Email : [email protected]
Password : 111111
Confirm password : 11111
Level : 1
47
Student
Username : Aziz
Email : [email protected]
Password : 222222
Confirm password : 222222
Level : 0
4. User click register button Registration successful.
4.4.3 Update Profile for Student and Lecturer
Table 4.3: Test Case Update Profile
Test Cases Table : Update Appointment
Step Test Step Test Result
1. Login page Successful login
2. Lecturer and Student Main Page View lecturer and student page of
the system
3. click hyperlink profile
Test data:
Lecturer
Name:Siti Aishah
Student
Name:Aishah Aziz
users will be redirect to profile page
to view profile
4. User click update button Update successful.
48
4.4.4 Add New appointment in Appointment List for Lecturer
Table 4.4: Test Case Add New Appointment
Test Cases Table : Login to the system
Pre-conditions
The date and time must not exist in the database.
Step Test Step Test Result
1. Login Page View login page of the system
2. Lecturer page and click appointment
list hyperlink
View appointment list page of the
system
2. The lecturer enter the following
details:
Test data:
Date : 2019-05-25
Start Time : 08:00
End Time: 11:00
3. User click add button Add successful.
49
4.4.5 Update Appointment in Appointment List for Lecturer
Table 4.4: Test Case Add New Appointment
Test Cases Table : Update Appointment
Step Test Step Test Result
1. Login page Successful login
2. Lecturer Main Page View lecturer page of the system
3. click hyperlink Appointment list
Test data:
“Update” any date
Lecturer will be redirect to
appointment list page to view
profile
4. User click update button Update successful.
4.4.6 Delete Appointement in Appointment List for Lecturer
Table 4.6 : Test Case Delete Appointment List
Test Cases Table : Delete Appointment
Step Test Step Test Result
1. Login page Successful login
2. Lecturer Main Page View lecturer page of the system
3. click hyperlink appointment
Test data:
“delete” appointment
Lecturer will be redirect to view
appointment list
4. User click delete button Delete successful.
50
4.4.7 Book Appointment for student
Table 4.7: Test Case Book New Appointment
Test Cases Table : Login to the system
Pre-conditions
The date and time must be free and did not book by any student.
Step Test Step Test Result
1. Login Page View login page of the system
2. Student page, click appointment list
hyperlink and click book button
View appointment list page and
book page of the system
2. The lecturer enter the following
details:
Test data:
Date : 2019-05-25
Time : 08:00
Duration : 00:20:00
Aim: education
Lecturer name : Siti
3. User click submit button Book successful.
51
4.4.8 Update Status Booking Appointment for Lecturer
Table 4.8: Test Case Update Status Booking Appointment
Test Cases Table : Update Appointment
Step Test Step Test Result
1. Login page Successful login
2. Lecturer Main Page View lecturer page of the system
3. click hyperlink Appointment list
Test data:
“Update” any status to accept
Lecturer will be redirect to
appointment list page to view
profile
4. User click update button Update successful.
4.4.9 Delete Status Booking Appointment for Lecturer
Table 4.9: Test Case Delete Status Booking Appointment
Test Cases Table : Delete Status Appointment
Pre-conditions
The date and time has been outdated and pass by for the appointment.
Step Test Step Test Result
1. Login page Successful login
2. Lecturer Main Page View lecturer page of the system
52
3. click hyperlink status appointment
Test data:
“delete” appointment
Lecturer will be redirect to view
status appointment.
4. User click delete button Delete successful.
4.5 Summary
This chapter shows brief details on the interfaces of the system that help the user to
interact with system. There are also several cases modules involving the main functions
of the system that is used to identify the possible errors and check either the flow of the
system are function smoothly or not.
53
CHAPTER V
CONCLUSION
5.1 Introduction
This chapter discusses the contribution and achievement of the developed project,
its constraint, future work and conclusion. The contribution and achievement will
discuss on how Student_Lecturer Appointment System can contributed and how it help
in assisting users when they used this system. The project constraint will state all the
difficulties during development of this system. Future work is more into discussing the
additional suggestion for future use and conclusion from this project and system.
5.2 Contribution and Achievement
Student_Lecturer Appointment System will be used by the student and lecturer in
UniSZA to undergo appointment between them. This system will be more systematic
and efficient management for appointment system from the existing current system.
This system also will be easy to understand and easy to understand and used by the
student and lecturer as the interface and the flow of the application is well organized.
54
Through this system, the waiting time for other student turn become short because this
system implement shortest job first. Shortest job first technique will select and make
the shortest duration will accepted and can make the appointment session first.
Using this system, there will be more appointment can be achieved and make during
that day and time. This system also include notification which means either lecturer or
student will be more alert about the appointment. The notification will acts as reminder
for them in case they forget the appointment that has been deal before.
5.3 Constraint
There are several problem and limitation that occurred throughout the development of
this system. The problem and limitation are:
1. The lecturer must decide manually the status of the appointment either reject
or accept the appointment.The problem will be faced is the lecturer may
accidently accept or reject the appointment that lecturer was not free or etc.
2. Some interfaces are not compatible with phone screem and it makes the user
feel uncomfortable when access the system or the interfaces.
3. The student must select or choose time manually based on appointment list.
The problem will happen if the student was not look at the appointment list
and choose the date and time without follow the list.
55
5.4 Suggestion for Improvement in Future
There are a lot of enhancement can be done to make this system better and more
complete. It still have to make a lot of improvements to reveal its potential as a final
product.
5.4.1 Generate Auto Set Up for Time and Date based on Lecturer Set Up
Another good improvement can be carried out is by making the time and date
for appointment will be chose based on the date and time state when fill the booking
appointment information. This function will reduce the problem encounter when
booking appointment because the student do not need to put manually their time and
date appointment and just choose as stated .
5.4.2 Generate Auto Booking Without to Wait for Lecturer Responses
The developed system require lecturer to response to status for booking
appointment from students manually. As the improvement this application can be
enhance by generating auto booking technique where the appointment will be auto
booking if the appointment free and follow certain condition that has been set.
56
5.5 Summary
At the end of this project, Student_Lecturer Appointment System has been
successful developed. This proposed system has solved the problem and achieved the
objectives. The added value which is hybrid application was chosen as one of the
solution to solve the problem for the lecturer and student that forget to bring laptop and
they can directly access using mobile application and can access the system anywhere
and anytime they want. Other than that, it would be easy to book appointment although
they did not know the lecturer number phone because they can directly access and
book appointment through the system.
57
REFERENCES
M. Landry, ‘‘there are good and bad ways to set up an appointment system’’. CMA
journal vol. 115, no. 2, pp. 160- 168, 1976.
Jafari, a.,. (2002). Conceptualizing intelligent agents for teaching and learning,
educause quarterly, vol. 25. No. 3.
Lu, k. M. And ab hamid, S.H.2007, conceptual design of web-based appointment
management system using object webml.
Leirer, morrow, parinute & doksum, “appointment system”, 1980.
Iterative Model. https://www.testingexcellence.com/iterative-model/. Accessed on
21 February 2018.
58
APPENDICES
59
APPENDIX A
Appendix A : Gantt Charts of Activities and Milestones For FYP 1
60
APPENDIX B
Appendix B : Gantt Charts of Activities and Milestones For FYP 2
61