Final Report- Quick Guide

Some of this is similar to what was included in the Interim Report, but with another 15 weeks
development.

Summary (Abstract)
The first section to appear, but probably the last to be written.
Call it either the summary, or abstract.
Encapsulates the whole report in about half a page.
The reader should be able to get an initial overview of the whole report, and therefore
the whole project from just reading the summary.

Contents
Second Section
Can be generated automatically by Word (See Writing Reports in Word for details)
All chapters, sections and subsections should be listed.

Introduction
The first numbered chapter (1.)
Scene-setting
Introduces the subject of the report (and in so doing the focus of the project) and the
structure of the report.

Background/Literature Review
Choose a suitable title for this chapter
This chapter shows your background research and reading around the subject.
The purpose of this chapter of the report is to show that you have a good grasp of the
current state of the field, that you have done extensive reading around the subject in
that area and are therefore competent and qualified to discuss the area in more detail
later in the report.
This is the chapter which will contain the most references (See Writing Reports in
Word for details). This section could easily contain 10 or more references- and dont
forget that it staff must instantly be able to tell what comes from each of these
references and what is your own original work.

What you have done...

May be 1, 2, or even 3 chapters here.
Give the chapters appropriate titles (What I have done is descriptive, but not in the
appropriate language for a formal report).
Follows on from ch 2 above.
Sets out problem
 Considers a range of possible solutions
Discussion of optimal solution with reasons
Development of that solution

(This is a progress report so you may not have done all these yet. The most important thing is
to say what you have actually done, not what you think we want to hear in an idealised
world.)

Testing/Analysis
Having set out what you believe to be the optimal solution to the problem, you must
now prove this to be the case by discussing the testing of the system, and presenting
any analysis which supports this.

You dont necessarily need to present absolutely every test here (although they should
all be recorded in your log book), but you should present all major tests which
demonstrate the ability of the system to meet the requirements. You should also detail
why such tests are relevant in proving the operation of the system.

Conclusions and Review

This section is a summing up of all that has gone before.

Review of what you have presented and the main results which prove the operation of
your system and its ability to meet the goals set.

Review any wider implications your system may have.

Comment on anything which is still outstanding or could be improved.

This is the end of the written part of the interim report but you also need to include:

References
List of references used earlier in the report.
All references identified in the text, use either IEEE (preferred in CT) or Harvard
system, and be consistent.
Note: this is different from the:

Bibliography
List of other books/ journals/ articles read and used in the formulation of your
argument but not specifically referred to.

Appendicies
Identify by letter, starting from A.
 Use sparingly for additional information with which the reader could not be expected
to be familiar, but which it is necessary for the reader to have on hand in order to
understand the report and which would get in the way if included in the main text.

General

Coherent Argument
The report should read as a coherent argument, from beginning to end. It should flow and
readers who are not familiar with your project should be able to understand what the project
is about and what you have done.

You should assumed that your audience has a good general understanding of your area of
work, so do not need to include basic details, but they may not be familiar with your specific
project.

Whilst the background and context are important, most of the report should focus on what
you have done- as detailed below.

Numbering
Chapters and sections should be numbered using the decimal numbering system

Figures, tables and equations should all be numbered.

Figures and tables should also be titled and referred to in the main text.

Chapters should start at the top of a new page.

Style
Use the template provided and the style guide to ensure a consistent presentation. Proof read
before submission to check for errors, what for layout problems such as titles for figures
jumping to the next page or units jumping to the next line (use CNTL+SHIFT+SPACE) to
insert a space which will not act as a line break.

Ensure you use the English spell checker (UK not US) and English (not continental)
presentation of numbers (decimal point is a full stop not a comma).

You should use formal English, and should check that spelling and grammar are correct. If in
doubt, use the check-facilities on Word, and get a friend who has good correct English to
proof read your report.

When starting new chapters start them on a new page. Use Insert-page break to move to the
next page, not repeated line breaks.

Acknowledgement
If you wish you can include a very brief acknowledgement. This should not be more than a
couple of lines and should be placed between the Summary and the Table of Contents.
Submission
Make sure you use the template provided on WebLearn and that you submit two
copies. Make sure that the reports are properly bound. At the very least, spiral or hot
glue binding should be used- reports should not be submitted with just a staple in the
top corner.