1
Q
Heuristics: Understanding
A
- Consistency
- Use Familiar Metaphors and Language
- Clean and Functional Design
2
Q
Heuristics: Action (What users can do)
A
- Freedom
- Flexibility
- Recognition over Recall
3
Q
Heuristics: Feedback
A
- Show Status
- Prevent Error
- Support Error Recovery
- Provide Help
4
Q
Visibility of system status
A
- Always keep users informed about what is going on.
- Provide appropriate feedback within reasonable time.
5
Q
Match between system and the real world
A
- 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.
6
Q
User control and freedom
A
- Users often choose system functions by mistake.
- Provide a clearly marked “out” to leave an unwanted state without having to go through an extended dialogue.
- Support undo and redo.
7
Q
Consistency and standards
A
- Users should not have to wonder whether different words, situations, or actions mean the same thing.
- Follow platform conventions.
8
Q
Error prevention
A
Even better than good error messages is a careful design which prevents a problem from occurring in the first place.
9
Q
Recognition rather than recall
A
- Make objects, actions, and options visible.
- User should not have to remember information from one part of the dialogue to another.
- Instructions for use of the system should be visible or easily retrievable whenever appropriate.
10
Q
Flexibility and efficiency of use
A
- Accelerators – unseen by the novice user – may often speed up the interaction for the expert user so that the system can cater to both inexperienced and experienced users.
- Allow users to tailor frequent actions.
11
Q
Aesthetic and minimalist design
A
- Dialogues should not contain information which is irrelevant or rarely needed.
- Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
12
Q
Help users recognize, diagnose, and recover from errors
A
- Expressed in plain language (no codes)
- Precisely indicate the problem
- Constructively suggest a solution.
13
Q
Help and documentation
A
- Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation.
- Help information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.
