FYP Guidelines Sem22021

FACULTY OF COMPUTER SCIENCE
AND INFORMATION TECHNOLOGY
UNIVERSITI PUTRA MALAYSIA

HANDBOOK FOR
FINAL YEAR PROJECT

SKM4949

To our students and colleagues…

Editor:
Lili Nurliyana Abdullah

TABLE OF CONTENTS

PART A: FINAL YEAR PROJECT IMPLEMENTATION 1
1.0 1
2.0 INTRODUCTION 1
3.0 1
RULES 2
4.0 3
ROLES AND RESPONSIBILITY 3
PART B: 3.1 COORDINATOR 3
1.0 3.2 SUPERVISOR
2.0 3.3 ASSESSOR 4
3.0 3.4 STUDENTS
4
PART C IMPLEMENTATION AND EVALUATION OF FINAL 6
1.0 YEAR PROJECT 6
2.0 4.1 BRIEFING SESSION 6
3.0 4.2 STUDENT DISTRIBUTION 7
4.0 4.3 WORKSHOP SESSION 7
4.4 PRESENTATION/SEMINAR SESSION 8
4.5 MARKS AND GRADES 8
4.6 PROJECT REQUIREMENTS
4.7 BEST PROJECT 10
4.8 PENALTY 10
12
GUIDE TO FORMATTING 17
INTRODUCTION 21
PROJECT PROPOSAL
2.1 FINAL YEAR PROJECT PROPOSAL TEMPLATE 44
FINAL YEAR PROJECT 46
REPORT/THESIS/DISSERTATION 48
3.1 FINAL YEAR PROJECT REPORT TEMPLATE 52
GUIDE TO ASSESSMENT AND EVALUATION

ASSESSMENT METHODS

GENERAL REQUIREMENT
TEACHING PLAN
FORMS

iii

PART A:
Final Year Project

Implementation

iv

1.0 INTRODUCTION

This is the Final Year Project handbook of the Faculty of Computer Science and Information
Technology, Universiti Putra Malaysia. This handbook contains information about the
preparation, the implementation and the completion of the Final Year Project.

This handbook is the result of an effort initiated to define the policy and improve the quality
of Final Year Project. The intention of this handbook is to develop a standardized framework for
our students. It serves as guideline to the expected format and content of the Final Year Project
deliverables for students and also provides evaluation rubrics for supervisors and examiners.

Management and coordination of the Final Year Project involves the cooperation of
coordinators, supervisors, assessors and students. Accordingly, the management and coordination
activities of the Final Year Project need to be well implemented. In this handbook, the duties and
responsibilities of each involved are detailed so that the activities of management of the Final
Year Project can be coordinated between departments.

The production of this handbook is expected to serve as a reference and guide throughout
the implementation of the Final Year Project for all stakeholders including coordinators,
supervisors, assessors and students. In addition, this handbook also includes documents related to
the implementation of the Final Year Project in the faculty. This handbook also comes with a
rubric-based thesis writing and scoring guide that will assist all parties in the process of
implementation, monitoring and evaluation of the Final Year Project.

The Final Year Project is part of the Faculty requirements consisting of two parts. The first
part involves writing a project proposal and some preliminary work while the second part involves
conducting the experimental work, writing the final project report and oral presentation. All
students must pass these courses to graduate.

2.0 RULES

Here are the general rules that every student should follow in the Final Year Project:
• Students should develop on their own and be prohibited from hiring or allowing
others to develop part or all of their projects.
• Students are not allowed to commit plagiarism, forgery or data fraud.
• Students who do the above may be given an F grade.

3.0 ROLES AND RESPONSIBILITY

There are several parties involved in the implementation of the Final Year Project. They
consist of project coordinators representing the department and assisted by lecturers as supervisors
and project evaluators and students themselves. The Faculty Final Year Project Committee (FFYP
Committee) govern the conduct of the final year project. Refer Table 1.

1

Table 1: The FYP Committee Framework

ITEM Faculty FYP Committee
Chairman Deputy Dean (Academic and Student Affairs)

Secretary Assistant Registrar (HEA)

Members All FYP Coordinators
Additional Members 1 support staff

Frequency of Minimum of once in an academic calendar year
Meeting
Terms of Reference • Appointment of members
• Enforcement of new academic policies
• Data on student performance and Step for Improvement
• Disputes and Conduct of Supervisors and Students
• Facilitiesand supports
• Distribution and allocation of students/supervisors.
• Update of Policy, Research Titles and Scope.
• Analyze, validate and endorse marks before entering into

e-smp
• Students training in project development skills and

techniques.
• Dispute of student/s and supervisor/s conduct and

progress.
Other matters related to the conduct of the projects.

To ensure that the implementation of the Final Year Project is carried out efficiently and
effectively, the following roles and responsibilities are listed below:

3.1 COORDINATOR

• Become an intermediary between the faculty / department and students
• Become an intermediary between students and supervisors
• Provide information on the Final Year Project
• Distribute students by supervisor based on supervisor's expertise
• Deciding the conduct and distribution of the supervision and the number of students

supervised.

• Announce student distribution results by the third week of the semester
• Appointing supervisors, assessors, seminar chairmen and project seminar time

watcher

• Hold a briefing session for Final Year Project implementation for students and
supervisors (Refer to Bachelor Dissertation/Project Registration Form (PU / PS /
BR06 / AJR) and Final Year Project Handbook, Log Book etc.)

• Conducting Briefing and Workshop
• Prepare and organize the schedule and rules of the Final Year Project seminars
• Ensure project seminars are carried out according to schedule
• Distribute and collect Assessment of Seminar Presentation on Bachelor

Dissertation/Project Form (PU / PS / BR30 / AJR)

• Manage information and records pertaining to the FYP and students

2

• Compile scores and record scores into the system (e-smp) according to the duration
and proportion of scores (Refer to Exam Result Management Procedures (UPM /
PU / PS / P011))

• Receive a copy of the Final Year Project report which is enclosed and recorded in
the Student’s Material Acceptance Form (PU / PS / BR28 / AJR)

• Compile student materials for filing and storage.

3.2 SUPERVISOR
• To supervise, guide and train the students towards their development of the FYP.
• Preparing and submitting the title of the Final Year Project at least three (3) weeks

before the semester commences to the Coordinator
• Assist and supervise students so that the process of learning, knowledge and project

development is carried out according to the level of achievement in line with the
learning outcomes set
• Ensure that the students follow the procedure relating to the conduct of the FYP.
• Monitor project progress at least 6 times/semester during project implementation
(Refer to Bachelor Dissertation/Project Implementation Form (PU / PS / BR07 /
AJR))
• Ensure students submit Project Management Records according to the phases set out
in the Project Management Standards
• Review the Final Year Project proposal students before starting the project
• Attend and evaluate students’ oral presentation.
• Be prompt in responding to students work and request
• Become the Chair of the Seminar during the project seminar session
• Evaluate and grade the project results and final reports of the students' Final Year
Projects (Refer to the Bachelor Dissertation/Project Assessment Form (PU / PS /
BR38 / AJR) ) and submit to the Coordinator by the due date
• Ensure students submit a copy of the Final Year Project report and the results of their
respective projects to the Supervisor and Coordinator by the due date

3.3 ASSESSOR
• Review the presentation of the Final Year Project seminar (Refer to Assessment of

Seminar Presentation Evaluation on Bachelor Dissertation/Project Form (PU / PS
/ BR30 / AJR)) and return the form to the coordinator by the due date
• Be the chairperson during the project seminar session

3.4 STUDENTS
• To conduct and complete the Final Year Project, which meet the standard

