Back to
Schedule
Design Notebook Entry for E2
In the design notebook, include the following information in your writeup. For
heuristic evaluation, include a screenshot of the completed evaluation worksheet from each evaluator, and describe at least 2-3 things you will improve in the final prototype based on what you learned from the heuristic evaluation. For
cognitive walkthrough, (1) record success and failure stories observed during the evaluation, (2) summarize the design suggestions from the evaluators, (3) describe at least 2-3 things you will improve in the final prototype based on what you learned.
P12: Create Final Products and Prepare for Final Presentation
Final Prototype (PO2a) and Demo Video (PO2b)
After the hi-fi prototype evaluation, spend some time improving/refining your high-fidelity prototype based on the feedback from the heuristic evaluation and cognitive walkthrough. Ensure the final prototype is what you believe would help solve your target problem (see
Deliverable PO2a). Your prototype will be graded using a
rubric based on "fit to problem", "usability" and "visual design". After completing the updates, create a 3 min (max) video (
Deliverable PO2b) demonstrating your final product (i.e., high-fi prototype). Your prototype will be graded using a
rubric based on "motivation" (i.e., having a compelling statement of the problem), "prototype demo" (i.e., having clear illustration of the key features) and "delivery". Throughout the video, you should have supporting caption/text to explain what is being shown. You can also describe your design process; for example, you can show your paper prototype briefly to illustrate the progression of the design. To see some examples of hi-fi prototype demo videos, visit the
CS449 Spring 2019 website (click on "Project").
As part of P12, include a link to the your draft interactive prototype (i.e., one that people can play with as if it is a real app) and a link to the your draft demo video under Week 13.
Final Presentation (PO2c)
The final presentation will be held in DC Foyer on
Monday December 2, 10am-11:20am just outside of DC 1350, where you will display a poster, give a 10 minute presentation, and show a demo of your high-fidelity prototype.
Please arrive at 9:45am at the latest to find your poster board and set up your poster.
The poster must be smaller than 5 feet (width) by 4 feet (height), and must include a title, your team name, and sections that describe the motivation behind your project and the entire design process you went through to create your app, with supporting photos, screenshots and illustrations. Make sure that the text is readable even for people who are standing slightly far away. Leverage the poster to help you give a compelling presentation. For the final presentation, designate two people from your team to take turn presenting. The presentation should be 10 minutes long, following the format as outlined in
Deliverable PO2c.
Each student (including presenters) is required to visit a number of posters presentations and provide their feedback and ratings. The presentation will be graded by the instructor, TA (not from your lab), guest judges and fellow students. The total score (out of 50) is based on the quality of the poster (20 points), quality of the presentation (20 points) and attendance to other team's posters (10 points).
As part of P12, include a link to your draft poster (PDF) under Week 13.
Design Porfolio (PO2d)
Create an interactive website or a blog post that documents your entire design process. This is simply a polished and concise version of the design notebook. The design portfolio should be self-contained and of an appropriate content length, and include carefully chosen visuals (e.g., images of the artifacts from your design activities) to illustrate your points and your process. You can embed the demo video into the design portfolio as well. See
Deliverable PO2d for more details on the expected structure/content of the design portfolio. For inspiration of what design portfolio can look like, see these examples (
Ex1,
Ex2,
Ex3).
As part of P12, include a link to your draft design portfolio under Week 13.
R2: CS649 Research Proposal
This final proposal report is 6 pages. Make sure that the feedback on the proposal draft has been adequately addressed in your final report. See
Deliverable R2 for more details on the expected structure/content of the research proposal.
Complete Course Perception and Team Evaluation Survey
Course Perception Survey: Each student should complete the
course perception survey. In the comments, please leave constructive and actionable feedback in the "I like...", "I wish...", "What if..." format.
Team Evaluation Survey: Each student should complete the
team evaluation survey to rate the relative contribution of each team member in your team, including yourself. This information will be taken into account in the final grading.