|Teaching home - Course home - List of Topics - Readings - Assignments - Resources|
||Electronically - eCollege|
|Objective||Conduct a heuristic evaluation of the prototype, and document your work|
Perform usability inspection by using heuristic evaluation.
Each of you will serve as a usability expert and be randomly matched with one (or two) prototypes created by your classmates from a different group. You must have your prototype ready for that week. You will perform a heuristic evaluation of the system assigned. A heuristic evaluation is an informal expert evaluation technique that relies on a series of ‘heuristics’ (rules of thumb). The intent is to determine if the interface conforms to these principles. These heuristics are based on a modified version of Nielsen’s original set as well as on heuristics created for mobile interfaces (Bertini et al, 2006). The intent is to identify as many problems as possible in allotted time.
I suggest that you take 30-45 minutes to assess each prototype. You will then write an assessment and a recommendation for the potential client group. For each problem indicate: a) which usability guideline was violated, i.e., what is the problem? and where is it? b) why is it a problem? c) a severity rating for the violation, and c) a recommended solution. You may not find problems for all heuristics and you may find many problems for a single heuristic. If the same problem exists in many locations, do not duplicate, but communicate that information. In the case of many problems per heuristic, please number each and use the same number in the corresponding severity cell, so that the reader can easily match problem with solution.
Your short report from the heuristic evaluation should include:
Review class notes, the tutorial and the readings about heuristic evaluation; in particular, I'd recommend a short section (#4.3) with a heuristic evaluation example in : http://hcibib.org/tcuid/chap-4.html
Assessment criteria : you will be getting comments and an overall indiation how well you did
Due dates are posted on the Assignments page
© 2005-forever Jacek Gwizdka - Page last modified: