Design Considerations Flashcards

1
Q

Who, what, and where/how?

A
  • Who is the user
  • What does the user want to accomplish
  • Where/How is the interaction taking place
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the order of importance in design considerations?

A
  1. User strengths and weaknesses
  2. How to help user
  3. What improves quality of user experience
  4. User opinion — involve them in the design
  5. User-centered design techniques
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is usability?

A

Design metric concerning UI/UX

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

What are the components of usability?

A
  • Learnability
  • Efficiency
  • Memorability
  • Errors
  • Satisfaction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the Nielsen’s 10 (Usability Problems)?

A
  • Consistency and standards
  • Recognition rather than recall
  • Error prevention
  • Aesthetic and minimalist design
  • Match between system and real world
  • Help users with error
  • Help and documentation
  • User control and freedom
  • Visibility of system status
  • Flexibility and efficiency of use
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is User-Centered Design?

A

Requirements and recommendations for designing and understanding human users who use computer interfaces

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

What steps are in User-Centered Design

A
  1. Specify context of use
  2. Specify requirements
  3. Produce design solutions
  4. Evaluate designs
    1. System satisfies requirements
    2. or back to step 1
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is context?

A

Situation or environment influencing decisions

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

What are context considerations?

A
  • When/Where – time and location tasks are carried out
  • Who – who is involved in decisions
  • What – information to make a decision
  • How – steps to get things done
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How do context considerations impact the design?

A

Considerations impose constraints and implications to the design

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

How do you describe a context?

A

Through a scenario describing activities in a story

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

What are the requirements for describing contexts?

A
  • Explain user goals naturally
  • Provide fuller picture of activities
  • Talk about frustrations and potential solutions
  • Describe future designs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are users?

A

The people who carry out tasks and make decisions

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

What should we consider in users?

A

Demographics and hopes and fears

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

What do demographics show in users?

A
  • Provide insight into the approach or attitude toward an interface
  • Characteristics — leads to complexity and accessibility of interface
  • System use — different levels of users have less/more constraints and need more/less information
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What do hopes and fears show in users?

A
  • Describes the mental state of the user
  • Affects the user’s judgements
17
Q

How do you find the right users?

A
  • Ideally through direct contact
    • Else intermediary
    • Else research and define expected users and tasks
  • Broad coverage of users
    • Expected
    • Occasional but important
    • Unusual/extreme
18
Q

How do you describe a user?

A

Through a persona

19
Q

What are the requirements for describing users?

A
  • Requirements:
    • Realistically represents real users
    • Characterized by goals relating to design
    • Describe behaviour, attitudes, activities and environments
  • Tips
    • Use stock photos
    • Don’t stereotype
    • Cover a spectrum of real users
20
Q

What are requirements?

A
  • A statement on what is expected to do or how it will perform
  • Can check for functionality or generate metrics
21
Q

How do you phrase requirements?

A

The interface should/allows ____________

22
Q

What are functional requirements?

A
  • What the product will do
  • Described as verbs (features)
  • Tested through functional testing
23
Q

What are non-functional requirements?

A
  • Characteristics (or constraints) of the product
  • Described as attributes (properties)
  • Tested through performance/usability testing
24
Q

How do you gather requirements?

A
  • Typical Interview — meet with users and ask questions
  • Probes — prompt users into actions by giving them an interactable artifact (probe)
  • Contextual Inquiry — one on one interview (user teaches you how to carry out tasks)
  • Brainstorming
25
Q

What are tasks?

A
  • Activities done by the user
  • Described by user, pre-requisites, consequence, frequency, and importance
    • Actionable, realistic, and complete
  • Break tasks down into sub-tasks recursively (Hierarchical Task Analysis)
    • Should be physical and observable actions
26
Q

What are the purposes of tasks?

A
  • Describe existing tasks
  • Describe wish list (user-wanted) tasks
  • Describe envisioned (new interface) tasks
27
Q

What are some interface types?

A
  • Computer User Interfaces
  • Command Line Interfaces (CLI)
  • WIMP/GUIs
  • Modern GUIs
  • Mobile
  • Touchscreens
  • Speech/Voice
  • Wearable
  • AR & VR