Project listing

2025 COMP4601 Project Deliverables (Released 6/06/2025)

This page outlines the deliverables expected for the 2025 COMP4601 Projects.

In previous years we have maintained a wiki containing links to the various project groups participating in the course and their project documentation. The school is no longer supporting this tool, so we will trial a different approach in 2025. For this year each group will maintain its own web pages (preferably using vanilla HTML & CSS) stored in the public_html directory of the designated group representative. These pages will be linked to from the projects section of the COMP4601 website while the course is running and at the end of the course the pages are to be transferred to the class account for permanent storage. The project documentation your group is asked to prepare (detailed below) should be linked to and clearly identified as such on the project pages you maintain during the course. The documentation should be publicly accessible while the course is running and at least until the start of Term 3.

After you have formed your project group, decide on a group representative and establish your public project web page, including a group name and a listing of the group membership. Please email Oliver a link to the project page when this is complete and definitely no later than Wednesday 18 June.

Week 7 Initial Project Investigation & Plan
Week 10 Final Presentation, demo video & report; code repository
Week 11 Personal Reflection

Week 7 Initial Project Investigation & Plan

Investigation & Plan Presentation
Due: schedule TBA
Format: 20 minute presentation with Q&A to follow
Presentations will be held during one of the two weekly lecture slots in Week 7. The schedule will be confirmed before Week 7.

The presentation is expected to include content addressing the following topics:

• Problem specification
• Project aims
• Algorithm to be investigated
  • Pseudocode
  • Initial findings reporting on Steps 1 - 3 of the suggested project development plan
  • Opportunities for acceleration
• Project plan including milestones and timeline
• Risks & contingencies
• Roles of team members

Please include names of team members and slide numbers in your presentation. Please practice your presentation and its timing before your presentation. Presentations should involve speaking roles for all team members.

Post a PDF copy of your presentation on your project pages before your scheduled talk and update afterwards if necessary.

[top]

Week 10 Final Presentation, demo videos & reports; code repository

Final Presentations
Due: schedule TBA
Final presentations will be held during one of the two weekly lecture slots in Week 10. The schedule will be confirmed before Week 10.

Presentation slides should be uploaded 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-25 minute PowerPoint presentation to the class.

Final presentations should include slides on the following topics:

• Project overview
  • Aims & results
• Design
  • Solution approach including the team's use of AI
  • HW/SW architecture of solution
• Results
  • Performance evaluation
  • Discussion
• Conclusion
  • What worked; what didn't; why?
  • What you would do (differently), given more time

Presentations should involve speaking roles for all team members.

Demonstration Video
Due: 5pm, Friday 8 August

The purpose of demo video(s) is to showcase the operation of your solutions. This visual demonstration of operation allows course staff to gain further insight into what has been achieved over the term.

Demo video requirements:

• Course staff are interested in seeing your (a) SW-only, and (b) accelerated, SW-only or HW/SW solution in operation. For the sake of comparison, we want to be able to observe the performance and observe the validation of the results of both solutions. Detailed design explanations and code walkthroughs are not useful — the design should be outlined in your project presentation.
• This means that we are mostly interested in verifying what is displayed in the terminal window for both the software and hardware implementations. Profiling information and program run-time are of interest, as are demonstrations that verify correct output. To this end, you may wish to use screen-capturing software, such as Open Broadcaster Software (https://obsproject.com/).
• The focus of the video recording(s) should be on conveying useful information that would normally be acquired during a face-to-face demonstration. We do not need to observe the board itself during operation, unless this is relevant.
• The team is free to choose how many recordings are used to demonstrate their work and how they are edited. However, as a guide, the total run time of the video(s) should not exceed 5 minutes.
• The production quality of the video won't be assessed as long as it conveys the desired meaning. The team's marks will be determined by the capabilities and results of their solutions.

The demo recordings should be labelled and posted to the project page by the due date.

Project Report
Due: 5pm, Friday 8 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 video(s).

There is no prescribed format or required content for this element. However, as with all other documentation, it should be relevant, clear and concise.

Code repository
Due: 5pm, Friday 8 August
Format: Zip file containing your project code

Please zip up your code repository and provide a link to the file on your project web page.

[top]

Week 11 Personal Reflection

Individual Report
Due: 5pm, Monday 11 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 do well and what do you think you could improve at? 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]