requirements of the University with guidance from the supervisors
• Conduct and execute assigned projects according to the requirements planned and

agreed upon with the supervisor and execute according to the level of achievement
in line with the specified learning outcomes
• Select the appropriate supervisor based on the supervisor's expertise
• Register project titles and supervisors (Refer to the Bachelor Dissertation/Project
Registration Form (PU / PS / BR06 / AJR) and return to the department's Final Year
Project Coordinator
• Submit Project Management Records based on the phases set out in the Project
Management Standards
• Present the respective project seminars as scheduled
• Prepare posters for the respective projects (optional)

3

• Submit Final Year Project reports and project deliverables to the respective
supervisors and coordinators according to the requirements and dates specified by
the faculty

• Attend the full session, conduct oral presentations and pass both oral presentations
for the Final Year Project proposal and report. Failure to do so will be given an F
(Fail).

• Observe all deadlines as stated in the schedule and as notified by the Coordinator.
• It is compulsory to meet and discuss with supervisor at minimum 6 times per

semester and submit report as schedule by the Coordinator.
• Ensure that the log book is filled and the Bachelor Dissertation/Project

Implementation Form (PU/PS/BR07/AJR) is signed
• Notify the supervisor(s) as soon as possible when struck by illness or other

emergencies. All illnesses must be supported by valid medical certification.
• Avoid plagiarism practices

4.0 IMPLEMENTATION AND EVALUATION OF FINAL YEAR PROJECT

The Final Year Project course provides an integrated assessment of the progress of the
students toward the desired information technology. It is therefore important to design a fair and
broad guideline for better assessment of this course. A final year project in the Faculty is a two-
semester course in which students select a designated project and are supervised by a faculty
member. The first course is the SKM4949A, while the second course is the SKM4949B.

The students are expected to discuss their progress with their supervisors in regular weekly
meetings. The students submit a written report, present and defend their work at the end of each
semester.

The main purpose of the project is to improve the students' technical, professional and
ethical skills, communication skills and entrepreneur skills by integrating writing, presentation
and computer programming opportunities. The designated project is comprehensive and focuses
on professional practice and includes a variety of non-technical issues such as economic factors,
safety, reliability, environment and social impacts.

The topics are normally suggested by the department faculty members. The students can
also suggest the topic; the selected topic should meet the requirements for the final year project.
The students are required to demonstrate their ability to conduct a literature survey, perform the
relevant design, propose a solution to the problem, and implement their design.

The implementation of the Final Year Project is as follows:

4.1 BRIEFING SESSION
A briefing on the implementation of the Final Year Project for final year students is held the

first or second week of each semester.

Final Year Project implementation guide and project requirements file containing Project
Management Record, synopsis and related documents will be provided to students. (Bachelor
Dissertation/Project Implementation Form (PU / PS / BR07 / AJR) and Log Book)

Notification of some information to final year students during briefing session as follows:
a. Supervisor Selection Process

4

• At the beginning of each semester, supervisors will be encouraged to submit their
ideas or proposals to the project coordinator. Project coordinator will check and
approve all the proposals.

• The supervisors are selected and nominated based on their expertise from each
department. Supervisors' areas of expertise and topics that have been identified to be
presented to students. (List of Final Year Projects)

b. Distribution of students - supervisor
• Students are allowed to be supervised only by the lecturers from their respective
departments.
• The number of students that a supervisor needs to supervise will be determined based
on the total number of students registering for the project for the semester involved.
The list of lecturers will be kept up to date.
• If there are still students who do not have supervisors, the Final Year Project
Coordinator should assign the relevant student to any appropriate lecturer.
• In case of difficulties of any kind, the student informs the supervisor as soon as
possible. If they are unable to do so, the student approaches the FYP coordinator as
soon as possible.
• Change of Topic or Supervisor Changes or adjustments to the project topic are
allowed before week 3. The FYP coordinator’s endorsement is necessary before the
request is submitted to the Department. The student will be notified about the
decision.

c. Project Registration
• Students are required to complete and submit their project registration form after
selecting the appropriate supervisor for their Final Year Project to the Coordinator
within a specified time. (Refer to Bachelor Dissertation/Project Registration Form
(PU / PS / BR06 /AJR))
• Final Year Project Coordinator collects project proposal headings and analyzes so that
there is no overlap between students (if necessary).

d. Proposal Writing
• Once students are divided into supervisors, students will need to discuss with their
supervisor on the selected project.
• Students should meet with their supervisor at least 6 times in a semester.
• Upon approval, students are required to prepare a proposal based on the scope of the
project agreed upon.
• Students will write project proposal papers in the specified writing format. (Refer to
Project Proposal Template)
• A briefing on the writing of the project proposal will be given by the Final Year
Project Coordinator.
• To keep track on student-supervisor meetings and to monitor student progress, the
students and the supervisors are required to fill and minutes the project
timeline/milestones/progress in Log Book (Refer to Bachelor Dissertation/Project
Implementation Form (PU / PS / BR07 / AJR)).
• The supervisor will need to assess the meetings and progress of their students in the
supervisor form.
• Students are advised to benefit from the supervisor’s guidance by scheduling regular
meetings. The student will record the main points of each meeting, summarize them
and submit them to the supervisor immediately following the meeting. This strategy
will help both sides to track the progress and identify any difficulties.
5

e. Score distribution

• Students will be notified of the score allocation that will contribute to the overall
project score.

4.2 STUDENT DISTRIBUTION

Some steps need to be followed to determine the distribution of students to supervisor. The
steps involved are as follows:

Identify students

• Identify compulsory and eligible students for the Final Year Project to meet the
program requirements.

Identify the supervisor involved

• A list of names of lecturers involved and who can serve as supervisors of the Final
Year Project will be provided to students.

• Information on the field/topics of lecturers should also be provided.

• Managing the distribution and appointment of supervisors according to their
respective departments.

Refer to List of Students by Supervisor of each department

4.3 WORKSHOP SESSION
Several identified workshops will be implemented to produce quality projects. The

coordinator will identify appropriate fields and speakers to provide the workshop. The details of
the workshop are as follows: -

• Workshop 1 (title, statement preparation, objectives, background and scope)

• Workshop 2 (literature review)

• Workshop 3 (methodology)

• Workshop 4 (system design)

• Workshop 5 (disclosure of use of project development tools)

• Workshop 6 (results and analysis)

• Workshop 7 (project presentation preparation)

The workshops will be conducted throughout the semester of study based on a specific week
and the chosen topic.

4.4 PRESENTATION SESSION

Several presentation sessions will be held to monitor student project progress throughout
the semester. This presentation consists of:

4.4.1 Project Proposal Presentation
•
Students must present the project proposal to the supervisor in the eighth or ninth (8
• or 9) week of each semester. Project proposal presentation form evaluation form to be
filled by assessor.

The coordinator will compile the Project Proposal Evaluation Form for inclusion in
the eSMP system to meet the 1-7-week assessment mark.

4.4.2 Poster
• Poster should be provided by the student.
• The posters should include abstract, goals, methodologies, results, and conclusion

6

• Students are required to prepare a poster for a poster session (optional) that is held
before the end of the semester (relevant dates can be found on the announcement
board).

• A poster of the project should be submitted along with project deadline submission.

4.4.3 Project Demonstration / Seminar Presentation Session
• A seminar presentation will be held. Assessors from each department will be
appointed to evaluate the presentation of the seminar. Selection of the appropriate
place and time will be determined by their department's Final Year Project
Coordinator. (Refer to the Assessment of Seminar Presentation on Bachelor
Dissertation/Project Form (PU / PS / BR30 / AJR))
• The Coordinator shall advise students on the presentation date and should attend it
upon the consent of the supervisor
• Students shall be evaluated by a minimum of two (2) panel members appointed by
the coordinator.
• During the project demonstration presentation session, the student’s supervisor will
be appointed automatically as the chairperson of the seminar session.
• The chairperson of the seminar will inform the rules of the seminar before the start
of the session.
• All registered students for the FYP reports must attend their program oral
presentations throughout the sessions.
• The students should adhere to the specified time for the oral presentation.
• Students should follow proper dress code.
• The students are encouraged to use visual aids.
• Evaluated items for the oral presentations as elaborated in these Guidelines
• The evaluation forms that the assessor and supervisor has completed, will be
collected by the coordinator.

4.5 MARKS AND GRADES

• This phase involves the determination of student grades based on the work done by
the students during the implementation of their respective projects.

• Supervisors evaluate and grade student project and reports/thesis/dissertation by
completing the Bachelor Dissertation/Project Assessment Form (PU / PS / BR38
/AJR)

4.6 PROJECT REQUIREMENTS

• Students are required to contribute to the knowledge of the subject and provide
evidence of originality.

• The student must submit on the specified date to the FYP Coordinator.
• one (1) electronic copy of the thesis and executable project in a CD, based on the

requirement of the Final Year Project.
• The project report must be written in English.
• The student’s FYP proposal and report shall be assessed and evaluated by the

supervisor, co-supervisor (if necessary), second examiner and moderator (if
required).
• Supervisor submits all relevant documents / forms and a copy of the student project
results to the coordinator by the due date..

7

• The coordinator will collect student scores from each supervisor for inclusion in the
Student Information System (eSMP) from time to time. (Refer to Exam Result
Management Procedures (UPM / PU / PS / P011) and Lecturer-Module Student
Information System User Manual (Score Management).

4.7 BEST PROJECT SELECTION

• A meeting will be held to select the best projects at the department level. Some
criteria will be taken into account when the election is made. Refer Bachelor
Dissertation/Project Assessment Form (PU / PS / BR38 /AJR).

4.7.1 Faculty competition best project competition (optional)
• A competition will be held to select the best projects at the faculty level.

4.8 PENALTY

• There is a penalty system for late reports: 2 penalty points per working day are
deducted. Three working days are allowed for late submission which is the cutoff
date. No project will be accepted after the cutoff date, and a zero mark will be
recorded in such case from the examiners side.

• Absolute academic integrity is expected of every student in all academic
undertakings. The Faculty takes a serious view of students who plagiarize any
previous work (including previous FYPs, journal articles or books).

• Plagiarism is the use of other people's work so that it appears to be your own Rule
of thumb: If the idea is not yours, you have to provide the appropriate citation. If the
wording is not yours, rephrase and rework the sentence in your own words and
provide the reference and the page number(s).

• Be careful to ensure that plagiarism does not occur accidentally. You can quote other
people's work, but you must clearly indicate that this is what you are doing, and
include the source. Direct quotation of narrative material should always be enclosed
in quotation marks and the source of the material cited either immediately before or
immediately after the quotation. The full description of the source must be given in
the references at the end of the report (for more information about plagiarism and
references style please visit:

http://files.ithuta.net/OpenJournals/HTS/Author/HTSREF.pdf
http://www.lsbu.ac.uk/library/helpsheets/hs28.pdf
http://www.library.dmu.ac.uk/Images/Howto/HowtoAvoidPlagiarism.pdf

If the material is paraphrased, it should not be enclosed in quotation marks, but the source
should still be stated clearly. Tables, diagrams, etc. copied from elsewhere must also be clearly
labeled as such, with reference to the source.

8

PART B:
GUIDE TO
FORMATTING

9

1.0 INTRODUCTION

After topic has been selected, the next step will be thesis proposal writing. A thesis
proposal is basically the research plan, clearly describing how you expect to
accomplish the goals of your study. It should be thoughtful, well written, and scholarly.

This formatting guideline is to help students prepare their FYP reports.

2.0 PROJECT PROPOSAL
It shall comprise of the following:

TABLE OF CONTENTS
LIST OF FIGURES
LIST OF TABLES

1. INTRODUCTION
1.1 PROBLEM STATEMENT
1.2 OBJECTIVES
1.3 SCOPE

2. LITERATURE REVIEW
3. METHODOLOGY

3.1 PROPOSED APPROACH/DESIGN/SOLUTION/CHARTS
3.2 TOOLS AND LANGUAGES
3.3 TIMELINE/GANTT CHART
3.4 EXPECTED OUTPUT

REFERENCES

Paper

Standard A4 size;

Width: 8.27”; Height: 11.69"

Fonts, Type Styles

Font Size = 12 (Normal Text)

Font = Times New Roman

Heading 1 (Font Size) = 14 (Bold), Font = Times New Roman

Margins

Top = 1.0" Bottom = 1.0"

Left = 1.25" Right = 1.0"

Spacing

Line Spacing = 1.5

Paragraph Spacing = 6 pts (before) and 0 pts (after)

10

Indentation
Indent all quotations comprising 4 or more lines by 5 spaces from left.
Page Numbers
Except for the title page, number all pages which come before the first page of the
body chapters consecutively with lower case roman numerals (i, ii, iii, iv…). The first
page with numeral (1, 2, 3, and so on) starts from the page of the INTRODUCTION.
Mention page numbers on the bottom right of the page

11

2.1 FINAL YEAR PROJECT PROPOSAL TEMPLATE
FACULTY OF COMPUTER SCIENCE AND
INFORMATION TECHNOLOGY
UNIVERSITI PUTRA MALAYSIA

Final Year Project Proposal
Semester and Academic Year

Title of the Project

Name
Matric No.
Supervisor:

12

Title

The statement of title at this stage of thesis writing must be tentative, or it may
be simply a description of the study to be undertaken. A tentative statement of title
should reflect the central purpose of the study in a brief but accurate and
comprehensive manner.

Table of Contents

This page should list all sections, chapters and sub-headings referred to the
respective page numbers as reflected in the body of the Proposal.

Introduction

The primary purpose of the chapter is to provide an overview of the study. It
explains the background of the study from a broad picture. The introduction must
also include the following components either separated into sections or integrated
into one narrative. Give a general introduction to the issue or research topic. State
the problem and provide background information supported by literature review.
Note how past research has addressed the problem, and identify similarities or
differences in their methodology or findings that have drawn you to study the
problem. Introduction should be at the level that make it easy to understand for
readers with a general science background and must capture the reader’s interest
for the investigated problem.

Problem Definition (or Motivation)

The statement of the problem and/or hypothesis presents a focal point in the
research as it clearly states the purpose of the study. You should state specifically
what major questions and/or hypothesis are to be studied and/or tested along with
all the minor questions to be explored.

If you choose Motivation, you should explain the significant of the study, how
it resembles supports and/or differs from other studies, and how it extends the
present knowledge or examines new issues.

Project Objectives

This section presents the objectives that the proposed project is going to
achieve. The objectives are the steps in achieving the goal(s) of the project and are

13

usually interrelated, brief and concise, and are also realistic given the time period.
Use SMART objectives. The following list shows the main objectives of the project:

• To enhance …
• To identify …
• To develop...
• To …

Project Scope

In this section you should state the expected deliverable(s) or the outcome of
your project. You should also provide a brief description of the intended system -
the characteristics or functions and the limitations. With this, it establishes the
boundaries of the proposed project.

Literature Review

The purpose of the study section introduces the reader to the focus of the
project. The content of this section should clearly lay out what is to be searched and
researched.

The student has to provide the historical background and inform the reader
about current achievements in the specific field of research. It is vital to use only
proven credible sources from peer-reviewed journals and books that are accepted
in academic circles. It is not necessary to describe in detail every item of the paper.
The main aim of the author is to present the subject briefly and clearly. In
addition, it is possible to add a few words about why this work will be interesting to
the reader and prove its relevance. This part of the paper usually consists of two or
three pages.

All the used sources have to be properly cited through the text. The
bibliography is situated in the end of the paper. It should follow the provided format.
Please refer References.

Methodology

Define the specific methodology and a discussion of its utility for the proposed
research including its benefits and limitations. In this section, students have to
outline how the investigation process will be conducted. It will contain an overall
description of the approach, materials, and procedures such as

• What methods will be used?
• How will data be collected and analyzed?
• What materials will be used?
• Include calculations, techniques, procedures and equipment
• Detail limitations, assumptions, and range of validity

14

• Flow Charts/ similar relevant charts
Project Timeline

The project timeline shows your (detail) plans and activities that will be
conducted for the whole project. You will need to indicate time frames and
deadlines. You can use the Gantt chart or any other project planning tool to illustrate
your activities.

Tools and Languages

In this section you should state the possible tools and/or languages that you
intend to evaluate and finally use in the project.

Expected Output/Result

In this section you should state/draw/sketch the possible and potential outputs
from the project that must be consistent with the objectives. It should contain
explanations on how the project is worth doing and how it will contribute to the
industry/community.

References

The purpose of a reference is to acknowledge the contributions of other
authors to which you owe an intellectual debt, and also to enable readers to locate
the source easily. In this section, you can use alphabetical or numerical system. For
the latter, we recommend IEEE system which is widely used in computer sciences
and engineering. IEEE system dictates the in-text citation to appear as a number
within square brackets (e.g. [1]). The full details of the reference appear in the
reference list in the order of citation in the text. The following is an example list of
references using IEEE system. Please refer to the IEEE citation reference for
details.

[1] I. Sommerville, "Software Engineering", 11th ed., Addison-Wesley, 2015.

[2] V. J. Blue, and J. L. Adler, “Cellular automata micro-simulation of bi-directional
pedestrian flows,” J. Transportation Research, pp. 135-141, 2000.

[3] S. Sarmady, F. Haron, and A. Z. H. Talib, “Modelling groups of pedestrians in
least effort crowd movements using cellular automata,” in Proc. 2009 2nd Asia
International Conference on Modelling & Simulation, Bali, Indonesia, 2009, pp. 520-
525.

15

[4] F. H. Hassan,”Heuristic search methods and cellular automata modeling for
layout design ,” Ph.D dissertation, Sch. of Info. Sys, Comp. and Math., Brunel Univ.,
UK, 2013.

[5] G. K. Still. (2010, July 15). Crowd Disasters [Online]. Available:
http://www.gkstill.com/CrowdDisasters.html.

As for the alphabetical system (also known as author-date system), Harvard or APA
system of referencing can be used. The advantage of author-date system, is that the
name of the author and the year appear in the text, hence this ease reading. The
reader only refers to the reference section for the details of the document since the
name and the year already exist in the text.

In-text citations: eg. Mitchell (2017) states… Or … (Mitchell, 2017) or
Mitchell and Smith (2017) state… Or … (Mitchell & Smith, 2017)

Book referencing examples: Jones, A.F & Wang, L. (2011). Spectacular creatures:
The Amazon rainforest (2nd ed.). San Jose, Costa Rica: My Publisher

eBook: Mitchell, J.A., Thomson, M., & Coyne, R.P. (2017). A guide to citation.
Retrieved from https://www.mendeley.com/reference-management/reference-
manager

Journal: Mitchell, J.A. (2017). Citation: Why is it so important. Mendeley Journal,
67(2), 81-95

Newspaper: Mitchell, J.A. (2017). Changes to citation formats shake the research
world. The Mendeley Telegraph, Research News, pp.9. Retrieved from
https://www.mendeley.com/reference-management/reference-manager
.

The maximum length of the proposal is TWENTY (20) pages including the cover
page.

16

3.0 FINAL YEAR PROJECT REPORT/THESIS/DISSERTATION

This guide can be used as a reference for students in preparing a thesis. This evaluation
is based on the Final Year Project report. Do ensure to arrange the presentation of reports in a
logical sequence; easy-to-understand sentence structure and diagrams or sketches that can be
easily understood and labeled

It shall comprise of three parts as follows:

a) The preliminaries:

i. Title page
ii. Approval sheet
iii. Abstract and Abstrak
iv. Acknowledgements
v. Table of contents
vi. List of tables
vii. List of figures
viii. List of plates
ix. List of symbols
x. List of abbreviations

b) The text or main body may include 5 chapters as follows:

I. Introduction
II. Literature review
III. Methodology
IV. System analysis and design
V. Implementation and discussion
VI. Conclusion and recommendations

c) The final part includes the following:

i. References
ii. Appendices
iii. Curriculum Vitae

17

Thesis organization structure

Student’s Declaration

Simple declaration from student and endorsed by supervisor.

Abstract/Abstrak

The abstract should provide a brief and concise summary of the objectives, research
method, findings or major results and conclusions. The length should be of one
paragraph, approximately between 200 - 300 words in single spacing. Abstract
generally do not have citations. Information in the title should not be repeated. Abstract
is written both in English and Bahasa Malaysia in separate pages

Acknowledgements

The acknowledgement statement enables the student to convey his or her gratitude
to all who have contributed in carrying out the research; intellectually (assistance or
advice), technically (materials or supplies) or financially (individuals, department or
organisation).

Table of contents

The title of parts, sections or chapters and their principal subdivisions should be listed
in the Table of Contents and must be worded exactly as they appear in the body of
the report. It should be written in sentence case except for abbreviations (which should
be in capital letters). Single spacing for preliminaries; and two singles spacing
between preliminaries and chapters; and two singles spacing between chapter and
the second main heading.

List of tables, figures and plates

List of tables shows the exact titles of all tables in the text and appendices together
with the page number of each table. List of figures includes graphs, diagrams, charts,
maps, drawings, etc while list of plates are printed images, photos and other forms of
illustration that is not a table. The exact title and page number of each figure is listed.

