PROJECT HANDBOOK

CDPR4103
(Diploma in Information Technology)

Faculty of Science and Technology

 CONTENTS

Page Number
Introduction 2
Requirements of Project 2
Learning Outcomes 2
Suggested Areas of Study 3
System Development (Application Based Project) 3
System Usability and System Function Evaluation (Research 3
Based Project)
How to Choose your Supervisor 4
Supervision 4
Implementation of Project 4
Project Proposal 4
Final Report 5
Content of Final Report 6
Format of Final Report 9
Final Project Rubrics 9
Appendix 1: Registration Form: Project 10
Appendix 2: Student Log Book 11
Appendix 3: Acknowledgement 18
Appendix 4: Declaration 19
Appendix 5: Assessment Rubric for Final Project 20

1
1.0 Introduction

It is well recognised that your project paper is an important component of the first-degree curriculum.
You are required to take the project paper towards or at the end of your studies. The project report is an
academic write-up that details the whole project process undertaken by you, right from the
conceptualisation of a problem to the discussion of his/her findings or outputs. Basically first-degree
project paper aims to train you to carry out a small-scale research activity (i.e. system development or
system evaluation in the context of IT).

The course consists of 3 credit hours and it is a compulsory.

1.1 Requirements of Project

1. You must obtain a CGPA of 2.00 and above before registering for this course.
2. Students registering for the course must be at least in their 3rd Year of study and above.
3. Project deliverables include:

Semester Deliverables Submit to

First Project Registration Form (Appendix 1) Faculty
Project proposal Supervisor
Second Log book (Appendix 2) Supervisor
Final report (soft cover binding)
CD (containing project report and system if
applicable)
CD (containing project report and system if Faculty
applicable)

4. For students who are able to complete within TWO semesters by following the deadline of
submission for that particular semester, the grade will be announced in the same semester. You
need to register for the project in both semesters.
5. If you fail to complete within the stipulated time (Total of 4 semesters) a grade F will be given and
you need to re-register the overall course/project.
6. To re-register for Final Project, please refer to myVLE for project registration datelines.

1.2 Learning Outcomes

You should be able to:

1. Understand and have the experience of doing a simple research in the field of information
technology.
2. Understand and have the ability to write a good report of the project.
3. Independent in carrying out research work.

2
2.0 Suggested Areas for Study

The scope of the first-degree project is program dependent. The project titles cover a wide range of
topics to meet the course objectives. Project topics can be proposed by you or the supervisor
concerned. There are two types of projects classified by the faculty, which are:

2.1 System Development (Application Based Project)

This type of project normally includes but not limited to development of new or improvement of
existing system, network, implementation, coding and working prototype.

Some of the examples for this type of project are listed below:
Inventory System Online Course Registration System
Web-based Booking System Student Attendance Management System
Online Monitoring System Online Typing Game
Online Recruitment System Personal Finance Management System
Room Booking System Interactive Kiosk
Scheduling System Interactive Map
Appointment System Short Video for Corporate Info
Reservation System Company Portal
Rental System Short Story Using 2D/3D Animation
Online Shop Digital Storybook
Online Travel Portal Azan SMS Notification
Online Voting System Notification Apps for Status Updates
Household Budget Management System Mobile Apps for Dictionary

2.2 System Usability and System Function Evaluation (Research Based Project)

This type of project typically includes but not limited to proof of concept and design, either new
algorithms or enhancement of ideas supported by information technology related data or laboratory
data or lab simulation or lab prototype, model or publication.

Some of the examples for this type of project are listed below:
Evaluation of Website Designs
Evaluation of e-Commerce Acceptance in Malaysia
A Comparative Study on e-Learning Frameworks and their Applications in Open Distance
Learning
Investigate the Efficiency of m-Learning
Designing Efficient Network Infrastructure for Small Medium Enterprise
Evaluation of Internet Navigation Methods
Network Simulation Using Packet Tracer to Investigate Network Performance

3
3.0 How to Choose your Supervisor

Your supervisor can be a lecturer who has a PhD or Masters in the field that you are interested to do
your project in. Supervisors can be appointed among your tutors or in certain cases, among lecturers
from IPTA or IPTS.

