Professional Documents
Culture Documents
ABSTRACT
ABSTRAK
1.1
Project Background
FTMK Lecturer's Appointment System (FLAS) is a proposed system for the
Projek Sarjana Muda (PSM) that allows students to book appointment with their
Iecturers in order to reduce difficulties between students and lecturers. The medium
for this system is the Internet so students can access the system wherever they are as
long as there is Znternet connection.
This system will be developed as 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 MYSQL as a database for the system.
The target users of this project are students, lecturers and administrator. The
system is develop to help students makes an appointment online with lecturer that
they want to meet depends on the lecturer's timetable. Only students who had
registered can use this system. User must login before use this system.
In this system the lecturer must always update new information in their
timetable so that the students will know about new information of the lecturer
whether the lecturer is on leave or have a meeting. Students can check the timetable
of the lecturer before going to meet the lecturer. The task of administrator is to
register the new user, edit or delete the information of the users. Other than that,
administrator also can addledit latest news or information about faculty or other
news about 1nr"omdtionTechoiogy.
The main purpose of FTMK Lecturer's Appointment System (FLAS) is to
provide more easy and convenient way of booking appointment and to propose new
way of data management and data processing. The main task for the system is to
process all the data and provide a good result.
1.2
Problem Statement
i)
ii)
iii)
room, the student must leave the note to the lecturer or come again to meet
1.3
Objective
In order to ensure that the system will develop smoothly, many objectives had
been stated. Objectives of this project are :
To build a system that has function that can help user manage booking
application.
To build the system with provides user level and security level and manage
the certain process with the authorization. The system was complete with the
password because some of the data may contain sensitive data and private
information.
To develop computerized lecturer's appointment system that can replace
manual system.
1.4
Scope
FLAS is developed based on FTMK lecturer's daily routine to ease the user in
managing their task. This part defines the limitations, functionality and target users
of the system. The scope of the system is as following :
Target User
- The target user of the system is committee members in FTMK who had
registered such as lecturers, students and administrator.
Functionality
..
1)
ii)
Type of System
1.5
Project Significance
FLAS is a web-based system that will give a lot of benefit to users and
system administrator. The system consists of databases that keep information about
lecturer's information, student's information and appointment information. This
system will help to reduce time consuming that occurs in daily routine when using
manual way.
The database is the most critical part of the system because it requires
complex data handling, detail design of the database can help prevent duplicate data
and easier for system administrator to maintain the database. Thus, it will reduce
workload for administrator to manage and maintain the data in the database. This
system also will display in a very user-friendly graphical user interface to ease the
users to use the system.
1.6
Expected Output
1.7
Conclusion
The main idea of developing FTMK Lecturer's Appointment System (FLAS)
is to improve the current manual system to make the process of making appointment
become more manageable, effective, and efficient in order to reduce time consuming.
It can bring a lot of benefits to students, lecturers and administrator.
The next activities will be developed is chapter 11. This part will review the
previous project and make a comparison with project that has been proposed. Besides
that, this chapter also explains about the methodology that will be used in this
project.
2.1
Introduction
This chapter focuses about literature review and project methodology that
will be used for developing this system. Literature review are searching, collecting,
analyzing and drawing conclusion from all arguments raised in relevant body of
literature. It is important to give the explanations of choosing the project. "According
to Cooper (1988), a literature review uses as its database reports of primary or
original scholarship, and does not report new primary scholarshp itself'.
Fact and finding will discuss and review about approach and related research,
reference and other findings about this system. Besides that, it also states other
approaches that will be used in this project by making comparison with previous
approach.
2.2
There are some reasons that cause the development of the system to solve the
existing problems. The sources for the finding in this topic can be found fiom
internet, magazine and book. Then, the literature review can be complete through
study, analysis and drawing conclusion from those sources.
2.2.1 Domain
software development life cycle. There are several types of model in software
development life cycle such as Waterfall model, Spiral model, Prototyping model,
Rapid Application Development model (RAD), Incremental Model, WIM.;lrM Spiral
model, Concurrent Development model, Component-based model and Formal
Method model.
ii)
Casestudy
There are three systems has been used for the case study. Those are list as
following :
Health Campus Universiti Sains Malaysia Quality Bulletin Website Fixed
Appointment System
This website is used by health campus of Universiti Sains Malaysia. The scope of
implementation of the Fixed Appointment System is to include Nephrology,
Cardiology and Hematology Clinics. According to Department of Health & Social
Security Report, NHS, UK said that "XheAppointment System succeeded in reducing
waiting times where doctors and stafS were committed to the implementation of the
systerrz, andfailed where they were not." .
The Cardiology Clinic is among the busiest clinics of HUSM managing
approximately 500 patients each month. Cardiologist, Dr. Mohd. Sapawi Moharned,
took on the challenge of implementing the fixed appointment system at the
Cardiology Clinic. His team reorganized systems and schedules to ensure clinics
were manned and operated according to schedule. Results have been impressive. In
August '06, 90% of patients who kept appointment time were seen within 1 hour of
the appointment. Staff at the clinic have also benefited from the more orderly
outpatient process.
The Nephrology Clinic, headed by AP Dr. Kamaliah herself, brought down
waiting times of patients. In February '06, only 12% of patients were seen within 1
hour of appointment, while in the first month of implementation, June '06 this went
up to 89%. The below graph is the graph that show statistics of patients see within
one hour of appointment.
According to Sr. Zaleha, Medical Specialist Clinic of HUSM, she said that
"
With the implementation of the system, work is less stressful, clinics are cleared early
and patient complaints have reduced. "
This system is used by Harvard University that allows students to make own
appointment with an advisor in the Harvard International Ofice (HIO) to discuss
immigration issues related to your studies or work. Students also can make a call to
HI0 or visit the H I 0 to schedule an appointment. Appointments regarding
permanent residency for faculty and high level researchers, health insurance
information, spouse and family related questions, and other matters not related to
immigration should be made by telephone in order to be scheduled with the
appropriate staff member.
Based on the case study above, here are several ways to use the appointment
system by searching through search engine and via the appointment schedule. The
comparison between existing system are stated as below :
of Heatth Campus
Universiti Sains
Seetec- Appointment
On-line
Systems
Appointment
Malaysia Quality
System (OLAS)
Bulletin Website
( F i e d Appointment
System)
User friendly
User friendly
secured
secured
Online system
Online system
Objective
achieve objective
achieve objective
Function
Understanding
to use
Security
secured
2.2.3
Technique
According to H.A.Simon (1969), there are three approaches to build a
(W)
Unified Modeling Language (UML) is a language for capturing knowledge
(partial semantics) and for expressing that knowledge (syntax). It provides a visual
illustration of that model and for modeling of systems. The major advantage of UML
is addition of process information into data model for an instance, when association
entities arise fiom many to many relationships there are no way to show the exact
number of business rule. In the case, LTML can show the accurate cardinality.
The third approach is waterfall model which become popular version for
software engineering in systems development life cycle model. This model is a linear
progression of the project activities, where an input is received by an activity,
processed and the output is delivered to the next sequential activity as the input to
that activity. Waterfall development has distinct goals for each phase of
development. Once a phase of development is completed, the development proceeds
to the next phase and there is no turning back.
deadlines for each stage of development .and a product can proceed through the
development process like a car in a carwash, and theoretically, be delivered on time.
Development moves from concept, through design, implementation, testing,
installation, troubleshooting, and ends up at operation and maintenance. Each phase
of development proceeds in strict order, without any overlapping.or iterative steps.
2.3
Project Methodology
Software engineering must integrate a development strategy to solve definite
2.3.1
Waterfall Model
Waterfall model is the most popular version of software development life
cycle for software engineer. This model also known as Linear Sequential Model
where an input is received by an activity, processed and the output is delivered to the
next sequential activity as the input to that activity. Below are representing 6 stages
in Waterfall Model.
(a) The problem is specified along with the desired service objectives
(goals)
(b) The constraints are identified
2.
detailed definitions of (a) and (b) above. This document should clearly define
the product hnction.
In the system and software design phase, the system specifications are
3.
Data structure
rn
Software architecture
rn
rn
Interface representations
4. In the implenzentation and testing phase stage the designs are translated into
5. In the integration and system testing phase all the program units are
integrated and tested to ensure that the complete system meets the software
requirements. After this stage the software is delivered to the customer
[Deliverable - The software product is delivered to the client for acceptance
testing.]
6. The maintenance phase the usually the longest stage of the software. In this
The waterfall lifecycle model is a traditional models, it had been used widely
by professional system developers. It also has been proved can help models the
system and produce a good product or system.
One reason of choosing waterfall models as the role model for developing
FTMK Lecturer's Appointment System (FLAS) is a good decision because waterfall
model offers a lot of benefits such as high quality product and enables developer to
reduce overhead and other benefits. Before developing FTMK Lecturer's
Appointment System (FLAS), user requirement, project specification and other must
be documented. The documents will enable developer to cautiously plan the
activities and stages in development process. This will help to reduce overhead and
finish the project on time.
Every phase in waterfall model is critical so that the developer must finish
previous phase before moving to the next phases. Since every phase is critical, at the
end of each phase, it must be tested and documented to prevent phase streaming
where previous phase had to restart while the next phase is still running. If this
ys
and
happen, developer had to spent more time and money to redo the p ~ e v i ~ phases
cancel the running phase.
2.4
Project Requirement
Project requirements for software development tools and hardware
requirement will define and listed at below to be used for FLAS purposes.
SOFTWARE
DESCRIPTION
Edit Plus
Macromedia Dreamweaver
Microsoft Project
Microsoft Visio
Microsoft Windows W
purpose.
a)
Windows 98/ME/XP/2000/Vista
b)
c)
d)
2.5
There are two kind of project coordination technique that will be use in order
to make sure that this FTMK Lecturer's Appointment System project success. The
first is formal, impersonal approaches. This includes project milestone and related
documentation. The second are formal, interpersonal procedures. This involves
quality assurance activities, meetings, and planning, analysis and design phase. There
are activities and duration for PSM 1 milestones.
Responsibility
Activities
Student
form to be approval by
Supervisor
mPSM 1
Start
End
Date
Date
Week 1
Week 1
- Project proposal
form.
- List of
Supervisor-Student
committee
Revenue
committee.
Student
n
Week 1
Week 3
Report of an
introduction,
Supervisor
objective, problem
literature review
and methodology
chapter I, literature
project.
- Language supervisor
Supervisor
Language
chapter I & 2.
Supervisor
Student
Week 3
Week 3
- List of Language
Supervisor-Student
Week 3
Week 4
Language
of student
Supervisor
language
Supervisor
(English).
Responsibility
Activities
- Define the
Student
Start
End
Date
Date
Week 3
Week 4
Revenue
- Analysis Report
requirement analysis
Supervisor
-Progress Analysis
Language
Report.
analysis report
Supervisor
of student language
(English).
status.
- Language Workshop
Student
Language
to Language
Supervisor
Week 4
Week 4
Week 5
Supervisor.
Student
Supervisor
Language
Supervisor
progress.
I
I
Semester Break
Student
18
Language
Supervisor
Supervisor
Supervisor
performance and
analysis report.
Week 6
Week 6
Week 7
Week 7
I
Week 7
Week 7
1 defined.
progress.
Week 9 Design report
Student
to Language
Language
Supervisor.
Supervisor
1
Week 9
I
Week 9
Activities
Respmsibility
Revenue
Start
Date
with Language
Week 10 Week
Student
Language
Supervisor
Supervisor
Completing the
Student
mplementation phase
Supervisor
I
1
Week 10 Week
- Implementation
Report
-Progress Report
70% (Prototype).
Project Progress
Supervisor
1 Week 1 2
Student
3 complete copy
PSM
(draft-
Supervisor,
Assessor
&
Language
Supervisor)
- Distribute the
presentation schedule
HPSM1
Presentation
committee
Schedule
- Presentation of PSMl
Student
project.
- Mark submission of
Language Supervisor
to supervisor
Supervisor
Language
Supervisor
I Week 15 / Week
1 Week 15
Week
Language
Evaluation Report
I
Supervisor
report of PSM I.
2.6
Conclusion
As the conclusion, literature review phase plays an important role before the
CHAPTER 111
ANALYSIS
Introduction
3.1
Analysis phase defines the requirements of the system, depends on how these
requirements will be accomplished. It contains problem analysis and requirement
analysis. This phase will determine the details of project requirement and how these
requirements will be accomplished. Problem analysis consist investigating and
description about existing system. For the requirement analysis, programmer must
list down and analyze the requirement to develop the project and the flow of the
system.
Developer should make the research about the analysis before starting to
develop the proposed system. Through the analysis, developer will identify the user
requirements after gather the information on their research. Consequently, the
problems that occur in the existing system will be solved according their capability.
The advantages that can achieve after analysis is developer can identify the
organization needs and also will define all weaknesses in existing system. The
developer can improve the weaknesses for a new system to make the new system
will accomplish user requirements.
Problem Analysis
3.2
After doing observation and studying the existing manual system, developer
will face the problem that need to identify and solve it. The problem analysis part
will provide the excellent understanding about the project. This part includes the
system improvement that can be use in new system. Below is the problem that have
been identified in the manual system :
i)
ii)
iii)