List of symbols, abbreviations or nomenclature

If an assortment of abbreviations and acronyms are used in the project report, they
are listed with their meanings in the List of Abbreviations, even though the full names
are given at the first mention in the text, provided they are used more than five times.
This list serves as ready reference to readers not familiar with the abbreviations.

18

Chapter I (Introduction)
This chapter covers Introduction, Statement of Problem, Objective, Scope and
Structure of Thesis. Introduction introduces a brief overview of the system / study
conducted and the current issues related to the system / study.

Statement of problem
It addresses the issues that make up the system / study to be run.

Objectives
It lists the goals for the system / study to be carried out. It should be in
point (1… ..2… .3…) and not in paragraph form.

Scope
It discusses the limits of systems (systems and users) and studies.

Thesis Structure
It provides a summary of each chapter in your thesis. For example: This
thesis contains five chapters. The first chapter discusses the introduction to
the research conducted.

Chapter II (Literature Review)
This chapter describes studies conducted by other parties or / and existing computer
systems / applications, in relation to the field of project underway. This chapter also
describes the techniques / methods / equipment or technologies used in the
implementation of the project / study. Many references need to be made in this
chapter. References can be from books, conference papers, journal articles,
magazines, theses or / and the Internet. All sources of reference should be clearly
stated in the text content and specified in the reference list.

