Project _Report_Guidelines V1.0
Project _Report_Guidelines V1.0
• The suggested word limit is 10,000 words. This length limit does not
include diagrams or appendices. "10,000" is a guide so you have an
idea of the extensiveness of the project.
• Get started, then you will have plenty to say and write.
• Use A4 paper
• Use a Times New Roman or similar style font, point size 12 for most of
the document.
• The report should be typed, with reasonable spacing (1.5 or double)
between the lines.
• Number all pages.
• Use both sides of the paper.
• Allow a 40mm margin on the left-hand side, 20mm margins on the
right hand side and top and bottom.
• Start each section on a new page.
Examples
Official (Closed) - Non Sensitive
Which style should you use? Technical reports are always written in the
third-person point of view. Because you are writing a report which
documents the work done (by you), using the first-person would be
“overdoing” it and inappropriate. So, use the third-person point of view.
Instead of
Use
Instead of
Use
1.5 Penalties
• A penalty will also be imposed if only one copy of the report is handed
in.
• The report must be submitted in its entirety, any parts handed in late
will not be accepted.
2 The Abstract
The purpose of the abstract is to provide the reader with enough specific
knowledge of what has been done. It is a self-contained account of the
project and its scope.
Make sure the abstract gives reasonable and balanced coverage of all the
important parts of the report.
The abstract should be quite short. The length limit is about 300 words.
3 Evaluation
• How far were the objectives achieved? Why were the objectives
achieved or not achieved? (Give a cross-reference to the objectives
section.)
• Are you satisfied with your overall achievements? Why or why not?
• Did you meet deadlines? Was each task completed on time? Why or
why not? (Give a cross-reference to the project schedule chart.) Was
each task done to your satisfaction? Are there better alternatives for
doing them?
• Can you suggest any improvements to the system? Note: This part
can, if you like, be given in the form of Recommendations. The
recommendations are assumed to be for someone who is going to
develop the system further in the future. Use "should be" for a
stronger recommendation, and "could be" for a weaker
recommendation - more of a suggestion, really. Some examples are
given as follows:
• What experience have you gained from the project? What have you
learned that might be helpful to you in the future?
Official (Closed) - Non Sensitive
4 The Bibliography
The bibliography is a list of all the books or journal articles that you have
mentioned, or quoted, in the report. These items should be listed in
alphabetical order of authors' names. Here is an example of a
bibliography.
Bibliography
Weiss, E.H. (1985), How to Write a Usable User Manual, ISI Press,
Philadelphia.
For example, see Barr and Feigenbaum, and Weiss entries in the above
bibliography.
5 What is Plagiarism?
Plagiarism is taking someone else’s words and ideas and using them as
your own. Students who steal an idea (eg, statement, program code,
illustration) from a book or other sources, and treat it as their own original
work, has committed an act of plagiarism and will be penalised severely.
• Provide a bibliography entry at the end of the report for every source
used (Please refer to Section 4 on bibliography.)