TIMETABLE MANAGEMENT SYSTEM (TTMS)

AHMAD LUKMAN BIN GHAZALI

BANCHELOR OF COMPUTER SCIENCE

(INTERNET COMPUTING) WITH HONOURS

UNIVERSITI SULTAN ZAINAL ABIDIN

2018
 TIMETABLE MANAGEMENT SYSTEM (TTMS)

AHMAD LUKMAN BIN GHAZALI

BANCHELOR OF COMPUTER SCIENCE (INTERNET COMPUTING)

WITH HONOURS

FACULTY OF INFORMATION AND COMPUTING

UNIVERSITI SULTAN ZAINAL ABIDIN

AUGUST 2018
 DECLARATION

I hereby declare that this 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 any other degree at Universiti Sultan Zainal Abidin or other
institutions.

________________________________

Name: ..................................................

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

i
 CONFIRMATION

This is to confirm that: The research conducted and the writing of this report was under my
supervisor.

________________________________

Name : ..................................................

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

ii
 DEDICATION

“In the name of Allah, Most Gracious, Most Merciful”

This Final Year Project report could not have been conducted without the support,

encouragement and cooperation of many people. First of all, I would like to express my

deepest gratitude to my supervisor, Encik Mohd Sufian B. Mat Deris, who has always

given valuable advice and encouragement throughout in developing this project

successfully. I would like to thank her for giving the opportunity to learn and work under

her guidance, which has been the most memorable experience. Also, thanks to all my

lectures, which guide me to make this project possible.

In addition, I would also like to thank all my friends for helping me in solving my

problems and difficulties during in making of this project. Their engorgement, criticism

and support help me a lot. Finally and most importantly, I would like to thank my parents

and my family. Their support, encouragement and endless love are undeniably the force

that moves me throughout the completion of this project and my entire life.

Thank You.

iii
 ABSTRAK

Penjadualan kelas merupakan suatu masalah bagi kebanyakan pusat-pusat pengajian

terutama universiti. Masalah utama adalah kelas yang amat terhad untuk bilangan pelajar,

pertembungan antara mata pelajaran dan pertembungan diantara pensyarah yang

mengajar pada waktu dan masa yang sama. Jadi sistem ini dibangunkan bagi mengatasi

masalah-masalah ini dan untuk menyediakan jadual kelas yang flesibel berdasarkan

bilangan pelajar dan ketersediaan kelas. Sebelum ini, sistem yang sedia ada hanya

menentukan bilangan pensyarah bagi sesuatu mata pelajaran. Tetapi sistem ini juga

menentukan bilangan pelajar serta bilagan kelas yang mempunyai kuantiti bilangan

pelajar. Sistem yang dicadangkan akan dibangunkan dalam PHP/MYSQL untuk mengatur

jadual kelas.

iv
 ABSTRACT

Class scheduling is a problem for most universities, especially universities. The main

problem is a very limited class for the number of students, a clash between subjects and

clashes between lecturers who teach at the same time and time. So this system is

developed to address these problems and to provide flexible class schedules based on the

number of students and class availability. Previously, the existing system only determined

the number of lecturers for a subject. But the system also determines the number of

students and classrooms that have a number of students. The proposed system will be

developed in PHP / MYSQL to set the class schedule.

v
Table of Contents
DECLARATION ............................................................................................................................ i
CONFIRMATION ......................................................................................................................... ii
DEDICATION .............................................................................................................................. iii
ABSTRAK ..................................................................................................................................... iv
ABSTRACT .....................................................................................................................................v
LIST OF ABBREVIATIONS / TERMS / SYMBOLS ................................................................x

CHAPTER 1 ....................................................................................................................................1
INTRODUCTION...........................................................................................................................1
1.0 Background ...........................................................................................................................1
1.1 Problem Statement ................................................................................................................2
1.1.1 Limited classroom for number of students ...................................................................2
1.1.2 Clash between subjects .................................................................................................2
1.2 Objectives .............................................................................................................................2
1.3 Scope .....................................................................................................................................3
1.3.1 Admin ...........................................................................................................................3
1.3.2 Lecturer .........................................................................................................................3
1.3.3 Student ..........................................................................................................................3
1.4 Limitation of Work ...............................................................................................................4
1.5 Chapter Summary .................................................................................................................4

CHAPTER 2 ....................................................................................................................................5
LITERATURE REVIEW ..............................................................................................................5
2.0 Introduction ...........................................................................................................................5
2.1 What is Heuristic Algorithm? ...............................................................................................5
2.2 Heuristic Algorithm Process .................................................................................................6
2.3 Advantages and Disadvantages of Heuristic Algorithm .......................................................7
2.4 University Exam Scheduling System Using Graph Coloring and RFID Technology ..........8
2.5 Automated Scheduling of University Exam ........................................................................9
2.6 Chapter Summary ................................................................................................................9

CHAPTER 3 ..................................................................................................................................10
METHODOLOGY .......................................................................................................................10

vi
3.0 Introduction .........................................................................................................................10
3.1 Rapid Application Development (RAD) Model .................................................................11
3.1.1 Phases in Rapid Application Development (RAD) Model .........................................12
3.1.1.1 Business modeling ................................................................................................ 12
3.1.1.2 Data modeling .................................................................................................... 13
3.1.1.3 Process Modeling ............................................................................................... 13
3.1.1.4 Application Generation ......................................................................................... 13
3.1.1.5 Testing and Turnover ............................................................................................ 14
3.1.2 Advantages and Disadvantages of RAD Model..........................................................15
3.1.3 Summary .....................................................................................................................16
3.2 System Requirements..........................................................................................................16
3.2.1 Software ......................................................................................................................16
3.2.1.1 Xampp Sewer, MySQL version 3.2.1 ................................................................... 16
3.2.1.2 (PHP) Programming Language ............................................................................. 16
3.2.1.3 Notepad++ ............................................................................................................ 17
3.2.1.4 Google Drive ...................................................................................................... 17
3.2.1.5 Wi-Fi UniSZA ...................................................................................................... 17
3.2.1.6 Draw.io Diagram Flowchart Software .................................................................. 17
3.2.1.7 MySQL Workbench 6.1 CE .................................................................................. 18
3.2.1.8 Microsoft Office.................................................................................................... 18
3.2.1.9 Photoshop........................................................................................................... 18
3.2.2 Hardware .....................................................................................................................18
3.2.2.1 Laptop Asus Windows 10 ..................................................................................... 18
3.2.2.2 Printer.................................................................................................................... 18
3.2.2.3 Pen drive & Hard disk........................................................................................... 19
3.3 Framework and Design .......................................................................................................19
3.3.1 Context Diagram .........................................................................................................20
3.3.2 Data Flow Diagram level 0 .........................................................................................21
3.3.3 Entity Relationship Diagram .......................................................................................22
3.3.4 Framework ..................................................................................................................23
3.3.5 Database Modelling ....................................................................................................24
3.3.5.1 Table Admin ........................................................................................................... 24
3.3.5.2 Table Lecturer ........................................................................................................ 24
3.3.5.3 Table Student ......................................................................................................... 25

vii
 3.3.5.4 Table Class.............................................................................................................. 25
3.3.5.5 Table Subject .......................................................................................................... 26
3.4 Chapter Summary ...................................................................................................... 26

CHAPTER 4 ..................................................................................................................................27
IMPLEMENTATION AND RESULT ........................................................................................27
4.0 Introduction .........................................................................................................................27
4.1 Implementation and Output ................................................................................................28
4.1.1 Login ...........................................................................................................................28
4.1.2 Admin .........................................................................................................................28
4.1.2.1 Admin Page ............................................................................................................ 28
4.1.2.2 Admin Register Lecturer ........................................................................................ 29
4.1.2.3 Admin Register Student ......................................................................................... 30
4.1.2.4 Admin Register Subject ......................................................................................... 31
4.1.2.5 Admin Register Class ............................................................................................ 31
4.1.2.6 Admin Set Timetable ............................................................................................. 32
4.1.2.7 Admin Display Timetable ...................................................................................... 33
4.1.2.8 Admin View Detail Lecturer.................................................................................. 33
4.1.2.9 Admin View Detail Lecturer (Personal) ................................................................ 34
4.1.2.10 Admin Update Detail Lecturer ........................................................................... 35
4.1.2.11 Admin View Detail Student ............................................................................... 35
4.1.2.12 Admin Popup Delete Student ............................................................................. 36
4.1.2.13 Admin Update Detail Student ............................................................................ 37
4.1.2.14 Admin View Subject .......................................................................................... 37
4.1.2.15 Admin Update Subject ....................................................................................... 38
4.1.2.16 Admin View Class ............................................................................................. 38
4.1.2.17 Admin Update Class .......................................................................................... 39
4.1.2.18 Admin Report Student ....................................................................................... 39
4.1.2.19 Admin Change Password ................................................................................... 40
4.1.3 Lecturer Page ..............................................................................................................41
4.1.3.1 Lecturer Home ....................................................................................................... 41
4.1.3.2 Lecturer Teach Subject .......................................................................................... 41
4.1.3.3 Lecturer View Timetable ....................................................................................... 42

viii
 4.1.3.4 Lecturer Update Profile.......................................................................................... 42
