Project Report
Due: Jun 11 Sunday, 11:59pm | Canvas link (rubric & submission) |Â Points: 10
For the project report you will update and extend your project proposal based on the final implementation and evaluation of your projects. We created an updated Overleaf template for this document and we recommend that you make a copy of the document, transfer the different components you already completed from your proposal, update any parts that have changed, and finally add the new parts in the placeholders as instructed. The parts that need your attention for the report (versus proposal) are highlighted in yellow. In particular:
Update your system description based on anything that was different than what you proposed. If you did not get to implement certain parts (such as stretch goals), move those to the "Future work" section.
Similarly, if you did a different system or user evaluation than what you proposed, be sure to update those sections. Move the description of any evaluation you did not get a chance to do (but you think is important to do) to the "Future works" section.
Fill out the findings section based on your evaluation. Be sure to discuss your findings to explain low performance or negative feedback, and discuss potential improvements to address them.
Add a couple paragraphs or a bullet list in the lessons learned section. These should be things that were not obvious in the beginning and would be valuable to someone who decides to tackle the same problem as your project with a similar approach. It could be reiterating feedback that you got from your participants that challenged your assumptions or something that took more effort or required a different approach to implement than what you anticipated.
Fill out the future works section with anything you had planned but did not get to, as well as additional ideas you got along the way.
In addition to uploading your proposal as a PDF on Canvas (for ease of grading/feedback) be sure to post your report on your blog so you have everything in one place (this should be Post #21).