Once you have identified your supervisor, you can contact him/her by phone or email. When the
supervisor has agreed to supervise you, fill up the Project Registration Form (Appendix 1) to be
submitted to the Faculty.

3.1 Supervision

Basically you need to have five meetings (face-to-face or virtual) with your supervisor. You must discuss
your project topic with your supervisor in the first meeting with him/ her. It is recommended that you
complete your project proposal by the second meeting with the supervisor. It is very important that you
record your meetings with your supervisor in your log book.

During your discussion, you need to bring along the Student Log Book (Appendix 2). The supervisors
comments are to be recorded in the Log Book. At the end of the meeting, you must also get your
supervisors signature (digital signature is accepted) as evidence that the meeting was conducted. The
log book has to be submitted together with the final report.

4.0 Implementation of Project

In the course of the project, there are several deliverables as mentioned in 1.1. The deliverables will be
explained in full here.

4.1 Project Proposal

The first task that need to be done by you after the registration process is to come up with a Project
Proposal. Project Proposal should contain the following:

Title of the project

Introduction
Problem Statement
Objective
Project Scope
Requirement of Software/Hardware needed in the project (if applicable)
Gantt Chart
Conclusion

The project proposal can be 3-5 pages (1.5 spacing) and you need to submit it to your supervisor by the
second meeting of the first semester.

4
4.2 Final Report

After your proposal has been approved by your supervisor, you can proceed to write the report and
eventually develop the system (if applicable). The following are the chapters (to be included in the final
report) and time frame that are proposed so that you can complete the project on time.

If you are doing the system development project, you can use the following guide for writing your final
report.

Table 1: Guide for System DevelopmentFinal Report

Proposed Chapters Proposed Time Frame Proposed Number of
Pages in the Final
Report
First semester
(1) Introduction (problem statement, 2 week 3 - 5 pages
objective, scope, limitation,
implementation plan)
(2) Literature Review 4 weeks 4 - 6 pages
(3) Analysis&Design: Program design, 4 weeks 10-15 pages
Database design,
Interface design, etc
Second semester
(4) Implementation/Programming and 8 weeks 10-15 pages
Testing
(5) Summary and Conclusion 2 week 3- 4 pages
(6) References -
Appendix
TOTAL 20 WEEKS 30-50 pages
(2 semesters)

5
If you are doing system usability and system function evaluation project, you can use the following
guide for writing your final report.

Table 2: Guide for System Usability and System FunctionEvaluation Final Report

Proposed Chapters Proposed Time Frame Proposed Number of

Pages in the Final
Report
First semester
(1) Introduction (problem statement, 2 week 3-5 pages
objective, scope, limitation,
implementation plan)
(2) Literature Review 5 weeks 10-15 pages
(3) Research Methodology 5 weeks 10 pages
Second semester
(4) Research Findings and Discussion 6 weeks 10 pages
(5) Summary and Conclusion 2 week 4-5 pages
(6) References -
Appendix
TOTAL 20 WEEKS 30-40 pages
(2 semesters)

4.3Content of the Final Report

Contents of the project paper should be arranged in the following order. However, this is only a guide,
as project papers differ in terms of the contents, headings and subheadings. You should consult with
your supervisor and discuss with them when finalising the arrangements and contents for the
finalreport.

6
Preliminary Section

TITLE PAGE
DECLARATION
ABSTRACT
ACKNOWLEDGEMENTS
TABLE OF CONTENTS
LIST OF TABLES
LIST OF FIGURES

Body of Final Report

CHAPTER 1INTRODUCTION
1.1 Background
1.2 Problem Statement
1.3 Objectives
1.4 Scope and Limitation
1.5 Implementation Plan

CHAPTER 2LITERATURE REVIEW

(Review of relevant past/current projects in order to give context of what has already been
done.)

CHAPTER 3SYSTEM ANALYSIS AND DESIGN

3.1 Feasibility Studies
3.2 Requirement Methods
3.3 System Development Methods
3.4 Data And Process Modelling Diagrams
3.5 Program Design, Database Design, Interface Design, Etc.

CHAPTER 4SYSTEM IMPLEMENTATION AND TESTING

4.1 System Guides / Manual
4.2 Installation Manual
4.3 Testing Plan, Test Output
4.4 Main Function Codes

