Milestone 6: Final Report
Due: 11:59pm on 12/21 (Tue)
25% toward your project grade
What do I do?
Now that you have deployed your system for a couple weeks, seen your crowd use the system, and collected useful data, it's time to wrap it all up!
You'll write a short report and make an engaging video that showcases your system.
Report
- Representative screenshots: Include a few most important screenshots that showcase the uniqueness of your application. Add callouts, annotations, or captions.
- Quality arguments (max. 500 words): Make convincing arguments for what makes your interface "great" and why the expected social interaction is successfully supported. Add comments from users, UI screenshots, etc. that could support your arguments. Depending on your interface, you may focus on different aspects: neat features, visual design, usability, novel UI components you designed, hardcore implementation, etc. This is your chance to convince us that what you created is a high quality user interface.
- Evaluation (max. 500 words): How did your deployment go? Report the number of users, results, analysis, etc. Use visual aids (e.g., charts, tables, graphs) to effectively communicate the results. NOTE: Please do not include results generated by your own team!!
- Discussion (max. 500 words): Connect the lessons from the project to important aspects of social computing covered in class: incentives for participation, quality control, supporting social interaction (communication, collaboration, networking...), privacy, ethics, etc. What worked well and what didn't? Why? What would you have done differently?
- Individual reflection (max. 500 words per person): Each member should write this part on their own, reflecting on their personal experience. Merge all members' mini-reports in the final report. Please answer the following questions:
- What part of the implementation did you contribute to? Be concrete and honest, please.
- What worked well and not in your team? How did you overcome any hurdle in teamwork? What lesson about teamwork did you learn that you might apply to your next team project?
- Through the team-based design project experience, what did you learn about social computing and web-based GUI implementation?
Video
Record a 2-minute video that captures the user context and the killer features of your UI. Be creative in how you plan, structure, and record the video! Check out last year's project gallery for inspiration. Revisit your storyboards, as they capture the rich usage context. You need to set the stage by starting with users and their problem. Avoid using slides and try to capture realistic context, and don't hesitate to "act". Do not show the UI from the beginning. You need to show parts of your final prototype to demonstrate how the user might perform the task using your system. Rather than describe all the features you implemented, focus on the flow of the task.
NOTE: Make sure to connect the user scenario and the solution. A common antipattern is to make the UI description too generic, not about solving the particular user problem captured earlier in the video.
NOTE: Due to the pandemic, we recognize it'd be near impossible to record a video of multiple humans interacting. In grading the videos, we will not focus on interaction between characters. Feel free to use animated characters, split screens with multiple characters captured separately, etc. to creatively communicate the idea behind your interface. We will not focus on the production quality regarding this aspect of your video.
Grading
Here's how your report will be graded.
Part 1: Report (12% toward your project grade)
-
Quality Arguments (25%)
- Convincing arguments with supporting evidence?
- Is it overall a high quality interface? We will look at a variety of aspects such as completeness, novelty, feasibility, UI-level contribution, etc.
- 500 words or less?
-
Evaluation (25%)
- The evaluation is complete and shows if and how the system worked as expected?
- Results are reported and communicated clearly?
- 500 words or less?
-
Discussion (25%)
- Discussion touches upon important aspects of social interaction supported by the team's application?
- Discussion has enough depth and insight?
- 500 words or less?
-
Individual Reflections (25%) - graded individually
- Individual contribution clearly specified?
- Teamwork discussion includes both the good and the bad?
- Teamwork discussion has enough depth and insight?
- Design process discussion has enough depth and insight?
- 500 words or less?
Part 2: Video (13% toward your project grade)
- 2 minutes or under?
- Overall organization and flow of the story?
- Quality and variety of shots and rhythm?
- User needs well captured?
- UI introduced convincingly but not as dry list of features?
- Engaging and creative?
Deliverables
- Report: One report per team. Your report should be submitted as a zip file. The main report should be written in Markdown (please use the .md extension). Also include your original video MP4 file in the zip file as well. Submit via KLMS.
- Video: (guidelines adopted from CHI 2017 Video Showcase, which also has links to many inspiring videos)
- Encoded as an MP4 using the H.264 codec. No exceptions!
- You'll upload your video file on YouTube. Include the URL of your posted video in your final report.
- All spoken dialog must be closed captioned (subtitled) to improve accessibility.
- Resolution of at least 1280px x 720px.
- The 16:9 aspect ratio is recommended.
Extra Credit #1: Cool Video
Up to +10% on the final milestone
We'll reward 1-2 teams with most engaging videos. We'll announce the winner(s) and explain why they deserve the "Cool Video" title.
Extra Credit #2: Best Crowdsourcer
Up to +10% on the final milestone
Teams that successfully engage active users deserve some credit! We'll reward 1-2 teams that most successfully showed the power of the crowd. This does not just mean the most number of users, but includes the overall participation, quality of data, and your analysis of the data. We'll announce the winner(s) and explain why they deserve the "Best Crowdsourcer" title.