CH11HCI Flashcards

(100 cards)

1
Q

What is a requirement?

A

A statement about an intended product that specifies what it should do or how it will perform.

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

What are the three guiding questions in requirements activity?

A

What, how, and why?

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

Why is exploring the problem space important?

A

To establish the design challenge to be addressed.

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

How can requirements be captured?

A

In prototypes, structured notations, criteria, or various representations.

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

What is the most common stage for miscommunication?

A

Requirements activity.

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

What is the structure of a user story?

A

As a <role>, I want <behavior>, so that <benefit>.</benefit></behavior></role>

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

Give an example of a user story.

A

As a traveler, I want to save my favorite airline so I can collect air miles.

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

What are the two goals of defining requirements?

A

Clarify intentions and avoid miscommunication.

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

What is the Volere shell?

A

A guideline and template set for documenting requirements.

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

Why use different representations for requirements?

A

Different formats highlight different aspects of the product.

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

What are functional requirements?

A

Define what the system should do.

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

What are non-functional requirements?

A

Describe how the system should perform or behave.

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

What are data requirements?

A

Define the type and characteristics of data to be stored.

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

What is an environment requirement?

A

Describes the context in which a product operates.

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

What are physical environment requirements?

A

Include factors like dust, noise, heat, and light.

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

What are social environment requirements?

A

Concern collaboration, data sharing, and privacy.

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

What are technical requirements?

A

Define compatible technologies or platforms.

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

What are support environment requirements?

A

Describe user support and training availability.

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

What is a user profile?

A

A collection of characteristics for a typical user.

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

Name types of system users.

A

Novice, expert, frequent, and casual users.

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

What are usability goals?

A

Goals to ensure the system is effective, efficient, and satisfying.

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

What are user experience goals?

A

Focus on emotional and psychological impact on users.

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

Why is usable security important?

A

Poor usability can lead to security being bypassed.

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

Name a feature that can improve usable security.

A

Showing password strength using sound or visuals.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What is a challenge of usable security?
Balancing usability with robust protection.
26
What can poor security usability cause?
Users to circumvent security measures.
27
What is 'usable security'?
Security mechanisms that don't negatively impact user experience.
28
What is a user characteristic requirement?
Describes educational, skill, or personal traits of users.
29
How does user type affect interaction design?
Novices need guidance, experts need power, frequent users want shortcuts.
30
How are usability and user experience goals measured?
Through user studies and performance metrics.
31
What are shortcuts useful for?
Frequent users.
32
What kind of UI is best for novice users?
Constrained and guided interfaces.
33
What kind of UI is ideal for expert users?
Flexible and powerful interfaces.
34
What does 'support requirement' mean?
Availability of help, training, and communication infrastructure.
35
Why define user experience goals?
To ensure the product is engaging and emotionally satisfying.
36
What are the three main data gathering techniques?
Interviews, observations, questionnaires.
37
What is direct observation?
Observing users directly in their environment.
38
What is indirect observation?
Reviewing logs, videos, or other records.
39
What's a benefit of studying documentation?
It reveals existing procedures and rules.
40
Why not rely solely on documentation?
It doesn’t capture user experience or context.
41
What is a benefit of researching similar products?
It prompts new requirement ideas.
42
Name a benefit of using diaries in data gathering.
Long-term tracking of user behavior.
43
What is a focus group?
A moderated group discussion to gather diverse insights.
44
What is a probe?
A tool or activity to elicit user thoughts and behaviors.
45
What is a design probe?
A prompt to encourage contextual user feedback.
46
What is a cultural probe?
Uses artifacts (e.g., maps, diaries) to explore user life.
47
What is a technology probe?
A prototype placed in real settings to learn from use.
48
What is a provocative probe?
Designed to challenge assumptions and provoke reactions.
49
What does combining techniques do?
Provides richer and more accurate data.
50
Give an example of combined techniques.
Interview + think aloud + questionnaire + prototype evaluation.
51
What's a benefit of focus groups?
Insight into group preferences and social dynamics.
52
Why use design probes?
They reveal insights in the user’s natural context.
53
What's an example of a cultural probe activity?
Taking photos of daily routines.
54
What is the goal of using probes?
To understand stakeholders' experiences and needs.
55
Why combine interviews and diaries?
To explore usage over time and in depth.
56
What is a persona?
A fictional character based on user research.
57
What is the purpose of personas?
Help make design decisions and keep users in focus.
58
What should a persona include?
Name, goals, background, characteristics.
59
Should personas be idealized?
No, they should be realistic.
60
What is a scenario?
A narrative story describing user interactions.
61
How do scenarios support design?
They explore context, needs, and tasks.
62
What are scenarios based on?
Real user activities and imagined usage.
63
What media can scenarios use?
Text, video, audio, animation.
64
What is a use of animation scenarios?
Show dynamic interaction sequences.
65
What is design fiction?
Storytelling about future technology to explore ideas.
66
How is design fiction different from scenarios?
It imagines future visions without current constraints.
67
What is the goal of scenarios?
To describe tasks in context.
68
What is a primary persona?
The main persona the product is designed for.
69
How many personas should be developed?
A small, focused set.
70
What is the difference between personas and user profiles?
Personas are fictional; profiles are general characteristics.
71
Why are personas useful in the design process?
They maintain user-centered focus.
72
What is an example of a scenario in the lecture?
Thomson family planning a sailing trip.
73
Why include children in scenarios?
To reflect all potential user types.
74
What is an 'in-the-wild' context?
Real-world environment where a product is used.
75
What is one benefit of design fiction?
It enables ethical exploration.
76
What is a use case?
A step-by-step description of a user interaction.
77
What do use cases focus on?
Functional requirements.
78
What are the two styles of use cases?
Essential and detailed (with alternatives).
79
What is an essential use case?
Abstract, focuses on user intentions and system responsibilities.
80
What is a detailed use case?
Includes normal and alternative paths.
81
What is the purpose of use cases?
To define expected interactions.
82
What are user intentions?
Goals the user wants to accomplish.
83
What are system responsibilities?
What the system does in response to user actions.
84
Give an example of a user action in a use case.
User enters destination country.
85
What happens if the country is invalid?
Error message, return to step 1.
86
What happens if the nationality is invalid?
Error message, return to step 4.
87
What if no visa info is found?
Provide a suitable message and restart.
88
What is captured in use case alternatives?
Exceptions and recovery steps.
89
What is the structure of a use case table?
User intention vs system responsibility.
90
What product example is used in use cases?
Travel organizer app.
91
Why define requirements early?
To avoid miscommunication and guide design.
92
What should be captured together with requirements?
Usability and user experience goals.
93
What type of requirement includes user skills?
User characteristics requirements.
94
Why study similar products?
To spark ideas and improve your own.
95
What is one benefit of combining data gathering methods?
Increased depth and accuracy.
96
What does 'context of use' mean?
The environment in which a product is used.
97
Why use personas and scenarios together?
They support each other throughout design.
98
What is the goal of the design process?
To create usable, desirable products for real users.
99
How do requirements support stakeholders?
By making sure their needs are addressed.
100
What is the final outcome of requirement gathering?
A clear, detailed understanding of what the product must do and how.