User Heuristics Flashcards

1
Q

What is the principle of “Visibility of system status” ?

A

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

(Ex: Caps Lock “on”, “off” )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the principle of “Match between system and the real world” ?

A

The system should speak the user’s 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.

(Ex: Red button for Exit )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the principle of “User control and freedom” ?

A

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. Support undo and redo.

(Ex : press title Button to go back to main menu )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the principle of “Consistency and standards” ?

A

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

(Ex : “Ctrl + C” should always copy )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the principle of “Error prevention” ?

A

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

(Ex : Disabling option to BOLD text when no text is selected )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the principle of “Recognition rather than recall “ ?

A

Minimize the user’s memory load by making objects, actions, and options visible. The 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.

(Ex : “Predictive text”, or “recent searches” )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the principle of “Flexibility and efficiency of use” ?

A

Accelerators – unseen by the novice user – may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

(Ex : Macros like “Ctrl + S = Save” )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the principle of “Aesthetics 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.

(Ex : PowerPoint Menu/Tool Box = Bad )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the principle of “Help users recognize, diagnose, and recover from errors” ?

A

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

(Ex : “File may not exist, or it may already be in use” )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the principle of “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. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large. The following interactive illustrates a situation you might have run into before!

(Ex : “Common asked questions” Help Type Buttons )

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is this principle?

“The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.”

(Ex: Caps Lock “on”, “off” )

A

Visibility of system status

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is this principle?

“The system should speak the user’s 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.”

(Ex: Red button for Exit )

A

Match between system and real world

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What principle is this?

“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. Support undo and redo.”

(Ex : “Are you sure?” Button )

A

User control and freedom

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What principle is this?

“Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.”

(Ex : “Ctrl + C” should always copy )

A

Consistency and standards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What principle is this?

“Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.”

(Ex : Disabling option to BOLD text when no text is selected )

A

Error prevention

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What principle is this?

“Minimize the user’s memory load by making objects, actions, and options visible. The 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.”

(Ex : “Predictive text”, or “recent searches” )

A

Recognition rather than recall

17
Q

What principle is this?

“Accelerators – unseen by the novice user – may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.”

(Ex : Macros like “Ctrl + S = Save” )

A

Flexibility and efficiency of use

18
Q

What principle is this?

“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.”

(Ex : PowerPoint Menu/Tool Box = Bad )

A

Aesthetics and minimalist design

19
Q

What principle is this?

“Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.”

(Ex : “File may not exist, or it may already be in use” )

A

Help users recognize, diagnose, and recover from errors

20
Q

What principle is this?

“Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large. The following interactive illustrates a situation you might have run into before!”

(Ex : “Common asked questions” Help Type Buttons )

A

Help and Documentation

21
Q

what is Internal consistency?

A

Consistent elements within that specific system.

(Ex : web pages being laid out the same within websites)

22
Q

what is the principle of external consistency?

A

Consistent elements within unrelated general applications

(Ex : Outlook and Gmail)

23
Q

what is the principle of Accessibility?

A

Make it diverse for the use of everyone

(Ex : making text bold for people with eye problems)