Chapter III (Methodology)
This chapter reports on the application / model development approach and the overall
framework adopted in the system / application development or implementation of the
study. The contents of this chapter cover the methods, techniques or approaches used
during project design and implementation. This chapter also describes the justification
of using such methods or approaches as well as the hardware and software
requirements. It not only describes the function of the phase but what it actually does
in that phase. For example, if the SDLC model is used, the description of each phase
should be directly linked to the system to be developed, rather than the definition
referenced from any source.

Chapter IV (System Analysis and Design)
Students will need to explain the expectations or work carried out including the
proposal system design architecture, interface design, database design, techniques
and related algorithms. This section also includes flow charts, storyboards, data flow
diagrams (DFDs), structure charts, use diagrams, sequential diagrams, class
diagrams or the like depending on the selected application development model
(structured or object oriented).

19

Chapter V (Implementation and Discussion)
The results of the project / study implementation are detailed in this chapter. Each
interface of the system should be labeled and discussed in detail as if it were a user
manual. This chapter also discusses the types, techniques and test results that are
carried out on the system that has been developed.
For research-based projects, data analysis and model development, the results of the
research and analysis should be detailed and systematic.
Chapter VI (Conclusion)
This chapter summarizes the overall project that has been implemented, the results
and achievements of the project, as well as the planning and expectations /
suggestions for improvement of the system being developed. Weaknesses,
advantages and suggestions for improvement need to be brief and accurate. Students
also need to state the creative or innovative features that have been demonstrated in
the work.
References
This section contains a list of specific references that have been used as references
in the writing of the project report (chapters above). Each reference list must be kept
in the report text.
Appendix
Curriculum Vitae

20

3.1 FINAL YEAR PROJECT REPORT TEMPLATE

Project Title

Student Name & Matric Number with single line space

A project submitted in partial fulfilment of the
requirements for the degree of

Bachelor of Computer Science (MULTIMEDIA)

Supervised by

Supervisor Name

Semester and Academic Year

21

STUDENT’S DECLARATION

I hereby declare that the work in this project is my own except for quotations and
summaries which have been duly acknowledged. The project has not been accepted
for any degree and is not concurrently submitted for award of other degree or
professional qualification.

Signature: ……………………………
Name:
Matric Number:
Date:

Endorsed by:
Supervisor Name:
Signature:
Date:

22

Abstract

The abstract should identify clearly and succinctly the purpose of the project, the
methods used, the results obtained and the significance of the results or findings. The
abstract must not exceed one page. Abstract section gives the readers a brief idea
about your project, which present in brief your problem statement and how you can
solve it.

Indent accordingly when you start a new paragraph. The abstract section should
not exceed a single page.

Keywords Word1; Word2; Word3; Word4; Word5

23

Abstrak

Abstract to be translate to Bahasa Malaysia

Kata kunci: Word1; Word2; Word3; Word4; Word5
24

Acknowledgement

The content of this single page is left to the discretion of the student. It is suggested however
that the page makes reference to guidance received by the student from his or her supervisor
and other members of the college. Reference should also be made to any financial assistance
received to carry out the project. Any extraordinary assistance received by the student for
example in word processing, data collection, data analysis, and so on, should be properly
acknowledged. Example acknowledgement can be found in books, reports and also papers.
The acknowledgements should not exceed 250 words.

25

Table of Content

Student’s Declaration
..................................................................................................................... 1
PARTB: ........................................................................................................ 9
Title 13
Table of Contents................................................................................... 13
Introduction ............................................................................................. 13
Problem Definition (or Motivation).................................................... 13
Project Objectives ................................................................................. 13
Project Scope.......................................................................................... 14
Literature Review ................................................................................... 14
Methodology ........................................................................................... 14
Project Timeline ..................................................................................... 15
Tools and Languages ........................................................................... 15
Expected Output/Result ....................................................................... 15
References............................................................................................... 15
STUDENT’S DECLARATION............................................................... 22
I hereby declare that the work in this project is my own except for
quotations and summaries which have been duly acknowledged. The
project has not been accepted for any degree and is not concurrently
submitted for award of other degree or professional qualification. .... 22
Signature: …………………………… ..................................................... 22
Name: ......................................................................................................... 22
Matric Number: ........................................................................................ 22
Date: ........................................................................................................... 22
Endorsed by: ............................................................................................. 22
Supervisor Name: ..................................................................................... 22
Signature: .................................................................................................. 22
Date: ........................................................................................................... 22
Abstrak ...................................................................................................... 24
Abstract to be translate to Bahasa Malaysia.......................................... 24
Acknowledgement..................................................................................... 25
List of Figures ........................................................................................... 27
List of Tables ............................................................................................. 28
List of Abbreviations ................................................................................ 28
1 Chapter 1: Introduction .............................................................. 29
1.1. Introduction .................................................................................... 29
1.2 Problem Definition (or Motivation) ............................................... 29
1.3 Project Objectives .......................................................................... 29
1.4 Project Scope.................................................................................. 29
1.5 Contributions of This Study (Optional) ......................................... 30
1.6 Project Timeline ............................................................................. 30
1.7 Thesis Organization ....................................................................... 30
2 Chapter 2: Literature Review ..................................................... 31
1.1 Introduction .................................................................................... 31

26

1.2 Background .................................................................................... 31

1.3 Related work .................................................................................. 31

1.3.1 Review of Relevant Work ............................................................... 31

1.3.2 Relationship between the Relevant Work and Our Own Work ...... 31

1.4 Summary ........................................................................................ 31

Summarize the chapter. You can do so by using tables or text. ................. 31

3 Chapter 4 System Analysis and Design ...................................... 33

4.1 Introduction .................................................................................... 33

4.2 Analysis of Existing Systems (Optional) ....................................... 33

4.3 Requirements Elicitation ................................................................ 33

4.3.1 Functional Requirements ............................................................... 33

4.3.2 Non Functional Requirements........................................................ 33

4.4 Requirements Specification ........................................................... 33

4.5 System design................................................................................. 34

4.6 Architectural design ....................................................................... 34

4.7 Object Oriented Design (not everyone will implement OOD) it

should be subject to the nature of the project................................. 34

4.7.1 Structural Static Models................................................................. 34

4.7.2 Dynamic Models............................................................................. 34

4.8 Data Modeling................................................................................ 34

4.9 User Interface Design..................................................................... 35

4.10 Summary ........................................................................................ 35

5.0 Chapter 5: System Implementation and Discussion ................. 36

5.1 Introduction .................................................................................... 36

5.2 System Hardware and Software ..................................................... 36

5.3 Mapping Design to Implementation............................................... 36

5.4 System Testing ............................................................................... 36

5.5 Results and Discussion................................................................... 36

5.6 Summary ........................................................................................ 36

6.0 Chapter 6: Conclusion and Future Work ................................. 37

6.1 Conclusion...................................................................................... 37

6.2 Goals Achieved .............................................................................. 37

6.3 Limitations and Future Work ......................................................... 37

7.0 References ..................................................................................... 38

8.0 Appendix A ................................................................................... 42

9.0 Appendix B ................................................................................... 43

PART C:...................................................................................................... 47

1.0 ASSESSMENT METHODS ................................................................ 48

11 Curriculum Vitae 41

List of Figures

Figure 4.1. Metrics for specifying non-functional requirements
[1]..…………………………6

27

Figure 2.1: Basic movement process
model…………………………………………………12

List of Tables

Table 2.1: An example of way-finding path table concept [2] …………………………12

List of Abbreviations

HCI Human Computer Interface
SDLC Software Development Life Cycle

28

1 Chapter 1: Introduction

1.1. Introduction
The primary purpose of the chapter is to provide an overview of the study. This

section sets forth the rationale, significance and objectives of the study. It includes details
of the background, problem statement, reasons for carrying out the project, and an
outline of what the student intend to do. The introduction must also include the following
components either separated into sections or integrated into one narrative.