4.1.3.5 Lecturer Change Password..................................................................................... 43
4.1.4 Student Page................................................................................................................43
4.1.4.1 Student Home......................................................................................................... 43
4.1.4.2 Student Register Subject ........................................................................................ 44
4.1.4.3 Student View Timetable......................................................................................... 44
4.1.4.4 Student Update Profile ........................................................................................... 45
4.1.4.5 Student Change Password ...................................................................................... 45
4.2 Testing ...............................................................................................................................46
4.2.1 Login testing ...............................................................................................................46
4.2.2 Logout testing .............................................................................................................47
4.2.3 Admin Module Interface testing .................................................................................47
4.2.3.1 Admin register lecturer, student, class and subject testing .................................... 47
4.2.3.2 Admin view lecturer, student, class and subject testing......................................... 48
4.2.3.3 Admin view timetable testing ................................................................................ 48
4.2.3.4 Admin manage class .............................................................................................. 49
4.2.4 Lecturer Module Interface testing ...............................................................................50
4.2.4.1 Lecturer register subject testing ............................................................................. 50
4.2.4.2 Lecturer view timetable testing .............................................................................. 50
4.2.4.3 Lecturer update profile testing ............................................................................... 50
4.2.4.4 Lecturer change password testing .......................................................................... 51
4.2.5 Student Module Interface testing ................................................................................52
4.2.5.1 Student register subject testing .............................................................................. 52
4.2.5.2 Student view timetable testing ............................................................................... 52
4.2.4.3 Student update profile testing ................................................................................ 52
4.2.4.4 Student change password testing ........................................................................... 53
4.3 Chapter Summary ..............................................................................................................53

CHAPTER 5 ..................................................................................................................................54
CONCLUSION .............................................................................................................................54
5.0 Discussion ...........................................................................................................................54
5.1 Limitation............................................................................................................................54
5.2 Future Work ........................................................................................................................55
5.3 Conclusion ..........................................................................................................................55

ix
 LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram
DFD Data Flow Diagram
ERD Entity Relationship Diagram
FYP Final year project

x
 CHAPTER 1

INTRODUCTION

1.0 Background

The management of timetable in the educational institution is very crucial

as to have well-managed schedule lectures, labs, semester and course. This system

is essential in distributing the resources needed in a right way without any faults.

As seen nowadays, a lot of solution or application system that help in generating a

timetable which has developed in an artificial intelligent way.

In Universiti Sultan Zainal Abidin, Tembila Campus, class scheduling is a

problem because of the classroom available in UniSZA Tembila is limited for huge

number of students from various courses and clash between subjects.

Thus, this system is proposed and developed to overcome these problems

and to provide flexible schedule regarding the proximity of students’ time, and class

availability. Before this, the existing system only provides the classroom, but this

system will also allocate seats for students.

This system will be used by students, lecturers, and admin of the system,

which is BPA. This proposed system will be developed in PHP/MySQL to arrange

the time timetable class schedule. The current system does not assign the student’s

1
 seat. In addition, the existing system also does not automatically assign which

invigilators and lecturers available to monitor the timetable.

1.1 Problem Statement

There are two main problems why this system is developed, which are:

1.1.1 Limited classroom for number of students

Classrooms in UniSZA Tembila are limited and not all the classes

are suitable according the number of students. So, this system will

use Heuristic algorithm to find the suitable class based on the

number of students in the class.

1.1.2 Clash between subjects

It while using this system, there is any clash between subjects, this

system will inform the admin there is a clash.

1.2 Objectives

There are three main objectives of this proposal. The three Objectives are derives

to overcome the problem that stated before. The objectives are:

1.2.1 To design a system that is able to execute a timetable schedule based on

the number of students and class availability.

2
 1.2.2 To allocate students’ seat and invigilators automatically.

1.2.3 To evaluate the system function.

1.3 Scope

This system will be used by three users that are admin, lecturers and students.

1.3.1 Admin

Admin, which is BPA can log in into this system and will use this system to

create and arrange the timetable schedule for every semester. Admin also

will use this system to allocate students’ seat and invigilators on duty.

1.3.2 Lecturer

Lecturer can log in and use this system to insert the subject information he

was teaching for current semester, see the time he needs to invigilate the

timetable, and view the timetable schedule.

1.3.3 Student

Student also can log in, register subject and use this system to view the

timetable schedule.

3
1.4 Limitation of Work

Limitations of work are the constraints I face while doing this project.

1.4.1 Only can be used in web based application.

1.4.2 Inexperience in using Heuristic Algorithm.

1.4.3 Limited time to complete this project with a lot of other projects at the same

time.

1.5 Chapter Summary

In conclusion, this chapter explains about overview of this system. Its

problem statement and objectives why this system is proposed and developed, who

will use this system and the limitation while doing this project.

4
 CHAPTER 2

LITERATURE REVIEW

2.0 Introduction

This chapter will continue with the research on what is Heuristic Algorithm

and its process. This chapter also discuss about the advantages and disadvantages

using Heuristic Algorithm.

2.1 What is Heuristic Algorithm?

Heuristic algorithm (HA) is an algorithm that either gives nearly the right

answer or provides solution not for all instances of the problem. Usually, HA are

developed to have low time complexity and is applied to the complex problems that

cannot be easily solved. There are two types of approaches in HA, which are basic

or local approach and modem approach. In basic approach, there are several type of

algorithm; Exhaustive Search, Local Search, Divide and Conquer. Branch-and

Bound, and Dynamic Programming. While in modern approach there are also

several types of algorithm that are Simulates Annealing Algorithm, Tabu Search,
5
 Swarm Intelligence, Evolutionary Algorithm, Neural Networks, and Support

