Homework 5: Heuristic Evaluation of Each Other's Implementations
Assigned: Mon, June 18, 2012; Due: Mon, June 25, 2012 (note: no late turn-ins for HW5!)
Each person will evaluate the user interfaces of two other people in the class. After you turn in your system for Homework 4, the TA will e-mail you the two systems you are to evaluate.
See the assignment of systems to people here. (Note -- you need to be on a CMU machine (or VPN) to access this file. It is also on Blackboard.)
You will be getting two (2) systems, as listed. You should write a heuristic evaluation of the site using Neilsen's Ten Usability Heuristics. (There are lots of different lists of heuristics, but for this assignment, you must use only the ones that Nielsen lists). Although two people are assigned to evaluate each project. you should do the evaluation individually.
Perform a heuristic evaluation of the systems you have been assigned, and write a report using the HE Report template. See the template here: http://www.cs.cmu.edu/~bam/uicourse/HE_Report_template.doc (see also the partial example in doc format).
- Your report can include both problems and things done well, but it is better to list problems.
- You should include pictures of the system that illustrate each of your points (either directly in the "Prototype Screen" column as in the example, or below the table with a hyperlink reference, as in the template). You can use screen captures to do this (on a PC, the print screen key puts the screen on the clipboard; on a Mac, command-shift-4 let's you pick a selection on the screen to send to a file, command-control-shift-4 puts it on the clipboard).
- Each point should be annotated with the particular Name of Heuristic that is being violated or being followed (put this in the "Name of Heuristic" slot). If violated, you might suggest a fix in the Way(s) to rectify column.
- For each system you are assigned, you must list at least 8 (eight) points that illustrate at least 4 (four) different guidelines. I am looking for insight, subtlety and depth. Thus, saying "the system doesn't have good color choices because it doesn't use color" is pretty trivial and won't count for much. Also, since this is a prototype, saying that functions aren't implemented also doesn't count. For example, prototypes generally won't have "documentation and help" so it is not useful to point that out.
- Be sure each row lists which heuristic is violated or upheld, and why, and what you recommend be done about it. Be sure it is clear in your description whether you are saying the interface violates the heuristic or does it well.
You will be graded for this homework on how well you evaluate the prototype, the quality of the feedback you are providing, how many problems and good things you found, and the extent to which you assign them to the correct heuristics.
In homework 6, you will be trying to fix the problems that other people identified with your system, and your grade will be based in part on your response to your classmate's Heuristic Analysis of your prototype (what you did based on what they found), so it is important to you to make sure your classmate gets a chance to evaluate your prototype.
- The deliverable for this assignment are two HE Report templates filled out, one for each of the systems you evaluated. This will be at least 2 (systems) x 8 (items) = 16 items.
- Please keep the documents as two files, so that we can email them to the people whose projects you evaluated. Please name your two files as follows: HE-Report-of-otherPersonsName-from-yourname. For example, if one of the systems I was evaluating was by Stephanie Chow, my file about that evaluation would be named: HE-Report-of-Chow-from-Myers.docx.
- Collect all your files together into one zip file, and upload the one zip file named HCI-HW5-lastname-firstname.pdf to Blackboard, as described in the submitting instructions.