Professional Documents
Culture Documents
General Instructions
head, bearing the signature of the project guide and project manager)
4. Acknowledgement
5. Table of Contents
i) Introduction
ii) Background
iv) Implementation
v) Conclusion
7. Appendices
8. Bibliography
Body of the document
1. Introduction
2. Background
o What the reader needs to know in order to understand the rest of
the report. Examiners like to know that you have done some
background research and that you know what else has been done
in the field (where relevant). Try to include some references.
o Related work (if you know of any)
What decisions you took, and why you thought at the time they were
good. Later, in the evaluation, you can criticise them.
4. Implementation
5. Testing
Test plan - how the program/system was verified. Put the actual test
results in the Appendix.
Appendices
• System manual
This should include all the technical details (where is the code? what do
you type to compile it? etc) that would enable a student to continue your
project next year, to be able to amend your code and extend it.
• User manual
This should give enough information for someone to use what you have
designed and implemented.
• Test results
Bibliography
Give publication details for all the references you have made in the report.