Final Presentation

Background

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.

Learning outcomes

Students should be able to:

Description of the task

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.

  1. The report should comprise a brief summary of the outcomes of the project, any software that has been developed, an evaluation of what has been achieved, and any shortfall from the original proposal (or the modified proposal following the design stage). The suggested structure of the report is described below.

    It is recommended that the report should be no more than five A4 pages long (with reasonably-sized font and margins), but there is no penalty for exceeding the recommended length.

    The report must be written by yourself using your own words (see the University guidance on academic integrity for additional information).

  2. The final presentation is intended to give an overall description of what has been achieved during the course of the project, rather than a detailed presentation of the outcomes (details should be included in the final dissertation).

    The use of presentation software is strongly recommended (such as the LaTeX "beamer" document class, PowerPoint, etc). You should give a copy of your presentation to both assessors at the beginning of the presentation. 15 minutes will be allocated for the presentation, plus time for questions from the assessors, typically 5 minutes.

Structure of report and presentation

A suggested structure for the report is as follows:

  1. SUMMARY OF PROPOSAL: A brief statement of what the project is about, including the main aims of the project.

  2. OUTPUTS: A description of what was produced in the project, along with a summary of any interesting aspects of the implementation (where appropriate).

  3. EVALUATION: An evaluation of what has been achieved, as well as any shortfalls from the original proposal. This can be brief, and is expected to be expanded upon more fully in the dissertation.

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 work and arrangement of presentation

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 28 August 2017 (5:00pm)  30 August 2017 (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 (30 Aug - 1 Sept). 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 11 September 2017 (5:00pm), with final presentations taking place during 11-15 September 2017.

The submission deadline for students who deferred their project is 13 November 2017 (5:00pm), with their presentation normally to take place during 13-17 November 2017.

Assessment

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.

COMP702 project marking descriptors

Table 1: Project marking descriptors
GradeClassificationPercentage Qualitative Description
A*Good Distinction80+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.
ADistinction70-79Logical; 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.
BGood Pass60-69Logical; 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.
CPass50-59Worthy 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.
DCompensatable Fail40-49Incomplete 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.
FFail< 40Serious omissions; significant errors/misconceptions; poorly directed at targets; evidence of inadequate effort. Shallow and poorly presented work showing failure in understanding.

Late submissions

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.

Other Penalties

  1. For every 5 minutes (or part thereof) in excess of the 15 minutes reserved for your presentation (excluding time spent on questions from the markers), 5 marks (out of 100 available for the assessment) will be subtracted.
  2. If the electronic submission of the report or the presentation slides is not a PDF file, then 5 marks (out of 100 available for the assessment) will be subtracted for each non-PDF file submission.
  3. NOTE: The use of a compression format other than ZIP poses a serious risk that your work may not be marked. If we can't decompress it, then we can't read it!

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.