Vector Machine (SVMs). When implemented in this timetable management system

(TMS), Heuristic Algorithm will find the most suitable classroom based on the

number of students. Even though this algorithm did not guarantee that the best one

will be found, but it will execute the most suitable one and it also will find it fast

and easily.

2.2 Heuristic Algorithm Process

Process in Heuristic Algorithm involves the use of judgmental rules of

“Heuristic”. Heuristic process makes minimal cognitive demands. However, there

are several constraints in HA by basic principles of knowledge activation and use -

namely, availability, accessibility and applicability (Higgins, 1996).

Heuristic always try to help the problem solver by guiding his decisions

during the course of moving from initial to solution state. HA process also includes

the running tests and getting results by trial and error. It became easier to create an

efficient algorithm to process similar types of data. These tests are designed to

isolate the problem by a step- by-step elimination of things that do not contribute

the problem.

The method used from a heuristic algorithm is one of the known methods,

such as greediness, but in order to be easy and fast the algorithm ignores or even

suppresses some of the problem’s demand.

6
2.3 Advantages and Disadvantages of Heuristic Algorithm

Table below shows the advantages and disadvantages of Heuristic algorithm.

Advantages Disadvantages

 Incorporates with both objective  Require certain level of knowledge

and subjective knowing, useful and experience to apply

when solving issues that do not

require formula.

 Allow the mind to apply all it  Does not allow a way to assess the

knows from different sources. quality of redesign

 Recognition heuristic enables us  Evaluations are loosely structured

to use a recognizable pattern of and therefore run the risk of finding

cues to quickly form a one-time, low priority problems.

conclusion.

 Involves in analyzing a short  Representative jump into an error

series of cues, and. a stopping Conclusion that is inaccurate.

when perceive a strong cue.

7
2.4 University Exam Scheduling System Using Graph Coloring and RFID

Technology

Map coloring is a type of problem that can be solved by using graph coloring

method. In this research paper, two algorithms have been used that are Hybrid

Approach and Graph Coloring Algorithm. There are also few constraints that been

used in this project. The constraints are no student can be assigned to more than one

exam at the same time and cannot exceed three exams in the same day, number of

students that taking the exam should not more than the available halls’ capacity,

exams that are most crowded should be placed in timetable primarily and at most

four exams should be held at the same time but in different exam hall. Besides, the

inputs while doing this project that will save in database include days, exam, hall

that the exam will be held, number of period in one day, number of exam that will

be held at the same period and maximum allowable ratio of common students

between two exams. In the beginning, blind search and brute force algorithm are

used as a hybrid approach, and the constraints are determined. As the second part

of project, RFlD card reader is used and it will connect to computers, and these

computers will be allocated in common areas in university.

8
2.5 Automated Scheduling of University Exam

This research paper is studied about the class availability during

examination period. Classroom in universities are differ from classroom in school

in term of size and range. This research paper had used HA and 7 graph coloring to

perform the search for timetable. Timetabling and graph coloring were linked by

Welsh and Powell in 1967. To split the exam into groups that may be scheduled

together, HA is used based on graph coloring. In this research paper, conflicts are

existed in form of students, staffs, and room. When an exam has been selected, then

it will be placed into the rooms by using the algorithm presented. There are also

other algorithms that can be used to place course into classroom and to optimize

other constraints. This project is currently in prototype stage and directed towards

developing further algorithm and to further widen the scope.

2.6 Chapter Summary

In conclusion, this chapter is discuss about the definition literature Heuristic

algorithm, its advantages and disadvantages and the literature review on other

research paper about timetable scheduling system

9
 CHAPTER 3

METHODOLOGY

3.0 Introduction

In this chapter, it will discuss about the methodology used to develop this

system. For software development life cycle (SDLC), the methodology that has

been chosen is Rapid Application Development (RAD) Model. This chapter also

will explain more about the method chosen, and its development phase.

Various model of SDLC have been created by universities, experts and

standards organizations such as Waterfall Model, Spiral Model, Top-Down Model,

Bottom-Up Model, and Rapid Prototyping or Rapid Application Development

(RAD) Model.

10
3.1 Rapid Application Development (RAD) Model

Rapid Application Development (RAD) model is a type of incremental

model. In this model, the components are developed in parallel and are integrated

to make the complete product for faster product delivery. This model is based on

prototyping and iterative development with no specific planning involved. RAD

uses minimal planning in favor of rapid prototyping. The most important aspect for

this model to be successful is to make sure that the prototypes developed are

reusable.

11
3.1.1 Phases in Rapid Application Development (RAD) Model

In Rapid Application Development (RAD) model, there are several

phases as shown in the figure below:

Figure 3.1.1: RAD Model

3.1.1.1 Business modeling

A complete business analysis is performed to find the

vital information for business, how it can be obtained, how

and when is the information processed and what are the

factors driving successful flow of information.

12
3.1.1.2 Data modeling
The information gathered in the Business modeling