CHAPTER 5SUMMARY AND CONCLUSION

5.1 Summary Of Main Findings
5.2 Discussion And Implications
5.3 Limitations Of The System
5.4 Future Development

Supporting Materials
REFERENCES
APPENDICES

Figure 1: Final Report Layout for System Development

7
Preliminary Section

TITLE PAGE
DECLARATION
ABSTRACT
ACKNOWLEDGEMENTS
TABLE OF CONTENTS
LIST OF TABLES
LIST OF FIGURES

Body of Final Report

CHAPTER 1 INTRODUCTION
1.1 Background
1.2 Problem Statement
1.3 Objectives
1.4 Research Questions / Hypotheses (If Applicable)
1.5 Scope And Limitation
1.6 Implementation Plan
1.7 Definition Of Terms

CHAPTER 2 LITERATURE REVIEW

(Review of relevant past/current projects in order to give context of what has already been
done.)

CHAPTER 3 RESEARCH METHODOLOGY

3.1 Research Design
3.2 Data Collection Method
3.3 Data Analysis Method

CHAPTER 4 Research Findings and Discussion

(Description of statistical analyses in relation to the research questions/ hypotheses/ objectives
and presentation of relevant tables and figures)

CHAPTER 5 SUMMARY AND CONCLUSION

5.1 Summary Of Main Findings
5.2 Discussion And Implications
5.3 Limitations Of The Study
5.4 Future Direction

Supporting Materials
REFERENCES
APPENDICES

Figure 2: Final Report Layout for System Usability and System Function Evaluation

8
4.4 Format of Final Report

It is very important for you to follow carefully the guidelines for preparing the report.

The following items are to be observed in preparing the project report:

a. Page set up:

Set the page margins with an offset of 1 inch (or 2.5 cm) from the top, bottom, left and right. All
text, figures and tables must be within this area.

b. Paper size:
Use only A4 size white paper. The report should be printed on one side of the paper.

c. Font type:
Times New Roman, size 12
Line spacing:
1.5 spacing between lines and triple spacing between paragraphs.

d. Numbering format for headings:

The sections and sub-section in the report must follow the numbering format below:
1.0 Main heading
1.1 Secondary heading
1.1.1 Third headingand etc.

e. Illustrations:
Label all charts, graphs and tables.

f. References:
The source of information or references should be placed at the end of the report in numbered
order. Please use the APA writing style for your references.

5.0 FINAL PROJECT RUBRICS

The purpose of the Final Project Rubrics is to ensure that you understand what is expected of you when
completing your final report. (Appendix 5)

Rubric A is provided for those student doing the System Development project and Rubric B is for
students doing the System Usability and System Function Evaluation Project.

9
 Appendix 1

REGISTRATION FORM: DIPLOMA PROJECT

Date:
Student Name:

Matric No:

Subject Code:

Semester:

Programme:

PPW / PPT:

Contact Number:

Email:

Postal Address:

Project Title:

Project Summary:

Supervisor Name:

Supervisor Signature:

Email :

Supervisors Expertise :

Contact Number :

Note: Please fill in the form and fax to 03-5518 8449. For any inquiries, please email at
amalia_fadhlina@oum.edu.my.

10
 Appendix 2

STUDENT
LOG BOOK

FACULTY OF SCIENCE AND TECHNOLOGY

STUDENT NAME:

MATRIC NO:

PROGRAMME:

PPW / PPT:

PROJECT TITLE:

SUPERVISOR NAME:

11
 MEETING 1
FOCUS OF DISCUSSION:

SUPERVISOR COMMENT ON THE STUDENT PROGRESS SO FAR:

SUPERVISOR SIGNATURE:
STUDENT SIGNATURE:
DATE:

12
 MEETING 2
FOCUS OF DISCUSSION:

SUPERVISOR COMMENT ON THE STUDENT PROGRESS SO FAR:

SUPERVISOR SIGNATURE:
STUDENT SIGNATURE:
DATE:

13
 MEETING 3
FOCUS OF DISCUSSION:

SUPERVISOR COMMENT ON THE STUDENT PROGRESS SO FAR:

SUPERVISOR SIGNATURE:
STUDENT SIGNATURE:
DATE:

14
 MEETING 4
FOCUS OF DISCUSSION:

SUPERVISOR COMMENT ON THE STUDENT PROGRESS SO FAR:

SUPERVISOR SIGNATURE:
STUDENT SIGNATURE:
DATE:

15
 MEETING 5
FOCUS OF DISCUSSION:

SUPERVISOR COMMENT ON THE STUDENT PROGRESS SO FAR:

SUPERVISOR SIGNATURE:
STUDENT SIGNATURE:
DATE:

16
SUPERVISOR END OF THE SEMESTER COMMENT ON THE OVERALL STUDENT PROGRESS

SUPERVISOR SIGNATURE:
STUDENT SIGNATURE:
DATE:

17
 Appendix 3

Declaration

I declare that this project report entitled XXXXXXXXXXXXXXXX is the result of my own work except
ascited in the references. The project report has not been accepted for any degree and is not
concurrently submitted in candidature of any other degree.

Signature:
Name: XXXXXXXXXXXXXXXXXXXXX
Matric Number: XXXXXXXXXXXX001
Date: XXXXXXXXXX (Date of Submission to Supervisor)

18
 Appendix 4

ACKNOWLEDGEMENT

I would like to take this opportunity to express my gratitude and appreciation to my

supervisor, XXXXXXXXXXXXX guidance, patience and invaluable advice throughout this project.

I also would like to express my appreciation to my family and friends for their endless
support whenever I face problems. Without the mentioned parties, it is impossible for me to
complete this project report successfully.

THANK YOU.

XXXXXXXXXXXXXX (STUDENT NAME)

Feb, 2017 (MONTH, DATE OF COMPLETION)

19

Dimension 1 2
Introduction The title hardly reflects
the focus of the system,
revealing little
information about the
variables, subjects &
system setting.
Background information is
hardly relevant and does
not provide a clear lead-in
to the problem
statement.
Problem statement is
hardly articulated clearly
and not supported/
justified by theory and/or
past system.
Objectives, scope and
limitation are hardly
focused and clear.
Implementation plan not
provided.
Assessment Rubric for Final Project
RUBRIC A
SYSTEM DEVELOPMENT
The title reflects the focus
of the system, revealing
some information about
the variables, subjects &
system setting.
Background information is
fairly relevant but does
not provide a clear lead-in
to the problem statement.
Problem statement is
articulated fairly clearly
but only minimally
supported/ justified by
theory and/or past
system.
Objectives, scope and
limitation are fairly
focused and clear.
Implementation plan is
inadequate.
Appendix 5
3 4 Weight Score
The title clearly reflects The title very clearly
the focus of the system, reflects the focus of the
revealing fairly adequate system, revealing
information about the adequate information
variables, subjects & about the variables,
system setting. subjects & system setting.
Background information is Background information is
relevant and provide a very relevant and provides
clear lead-in to problem a very clear lead-in to the
statement. problem statement.
Problem statement is Problem statement is
2.5 10
articulated clearly and articulated very clearly &
supported/justified by well supported /justified
theory and/or past by theory and/or past
system. system.
Objectives, scope and Objectives, scope and
limitation are focused and limitation are highly
clear. focused and clear
Implementation plan is Implementation plan is
sufficient but can be complete and well
improved. planned.
20
Literature Review Hardly any evidence of
critical analyses of past
systems.
The review indicates little
understanding of the
system.
System Analysis Somewhat appropriate
and Design research design that is
capable of addressing
only some of the
objectives.
Rather vague description
of the requirements
analysis technique(s).
Only one feasibility study
reviewed: cost-benefit
analysis, technical
feasibility, time feasibility
and operational
feasibility.
Justifications for the use
of the methodology are
vaguely presented and
not discussed.
Very little description of
methodology use:
SDLC/prototyping.
Only one method of
systems analysis & design
Little evidence of critical
analyses of theory and/or
past systems.
The review indicates fairly
good understanding of the
system.
Fairly Appropriate
research design that is
capable of addressing
some of the objectives.
Fairly clear description of
the requirements analysis
technique(s).
Some feasibility studies
reviewed like cost-benefit
analysis, technical
feasibility, time feasibility
and operational
feasibility.
Justifications for the use
of the methodology are
presented but not
adequately discussed.
Some description of
methodology used:
SDLC/prototyping.
Some methods of systems
analysis & design given:
DFD,ERD, Normalization,
Some evidence of critical
analyses of theory and/or
past systems.
The review indicates good
understanding of the
system.
Appropriate research
design that is capable of
addressing all the
objectives.
Clear description of the
requirements analysis
technique(s).
Detailed feasibility studies
reviewed like cost-benefit
analysis, technical
feasibility, time feasibility
and operational feasibility
Justifications for the use
of the methodology are
presented and somewhat
adequately discussed.
Accurate description of
methodology used:
SDLC/prototyping.
Nearly all methods of
systems analysis & design
given: DFD,ERD,
Normalization, UML.
21
Ample evidence of critical
analyses of theory & past
systems.
The review indicates very 2.5 10
good understanding of the
system.
Very appropriate research
design that is capable of
addressing all the
objectives.
Very clear description of
the requirements analysis
technique(s).
Very detailed feasibility
studies reviewed like cost-
benefit analysis, technical
feasibility, time feasibility
and operational feasibility. 5 20
Justifications for the use
of the methodology are
clearly presented and
adequately discussed.
Very accurate description
of methodology used:
SDLC/prototyping.
All methods of systems
analysis & design given:
DFD,ERD, Normalization,
UML.
 given: DFD,ERD,
