Usability Evaluation/Testing

Question 1

What methods can we use for evaluating the quality of web apps?

Answer 1

1) Usability Testing

2) UX (user experience evaluation)

Question 2

Why do we do usability evaluations?

Answer 2

Don’t want to send wrong message to users
Don’t want to annoy end users
Can see when customers are confused
Want to make sure we are building the right thing - goat’s trail paths: ensure users are finding shit where they want
Cost changes are you get further

Question 3

What types of prototypes can we do usability evaluations with?

Answer 3

Low-fi or high-fi

Question 4

Explain the difference between low-fi and high-fi prototypes

Answer 4

Low-fi: paper, cheap, nasty

High-fi: high tech, partial to high completeness

Question 5

When displaying a prototype to users, why is it important to break it?

Answer 5

This allows stakeholders to see where you’re actually at with progress so that it doesn’t look more complete than it is

Question 6

What consideration objectives are there within usability testing?

Answer 6

Learnability
Efficiency
Task completion
Errors
Error recovery
Safety
Criteria (measurable)
Data/evidence

Question 7

What methods do we have for user evaluation?

Answer 7

Observation, questionnaires/surveys, interviews, lab

Question 8

List Nielson’s Heuristic Evaluation Criteria

Answer 8

1) Visible system status
2) Match between system and real world (metaphors - trash is where you throw junk)
3) User control and freedom
4) Consistency and standards
5) Error prevention
6) Recognition rather than recall
7) Flexibility and efficiency of use
8) Aesthetics and minimalist design
9) Recognise, diagnose and recover from errors
10) Help and documentation

Question 9

What is a cognitive walkthrough?

Answer 9

Usually done in pairs. One person facilitates and the other role plays.

Question 10

What is a desire path?

Answer 10

The natural path people or animals follow. Don’t try to create from scratch. Let form naturally.