1.2 Problem Definition (or Motivation)
The statement of the problem and/or hypothesis presents a focal point in the

research as it clearly states the purpose of the study. You should state specifically what
major questions and/or hypothesis are to be studied and/or tested along with all the minor
questions to be explored.

If you choose Motivation, you should explain the significant of the study, how it
resembles, supports and/or differs from other studies, and how it extends the present
knowledge or examines new issues.

1.3 Project Objectives
This section presents the objectives that the proposed project is going to achieve.

The objectives are the steps in achieving the goal(s) of the project and are usually
interrelated, brief and concise, and are also realistic given the time period.

The objectives are the main or specific issues that are being looked at. They must
be measurable, either qualitatively or quantitatively and form a guide to the research
methodology, data analysis and presentation of results. The number of objectives
recommended is three or less. The verbs are appropriate to the subject matter of study.

The following list shows the main objectives of the project:
• To study …
• To identify …
• To develop...

1.4 Project Scope
Project scope defines the range or extent of the project and helps to establish the

boundaries of the intended systems.

29

1.5 Contributions of This Study (Optional)
Please indicate the potential contribution of your project and how others can
benefit from it. Note, that this section is optional (you may exclude it).

Examples;
The research will be beneficial to …………………………………………
The project will be helpful to …………………………………..……….
The study will be a significant endeavor to ………………………….….…...

1.6 Project Timeline
The project timeline shows your (detail) plans and activities for the whole

semester. You can use the Gantt chart or any other project planning tool to illustrate
your activities.

1.7 Thesis Organization
This project consists of six chapters in addition to one (or several) appendixes.
These chapters are organized to reflect the scientific steps toward our main objective.
A brief description about the contents of each chapter is given in the following
paragraphs:
Chapter 1 introduces the project objectives, the motivation of the project, the approach
used in this project, the contribution of this project, the scope of the work, and project
layout.
Chapter 2 provides the reader with an overview of the literature review.
Each chapter should end with a conclusion in which we summarize the content of the
chapter and we announce what we are going to have in the next chapter.

30

2 Chapter 2: Literature Review

1.1 Introduction
A project must always be put in the context of existing works relevant to the topic.
Discussion of that context is referred to as a review of the literature. The list of
references should endorse that a thorough examination of similar and related existing
works have taken place.

This section includes a fully referred and discussions of previous studies
including substantial findings as well as theoretical and methodological related to
the project.

Students must include a review of the relevant literature especially the most
current reports (the past five to ten years at the most) related to the study. It should
contain a fully referenced review of previous studies, which may obtain from
journals, books, proceedings, articles or applications. Students must not duplicate
texts in the Introduction section with text written in the Literature review.

1.2 Background
You should provide a brief section giving background information on the materials
needed to follow your project because the information and experience of the readers with
the subject and materials involved may vary.

1.3 Related work
1.3.1 Review of Relevant Work

Categorize the literature into recognizable topic clusters:
• present the various studies that are relevant to your project,
• build on conclusions that lead to your project, or demonstrate the places where

the literature is lacking.
1.3.2 Relationship between the Relevant Work and Our Own Work

Highlight the uniqueness of your work and its relation to others.

1.4 Summary
Summarize the chapter. You can do so by using tables or text.

31

3 Chapter 3: Methodology
Final Year Project development methodology must be clearly written and

described precisely. It is the guide on how the study and the analysis of data
will be conducted. It is a plan of action of how the objectives will be achieved.
This section should provide relevant information on a description of the overall
approach, its relevance, effectiveness, and innovativeness. It gives details on
methodology, study place, study period, sample size, the population being
addressed, and how anticipated problems will be managed. The methodology
to be used should be cited from references.

The description of the developmental (or research) methodology is to
explain clearly and accurately "How" you solve the problem. This section may
explain the applied development process model. The description of the
methodology comprises the following:

• Description of the working procedure used (list of steps);
• The conditions necessary to achieve each step (e. g., equipment,

software, tools, instruments, parameters, etc.);
• Describe the processing of data collected;
• Identify the constraints imposed on the project.
There are many software development models and methods are available
in the market: waterfall, v, incremental, RAD, Agile, iterative, spiral, multimedia,
etc. Each of them has their own requirements and names. You are not restricted
to only using 1 type of these models. It should be flexible and of course depend
on the project requirement and deliverables. And do not forget the project
management activities as well.
Students must also describe the project design and the appropriate tools
to be used for verification of the results.

32

3 Chapter 4 System Analysis and Design

4.1 Introduction
It is necessary to study and analyze the current system to understand the

shortcomings and the problems, and generate solutions to solve the problems.
4.2 Analysis of Existing Systems (Optional)

This section may contain any of the following information; document
review, data collection, user interviews, or questionnaires.
4.3 Requirements Elicitation
The requirements are the descriptions of the system services and constraints.

4.3.1 Functional Requirements
§ Statements of services the system should provide how the system should

react to particular inputs and how the system should behave in particular
situations.
§ May state what the system should not do.

4.3.2 Non Functional Requirements
§ Constraints on the services or functions offered by the system such as

timing constraints, constraints on the development process, standards, etc.
§ Often apply to the system as a whole rather than individual features or

services.
§ Use metrics for specifying non-functional requirements (see Figure 2).

Figure 4.3. Metrics for specifying non-functional requirements [1].
4.4 Requirements Specification

Use case diagrams and description. This will depend on the nature of the
project. Not all project has this item. Use-cases are a scenario-based technique
in the UML which identify the actors in an interaction and describe the interaction
itself. A set of use cases should be describe with all possible interactions with the
system.

33

4.5 System design

The design is concerned with presenting the design of the artifact developed
and justifying how it should meet the identified requirements. It is likely to consist
of three parts:

1. how and why the design has been carried out – the approach and
notation used, etc;

2. the conceptual level design;
3. communication and description of the design.

As appropriate, alternatives considered may be discussed with justification for
the approach taken. The design should be expressed and detailed in a suitable
form.

4.6 Architectural design
The architectural design is concerned with understanding how a system

should be organized and designing the overall structure of that system, i.e. it
involves identifying major system components and their communications.

4.7 Object Oriented Design (not everyone will implement OOD) it should
be subject to the nature of the project.

4.7.1 Structural Static Models
The diagrammatic representation depends on the modeling language that

you use. For example, class diagram, DFD, ERD, etc.
For research-based or simulation project you probably need the (detail) flowchart,
experimental design, etc.

4.7.2 Dynamic Models
The student may present Activity diagrams, Statechart diagrams or

Sequence diagrams. For example, a sequence diagram may be used to add detail
to use-cases by showing the sequence of event processing in the system (shows
the sequence of interactions that take place during a particular use case or use
case instance). The sequence diagrams are used to model the interactions
between the actors and the objects within a system.

4.8 Data Modeling
The databases design or the developed algorithms should be presented

here. This section will reveal the final design and detailed description of all the
DBMS files and non-DBMS files. This section should contain criteria for the data
elements, including specific values, range of values, mandatory/optional,
alphanumeric values, and length.

34

4.9 User Interface Design
This section provides the detailed design of the system and subsystem

inputs and outputs relative to the user/operator.
• Provide the layout of all input data screens or graphical user interfaces
(GUIs) (for example, windows).
• Provide a graphic representation of each interface.
• Define all data elements associated with each screen or GUI, or reference
the data dictionary.
This section should contain criteria for the data elements, including specific

values, range of values, mandatory/optional, alphanumeric values, and length.
Also address data entry controls to prevent bypassing.