Normalization, UML.
Data analyses are
appropriate but hardly
adequate to address the
research questions.
UML. Data analyses are Data analyses are
appropriate, and are appropriate, extensive
Data analyses are
adequate to address most and sophisticated, and are
appropriate but only
of the research questions. adequate to address all
adequate to address some
the research questions.
of the research questions.

System Program may have Some syntactically & Mostly syntactically & Syntactically & logically
Implementation syntactic and / or logic logically correct codes, logically correct codes correct codes, complete
and Testing errors, incomplete test complete test scenarios mostly complete test test scenarios that tests
scenarios that tests some that tests data and scenarios that tests data data and processes.
data some and processes. processes. and processes.
The discussion on 10 40
The discussion on The discussion on some The discussion on most installation strategies is
installation strategies is installation strategies is installation strategies is complete with user and
incomplete with only complete with user and complete with user and system guides.
either the user or system system guides. system guides.
guides.

Summary and The discussion may be The discussion interprets The discussion interprets The discussion soundly
Conclusion incomplete or some of the findings and most of the findings and is interprets all the findings
partially/not clearly is somewhat connected connected with other and is carefully connected
connected to the with other sections of the sections of the report with other sections of the
objectives. The report such as the such as the background, report such as the
connection with other background, problem problem statement and background, problem
sections is vague. statement and objectives. objectives. statement and objectives.
2.5 10
Implications and Implications and Implications and Implications and
recommendations are not recommendations are recommendations are recommendations are
discussed. insufficient. discussed adequately. well discussed.
Limitations and future Limitations of the study Limitations of the study Limitations of the study
development of the study are fairly relevant but not are relevant and are very relevant and
are somewhat irrelevant. adequately described. adequately described. extensively described.

22
Writing Style, Writing style and Writing style and language Writing style and language Writing style and language
Language Use & language use are not apt use are fairly apt for use are apt for academic use are very apt for
grammatical for academic writing. academic writing. writing. academic writing.
accuracy 1.25 5
Many grammatical errors Some grammatical errors A few grammatical errors Hardly any grammatical
that impede that impede that impede errors that impede
communication. communication. communication. communication.

Overall The abstract is missing, The abstract summarizes The abstract summarizes The abstract concisely
Presentation of incomplete or inaccurate. the study by mere lifting the study with some summarizes the study
the Final Report sentences, at times essentials points missing. with all the essential
The presentation format
irrelevant, from the final points included.
including the graphics is The presentation format
project report.
at a minimum level of including the graphics is The presentation format
acceptability, though at The presentation format acceptable. including the graphics
times messy and including the graphics is demonstrates authors
Most sources are cited
confusing. fairly acceptable. attention to detail,
accurately to demonstrate
neatness and care.
Citations are rather Some sources are cited in the credibility of the
incomplete or inaccurate a proper format to enable information presented. All sources are cited 1.25 5
and provide little avenue accuracy checking. accurately to demonstrate
Chapters are organised
to check the validity of the credibility of the
Chapters are somewhat with logical sequencing.
the information gathered. information presented.
loosely organised but the Ideas are developed with
Organisation of chapters main sections still stand some support. Chapters are well
lacks logical sequencing out. Ideas are stated but organised with logical
and ideas are not clearly at times not clearly sequencing. Ideas are
developed. developed. clearly developed with
adequate support.

23
 RUBRIC B
SYSTEM USABILITY AND SYSTEM FUNCTION EVALUATION

Dimension 1 2 3 4 Weight Score

The title hardly reflects The title reflects the focus
Introduction
the focus of the study,
revealing little
information about the
variables, subjects &
research setting.
Background information
is hardly relevant and
does not provide a clear
lead-in to the research
problem.
Problem statement is
hardly articulated clearly
and not
supported/justified by
theory and/or past
research.
Research Objectives &
Questions/ hypotheses,
scope and limitation are
hardly focused and clear.
Hardly any key terms are
operationally defined
clearly.
Implementation plan not
provided.
The title clearly reflects
of the study, revealing the focus of the study,
some information about revealing fairly adequate
the variables, subjects & information about the
research setting. variables, subjects &
research setting.
Background information is
fairly relevant but does Background information is
not provide a clear lead-in relevant and provide a
to the research problem. clear lead-in to research
problem.
Problem statement is
articulated fairly clearly Problem statement is
but only minimally articulated clearly and
supported/ justified by supported/justified by
theory and/or past theory and/or past
research. research.
Research Objectives & Research Objectives &
Questions/ hypotheses, Questions/ hypotheses,
scope and limitation are scope and limitation are
fairly focused and clear. focused and clear.
Some key terms are Most key terms are
operationally defined operationally defined
clearly. clearly.
Implementation plan is Implementation plan is
inadequate. sufficient but can be
improved.
The title very clearly
reflects the focus of the
study, revealing adequate
information about the
variables, subjects &
research setting.
Background information is
very relevant and provides
a very clear lead-in to the
research problem.
Problem statement is
articulated very clearly &
well supported /justified
by theory and/or past 2.5 10
research.
Research Objectives &
Questions/ hypotheses,
scope and limitation are
highly focused and clear.
All key terms are
operationally defined
clearly.
Implementation plan is
complete and well
planned.

