How to write a structured Project
Report
The Project Report
The project report is an extremely important aspect of the project. It should be properly
structured and also necessary and appropriate information regarding the project. No data fields
are to be exposed in the project field.
The aim of the project is to produce a good product and a good report and that software,
hardware, theory etc. that you developed during the project are merely a means to this end.
Design document has to be progressively converted to a project report as and when the various
stages of project are completed. Ideally you should produce the bulk of the report as you go along
and use the last week or two to bring it together into a coherent document.
How to write a Project Report
A tidy, well laid out and consistently formatted document makes for easier reading and is
suggestive of a careful and professional attitude towards its preparation. Remember that quantity
does not automatically guarantee quality. A 150 page report is not twice as good as a 75-page
one, nor a 10,000 line implementation twice as good as a 5,000 line one. Conciseness, clarity and
elegance are invaluable qualities in report writing, just as they are in programming, and will be
rewarded appropriately. Try to ensure that your report contains the following elements (the exact
structure, chapter titles etc. is up to you):
Title page
This should include the project title and the name of the author of the report. You can also list
the name of your supervisor if you wish. IMPORTANT: Before submission you should assemble a
project directory which contains all your software, READMEs etc. and your project report (source
files and pdf or postscript).
Abstract
The abstract is a very brief summary of the report's contents. It should be about half a page long.
Somebody unfamiliar with your project should have a good idea of what it's about having read the
abstract alone and will know whether it will be of interest to them.
Acknowledgements
Report
The Project Report
The project report is an extremely important aspect of the project. It should be properly
structured and also necessary and appropriate information regarding the project. No data fields
are to be exposed in the project field.
The aim of the project is to produce a good product and a good report and that software,
hardware, theory etc. that you developed during the project are merely a means to this end.
Design document has to be progressively converted to a project report as and when the various
stages of project are completed. Ideally you should produce the bulk of the report as you go along
and use the last week or two to bring it together into a coherent document.
How to write a Project Report
A tidy, well laid out and consistently formatted document makes for easier reading and is
suggestive of a careful and professional attitude towards its preparation. Remember that quantity
does not automatically guarantee quality. A 150 page report is not twice as good as a 75-page
one, nor a 10,000 line implementation twice as good as a 5,000 line one. Conciseness, clarity and
elegance are invaluable qualities in report writing, just as they are in programming, and will be
rewarded appropriately. Try to ensure that your report contains the following elements (the exact
structure, chapter titles etc. is up to you):
Title page
This should include the project title and the name of the author of the report. You can also list
the name of your supervisor if you wish. IMPORTANT: Before submission you should assemble a
project directory which contains all your software, READMEs etc. and your project report (source
files and pdf or postscript).
Abstract
The abstract is a very brief summary of the report's contents. It should be about half a page long.
Somebody unfamiliar with your project should have a good idea of what it's about having read the
abstract alone and will know whether it will be of interest to them.
Acknowledgements
