××× (Put the Project title)

××× (Put the Project title)

Final Report

Course name: ×××

Student name: ×××
Course: ×××
Supervisor name: ×××
Submission date: ×××

At the bottom of the title page you should include the following statement:
This report has been submitted for assessment towards a Bachelor of Engineering Degree
in . . . . . . (subject). . . in the School of Engineering, London South Bank University. The
report is written in the author's own words and all sources have been properly cited.

Author's signature:

Page 1 of 14
 ××× (Put the Project title)

Abstract

The abstract should be a short summary (about 200 words) of the report and include the aims/objectives of
your work, the methods used and your main results/achievements/conclusions. It should be written last,
after the main report is finished. It can be distilled from the introduction, conclusions and recommendations
of your report. Abstracts play a key role in engineering and scientific reporting. They tell the reader what
your work is about and what has been achieved. If the reader is interested, they can continue reading the
report. If not they will have wasted little time.

It cannot be stressed how important it is to write an effective abstract. Any written work you do for a future
employer will require an executive summary or abstract and must be done properly.

Page 2 of 14
 ××× (Put the Project title)

Contents
Abstract.............................................................................................................................................................2
1. Project Introduction................................................................................................................................4
2. Aims/Objectives and Scope of the Project.............................................................................................5
3. Deliverables..............................................................................................................................................6
4. Technical Background and Context.......................................................................................................7
5. Technical Approach.................................................................................................................................9
6. Results and Discussion...........................................................................................................................10
7. Conclusions and Recommendations for Further Work......................................................................11
References.......................................................................................................................................................12
Appendix.........................................................................................................................................................13
Project Planning.............................................................................................................................................14

Page 3 of 14
 ××× (Put the Project title)

1. Project Introduction
This 'sets the scene' and gives the reader a brief background to the general area of your project.
Describe in general terms what you are doing and why. The introduction should also guide the reader
through your report e.g. what is addressed where. This section should be long enough to cover the
essentials but short enough to maintain interest.

Page 4 of 14
 ××× (Put the Project title)

2. Aims/Objectives and Scope of the Project

 Aim

Give the main aim of your project. This is what you hope to achieve by the end of the project. Try to
make this as specific as possible so that you and others can assess how successful you have been at
the end of the project. Your aim must be realistic and achievable.

 Objectives

These are subsidiary aims whose completion will enable the main aim to be met. There can be several
of these. Again try to make them specific and measurable wherever possible.

Page 5 of 14
 ××× (Put the Project title)

3. Deliverables
Deliverables are the main outputs of the project e.g. the final report, any hardware you will construct,
software, user manuals etc. Deliverables are obviously related to the aims/objectives. List the key deliverables
for your project.

Page 6 of 14
 ××× (Put the Project title)

4. Technical Background and Context

This sets the scene for your project work in more detail and gives a description of the field. It
reviews and summarizes the existing knowledge (theoretical, practical, experimental) available in the
'literature' (text books, journals, patents, etc. ) i.e. the work other people have done in the area. You
need to critically evaluate this work in the context of your project. Describe why you are doing the
project and identify where it makes a contribution to the area e.g. is the work you are doing going to
improve anything, make something more useful, add to the general understanding of the topic, etc.
References must be given to any literature you cite in your report. Stick to the project theme. This
section and the references to published work should bring the reader to the point where he/she is in a
position to read and understand your report in detail. It is often the case that students do not do
enough background reading and as a result cannot put their projects into context. Do not
underestimate the importance of a proper literature search. Make full use of the Library and
electronic resources at your disposal.

Page 7 of 14
××× (Put the Project title)

Page 8 of 14
 ××× (Put the Project title)

5. Technical Approach
This is the 'how you did it' part of the report. Describe exactly what you have done and the methods used.
Generally topics like scope, design work, construction of equipment, procedures for testing and measurement,
etc. are covered here. Any apparatus used to carry out experimental measurements should also be described
here. It is difficult to give examples covering all the different types of projects students do because there are
so many. If in any doubt discuss with your supervisor what should be covered. You can always do things in
more than one way and this section should also describe other methods you have considered and the reasons
for their rejection. You should also describe the technical problems you encountered and your attempts to
solve them. Don't forget that experiments which go wrong can be important too!

Page 9 of 14
 ××× (Put the Project title)

6. Results and Discussion

In this section you need to present your main results and analyze them in a critical manner against
expectations, predictions, models, assumptions etc. For example, if you have done software or a
hardware project, the results of testing the software or hardware and a critical discussion of how it
has performed must be given here. Present all your results carefully using diagrams, tables and
graphs as appropriate. If the results are extensive, (e.g. lots of data tables, graphs/_gures, program
listings, etc), include the key ones in this section and the rest in appendices, referring to the latter as
necessary. State how signi_cant you think the work is and support your claims with evidence from
your results, the literature, etc. You must also give a discussion of the experimental errors associated
with your measurements if you have done an experimental/modelling project. This section can be
divided into a separate results and a separate discussion section if you wish. As you would expect
most of the marks will be gained from how well you discuss your _ndings. Do not present results
without analysis and discussion unless you want to fail!

Page 10 of 14
 ××× (Put the Project title)

7. Conclusions and Recommendations for Further Work

Summarize your key findings and results, successes and failures and problems encountered. Assess the work
against the aims and objectives listed at the beginning of the report and the deliverables. Have you met these?
Try to put your work into the wider context of the area. Finish off with recommendations for further work
where you identify areas that need completing or further research which needs to be done. The use of bullet
points is a very effective way of listing the conclusions and is recommended. This section should be very
brief. There must be nothing new in the conclusions. Your discussion must logically lead the reader to your
conclusions.

Page 11 of 14
 ××× (Put the Project title)

References

Page 12 of 14
 ××× (Put the Project title)

Appendix

Only include items that are referred to in the report. Do not include published work this should just be listed in
the references. Inserts such as oppy disks must be securely attached to the inside-back cover of the report;
they must be easily accessible and replaceable. If you have a large document as an appendix e.g. a user
manual, this may be submitted separately if absolutely necessary. In this case it must be labelled clearly on the
cover and spine to indicate the content.

Page 13 of 14
 ××× (Put the Project title)

Project Planning

Required with Progression, Interim and Final Project Reports See page 14 of MG for a full description.
Ensure that Planning is clearly shown in your Interim and Final report.

Length of Report This final report should not be more than 30 pages long excluding reference and appendices.

Page 14 of 14