24
Literature Review The number of empirical
studies being reviewed is
inadequate.
Articles reviewed are
dated and hardly
relevant to the focus of
the study.
Hardly any evidence of
critical analyses of theory
and/or past research.
The review indicates
little understanding of
the research topic.
Methodology Somewhat appropriate
research design that is
capable of addressing
only some of the
research questions.
Rather vague description
of the research sample,
sampling techniques and
data collection
procedures.
Justifications for the use
of the methodology are
vaguely presented and
not discussed.
The number of empirical
studies being reviewed is
fairly adequate.
Articles reviewed are fairly
relevant to the focus of
the study but somewhat
dated.
Little evidence of critical
analyses of theory and/or
past research.
The review indicates fairly
good understanding of the
research topic.
Fairly Appropriate
research design that is
capable of addressing
some of the research
questions.
Fairly clear description of
the research sample,
sampling techniques, data
collection procedures and
methods of data analysis.
Justifications for the use
of the methodology are
presented but not
adequately discussed.
The number of empirical The number of empirical
studies being reviewed is studies being reviewed is
adequate. more than adequate.
Articles reviewed are Articles reviewed are very
current and relevant to current and relevant to
the focus of the study but the focus of the study.
somewhat dated.
Ample evidence of critical 5 20
Some evidence of critical analyses of theory & past
analyses of theory and/or research.
past research.
The review indicates very
The review indicates good good understanding of the
understanding of the research topic.
research topic.
Appropriate research Very appropriate research
design that is capable of design that is capable of
addressing most of the addressing all the
research questions. research questions.
Clear description of the Very clear description of
research sample, sampling the research sample,
techniques, data sampling techniques, data
collection procedures and collection procedures and 5 20
methods of data analysis. methods of data analysis.
Justifications for the use Justifications for the use
of the methodology are of the methodology are
presented and somewhat clearly presented and
adequately discussed. adequately discussed.
25
Research Findings Results and findings are Results and findings are
and Discussions somewhat inaccurate or presented correctly but
incompletely presented. the interpretation lacks
accuracy.
Data analyses are
appropriate but hardly Data analyses are
adequate to address the appropriate but only
research questions. adequate to address some
of the research questions.
The discussion may be
incomplete or The discussion interprets
partially/not clearly some of the findings and
connected to the results. is somewhat connected
The connection with with other sections of the
other sections is vague. report such as the
background, problem
statement, research
questions, instruments
and results.
Summary and The discussion may be The discussion interprets
Conclusion incomplete or some of the findings and
partially/not clearly is somewhat connected
connected to the results. with other sections of the
The connection with report such as the
other sections is vague. background, problem
statement, research
The findings presented
questions, instruments
are mere repetitions of
and results.
the results without
appropriate The findings are either
interpretation. superficially discussed or
not discussed in relation
Implications,
to theory and findings of
recommendations and
past studies cited in
Results and findings are Results and findings are
presented correctly with
accurate interpretation.
Data analyses are
appropriate, and are
adequate to address most
of the research questions.
The discussion interprets
most of the findings and is
connected with other
sections of the report
such as the background,
problem statement,
research questions,
instruments and results.
The discussion interprets The discussion soundly
most of the findings and is
connected with other
sections of the report
such as the background,
problem statement,
research questions,
instruments and results.
The findings are discussed
in relation to theory and
findings of past studies
cited in literature review.
Implications,
26
presented correctly with
accurate and detailed
interpretation.
Data analyses are
appropriate, extensive
and sophisticated, and are
adequate to address all
the research questions.
7.5 30
The discussion soundly
interprets all the findings
and is carefully connected
with other sections of the
report such as the
background, problem
statement, research
questions, instruments
and results.
interprets all the findings
and is carefully connected
with other sections of the
report such as the
background, problem
statement, research
2.5 10
questions, instruments
and results.
The findings are
judiciously discussed in
relation to theory and
findings of past studies
 directions for future literature review.
research are hardly
Implications,
drawn from the research
recommendations and
findings.
directions for future
Limitations of the study research are drawn from
are somewhat irrelevant. some of the research
findings.
Limitations of the study
are fairly relevant but not
adequately described.
recommendations and cited in literature review.
directions for future
Implications,
research are drawn from
recommendations and
most of the research
directions for future
findings.
research are carefully
Limitations of the study drawn from all the
are relevant and research findings.
adequately described.
Limitations of the study
are very relevant and
extensively described.

Writing Style, Writing style and Writing style and language Writing style and language Writing style and language
Language Use & language use are not apt use are fairly apt for use are apt for academic use are very apt for
grammatical for academic writing. academic writing. writing. academic writing.
accuracy 1.25 5
Many grammatical errors Some grammatical errors A few grammatical errors Hardly any grammatical
that impede that impede that impede errors that impede
communication. communication. communication. communication.

Overall The abstract is missing, The abstract summarizes The abstract summarizes The abstract concisely
Presentation of incomplete or the study by mere lifting the study with some summarizes the study
Final Report inaccurate. sentences, at times essentials points missing. with all the essential
irrelevant, from the final points included.
The presentation format The presentation format
project report.
including the graphics is including the graphics is The presentation format
at a minimum level of The presentation format acceptable. including the graphics
acceptability, though at including the graphics is demonstrates authors 1.25 5
Most sources are cited
times messy and fairly acceptable. attention to detail,
accurately to demonstrate
confusing. neatness and care.
Some sources are cited in the credibility of the
Citations are rather a proper format to enable information presented. All sources are cited
incomplete or inaccurate accuracy checking. accurately to demonstrate
Chapters are organised
and provide little avenue the credibility of the
Chapters are somewhat with logical sequencing.
to check the validity of information presented.
loosely organised but the Ideas are developed with
the information

27
 gathered. main sections still stand some support. Chapters are well
out. Ideas are stated but organised with logical
Organisation of chapters
at times not clearly sequencing. Ideas are
lacks logical sequencing
developed. clearly developed with
and ideas are not clearly
adequate support.
developed.

28