User Requirements Gathering Flashcards

(21 cards)

1
Q

What is the goal of requirements gathering?

A

To develop accurate system, user, and usability requirements that ensure a usable system.

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

Why is defining requirements considered difficult?

A

It involves deciding exactly what to build and interfaces with users, machines, and systems.

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

What is ISO 13407?

A

A standard for applying human-centred design and evaluation, supporting existing lifecycles.

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

Why is early design usually high-level?

A

Because it’s too soon to finalize details; mockups are used until more information is gathered.

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

Why might users struggle to articulate their needs?

A

They may not know what’s possible or struggle to express goals and interests.

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

Why gather requirements?

A

Because needs aren’t always obvious, can change during development, and often cause stakeholder conflicts.

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

What should user and organisational requirements specify?

A

User range, design goals, requirement priorities, test criteria, and documentation.

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

What are functional requirements?

A

They define what a system should do (e.g., features and tasks).

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

What are non-functional requirements?

A

They define how a system should behave or perform, like usability or performance.

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

What are usability requirements?

A

Measurable qualities like efficiency, intuitiveness, and low cognitive load.

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

How are user requirements defined?

A

By identifying who will use the system, where, how, and what their physical/cognitive needs are.

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

What makes a ‘right’ requirement?

A

Realistic, relevant, clearly defined, timely, and enough detail but not excessive.

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

What is a persona?

A

A fictional, data-informed user profile that guides design decisions.

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

What are scenarios?

A

Stories describing how a persona would use a system in a specific context.

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

What is a user story?

A

A short statement describing a user’s goal, often structured as ‘As a [user], I want [action], so that [value].’

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

How do personas help design?

A

They help teams empathise with users, focus requirements, and inform design decisions.

17
Q

What are the benefits of personas?

A

They provide user insight, guide design, and serve as constant reminders of user needs.

18
Q

What are limitations of personas?

A

They can be too abstract, impersonal, or misleading if poorly constructed.

19
Q

What is the minimum data needed for a persona?

A

Picture, name, age, location, occupation, and a realistic backstory.

20
Q

What are guerilla personas?

A

Quickly created personas with limited resources, used when time and budget are tight.

21
Q

What are empathy maps used for?

A

To visualise user pains, goals, and behaviours, helping to humanise data.