Project listing

2021 COMP4601 Project Deliverables (Released 11/06/2021)

This page outlines the deliverables expected for the 2021 COMP4601 Pojects.

All project documentation and code is required to be posted to its own project-specific section of the COMP4601 wiki.

• We hope that requiring you to do so will contribute to the sharing of knowledge across year groups and contribute to the creation of a helpful learning community.
• The idea is to share the experiences you have gained in COMP4601 in the most effective (direct, concise) and transparent manner possible.
• Ask yourself: "What information would I have liked to have known before I found the solution to the problem I just solved?" If you are able to answer this question now, but couldn't find the answer on the COMP4601 Wiki before you began your search, you should consider writing about it in the Wiki!

Week 7 Project Plan and presentation
Week 10 Final Presentation, demo video & report

Week 7 Project Plan

Project Plan
Due: 5pm Friday 16 July
Format: When printed from the wiki, equivalent to a 2–3 page PDF of clear, succinct text & diagrams

The Project Plan is expected to include content addressing the following topics:

• Project objectives
• Algorithm to be investigated
  • Description
  • Pseudocode
  • Opportunities for acceleration
• Project plan including milestones
• Roles of team members
• Risks/concerns

Please include the names of your group members on your report.

Project Plan Presentation
Due: 14-15 July
Project plan presentations will be held during one of the two weekly lab classes in Week 7 at the latest.

Your group is expected to give a 10 - 15 minute (approx. 3-5 slide) PowerPoint presentation on your project plan to the course staff and interested participants during one of the two weekly lab classes before Week 8. Please email Oliver of your intention to present for scheduling purposes.

[top]

Week 10 Final Presentation, demo video & report

Final Presentation
Due: 4-5 August
Final presentations will be held during one of the two weekly lab classes in Week 10. The schedule will be confirmed before Week 10.
Presentation slides should be uploaded to your project pages on the course wiki prior to your team's presentation..

For each project team, these will involve a 15-20 minute (5-10 slide) PowerPoint presentation to the attendees of the lab class.

Final presentations should include slides on the following topics:

• Project overview
  • Aims & results
  • Challenges
• Design
  • Solution approach
  • HW/SW architecture
• Results
  • Performance evaluation
  • Discussion
• Conclusion
  • What worked; what didn't
  • What you would do, given more time

Presentations should involve speaking roles for all team members.

Demonstration Videos
Due: 5pm, Friday 6 August

The purpose of the demo video is to showcase the operation of your hardware/software solutions to your chosen algorithm. The 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 results of both solutions.
• This means that we are mostly interested in verifying what is displayed in the terminal window of the SDK/Vitis 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.
• The production quality of the video won't be assessed. The team's marks will be determined by the capabilities and results of their solutions.
• This is a demo of system operation and performance, not a code walk-through.
• The demo recordings should be labelled and posted to the project wiki by the due date.

Project Reports
Due: 5pm, Friday 6 August
Format: When printed from the wiki, equivalent to a 5-10 page PDF of clear, succinct text & diagrams

Project Reports are expected to include content addressing the following topics:

• Project objectives
• Investigation (about 3-5 pages)
  • algorithm
  • system design
  • SW design & performance
  • HW accelerator design & performance
  • results
• Discussion (about 1 page)
  • future work
• Project management (about 1 page)
  • project history
  • teamwork
  • reflection
• References (if required)

Please include the names of your group members on your report.

[top]