Module 1: Why Evaluate UX Experience? Flashcards

1
Q

Utility

A

The extent to which a user perceives a technology to improve their ability to perform a task

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

Effectiveness

A

The precision, ease and level to which users achieve a specific goal. How users expect the technology to behave

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

Efficiency

A

The quickness with which users’ goals can be accomplished accurately and completely

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

Satisfaction

A

the absence of discomfort and frustration towards a product

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

Learnability

A

the extent to which a digital product/service allows users to quickly become familiar w/ them (intuitivity)

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

Accessibility

A

the extent to which X can be used by people in a population w/broad characteristics

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

ISO 9241-210 definition of user experience

A

“a person’s perceptions and responses resulting from the use and/or intended use of a product, system, or service”

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

Perception

A

is the conscious experience , subject to cognitive bias (able to explain and verbalize)

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

Retrospective bias

A

difficult to recall, the perception might be tainted from the 1st impression’s last moment

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

Response

A

automatic and unconcious

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

Expert evaluation/inspection based

A

based on previously determined guidelines (Jabok Neilson’s 10 general principles for interaction design)

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

Jakob Neilson’s 10 general principles for interaction design

A
  1. Visibility of system status
  2. Match between system status
  3. User control & freedom
  4. Consistency and standards
  5. Error prevention
  6. Recognition rather than recall
  7. Flexibility and efficiency of use
  8. Aesthetic and minimal
  9. Help users recognize, diagnose, & recover from errors
  10. Help and documentation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

what are the 3 types of evaluation?

A

expert evaluation (heuristics), user-based and conformity assessments

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

difference between formative and summative evaluation?

A

formative: done during the development phase of the product
(aims for recommendations + improvement)
(100x less expensive)

summative: done when design is near completion
(aims to evaluate quality and met of requirements)

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

Type 1 Error

A

Concluding that “There are No errors!” when in fact, there were

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

Type 2 Error

A

“There are errors!” when in fact there were not

17
Q

System

A

combination of interacting elements organized to achieve one or more stated purposes

18
Q

User interfacee

A

all the components of an interactive system

19
Q

Prototype

A

representation of all or part of an interactive system

20
Q

User

A

person interacting w/ a system/product/service

21
Q

Purpose

A

expected result

22
Q

context of use

A

refers to users, tasks equipment, etc in which a product is used

23
Q

Task

A

activity required to achieve a goal

24
Q

Action

A

user behaviour that the system accepts as a request for a particular operation

25
Q

Objects of the task

A

key units of info/data which users interact to perform their tasks

26
Q

user interface elements

A

basic components of a user interface presented to the user by the interactive system

27
Q

dialogue

A

interaction between user and system

28
Q

need

A

prerequisite identified as a necessity for a user

29
Q

requirement

A

condition/capability that must be met by the system