phase is reviewed and analyzed from sets of data objects vital

for the business. The attributes of all data sets is identified

and defined. The relation between these data objects are

established and defined in detail in relevance to the business

model.

3.1.1.3 Process Modeling

The data object sets defined in Data modeling phase

are converted to establish the information flow needed to

achieve specific business objectives as per the business

model. The process model for any changes or enhancements

to the data object sets is defined in this phase. Process

descriptions for adding, deleting, retrieving, or modifying a

data object are given.

3.1.1.4 Application Generation

The actual system is built and coding is done by using

automation tools convert process and data models into actual

prototypes.

13
3.1.1.5 Testing and Turnover

The overall testing time reduced is RAD model as the

prototypes and independently tested during every iteration.

However the data flow and the interfaces between all the

components need to be thoroughly tested with complete test

coverage. Since most of the programming components have

already been tested, it reduces the risk of any major issues.

14
3.1.2 Advantages and Disadvantages of RAD Model

Advantages Disadvantages

 Changing requirements can be  Dependency and technically strong

accommodated. team members for identifying

business requirement.

 Progress can be measured.  Only system that can be

modularized can be built using

RAD.

 Iteration time can be short with use  Requires highly skilled

of powerful RAD tools. developers/designers.

 Reduced development time.  Inapplicable to cheaper projects as

cost of modelling and automated

code generation is very high.

 Productivity with fewer people in  High dependency on modeling

short time. skills.

 Quick initial reviews occurs.  Suitable for systems that are

component based on scalable.

Table 3.1.2: Advantages & Disadvantages RAD Model

15
3.1.3 Summary

In conclusion, this part discusses more about Rapid Application

Development (RAD) Mode, and its advantages and disadvantages. Other than that,

this chapter also explains about comparison of other methodologies in SDLC.

3.2 System Requirements

System requirement is a very essential part to develop a system. They are

the software and the hardware that built up the system from the scratch into the

complete system. Thus, ESS deployed several software and hardware when

developing the system as listed below.

3.2.1 Software

3.2.1.1 Xampp Sewer, MySQL version 3.2.1

Xampp was used as localhost to create database for this

system.

3.2.1.2 (PHP) Programming Language

PHP is the programming language used to write the program.

16
3.2.1.3 Notepad++

Notepad++ is the platform used to write the coding to be run

into localhost.

3.2.1.4 Google Drive

Google Drive is cloud storage software which is used to back

up all the coding and report. Thus, if the laptop having

problem, the system still can be used by downloading it using

another PC or laptop.

3.2.1.5 Wi-Fi UniSZA

Internet connection that is used to search information and

coding-solve alternatives.

3.2.1.6 Draw.io Diagram Flowchart Software

Draw.io is the software used to draw all the ERD, DFD, and

Context Diagram.

17
 3.2.1.7 MySQL Workbench 6.1 CE

Workbench was used to import table from MySQL database

to design the real ERD.

3.2.1.8 Microsoft Office

This is the software used to write the report for references

and do the slide for presentation.

3.2.1.9 Photoshop

Photoshop is software used to edit images.

3.2.2 Hardware

3.2.2.1 Laptop Asus Windows 10

Laptop Asus was used while doing this project to develop the system

with Apache Server, MySQL, with RAM 2.0GB, 64 bits operating

system, and write report using Microsoft Office.

3.2.2.2 Printer

This hardware is used to print the hard copy of related information

and the report of this system.

18
 3.2.2.3 Pen drive & Hard disk

Pen drive and hard disk are the other option of storage used to back

up all the data, coding and report.

3.3 Framework and Design

This section will discuss about the framework and design used in developing

this project. Project modeling has been used in order to define and analyze the data

required in this project.

Context Diagram, Data Flow Diagram, and Entity Relationship Diagram are

used in order to explain the project modeling. These diagrams also will represent

the database of the system.

In other words, this section will explain more about how the system is

designed and modeled.

19
3.3.1 Context Diagram

Diagram below shows the context diagram that displays all the

function of the systems.

Figure 3.3.1: Context Diagram

Figure 3.3.1 shows the context diagram that includes all the three

main entities and their main process in this system. The lecturer will input

the select information based on the subject he teach in current semester.

Lecturer also will be able to view, update, and delete the profile information.

Besides, lecturer also will be able to view the schedule to know when he

needs to invigilate the class. When lecturer has inserted the data information,

admin will create the time table schedule based on the information. Admin

also will assign the suitable classroom by using Heuristic algorithm, allocate

students, and generate their time table class. Last but not least, students will

be able to view and download the time table schedule.

20
3.3.2 Data Flow Diagram level 0

Diagram below shows the Data Flow Diagram level 0 that displays

all the function of the systems.

Figure 3.3.2: Data Flow Diagram level 0

21
 Figure 3.32 above shows the Data Flow Diagram (DFD) Level 0.

Data Flow Diagram (DFD) Level 0 is an expansion from context diagram.

