COMS6200 Project Part B - Final Report Information and Structure
Below is an example/template for the expected report structure. However, the exact structure of
your report might vary, depending on the nature of your project, e.g. an implementation project vs.
a research focussed project.
There is no strict page limit, and quality/contribution is more important than quantity, i.e. number of
pages. However, as a very rough guideline, the final report should be 15-25 pages long. (For smaller
teams, this can be somewhat less.) Make sure you use section numbering and provide a table of
content.
Title Page
Course Code
Name of institution (UQ, EECS)
Title of Project
Team Name (e.g. “Team A”)
List of team members, name and student ID

Abstract
Brief summary of the project aims and its outcomes. (~80-100 words)
Introduction
Context and the ‘what’ (scope) and the ‘why’ (motivation) of the project.
A brief summary of what was achieved.
Background
Briefly explain basic key concepts technology that is relevant to your project and is required for understanding
the rest of the report, e.g. a very brief overview of SDN if relevant for your project.
Related Works
Discuss other works that are related to your project, ideally with a focus on peer reviewed literature.
Key contributions Section/Chapter, e.g. “Efficient Topology Discovery in ONOS”
(Name and structure of this section will depend on the type of your project!!! )
Design
Implementation/ Experimental Results
Evaluation

Discussion
Summary of contributions/achievements, critical discussion, directions for future work

References
As you can see, it is similar to the structure of the project proposal/progress report, but without the
Project Plan component.
The key difference is the main chapter/section, which discusses your main contribution, e.g. the
design, implementation, experiments, etc. and evaluation.
For the Introduction, Background and Related Works sections of the final report, you can use the
relevant parts from the Project Proposal/Progress as a basis (there is no issue with self-plagiarism for
this). However, I would expect these parts to be updated, based on additional insights gained during
the second phase of the project.