This stage is intended to provide an overview of what has been achieved in the project. The purpose of the two deliverables for this stage, a short report and a presentation, is to summarise the main outcomes of the project. If software has been developed during the course of the project, it is appropriate to give a brief demonstration illustrating the primary function(s) of the software.
Students should be able to:
Your task is to produce a short report for your project, and to conduct an oral presentation about the outcomes of the project. Where appropriate, a brief demonstration of the main functionality of developed software should be given.
A suggested structure for the report is as follows:
The final presentation should follow the same structure as the report but focus on the most important features or most interesting aspects of the project. It is expected that the majority of the time allocated for the presentation will be spent on demonstration of the software developed (if that is the main outcome of the project), its functionality, features, etc.
Posters: Some projects may not result in the production of demonstrable software, either due to the nature of the project, because the project has been developed externally, or because of problems encountered in due course. However, the principle of an informal presentation remains important. In such cases students will be expected to produce a poster which they will use to talk about their project, and will be expected to answer questions and respond to their audience as for a software demonstration.
Software demonstration: Most projects, however, are expected to contain an integral software component. After a very brief formal presentation, students are asked to engage in a less formal and more interactive demonstration where the student and the markers should talk through the developed software. In such a situation, flexibility to respond to the person to whom one is demonstrating, and the ability to answer questions is important. Use of supporting material, such as diagrams, tables, etc is recommended if this improves presentation of the project and the work that has been performed. The demonstration should be focused on functionality of the working software, and students should be prepared to answer questions about the software, and to explain implementation of requested fragments of the software (e.g code listings, etc).
The final presentation and report should clearly show the main outcomes/achievements of the project so as to inspire confidence that the project has been completed successfully (to the satisfaction of the supervisors).
Submission of the report and a copy of the final presentation
slides is done in electronic form (PDF format only)
via the Coursework Submission System.
The deadline for the submission of both the report and the presentation
slides is 21 August 2020 (5:00pm) (and before your
presentation takes place).
Zipped versions of the documents are acceptable for the
electronic submission.
Do not use any
form of compression other than ZIP!!
Note that during submission of your work, you are also making an online
Declaration of Academic Integrity.
You should arrange (with the markers) a convenient time for the presentation.
The final presentation is expected to take place during
Week 13 (Aug 24-28). As mentioned previously,
a copy of the presentation slides should be given to each assessor at the
beginning of the presentation.
Students who took two or more resit exams are allowed to submit their report and final presentation by 4 September 2020 (5:00pm), with final presentations taking place during 7-11 September 2020.
The submission deadline for students who deferred their project is 5 November 2020 (5:00pm), with their presentation normally to take place during 9-13 November 2020.
The assessment will determine to what extent learning outcomes stated above
have been achieved and will cover both the report and
the final presentation. The assessment will be conducted by two markers.
Each marker will produce separate feedback and grades (according to the
COMP702 project marking descriptors below)
that will be reported back to you as well as a combined mark (with a maximum
of 100 points).
This mark will count for 20% of the overall final grade for the project.
Failure in this task can be compensated by higher marks on the other assessments
of the project.
For your guidance, a copy of the feedback form that will be used to assess
your design and presentation is
available.
| Grade | Classification | Percentage | Qualitative Description |
|---|---|---|---|
| A* | Good Distinction | 80+ | Factually almost faultless; perceptive and focused treatment of all issues. Clearly directed; logical; comprehensive coverage of topic; strong evidence of reading/research outside the material presented in the programme; substantial elements of originality and independent thought; very well written. critical and scholarly presentation. |
| A | Distinction | 70-79 | Logical; enlightening; originality of thought or approach; good coverage of topic; clear, in-depth understanding of material; good focus; good evidence of outside reading/research; very well written and directed. |
| B | Good Pass | 60-69 | Logical; thorough; factually sound (no serious errors); good understanding of material; evidence of outside reading/research; exercise of critical judgement; some originality of thought or approach; well written and directed. |
| C | Pass | 50-59 | Worthy effort, but undistinguished outcome. Essentially correct, but possibly missing important points or inadequate treatment. Largely derived from material delivered in the programme, but with some evidence of outside reading/research; some evidence of critical judgement; some weaknesses in expression/presentation. |
| D | Compensatable Fail | 40-49 | Incomplete coverage of topic; evidence of poor understanding of material; Poor presentation; lack of coherent argument. Very basic approach to a narrow or misguided selection of material. Lacking in background and/or flawed in structure. |
| F | Fail | < 40 | Serious omissions; significant errors/misconceptions; poorly directed at targets; evidence of inadequate effort. Shallow and poorly presented work showing failure in understanding. |
The University's standard policy on lateness penalties will be applied with respect to the latest electronic submission of the report and/or presentation slides. See Section 6 of the Code of Practice on Assessment for further details.
However, penalties will not reduce the mark below the pass mark for the assessment. Work assessed below the pass mark will not be further penalized for exceeding the presentation time limit or electronic submission in an incorrect format.