Released 26/05/2026
This page outlines the deliverables expected for the 2026 COMP4601 Projects.
All documentation for a particular 2026 COMP4601 project is to be stored in a publicly accessible git repository. This repository is to be established by the team by 5pm on Friday 19 June, by when the URL of the repository is to be emailed to Oliver by a team representatitive. When established, the repository will contain a readme file that explains what project the team will work on, who the team members are, and whom to contact for further information (team representatitive's email). The team should also choose a team name and provide this information in the file.
Week 5 Initial Project Investigation & Plan
Weeks 9 & 10 Final Presentation, demonstrations & report; code repository
Week 11 Personal Reflection
Investigation & Plan Powerpoint
Due: 5pm, Friday 3 July
Format: PDF of at most 8 PowerPoint slides
Note: The slides will not be presented
The PowerPoint slides are expected to cover content addressing the following topics:
Please include names of team members and slide numbers in your presentation.
Link a PDF copy of your presentation to your project page before the due date.
Maintain a project updates page where unplanned changes in direction are dated, recorded and briefly explained.
[top]
Final Presentations
Due: schedule TBA
Final presentations will be held during one of the two weekly lecture slots in Weeks 9 & 10. The schedule will be confirmed by Tuesday of Week 9.
A PDF copy of your presentation slides should be linked to your project page prior to your team's presentation and may be updated afterwards if necessary.
For each project team, this will involve a 20 minute PowerPoint presentation to the class.
Final presentations should include no more than 10 slides on the following topics:
Presentations should involve speaking roles for all team members.
Demonstration
Due: In the lab sessions immediately following your presentation in Week 9 or 10
The purpose of the demonstration is to showcase the operation of your solutions. This visual demonstration of operation allows course staff to gain further appreciation of what you worked on for the course. It's important that you plan your demonstration carefully. To that end, you are expected to link a demonstration plan to your project page by 1pm on the day of your demonstration.
Demonstration requirements:
Demonstrations are expected to take 10-15 minutes each.
Project Report
Due: 5pm, Friday 7 August
Format: Strictly no more than 10 pages PDF of clear, succinct text & diagrams
Up to 10 pages of project documentation may be submitted. These should only cover aspects of your project that were not adequately discussed during the presentation or demonstration.
There is no prescribed format or required content for this element. However, as with all other documentation, it should be relevant, clear and concise.
The PDF is to be linked to the project page by the due date.
Code repository
Due: 5pm, Friday 7 August
Format: Zip file containing your project code
Please zip up your code repository and link the file to your project page by the due date.
[top]
Individual Report
Due: 5pm, Monday 10 August
Format: One page PDF to be emailed to Oliver
Write a one page reflection on your personal experience of the project and the team dynamics.
What do you feel you accomplished? What did you and the team do well and what do you think you and the team could improve upon? What have you learned through your engagement with the project?
Describe and reflect upon how the project was managed. Was your team successful? Explain who took leadership and of which aspects. In which way, if at all, could the actions of the team or your own actions have been improved?
[top]