Section 2 Flashcards

1
Q

What are the principles of User-Centered Design?

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

What is the User-Centered Design process and why use it?

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

What are the goals for each stage of the User-Centered Design Process?

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

What are good investigation Questions

A

Identify users
Identify stakeholders
What are the requirements? How do they do it now?
How long does it take?
What do they want?
What do they need?
What have they already tried? Is there another solution?

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

What is the stage Ideation about?

A

“To get good ideas… Get lots of ideas”

One of the worst things: go with the first one you have

You can always come back to it later

Volume matters the most

Increase chance of success by considering a huge volume of ideas in a systematic way

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

What is a prototype?

A

It’s cheap and fast

Easier for users to react to concrete things rather than abstract concepts

Prototyping brings subtleties and nuances to light

Working against some technical

constraints is good

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

What are the prototype fundamentals?

A

Build it fast

Concentrate on unknowns

Don’t be attached to themeasy to throw away

Build multiple concurrentlyeasier to compare pros/cons

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

Why use the Evaluation stage?

A

What is wrong with automated software testing?

  • Automated processes can find bugs, but not usability issues

Evaluation gives you a way to move forwardWhat needs to be fixed, added, removed?

  • Answers to two questions:Did we build the right thing? Did we build the thing right?

Evaluation Drives Iteration

Problem: usefulness/appropriateness

Return to investigation phase

Problem: users don’t understand

Return to ideation phase

Problem: user performance

Return to prototyping phase

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

What are the steps required to go from functional prototype to release candidate?

A

These are steps required to go from functional

prototype to release candidate:

  • Software architecture
  • Programming, building
  • Manufacturing
  • Help systems
  • Manuals
  • Training Customer support
  • Marketing
  • Branding
  • Distribution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Good design summary

A

Design starts with understanding your user, and should keep users’ interests central through entire process

Design is iterative -> trade-offs are difficult to see in advance

Designs are never “perfect” -> they can be improved

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

In general, who are your users?

A

People who directly interact with the product/application to accomplish a task

But is that it?

Others
Those who manage direct users
Those who receive products from the system Those who maintain the system
Those who make purchasing decisions Competitors

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

What are the categories of users?

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

What are the user factors that affect the development process?

What are the three types of user experience?

A

Age: reduce number of tasks, simplified interface

Disabilities: larger buttons, sound cues
Gender: spatial vs. temporal relations

Culture: icons, color Experience

Three types of experience:

Novices: highly visible functions, restricted set of tasks, tutorials to more complex tasks

Intermediate: reminders and tips, interface facilitates advanced tasks

Experts: shortcuts visible functions, restricted set of tasks, for efficiency, customizable interface

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

Who are the stakeholders for an automated check-out system at a large grocery store?

A

Customers:

Primary users: customers will operate it every time they make purchases

Check out operators:

Primary/secondary users: they interact with the system (often daily) when customers are having difficultly

Managers and owners:

secondary or tertiary users: they may occasionally interact with the system but mostly concerned about satisfied customers, safety and good functionality of system

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

What are the primary types of requirements?

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

Describe what each of the primary types of requirements

A
  1. Functional
    • What a product should do
  2. Data
    • What kinds of data need to be stored
  3. Environment / Context of Use
    • Circumstances in which the product will be expected operate:
      • Physical environment
      • Social environmnet
      • Organizational environment
      • Technical environment
  4. User Characteristics
    • What are the requirements imposed by the user group?
    • User characteristics:
      • ability
      • background
      • attitute to computers
    • System use:
      • Novice, expert, causual, frequent
  5. Usability
    • What is required to make the system usable?
    • Shuold capture the usability goals associated measures for a particular product (learnability, memorability, safety
17
Q
A