In DFD, all the processes are connected with an entity and saved in data

store. All users in this system need to login into system in order to view,

insert, update, delete and create the schedule.

3.3.3 Entity Relationship Diagram

Figure 3.3.3: Entity Relationship Diagram

Figure 3.3.3 above shows the relationship among each other table.

Admin can register tables that are table subject and generate schedule.

22
Students can only view and register subject, Lecturer can teach one or more

subject. Admin of this system is able to manage more than subject schedule.

3.3.4 Framework

Figure 3.3.4: Framework

Figure 3.3.4 above shows the framework of the whole system. This figure

explains all the processes involve in this system in form of diagram. The

outputs from this system are timetable management. As shown in the figure

above, both outputs are stored in database server. While admin assign the

classroom, subject and course, Heuristic algorithm will be implementing.

23
3.3.5 Database Modelling

Database modelling show the database that has been used in this
system.

3.3.5.1 Table Admin

Figure 3.3.5.1: table admin

This table show admin_id, username, password and type.

3.3.5.2 Table Lecturer

Figure 3.3.5.2: table Lecturer

Table lecturer shows the lecturer details (lecturer_id, name, IC

number, and phone number), their working details (position,
faculty, campus, address, postcode, city, state, and email) and their
username and password to log in to the system.

24
3.3.5.3 Table Student

Figure 3.3.5.3: table Student

This table shows the details of the student, registered by admin

contain their personal details (student_id, name, matric number, IC
number, address, postcode, city, state, email, and phone number),
their study details (course, faculty) and their username and
password used to log in to the system.

3.3.5.4 Table Class

Figure 3.3.5.4: table Class

This table shows the details of the class, registered by admin

contain their personal details (classID,class_capacity).

25
 3.3.5.5 Table Subject

Figure 3.3.5.5: table Subject

This table shows the data about the course registered by admin for
student (subjectlD, course name, course code, credit hour,
semester, and year).

3.4 Chapter Summary

As a conclusion, System Development Life Cycle (SLDC) help a lot to make

sure this system working as planned. With an efficient Wi-Fi, software, and

hardware, it makes sure the system developed as smooth as it should be, for example

the database that is developed using PHP MySQL.

26
 CHAPTER 4

IMPLEMENTATION AND RESULT

4.0 Introduction

In this chapter, it will discuss overall system including the interface and its

function. The interface of this system uses the template from Bootstrap, but has

been edited to make it look more compatible with this Timetable Management

System.

27
4.1 Implementation and Output

4.1.1 Login

Figure 4.1.1: Login

Figure 4.1.1 shown the login page of the system. At this page, the user has

to enter their username, password and select their position type.

4.1.2 Admin

4.1.2.1 Admin Page

28
 Figure 4.1.2.1: Admin Page

Figure 4.1.2 shown the interface including the entire button on menu list

for admin action.

4.1.2.2 Admin Register Lecturer

Figure 4.1.2.2: Admin Register Lecturer

29
 In this interface, admin will be able to register new lecturer for them to log

in to the system. Admin need to filling all columns otherwise the system cannot

add the data into database.

4.1.2.3 Admin Register Student

Figure 4.1.2.3: Admin Register Student

In this interface, admin will be able to register new student for them to log

in to the system. Admin need to filling all columns otherwise the system cannot

add the data into database.

30
4.1.2.4 Admin Register Subject

Figure 4.1.2.4: Admin Register Subject

In this interface, admin will be able to register new subject for student and

lecturer. Admin need to filling all columns otherwise the system cannot add the

data into database.

4.1.2.5 Admin Register Class

Figure 4.1.2.5: Admin Register Class

31
 In this interface, admin will be able to register new class for quantity of

student. Admin need to filling all columns otherwise the system cannot add the

data into database.

4.1.2.6 Admin Set Timetable

Figure 4.1.2.6: Admin Set Timetable

In this interface, admin will be able to choose the student of program for

generate timetable class. Admin need to filling all columns otherwise the system

cannot add the data into database.

32
4.1.2.7 Admin Display Timetable

Figure 4.1.2.7: Admin Display Timetable

In this interface, admin will be able to display the timetable class from the

list program by semester.

4.1.2.8 Admin View Detail Lecturer

Figure 4.1.2.8: Admin View Detail Lecturer

33
 In this interface, admin will be able to view the lecturer list details with the

certain information. Admin will able to view all information of one lecturer in link

of lecturer id (blue links).

4.1.2.9 Admin View Detail Lecturer (Personal)

Figure 4.1.2.9: Admin View Detail Lecturer (Personal)

In this interface, admin will able to view detail information of one lecturer

by click of a link lecturer id.

34
4.1.2.10 Admin Update Detail Lecturer

Figure 4.1.2.10: Admin Update Detail Lecturer

In this interface, admin will able to update details information of lecturer.

4.1.2.11 Admin View Detail Student

Figure 4.1.2.11: Admin View Detail Student

35
 In this interface, admin will be able to view the student list details with the

certain information. Admin will able to view all information of one student in link

