Chapter 10B Flashcards
Heuristic Evaluation?
Developed by Jakob Nielsen
Helps find usability problems in a UI design
How many evaluators are used to examine UI? Why?
3-5 evaluators
Different evaluators will find different problems
Why 10 general principles for interaction are called heuristics?
Because they are broad rules of thumb and not specific usability guidelines
10 Original Heuristics?
- Simple and Natural Dialog
- Speak the users’ language
- Minimize users’ memory load
- Consistency
- Feedback
- Clearly marked exits
- Shortcuts
- Precise and constructive error messages
- Prevent errors
- Help and documentation
10 Latest Version Heuristics?
- Visibility of system status
- Match between system and the real world
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors.
- Help and documentation
Heuristics Evaluation Process?
Briefing session to tell experts what to do
Evaluation period of 1-2 hours
Debriefing session in which experts work together to prioritize problems
What is the Evaluation Period in the Evaluation Process?
Each experts works separately
Take one pass to get a feel for the product
- Inspect various elements
- Compare with list of usability principles
- Consider other principles/results that come to mind
Take a second pass to focus on specific features
Nielsen suggests that on average?
5 evaluators identify 75-80%
Why use many evaluators?
Every evaluator doesn’t find every problem
Good evaluators find both easy and hard ones
Biggest problems of Expert Evaluation?
Important problems may get missed
Many trivial problems are often identified
Experts have biases
H2-1 Visibility of System Status?
The system should always keep the users informed about what is going on, through appropriate feedback within a reasonable time
H2-2 Match Between System and The Real World?
The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order
H2-3 User Control and Freedom?
Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue
H2-4 Consistency and Standards?
Users should not have to wonder whether different words, situations, or actions mean the same thing
H2-5 Error Prevention?
Even better than good error messages is a careful design which prevents a problem from occurring in the first place.