LU 5 EVALUATION Flashcards

1
Q

What is evaluation?

A

Evaluation is about understanding if your newly designed interface is usable or not.

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

Key step in evaluation (3)

A

First, understand why you evaluate? Evaluation can be for feedback or proof.

Second, think about what you want to observe. Decide between observing behavior or attitude.

Third, think about the type of data you want. Determine if you need to understand “why” something happens or “how much” it happens

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

Why do we evaluate? (2)

A

Gather feedbacks with the goal of improving the product.

Prove that the product is usable or is not, usable

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

What are you evaluating? (2)

A

Attitude

a person’s feelings or opinions, influenced by culture and experiences.

Behavior

a person’s actions in a situation, observable and measurable.

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

What is the purpose of qualitative metrics?

A

aim to answer the “why” question about user behavior and preferences.

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

What types of data are used in qualitative metrics?

A

Qualitative metrics use observations, symbols, and words to understand user experiences and perceptions.

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

How do you approach qualitative metrics?

A

Qualitative metrics involve observing user interactions and interpreting their meaning within the context of the study.

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

How do you analyze qualitative metrics?

A

Qualitative metrics are analyzed by grouping common data themes and patterns, focusing on non-statistical analysis methods.

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

What is the purpose of quantitative metrics?

A

Quantitative metrics aim to answer “how many” or “how much” in user interactions and behaviors.

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

What types of data are used in quantitative metrics?

A

Quantitative metrics use numerical data and statistical results to measure user activities and engagement.

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

How do you approach quantitative metrics?

A

Quantitative metrics involve measuring and testing user behaviors objectively to gather numerical data.

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

How do you analyze quantitative metrics?

A

Quantitative metrics are analyzed using statistical methods to identify trends, correlations, and significant findings in user data.

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

What are inspection techniques in usability evaluation?

A

methodologies where evaluation is conducted by experts rather than involving participants or users.

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

What are the pros of using inspection techniques?

A

Cheaper and faster compared to user studies.

Experts bring specialized knowledge and experience.

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

What are the cons of using inspection techniques?

A

Experts may overlook issues that real users might identify.

There can be a bias towards more common errors, potentially missing less frequent but critical issues.

Different inspection techniques may have varying definitions of usability.

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

What is GOMES in usability evaluation?

A

GOMES stands for Goals, Operations, Methods, and Selection rules. It’s an inspection methodology where experts break down tasks into physical actions, like pressing keys or moving a mouse, and calculate how long these actions would take an average person.

17
Q

How does GOMES categorize actions?

A

Actions in GOMES are categorized into general action classes based on the Keystroke-Level Model, which predicts the time it takes to perform various actions.

18
Q

Why is GOMES used in usability evaluation?

A

GOMES helps evaluate the efficiency of user interactions by analyzing the time required to perform specific tasks, providing insights into usability and potential improvements.

19
Q

What is Heuristic Evaluation?

A

Heuristic Evaluation involves experts evaluating an interface using a set of established criteria (heuristics), such as Nielsen’s 10 heuristics.

20
Q

What are the pros of Heuristic Evaluation?

A

Can be conducted by a single person.

-No ethical or recording issues.

-Identifies numerous potentially costly problems at minimal expense.

21
Q

What are the cons of Heuristic Evaluation?

A

Experts may overlook issues that end users would identify.

22
Q

What is Cognitive Walkthrough?

A

Cognitive Walkthrough is a method to evaluate if the sequence of cues and prompts in a system supports how people naturally process tasks and anticipate next steps.

23
Q

When to use Cognitive Walkthrough?

A

Initial evaluation of a system.

Low budget evaluations.

Systems that are walk-up-and-use or first-time use scenarios.

When access to HCI (Human-Computer Interaction) experts is available.

When not to use Cognitive Walkthrough?

Formal evaluation of your own system where you are the evaluator.

24
Q

What is the Cognitive Walkthrough process?

A

The Cognitive Walkthrough is a method used to evaluate whether the sequence of cues and prompts in a system supports users’ task processing and anticipation of next steps.

25
Q

When should you use Cognitive Walkthrough?

A

It is ideal for initial evaluations of systems, especially in low-budget scenarios, walk-up-and-use systems, or first-time user interactions, with access to HCI (Human-Computer Interaction) experts.

26
Q

When should you avoid using Cognitive Walkthrough?

A

Avoid using it for formal evaluations of your own system where you act as the evaluator.

27
Q

What are the key steps in the Cognitive Walkthrough process?

A

Briefing Session: Introduce experts to tasks and objectives, provide necessary materials like personas and task descriptions.

Evaluation Period (1-2 hours): Experts work individually, taking two passes to familiarize with the product and focus on specific features. They answer predefined questions for each correct step and document issues and good aspects.

Debrief Session: Experts collaborate to prioritize identified problems and discuss findings.

Reporting: Compile a detailed report for the client, outlining identified problems and their severity, along with positive observations.

28
Q

What are the four questions used in Cognitive Walkthrough?

A

Will users want to produce whatever effect the action has?

Will users see the control (button, menu, label, etc.) for the action?

Once users find the control, will they recognize that it will produce the effect they want?

After the action is taken, will users understand the feedback they receive and confidently proceed to the next action?

29
Q

What is a Usability Aspect Report (UAR)?

A

A Usability Aspect Report (UAR) is a structured document used to record findings from a usability evaluation, focusing on both positive and negative aspects of an interface.

30
Q

How does a Usability Aspect Report (UAR) differ from a bug report?

A

While a bug report typically focuses on technical issues and errors, a UAR specifically addresses usability issues identified through evaluations like Cognitive Walkthroughs. It documents observations related to how well the interface supports user tasks and interactions.

31
Q

What does a Usability Aspect Report (UAR) include?

A

It includes:

Answers to the 4-Question questionnaire used in Cognitive Walkthroughs.

Descriptions of usability issues, categorized by severity.

Positive observations highlighting effective interface elements.

32
Q

Why is a Usability Aspect Report (UAR) important?

A

It provides a clear record of usability strengths and weaknesses, guiding design improvements and ensuring that user-centered considerations are addressed in interface development.