of student id (blue links).

4.1.2.12 Admin Popup Delete Student

Figure 4.1.2.12: Admin Popup Delete Student

In this interface, admin will be able to delete the data list student details

and will get popup confirmation to delete data student.

36
4.1.2.13 Admin Update Detail Student

Figure 4.1.2.13: Admin Update Detail Student

In this interface, the admin will be able to update the data student details

have been registered.

4.1.2.14 Admin View Subject

Figure 4.1.2.14: Admin View Subject

In this interface, admin will be able to view all subject have been

registered.

37
4.1.2.15 Admin Update Subject

Figure 4.1.2.15: Admin Update Subject

In this interface, the admin will be able to update subject have been

registered.

4.1.2.16 Admin View Class

Figure 4.1.2.16: Admin View Class

In this interface, the admin will be able to view class have been registered.

38
4.1.2.17 Admin Update Class

Figure 4.1.2.17: Admin Update Class

In this interface, the admin will be able to update class have been

registered.

4.1.2.18 Admin Report Student

Figure 4.1.2.18: Admin Report Student

39
 In this interface, the admin will be able to view report student have been

registered by subject.

4.1.2.19 Admin Change Password

Figure 4.2.19: Admin Change Password

In this interface, the admin will be able to change current password to new

password.

40
4.1.3 Lecturer Page

4.1.3.1 Lecturer Home

Figure 4.1.3.1: Lecturer Home

Figure 4.3.1 shown the interface including the entire button on menu list

for lecturer action.

4.1.3.2 Lecturer Teach Subject

Figure 4.1.3.2: Lecturer Teach Subject

In this interface, the lecturer will be able to add their teaching subject.

41
4.1.3.3 Lecturer View Timetable

Figure 4.1.3.3: Lecturer Teach Subject

In this interface, the lecturer will be able view timetable class that subject

have their registered.

4.1.3.4 Lecturer Update Profile

Figure 4.1.3.4: Lecturer Update Profile

42
 In this interface, the lecturer will be able update their profile detail.

4.1.3.5 Lecturer Change Password

Figure 4.3.5: Lecturer Change Password

In this interface, the lecturer will be able to change current password to

new password.

4.1.4 Student Page

4.1.4.1 Student Home

Figure 4.1.4.1: Student Home

43
 Figure 4.1.4.1 shown the interface including the entire button on menu list

for student action.

4.1.4.2 Student Register Subject

Figure 4.1.4.2: Student Home

In this interface, the student will be able to add their register subject.

4.1.4.3 Student View Timetable

Figure 4.1.4.3: Student View Timetable

In this interface, the student will be able to view timetable class.

44
4.1.4.4 Student Update Profile

Figure 4.1.4.4: Student Update Profile

In this interface, the student will be able to update their profile.

4.1.4.5 Student Change Password

Figure 4.1.4.5: Student Change Password

In this interface, the student will be able to change current password to

new password.

45
4.2 Testing

The testing approach used in this system is known as the testing module by

module.

4.2.1 Login testing

No. Testing Procedures Expected Result Result

1 On the text field username, user Live validation. Success

has to insert his username, cannot “Invalid username and

be left empty. password”

2 On the text field password, user Live validation. Success

has to insert his password, cannot “Invalid username and

be left empty. password”

3 On the select type, user has to Live validation. Success

insert his type, cannot be left “Invalid username and

empty. password”

4 SQL Injection Live validation. Success

Insert ‘OR’1’=’1__ into username “Invalid username and

and password. password”

5 Valid login credentials Successful login. Success

Username: admin (direct to admin

Password: admin5454 homepage)

Type: admin

46
4.2.2 Logout testing

No. Testing Procedures Expected Result Result

1 User click logout button. Successful logout. Success

(direct to login page)

4.2.3 Admin Module Interface testing

4.2.3.1 Admin register lecturer, student, class and subject testing

No. Testing Procedures Expected Result Result

1 On the text field, admin has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

2 On the text field, admin has to Live validation. Success

select faculty, cannot be left “Please fill out this field”

empty.

3 On the select type, admin has to Live validation. Success

insert his type, cannot be left “Please fill out this field”

empty.

4 If all detail completes, the system Live validation Success

will notify admin that data has “Success”

been successfully insert into

database.

47
4.2.3.2 Admin view lecturer, student, class and subject testing

No. Testing Procedures Expected Result Result

1 Admin click button between System directed to next Success

student and lecturer to view detail page according to admin

choose

2 Admin click button between class System directed to next Success

and subject to view detail page according to admin

choose

3 Admin click link and display the System directed to view Success

data have been click detail

4.2.3.3 Admin view timetable testing

No. Testing Procedures Expected Result Result

1 Admin click the drop button System directed to next Success

between to choose a class of page according to admin

program and semester choose

2 Timetable will be display when System directed to next Success

admin choose classes. timetable

48
4.2.3.4 Admin manage class

No. Testing Procedures Expected Result Result

1 Admin update class has be System directed to next Success

