Project Step 5:  Final Presentation and Paper

It is the end of the semester and time to present what you have accomplished. You should be proud of what you have done and we want you to tell us why. The final presentation (project step 7) and final implementation with written report and code (project step 8) are tightly related and simultaneous, so they are assigned here together.

Final Presentation:

While we have some things we want you to cover in your presentation, the actual form is up to you. This is a chance to be creative, such as performing your scenario as a skit with props, showing a video of your user's actual environment, re-creating your empirical user testing, etc. Risk-taking will be rewarded.

The ~20-minute presentation must include:

• a working demonstration of your project. This should be scenario-based, not just a listing of features.
• some key usability evaluation results (project step 4) and refinements made.
• your hypothesis about the solution to the Stegosaurus sample data resulting from your longitudinal usability test (step 4, part2).
• a summary of how well your project met your requirements analysis, and how much your requirements were refined throughout the usability process.

Since everyone in the audience has done more or less the same process during the semester, please avoid presentations that are of the form "first we did this, then we did that, and then we did this next thing".  Tell us only the most important things that shaped the final result. Reflections on mistakes that you would do differently are especially valuable.

Final presentations will occur during the last 2 weeks of class, as shown on the Calendar.  The best way to bring your materials is to have the running demo and presentation on a laptop that can be plugged into a VGA projector cable. 

Final Paper:

The final report is due on the last day of class, for all teams regardless of the schedule of the presentations.  The final report should include:

• An illustrated guide to your interface. This should include scenario(s) and claims analysis. Illustrate with screen shots, annotate with captions, arrows, boxes, etc., whatever graphical device that will make it clear how it is used.  Find a way to illustrate the interaction.
  • How did you respond to issues identified in the usability testing?
  • Indicate portions of your design that you were not able to implement fully, and a listing of what your future work would be if your were to continue the project.
• Your final solution scenarios (e.g. these are the scenarios that you carried throughout the scenario-based usability engineering process;  these should demonstrate how your final evaluated and refined design solution improves the situation in your problem scenarios).
  • How well does your project satisfy the problem scenarios of your requirements analysis, and how have your problem scenarios evolved through the usability process?
• Final claims analysis of your final design.
• Brief reflections on mistakes that you would do differently if you could do the project again.
• A detailed list of credits describing what each team member did throughout the entire project.

Submission Instructions: 

1. Submit a hardcopy of your Final Report in class.
2. Submit via Blackboard DropBox a ZIP file containing all relevant project files (source code, libraries, executable, etc.), including your Final Report AND your Evaluation Report (from project step 4).

Congratulations!  You are done.

FYI:  Your Portfolio: You should take great pride in your project and save it for your portfolio. The portfolio can be useful for job and graduate school applications, or for reminding yourself of the elements of HCI. The easiest way to create a record of this project is to start with the illustration of the system that you include in your final report. Imagine that you would be sending it to your family to explain what you did in this class; so tell the shortest and simplest story about who the users are and what it does. If your family can understand it, then it probably is just about right for your portfolio.