This section also describes of the system output design relative to the
user/operator; show a mapping to the high-level data flows. System outputs
include reports, data display screens and GUIs, query results, etc.
4.10 Summary

35

5.0 Chapter 5: System Implementation and Discussion
5.1 Introduction
5.2 System Hardware and Software
In this section you should state the tools and/or languages that you intend
to use and its justifications.
In this section, describe the overall system hardware and organization.
Include a list of hardware components (with a brief description of each item) and
diagrams showing the connectivity between the components.
In this section, describe the overall system software and organization.
Include a list of software modules (this could include functions, subroutines, or
classes), computer languages, and programming computer-aided software
engineering tools (with a brief description of the function of each item).

5.3 Mapping Design to Implementation
Detail explanation is required on how the discussion on system design (in

Chapter 4) relates with the actual implementation.

5.4 System Testing
The system testing can cover one or more of the following test types:

• Testing tools
• Unit tests.
• Verify that all system components are integrated properly and that actual

processing situation will be handled correctly (integration test).
• System and release testing.
• Demonstrate that users can interact with the system successfully (usability

tests).
• Functional requirements testing
• Code inspection
• Non-functional requirements testing
• Stability testing
• Security testing
• Exception handling testing

5.5 Results and Discussion
The student presents his results and interprets them by making links

between the required solution and the results obtained. The student writes
arguments and explanations, justifications and logical deductions so that the
reader is led to understand his position. All this interpretation approach must be
based on facts (existing data and results) and on technical and scientific
knowledge of the student.

5.6 Summary

36

6.0 Chapter 6: Conclusion and Future Work
6.1 Conclusion
In the conclusion the student should make a brief review of the problem,
objectives, assumptions and the methodology used, and summarize the solutions
and the obtained results.
6.2 Goals Achieved
This section describes to which degree the final outcome supports the original
objectives of the project (partially, fully achieved, or exceeded expectations). Here
you will summarize the achievements and deficiencies of your project. You may also
state what you would/could have done, if you had had more time or if things had
worked out differently.
6.3 Limitations and Future Work
In this section the student should set out the limits of his work and suggest new
works to be undertaken to complement or improve the present work. You should
also mention any unforeseen problems you encountered when implementing the
system and how and to what extent you overcame them. Common problems are:
o difficulties involving existing software, because of, e.g., its complexity,
o lack of documentation;
o lack of suitable supporting software;
o over-ambitious project aims.

37

7.0 References

The purpose of a reference is to acknowledge the contributions of other authors
to which you owe an intellectual debt, and also to enable readers to locate the source
easily. In this section, you can use alphabetical or numerical system. For the latter, we
recommend IEEE system which is widely used in computer sciences and engineering.
IEEE system dictates the in-text citation to appear as a number within square brackets
(e.g. [1]). The full details of the reference appear in the reference list in the order of
citation in the text. The following is an example list of references using IEEE system.
Please refer to the IEEE citation reference for details.

[1] I. Sommerville, "Software Engineering", 11th ed., Addison-Wesley, 2015.

[2] V. J. Blue, and J. L. Adler, “Cellular automata micro-simulation of bi-directional
pedestrian flows,” J. Transportation Research, pp. 135-141, 2000.

[3] S. Sarmady, F. Haron, and A. Z. H. Talib, “Modelling groups of pedestrians in least
effort crowd movements using cellular automata,” in Proc. 2009 2nd Asia International
Conference on Modelling & Simulation, Bali, Indonesia, 2009, pp. 520-525.

[4] F. H. Hassan,”Heuristic search methods and cellular automata modeling for layout
design ,” Ph.D dissertation, Sch. of Info. Sys, Comp. and Math., Brunel Univ., UK, 2013.

[5] G. K. Still. (2010, July 15). Crowd Disasters [Online]. Available:
http://www.gkstill.com/CrowdDisasters.html.

In-text Citing: It is not necessary to mention an author's name, pages used, or date of
publication in the in-text citation. Instead, refer to the source with a number in a square
bracket, e.g. [1], that will then correspond to the full citation in your reference list.

• Place bracketed citations within the line of text, before any punctuation, with a
space before the first bracket.

• Number your sources as you cite them in the paper. Once you have referred to a
source and given it a number, continue to use that number as you cite that source
throughout the paper.

• When citing multiple sources at once, the preferred method is to list each number
separately, in its own brackets, using a comma or dash between numbers, as
such: [1], [3], [5] or [1] - [5].

• Example: "Several recent studies [3], [4], [15], [16] have suggested that...."
38

• Examples of citations for different materials:

Material Type Works Cited
Book in print
Chapter in book [1] D. Sarunyagate, Ed., Lasers. New York: McGraw-Hill, 1996.
eBook
Journal article [2] G. O. Young, "Synthetic structure of industrial plastics,"
in Plastics, 2nd ed., vol. 3, J. Peters, Ed. New York: McGraw-
eJournal Hill, 1964, pp. 15-64.
(from database) [3] L. Bass, P. Clements, and R. Kazman, Software
Architecture in Practice, 2nd ed. Reading, MA: Addison
eJournal Wesley, 2003. [E-book] Available: Safari e-book.
(from Internet) [4] G. Liu, K. Y. Lee, and H. F. Jordan, "TDM and TWDM de
Conference paper Bruijn networks and shufflenets for optical
communications," IEEE Trans. Comp., vol. 46, pp. 695-701,
Conference June 1997.
proceedings [5] H. Ayasso and A. Mohammad-Djafari, "Joint NDT Image
Restoration and Segmentation Using Gauss–Markov–Potts
Newspaper article Prior Models and Variational Bayesian Computation," IEEE
(from database) Transactions on Image Processing, vol. 19, no. 9, pp. 2265-77,
2010. [Online]. Available: IEEE Xplore, http://www.ieee.org.
Technical report [Accessed Sept. 10, 2010].
Patent [6] A. Altun, “Understanding hypertext in the context of reading
Standard on the web: Language learners’ experience,” Current Issues in
Thesis/Dissertation Education, vol. 6, no. 12, July, 2005. [Online serial]. Available:
http://cie.ed.asu.edu/volume6/number12/. [Accessed Dec. 2,
2007].
[7] L. Liu and H. Miao, "A specification based approach to
testing polymorphic attributes," in Formal Methods and
Software Engineering: Proceedings of the 6th International
Conference on Formal Engineering Methods, ICFEM 2004,
Seattle, WA, USA, November 8-12, 2004, J. Davies, W.
Schulte, M. Barnett, Eds. Berlin: Springer, 2004. pp. 306-19.
[8] T. J. van Weert and R. K. Munro, Eds., Informatics and the
Digital Society: Social, ethical and cognitive issues: IFIP
TC3/WG3.1&3.2 Open Conference on Social, Ethical and
Cognitive Issues of Informatics and ICT, July 22-26, 2002,
Dortmund, Germany. Boston: Kluwer Academic, 2003.
[9] J. Riley, "Call for new look at skilled migrants," The
Australian, p. 35, May 31, 2005. [Online]. Available: Factiva,
http://global.factiva.com. [Accessed May 31, 2005].
[10] K. E. Elliott and C.M. Greene, "A local adaptive protocol,"
Argonne National Laboratory, Argonne, France, Tech. Rep.
916-1010-BB, 1997.
[11] J. P. Wilkinson, “Nonlinear resonant circuit devices,” U.S.
Patent 3 624 125, Jul. 16, 1990.

[12] IEEE Criteria for Class IE Electric Systems, IEEE Standard
308, 1969.

[13] J. O. Williams, “Narrow-band analyzer,” Ph.D. dissertation,
Dept. Elect. Eng., Harvard Univ., Cambridge, MA, 1993.

