L15: Agile UX: Use Studies, Stories and Senarios Flashcards

1
Q

Describe the difference between functional and non-functional requirements.

A

​The difference between functional and non-functional requirements is a functional requirements communicate how it functions but it doesn’t dictate how to create it from a design. A non-functional requirements are constraints solution must satisfy for example usability requirements, look-and-feel requirements, performance requirements, etc.

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

Which of the following is NOT true of constraints?

a. They are also referred to as non-functional requirements
b. They can affect all or many user stories
c. They should be treated like any other user story

A

c. They should be treated like any other user story

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

Requirements should be:

A

Necessary: What is the worst thing that could happen if this requirement were not included?
Verifiable: What are the criteria for acceptance?
Attainable: Must be affordable in cost, time & practicality
Clear: Express a single thought, be concise & simple

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

Software requirements should address?

A

Functionality: What is the software supposed to do?
External Interfaces: How does the software interact with people, the system’s hardware, other hardware, and other software?
Performance: What is the speed, availability, response time, recovery time of various software functions.
Attributes: What are the portability, correctness, maintainability security, etc. considerations?
Design constraints imposed on an implementation.

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

Which of the following use case level is most relevant to interaction design…?

a. Cloud level
b. Clam level
c. Sea level

A

c. Sea Level

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

What is a Use case?

A

Describes interaction between the system (or component) and something external. The external entity can be anything: An organization, a user or a peripheral device.

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

High Summary = ____ Level

A

Cloud Level

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

Summary = ____ level

A

Kite Level

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

User Goal = _____ Level

A

Sea

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

Sub-function = _____ Level

A

Fish

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

Too Low = ____ Level

A

Clam

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

What do scenarios need?

A

Clarity, brevity, and precision. Short paragraphs focused on a single subject

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

Which of the following is NOT true of the differences between sketches and wireframes?

a. Wireframes are seen by users as being more malleable than sketches
b. Sketches provide less detail than wireframes
c. Wireframes are retained, sketches discarded

A

a. Wireframes are seen by users as being more malleable than sketches

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

How do sketches help?

A

It helps fill the gap between abstract requirements and concrete solutions. It’s quick, malleable, tentative, visualization an important part of design.

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

Sketches or wireframes are usually included with _____ ____ as the specification of a user story (or use case)

A

design maps

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

Sketches or wireframes can be replaced by ___-_____ designs if pixel-perfect screens are needed by the development team.

A

high fidelity