The final projects will be a Python program implemented in your groups. You will take the idea you have created in your project proposal and realize it into a functioning product.
The Final Project has two components:
While you may use online resources to help you with implementation details it is still expected that the project will be your own work and not simply a tutorial implementation or an “asset flip” (taking an existing working project, swapping out the assets to make it appear different).
Final projects will be due on presentation days:
Everyone will be expected to be in attendance and will be asked to complete a peer evaluation of the work and presentation. These will be submitted at the end of the presentations.
The project will be worked on in your groups.
Since the project is very open-ended, it will be evaluated on:
When it comes to features, focus on quality over quantity. No one will notice if extra features are not present, but they will notice things do not work or have odd behavior.
You are not required to create any slides for your presentation, demonstrating and discussing your application is sufficient. Your presentation must:
All project must be submitted to Moodle before 8am on the scheduled exam day. The entire project must be contained within a single zip file (I recommend zipping the folder that contains the project). This should include all code files, images, or other assets.
It is wise to have your application implementation “frozen” before your presentation to ensure that it works on presentation day. Last minute changes rarely go well in project demos.
While this is a team project, if it becomes apparent that member contributions are not equitable, gradig adjustments will be made on an individual basis.