Faculty of Computing Project Report: Structure, Format, and Content

This document provides a comprehensive guide to structuring a computing project report. It outlines the essential components, including the introduction, which provides background information and project purposes; the body text, which forms the main content of the report; and the conclusions, which summarize findings and learning outcomes. Additionally, it covers the requirements for references, including proper formatting and citation styles, along with the inclusion of appendices. The document also specifies formatting guidelines, such as page size, font, and font size. This guide serves as a valuable resource for students, offering a detailed framework for creating a well-structured and informative project report, ensuring clarity and adherence to academic standards.

Faculty of Computing
Module name and Project name
<Version>
Your Name and ID number
Your E-mail address
2012

CSP065 template for Developing Software Engineering Documentation
Abstract
London Metropolitan University FOC
2

CSP065 template for Developing Software Engineering Documentation
Table of contents
1. Introduction.............................................................................................................................4
1.1 Purpose.............................................................................................................................4
1.2 Scope.................................................................................................................................4
1.3 Definitions, Acronyms, and Abbreviations......................................................................4
2. . Body of document...................................................................................................................4
2.1
2.2
2.3
Conclusions......................................................................................................................................4
References........................................................................................................................................4
A. Appendices..................................................................................................................................4
A.1 Appendix 1................................................................................................................................4
A.2 Appendix 2................................................................................................................................4
Other requirements..........................................................................................................................4
London Metropolitan University FOC
3

CSP065 template for Developing Software Engineering Documentation
1. Introduction
In this section, you should briefly introduce the project background and related information.
1.1 purposes
This subsection should present the purposes, or what are the achievements for the project.
1.2 Scope
This subsection should explain what is including in the project, what is not.
1.3 Definitions, Acronyms, and Abbreviations
This subsection should explain some special items, glossary, acronyms and abbreviations
used in the report.
2. Body text
Any report must have body text. This is the main part of the report. It could have several
sections based on the report type, express need or coursework requirements.
Conclusions
In this section, the author should summarise the report, what you did, what results you got,
and what are you learned from the coursework, etc.
References
This subsection should:
(1) Provide a complete list of all documents referenced elsewhere in the report, or in a
separate, specified document.
(2) Identify each document by title, report number - if applicable - date, and publishing
organization.
(3) Specify the sources from which the references can be obtained.
This information may be provided by reference to an appendix or to another document.
References should be done in Harvard Referencing Style.
Other requirements
1. Cover/Front page
Any document must have cover/Front page with sufficient information on the content of the
document. Here sufficient information is:
 The name of the document;
 The type of the document;
 The name of the organisation, which faculty/department/school, course and module
 The author(s) (including ID number, e-mail) of the document;
 The year of issue.
2. Table of contents
Any document must have the table of contents with page for any entry of the document. Pages
of the document must be numbered.
3. Size of page/Font/Font size
A4 page format must be used for the documentation. The margins should be 25.mm. The
recommended font is the Times New Roman and recommended size for paragraphs is 12pt.
London Metropolitan University FOC
4