COLLEGE OF COMPUTING AND INFORMATICS

UNIVERSITI TENAGA NASIONAL

TITLE OF FYP

STUDENT’S NAME

MONTH YEAR
 FYP TITLE

by

STUDENT’S NAME

Project Supervisor: Supervisor’s Name

PROJECT REPORT SUBMITTED IN PARTIAL FULFILLMENT OF THE

THE REQUIREMENTS FOR THE BACHELOR OF INFORMATION TECHNOLOGY

(INFORMATION SYSTEMS) (HONS.)

UNIVERSITI TENAGA NASIONAL

MONTH YEAR
 APPROVAL PAGE

TITLE: TITLE OF PROJECT

AUTHOR: NAME OF CANDIDATE

The undersigned certify that the above candidate has fulfilled the condition of the Final Year

Project in partial fulfilment for the Bachelor of Information Technology (Information

Systems) (Hons.)

SUPERVISOR:

Signature: _______________________

Name: Supervisor Name

Date: _______________________

2
 DECLARATION

I hereby declare that this report, submitted to Universiti Tenaga Nasional as a partial

fulfilment of the requirements for the Bachelor of Information Technology (Information

Systems) (Hons.) has not been submitted as an exercise for a bachelor at any other university.

I also certify that the work described here is entirely my own except for excerpts and

summaries whose sources are appropriately cited in the references.

This report may be made available within the university library and may be photocopied or

loaned to other libraries for the purposes of consultation.

Date

_______Signature______

STUDENT”S NAME

STUDENT”S ID

3
 EXECUTIVE SUMMARY

[An executive summary is a concise summary of a larger project (a thesis, research report,

performance, service project, etc.) that concisely describes the content and scope of the

project and identifies the project’s objective, its methodology and its findings, conclusions, or

intended results.

Remember that your executive summary is a description of your project (what you

specifically are doing) and not a description of your topic (whatever you’re doing the project

on).

What should an abstract include?

i. Background problem and purpose of report

ii. Brief details of the approach, procedure or methodology used in developing the
application
iii. New findings such as improved solutions, invention, new theory, interpretation or
accurate reevaluation of old ideas or concepts
iv. Major conclusion(s)

Your executive summary need to be written in ONE LONG PARAGRAPH ONLY and its
length between 150 and 250 words]

4
 ACKNOWLEDGEMENT

content

5
 TABLE OF CONTENTS

PAGE

APPROVAL PAGE 2
DECLARATION 3
EXECUTIVE SUMMARY 4
ACKNOWLEDGEMENT 5
TABLE OF CONTENTS 6
LIST OF TABLES 8
LIST OF FIGURES 9
LIST OF ABBREVIATIONS/NOTATIONS/GLOSSARY OF TERMS 10
CHAPTER 1 11
1.1 Project Background 11
1.2 Problem Statements 12
1.3 Project Objectives 12
1.4 Project Scopes 12
1.5 Project Timeline 12

CHAPTER 2 13
2.1 Review on Current Systems 13
2.2 Review on Existing Systems 13
2.2.1 System 1 (URL/SOURCE) 14
2.2.2 System 2 (URL/SOURCE) 14
2.2.3 System 3 (URL/SOURCE) 15
2.2.4 Comparison between similar systems and proposed system 15
2.3 Business process flow diagram 16
2.4 Software development methodology 16
2.5 Requirements gathering technique 16
2.6 Tools and technology 17

CHAPTER 3 18
6
3.1 Flow Chart/Swimlane Flowchart /Hierarchical Task Analysis (HTA)/Use Case
Diagram 18
3.2 Data Flow Diagram (DFD) - Context Diagram & Level 0 18
3.3 Database Design - Entity Relationship Diagram (ERD), Data Dictionary 18
3.4 Navigation Diagram 19
3.5 Interface Design 19

CHAPTER 4 20
4.1 Introduction 20
4.2 System architecture Outcome of Project 1 20
4.3 Problems Encountered 20
4.4 Limitations 21
4.5 Planning for Project 2 21
REFERENCES 22

7
 LIST OF TABLES

Table No..................................................................................................................Page

Table 3.1 Geographical Objects and Representations.......................................................6

8
 LIST OF FIGURES

Figure No................................................................................................................Page

Figure 2.1 ABC Methodology...........................................................................................4

Figure 4.1 Login Page for the Sandbox system.................................................................9

9
 LIST OF ABBREVIATIONS/NOTATIONS/GLOSSARY OF TERMS

OBTS Online Bus Tracking System

SDLC System Development Life Cycle

10
 CHAPTER 1

INTRODUCTION

1.1 Project Background

This is one of the most important components of the report. It should begin with a clear
statement of what the application is about so that a lay reader can understand the nature and
scope of the application.