register in database. page according to view

class detail.

2 Admin can drop down quantity Will show drop down Success

student in class. Quantity has be button.

set.

3 Admin click submit button to Live validation Success

update data. “Success”

49
4.2.4 Lecturer Module Interface testing

4.2.4.1 Lecturer register subject testing

No. Testing Procedures Expected Result Result

1 On the text field, lecturer has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

2 If all detail completes, the system Live validation Success

will notify lecturer that data has “Success”

been successfully insert into

database.

4.2.4.2 Lecturer view timetable testing

No. Testing Procedures Expected Result Result

1 Lecturer need to click button System directed to Success

timetable to see timetable class dropdown class

2 lecturer will see subject teaching System directed to Success

in timetable class timetable

4.2.4.3 Lecturer update profile testing

No. Testing Procedures Expected Result Result

1 On the text field, lecturer has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

50
2 If all detail completes, the system Live validation Success

will notify lecturer that data has “Success”

been successfully insert into

database.

4.2.4.4 Lecturer change password testing

No. Testing Procedures Expected Result Result

1 On the text field, lecturer has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

2 If all detail completes, the system Live validation Success

will notify lecturer that data has “Success”

been successfully insert into

database.

51
4.2.5 Student Module Interface testing

4.2.5.1 Student register subject testing

No. Testing Procedures Expected Result Result

1 On the text field, student has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

2 If all detail completes, the system Live validation Success

will notify student that data has “Success”

been successfully insert into

database.

4.2.5.2 Student view timetable testing

No. Testing Procedures Expected Result Result

1 Student need to click button System directed to Success

timetable to see timetable class dropdown class

2 Student will see subject System directed to Success

registration in timetable class timetable

4.2.4.3 Student update profile testing

No. Testing Procedures Expected Result Result

1 On the text field, Student has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

52
 2 If all detail completes, the system Live validation Success

will notify lecturer that data has “Success”

been successfully insert into

database.

4.2.4.4 Student change password testing

No. Testing Procedures Expected Result Result

1 On the text field, student has to Live validation. Success

insert all data, cannot be left “Please fill out this field”

empty.

2 If all detail completes, the system Live validation Success

will notify student that data has “Success”

been successfully insert into

database.

4.3 Chapter Summary

In conclusion, this chapter briefly describes about the technical art of

system. The interfaces are shown to give visual idea for user on how the process

of input data and how the output been display.

53
 CHAPTER 5

CONCLUSION

5.0 Discussion

In this chapter, it will discuss the overall project proposal. The expectation

result, its contribution and planning for improvement of the result in the

implementation phase as well as the conclusion of this project.

5.1 Limitation

“Success is not measured by what you accomplish, but by the Opposition

you have encountered, and the courage with which you have maintained the struggle
against overwhelming odds.” (Orison Swett Marden).

Basically, every project has its own constraints and limitation. This project
also has constraints and limitation such as time constraints, source limitation, and
so on. While doing this project, the biggest constraint is poor internet connection in
UniSZA Tembila Campus. This makes me difficult to search for sources in internet.
Other than that, there is also a few existing system that use the same algorithm in
internet. This system also can only be used in web based application.

Time constraint is also one of the major problems while doing this project.
A lot of things have to be done but the time is limited. This project takes one whole
semester to be done. with a lot of others projects that are also need to be done this
semester. In within two months, this system has to completed and fully functioning

54
 with its main function to create a timetable class and assign class room by using
HA.

5.2 Future Work

Based on the research on the internet about this system, there is a lot of
improvements that can be made and applied to this system to cover up all the
function to make this system perfect. This system also can be more attractive if it is
develop and implement using mobile application. Thus, user can access and use this
system anywhere computer.

5.3 Conclusion

In conclusion, Timetable Management System (TTMS) is a system

developed in web based application by using PHP and MYSQL. The main function
of TTMS are to create schedule timetable, assign classroom based on number of
student, number of subject, class and lecturer by using Heuristic algorithm (HA),
automatically. Hopefully, this system can help to easier admin to works to create a
timetable class.

55
 REFERENCES

[1] Natalia Kokash, Department of informatics and telecommunication, university of

Trennto, Italy. An introduction to heuristic algorithm

[2] E.K.Burke et. al., Department of Computer Science, University of Nottingham,

University Park, Nottingham. NG7 2RD. Automated Scheduling for University Exams.

[3] James E. Purcell, CISSP, GSEC, GCIH, PMP, MCSE. Comparison of Software

Development Lifecycle Methodologies

[4] Akhan Akbulut et. al., International Journal of Innovation, Management and

Technology, Vol 4, No 1. University Exam Scheduling System Using Graph Coloring

Algorithm and RF ID Technology, February 2013.

[5] Ademir Aparecido Constantino et. al. 2010. Iterated Heuristic Algorithm, for the

Classroom Assignment Problem. Computer Science Department. State University of

Maringa, Brazil. ASAP Research Group; School of Computer Science, University of

Nottingham, UK.

56