CS 589: Human-Computer Interaction: Spring 2004
Final Project Details

Your final project should be structured as follows in the written report:

• Introduction: A brief description of what this product is intended to be about and to do (say, 1 paragraph). It would be useful to include information about the intended users and intended work. This is just to give future readers an intuition of the product, in case they aren't familiar with it.
• Section 1: Usability requirements
  • The usability requirements themselves (don't forget the fit criteria, etc.). Remember, this is about usability requirements, not about functionality requirements. For example, don't give me a list of functionality features here.
  • Documents referenced by the requirements, such as scenarios, use cases, task analyses...
• Section 2: Diagnoses
  • Problems that impact usability requirements.
  • Documentation of every problem listed (eg, cognitive walkthroughs, representation benchmarks, attention investment discussions, use cases, etc.)
• Section 3: Recommendations
  • Specific fixes to some of the problems in Section 2 above.
  • It is not expected that you'll have time to make recommendations for all the problems above, given that this course emphasized diagnosis.
  • You might be able to point to "similar" solutions to some problems that have a lot in common with the ones for which you have specific fixes.

---

Here are some guidelines for the in-class presentation.

Margaret M. Burnett, burnett@cs.orst.edu
Date of last update: June 1, 2004