It also should include a clear summary of the application's background and relevance to other
work and give pointers to the remaining sections of the report, which contain the bulk of the
technical material.

11
1.2 Problem Statements

Students are expected to include clearly determined and organized the current problem an
organization or a user is facing, the opportunity, and the needs of developing the proposed
system (Rihaya Ahmad, 2014).

1.3 Project Objectives

Students are required to clearly indicate the purpose of the proposed solution/system.

Objective should be written in point form, can be measurable and suite all problem

statements.

1.4 Project Scopes

Students are required to explain about the system scopes and user scopes in this section.

System scopes should include functionalities that the students would like to provide, while

user scopes should include types of users who will be using the system.

1.5 Project Timeline

Students need to attach their proposed timeline (Gantt chart) for this project.

12
 CHAPTER 2

ANALYSIS AND SYSTEM REQUIREMENTS

1.6 Review on Current Systems

This section of the report should set the project into context by relating it to existing systems

used (computer based system or manual) that are related to the solution the student is

providing.

1.7 Review on Existing Systems

Reviewed of existing system that are related to this project is carried out to get a brief idea on

how existing system application been developed and worked. Screenshot of the existing

system can also be included. Students should compare the functionalities of the reviewed and

proposed system in table.

13
2.2.1 System 1 (URL/SOURCE)

Reviewed of existing system that are related to this project is carried out to get a brief

idea on how existing system application been developed and worked. Screenshot of

the existing system should also be included.

Figure 2.1 ABC Methodology

2.2.2 System 2 (URL/SOURCE)

Reviewed of existing system that are related to this project is carried out to get a brief

idea on how existing system application been developed and worked. Screenshot of

the existing system should also be included.

14
 Figure 2.2 System 2 screenshot

2.2.3 System 3 (URL/SOURCE)

Reviewed of existing system that are related to this project is carried out to get a brief

idea on how existing system application been developed and worked. Screenshot of

the existing system can also be included.

Figure 2.3 System 3 screenshot

2.2.4 Comparison between similar systems and proposed system

Comparison the functionalities of the reviewed and proposed system in a table.

15
 Table 2.1 Comparison table

Functions System 1 System 2 System 3 Proposed System

Function 1

Function 2

Function 3

Function 4

1.8 Business process flow diagram

Explain ALL existing business processes visually by using flow chart diagram. All affected

users must be stated in the flow chart.

1.9 Software development methodology

Students are expected to discuss the CHOSEN methodology ONLY and each phase should be

explained by relating the activities to your system development.

1.10 Requirements gathering technique

Students are expected to explain the techniques they use in gathering requirements for the

proposed system. You are supposed to describe the results from the technique(s) that you

16
have chosen. You may present your findings using charts or graph. Provide some discussion

to summarize all your findings and how it will help to develop the project in FYP2.

1.11 Tools and technology

Students are expected to briefly describe the tools and technology to be used in developing

the proposed system.

17
 CHAPTER 3

DESIGN

1.12 Flow Chart/Swimlane Flowchart /Hierarchical Task Analysis (HTA)/Use Case

Diagram

Include diagram to represent your process.

1.13 Data Flow Diagram (DFD) - Context Diagram & Level 0

Include diagram to represent the data movement of your system.

1.14 Database Design - Entity Relationship Diagram (ERD), Data Dictionary

Describe how the data was organized, stored and its relationship. Data modelling diagram

and data dictionary is included in this section.

18
1.15 Navigation Diagram

For web-based system, it is advisable to include this diagram. This diagram is to illustrate

the navigation on a home page

1.16 Interface Design

Include the interface design that will be used to interact with users. Provide discussion on

how the interaction works.

19
 CHAPTER 4

CONCLUSION

1.17 Introduction

Finally, it is a good idea to add a sentence or two to reinforce the objectives of the project
which was used in your introduction. This shows the reader that you have done what you
said you would do and gives a sense of unity the report.

1.18 System architecture Outcome of Project 1

This section should discuss the outcome of your project 1

1.19 Problems Encountered

Discuss the problems faced in completing project 1

20
1.20 Limitations

This section should explain the limitations of your project 1

1.21 Planning for Project 2

Provide some insights on how the system will be implemented in FYP2.

21
REFERENCES

J. C. Fairbanks, J. C. (2008). Oswestry Low Back Pain Disability Questionnaire.

academia.edu, 2. Retrieved January 11, 2017

Kenneth E. Kendall, J. E. (2013). Systems Analysis and Design (Vol. 9th Edition ).

Rohaya Ahmad, M. Y. (2014, July 11). TNB Data Collection Method. (N. N. Azmi,

Interviewer)

W3.CSS. (1997, February 10). SQL Tutorial. Retrieved 2017, from w3schools:

http://www.w3schools.com/sql/default.asp

22