39

As for the alphabetical system (also known as author-date system), Harvard or
APA system of referencing can be used. The advantage of author-date system, is that
the name of the author and the year appear in the text, hence this ease reading. The
reader only refers to the reference section for the details of the document since the name
and the year already exist in the text.

In-text citations: eg. Mitchell (2017) states… Or … (Mitchell, 2017) or

Mitchell and Smith (2017) state… Or … (Mitchell & Smith, 2017)

Book referencing examples: Jones, A.F & Wang, L. (2011). Spectacular creatures: The
Amazon rainforest (2nd ed.). San Jose, Costa Rica: My Publisher

eBook: Mitchell, J.A., Thomson, M., & Coyne, R.P. (2017). A guide to citation. Retrieved
from https://www.mendeley.com/reference-management/reference-manager

Journal: Mitchell, J.A. (2017). Citation: Why is it so important. Mendeley Journal, 67(2),
81-95

Newspaper: Mitchell, J.A. (2017). Changes to citation formats shake the research world.
The Mendeley Telegraph, Research News, pp.9. Retrieved from
https://www.mendeley.com/reference-management/reference-manager

Curriculum Vitae

This gives a summary of the biographical, educational and other information and
experience of the student. It should include the name, date of birth, home address,
hobbies, educational background, achievements and experiences if any.

Poster
Posters are widely used in the academic community, and most conferences

include poster presentations in their program. Project posters summarize information
concisely and attractively to help publicize it and generate discussion.

The poster is usually a mixture of a brief text mixed with tables, graphs, pictures, and
other presentation formats.

The poster is good if

• Title is short and draws interest
• Word count of about 300 to 800 words

40

• Text is clear and to the point
• Use of bullets, numbering, and headlines make it easy to read
• Effective use of graphics, colour and fonts
• Consistent and clean layout
• Includes acknowledgments, your name and institutional affiliation

41

8.0 Appendix A
For the report, you should prepare an appendix explaining file structure on the CD

submitted with it. The appendix must also contain information on how the code should
be run (i.e. the user guide or manual). Other appendices may include documents such
as: the checklist of examiners’ comments, questionnaire, selected experimental data,
schedules, testing strategy or risk management plans. Do not include the source code
as an appendix (submit it on a CD). Do not include voluminous appendices (these should
also be submitted on a CD, if necessary).

Students who have successfully completed their final year project, oral
examination and made all the revisions and corrections required by the examining
committee, must submit one set of copy CD to the Project Coordinator.

42

9.0 Appendix B

This section shows examples of figure, table and equation. We assume that the
figure, table and equation appear in Chapter 2, therefore their numberings will be preceded
by number 2. Whenever possible please place the figures and tables alongside with the
captions, immediately following the first text that refer to it. If this is not possible, then the
figure or table should appear in the following page. More than one figure or table can be
placed in a single page. However, it is advisable to disperse the figures and tables
throughout the report. Please ensure that the figures and tables do not run across pages.

Inte ntion & De cis ion
Action

Ma cros copic Move me nts :
Wa y finding a nd Na viga tion, Me nta l Ma p

Ge ome try, Eve nts , Othe r Info ... Micros copic Move me nts :
Avoid collis ion, s horte s t pa th

Da ta a nd Vis ua l Outputs
E nvironment

Figure 2.1: Basic movement process model.

Figure 2.1 shows that before and after spacing should be equal to 12pt. The figure
caption is under the figure. Figures are center justification. If you start a paragraph with the
word “Figure” then use capital F, otherwise small f.

Tables are similar to the figures, but the difference is that the table caption is

above the table, for example, table 2.1 shows an example of way-finding path table

concept.

Table 2.1: An example of way-finding path table concept [2].

Source Destination Cost MidP- MidP- MidP- MidP-4 MidP-5 MidP-
1 2 3 6
Gate1 Gate2 1 - - - - - -
Gate1 Gate6 2 - - - -
Room4 Room7 3 Room1 - - - -
… Room3 Room5 … … … …
… … …
…

Each equation in a chapter is to be numbered consecutively using a decimal

system appearing flush with the right-hand margin. For example:

Y = mx + b (2.1)

The numbers in parentheses are the chapter number and equation number
respectively. Every new symbol used in the report text for the first time must be
explained. When a large number of special symbols are used, it is permissible to
collect them in a table or in a special appendix.

43

Appendix C

The following describe the details of the required report format.

Paper

Standard A4 size; Weight: 80 Grams

Width: 8.27"; Height: 11.69"

Fonts, Type Styles
Font Size = 12 (Normal Text)
Font = Times New Roman
Heading 1 (Font Size) = 22 (Bold), Font = Times New Roman
Heading 2 (Font Size) = 16 (Bold), Font = Times New Roman
Heading 3 (Font Size) = 14 (Bold), Font = Times New Roman

Margins
Top = 1.0" Bottom = 1.0"
Left = 1.25" Right = 1.0"

Spacing
Line Spacing = 1.5
Paragraph Spacing = 6 pts (before) and 0 pts (after)

Indentation
Indent all quotations comprising 4 or more lines by 5 spaces from left.

Page Numbers
Except for the title page, number all pages which come before the first page of the body
chapters consecutively with lower case roman numerals (i, ii, iii, iv…).

The first page with numeral (1, 2, 3, and so on) starts from the page of the
INTRODUCTION but it is mentioned on page 2 onwards. Mention page numbers on the
bottom right of the page. The first page of each chapter will not carry the page number,
however the page number will be counted for the thesis pages.

WRITING CONVENTIONS

Units of measure
The quantity of any measurement must be spelled out if it appears at the beginning
of a sentence. All measurements shall use SI units such as:

Normal measurement Abbreviation
2 kilometers 2 km
25 milliliters 25 ml
15 kilograms 15 kg
15 grams 15 g

44

Numbers

Spell out all numbers less than 10, unless the numbers are part of a series of
number or the numbers are attached to units of measurement.

Examples:
a) There are six children walking to the play ground.
b) The children were aged 2, 6, 7, 12 and 13 years old.
c) The standard deviations for each group were 3, 4, 8 and 15.
d) Its height and volume is 8 cm and 25 L respectively.

Use figures for quantities of 10 or more.
Example: There are 12 mothers waiting outside the classroom.

Percentage

The symbol % may be used in place of percentage; e.g. 25.5% and typed
without a space. If the candidate prefers to use “25.5 percent” in full, then
this should be consistent throughout the report.

Equations

Use Microsoft (MS) equation editor or equivalent for all equations. Numbering
of equations should be numbered consecutively bearing its chapter number
and in Arabic numerals.

TECHNICAL SPECIFICATIONS

Typing and printing

Use MS Word processor or equivalent for typing. Use laser printer for printing
text and illustrations on one side of each sheet.

Submission of FYP Report

Students are reminded to submit two copies of the corrected version of the
FYP report in CD a week after the oral presentation to the FYP coordinator.

One (1) complete copy of the FYP report, executable file, poster, abstract
and relevant documents to the Coordinator.

One (1) CD is to be submitted together with complete copy of the FYP
report, executable file, poster, source codes, and relevant documents to the
supervisor

Label the CD with project code, project title, student name, matric number
and supervisor name on Maroon colour paper pasted on CD and gold
lettering.

• The text on the label should be typed.
• One hardcopy thesis, if needed (for supervisor, if requested).

45

Cyberbully Detection System Cyberbully Detection System
This system is ….
Aida Adiana bt Azmi 199999

Bachelor of Computer Science (Multimedia)
Faculty of Computer Science and Information Technology

Universiti Putra Malaysia
June 2020

46