Human-Centered Design (HCD): Principles, Process, and Modeling in UX

0.0(0)
studied byStudied by 2 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/97

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

98 Terms

1
New cards

Week: 2 What is Human-Centered Design (HCD)

A process that puts users first through observation, ideation, prototyping, and testing

2
New cards

What is the HCD process cycle?

Observe → Ideate → Prototype → Test.

3
New cards

What are affordances?

The perceived possible actions an object or interface allows.

Example: A door handle invites pulling; a flat plate invites pushing.

4
New cards

Who introduced the term "affordances"?

Psychologist James J. Gibson, adapted for design by Don Norman.

5
New cards

What's the difference between affordances and features?

Affordances = what users think they can do; Features = what something actually does.

💡 Example: A raised button (affordance) suggests pressing it; pressing it turns on a flashlight (feature).

6
New cards

What are examples of physical affordances?

Door handle = pull, flat plate = push, button = press, slider = drag.

7
New cards

What are digital affordances?

Screen cues like buttons, hyperlinks, sliders, or text fields that suggest actions.

8
New cards

What are signifiers?

Visual or sensory cues that indicate how to use something (like labels, icons, or color).

Examples: "Push/Pull" labels on doors, magnifying glass for search, trash can icon for delete.

9
New cards

What is the purpose of signifiers?

To make affordances clear and reduce cognitive load.

10
New cards

Give examples of signifiers in the digital world.

Trash can = delete, magnifying glass = search, hover effects on buttons.

11
New cards

What is mapping in design?

The relationship between controls and their effects.

Spatial mapping: arrows, scrollbars.

Conceptual mapping: icons representing actions.

Cultural mapping: colors, reading direction.

12
New cards

What is natural mapping?

When controls directly correspond to real-world outcomes (e.g., steering wheel turns car left).

13
New cards

What are mental models?

It's what users expect to happen when they use something, based on past experiences (ex: push plate = push door).

14
New cards

What are conceptual models?

The designer's idea of how a system should work and how it's shown to users (ex: online store works like a real store).

15
New cards

Why must mental and conceptual models align?

So users can predict how the system behaves.

16
New cards

What is feedback in design?

Responses that confirm user actions (e.g., button light-up, sound, or progress bar).

17
New cards

What are symbolic systems?

Shared meanings of icons, colors, and symbols that represent actions (ex: 🗑️ = delete, 🔒 = lock, red = stop).

18
New cards

What are the core principles of good design?

Visible affordances, clear signifiers, natural mapping, mental model alignment, consistent feedback.

19
New cards

week 3 What are the four stages of the complete HCD process?

Observation, Ideation, Prototyping, Testing.

20
New cards

What's the purpose of observation?

To understand context, discover unmet needs, and identify real problems.

21
New cards

What are common observation methods?

Contextual inquiry, shadowing, ethnographic research, and journey mapping.

22
New cards

What was learned from the hospital hygiene case study?

Designers learned to observe real user behavior; poor placement and lack of feedback reduced handwashing. Improving visibility and convenience boosted compliance.

23
New cards

Why does traditional brainstorming often fail?

Dominant voices, conformity, expertise bias, and early judgment.

24
New cards

What is a "How Might We" question?

It's an open-ended question that reframes a problem into a creative challenge (ex: "How might we help users recycle more easily?").

25
New cards

What is the "Worst Possible Idea" technique?

A brainstorming method where people share intentionally bad ideas to reduce fear, spark creativity, and uncover new insights.

26
New cards

What are the levels of prototypes?

Low-fidelity (paper), medium (wireframes), high-fidelity (interactive), working (functional).

27
New cards

What is the purpose of prototyping?

To test ideas and gather feedback quickly and cheaply.

28
New cards

What should testing evaluate?

Usability, desirability, feasibility, and viability.

29
New cards

What types of data should be collected during testing?

Behavioral, performance, emotional, and preference data.

30
New cards

What is systems thinking?

Understanding how multiple components and people interact within a larger system. basically thinking bout something as a whiole

31
New cards

Why are models needed in design?

They help communicate complex systems clearly across teams.

32
New cards

What are characteristics of good models?

Accurate, clear, appropriately detailed, and useful.

33
New cards

Why is standardization important in design?

helps users by keeping things familiar — once they learn it once, they can use it anywhere.

34
New cards

Week4 What does UML stand for?

Unified Modeling Language.

35
New cards

What is UML used for?

Communicating and visualizing software design.

36
New cards

Why was UML created?

To standardize software design communication and eliminate ambiguity(vague).

37
New cards

What are the three pillars of design communication?

Models, Views, and Diagrams.

38
New cards

What is a design model?

A blueprint or diagram that shows how a system's parts connect and work together (ex: use case, class, or sequence diagram in UML).

39
New cards

What is a design view?

It's one perspective of the system's design (like user interactions, structure, or processes). Each view focuses on a different aspect, such as logical, process, or deployment.

40
New cards

What are the main types of design views in UML?

Structural, Behavioral, User Experience, and Implementation.

41
New cards

What is a UML diagram?

A visual tool to communicate a specific design view.

42
New cards

List the main types of UML diagrams.

Class, Component, Deployment, Use Case, Activity, Sequence, and State.

43
New cards

Which diagram shows system structure?

Class diagram.

44
New cards

Which diagram shows user interactions?

Use Case diagram.

45
New cards

Which diagram shows workflow or process?

Activity diagram.

46
New cards

Which diagram shows communication between components?

Sequence diagram.

47
New cards

Which diagram shows hardware or deployment layout?

Deployment diagram.

48
New cards

What are the five UML communication principles?

Purpose-driven, audience-aware, appropriate detail, consistent notation, clear communication.

49
New cards

What is the Goldilocks principle in UML?

Include just enough detail — not too much, not too little.

50
New cards

What is a common UML beginner mistake?

Creating "diagram soup" with too many details or unclear purpose.

51
New cards

week 5 What are class diagrams used for?

Showing the structure of a software system through classes and relationships.

52
New cards

What is the "three-box rule"?

Class Name | Attributes | Methods.

53
New cards

What do visibility symbols mean?

+ Public, - Private, # Protected, ~ Package.

54
New cards

What are the five key class relationships?

Association, Aggregation, Composition, Inheritance, Realization.

55
New cards

What is an association?

A connection between independent classes (e.g., Customer—Order).

56
New cards

What is aggregation?

"Has-a" relationship with loose ownership (e.g., Team—Players).

57
New cards

What is composition?

"Owns-a" relationship with strong ownership (e.g., House—Rooms).

58
New cards

What is inheritance?

: "Is-a" relationship where one class extends another (e.g., Car—Vehicle).

59
New cards

What is realization?

class implementing an interface (e.g., Car implements Drivable).

60
New cards

What is multiplicity?

The number of instances involved in a relationship (e.g., 1..*, 0..1).

61
New cards

What are the steps to create a class diagram?

Identify classes → Add attributes/methods → Define relationships → Add multiplicity → Review.

62
New cards

Example: In an online shopping system, what relationship exists between Order and OrderItem?

Composition (Order owns OrderItems).

63
New cards

What's the relationship between GuestUser and Customer?

Inheritance (GuestUser IS-A Customer).

64
New cards

What memory tricks help remember relationships?

Association = Facebook friends

Aggregation = Sports team

Composition = House & rooms

Inheritance = Family tree

Realization = Contract signing

65
New cards

week 6 What's the difference between component and deployment diagrams?

Component Diagram: Shows what software parts exist and how they connect.

Deployment Diagram: Shows where software runs and what hardware it uses.Think: WHAT vs. WHERE.

66
New cards

What is a component?

A small, self-contained part of a system that does one main job.Like a LEGO brick: you can swap, reuse, and connect it with others.

67
New cards

What makes a good component?

Self-contained - works on its own

Replaceable - can swap with similar part

Encapsulated - hides inner details

Interface-based - connects only through clear "plugs"

68
New cards

What is a component interface?

The "connection point" where components interact — like an electrical outlet.It defines what service is provided, not how it's done.➡️ Makes components safe and interchangeable.

69
New cards

What is a deployment node?

A device or environment that runs the software.Examples: phones, laptops, servers, or the cloud.Nodes can be physical (hardware) or virtual (software environment).

70
New cards

What are the parts of a deployment diagram?

Nodes: physical or virtual machines

Artifacts: software files or apps inside nodes

Connections: network links showing communication

71
New cards

When should you use each diagram?

Component Diagram: when planning software structure, modules, or interfaces

Deployment Diagram: when planning servers, cloud setups, or performance➡️ Use both to see the full system.

72
New cards

Common mistakes with these diagrams?

Mixing software and hardware in the same view

Making components too tiny or too big

Forgetting to show interfaces or connections

Ignoring scalability or backups

73
New cards

(What + How)

Component = Software structure ✅ .

74
New cards

(Where)

Deployment = Hardware setup You need both to build a full system.

75
New cards

you need both___and ___to build a system

component and deployment

76
New cards

week 7 What's the main difference between Use Case and Activity diagrams?

Use Case Diagram: Shows who uses the system and what they can do.

Activity Diagram: Shows how each process works step-by-step.Think: WHAT vs. HOW or Menu vs. Recipe.

77
New cards

What are the main parts of a Use Case diagram?

Actors: People or systems using it (stick figures)

Use Cases: Actions they can do (ovals)

System Boundary: The box showing what's inside the system

78
New cards

What's important to remember about actors?A:

Actors are roles, not real people.Example: Doctor, Nurse, Patient — not "Dr. Smith."

79
New cards

What's the goal of a Use Case diagram?

To show all the functions a system provides to each user and define system scope.

80
New cards

What are Activity Diagrams used for?

To show the process flow — how things get done.Like a flowchart: actions, decisions, and outcomes.

81
New cards

What are the main symbols in an Activity diagram?

Start/End: Circles

Actions: Rounded rectangles

Decisions: Diamonds

Flows: Arrows showing order

Fork/Join: Thick lines for parallel work

82
New cards

What do loops in activity diagrams show?

Repeating actions (e.g., adding more items to a cart).

83
New cards

How do Use Case and Activity diagrams connect?

Use Case = Goal (e.g., "Register for Course")

Activity = Process (e.g., "Login → Search → Add Course → Confirm")Together, they show what users want and how they achieve it.

84
New cards

When should you use each one?

Use Case: To find users, goals, and features

Activity: To find steps, decisions, and issues in workflows➡️ Use both for full user-centered design.

85
New cards

Who & What

Use Case

86
New cards

How

Activity

Together they describe user goals and system actions clearly.

87
New cards

week 8 What's the difference between Sequence and State diagrams?

Sequence Diagram: Shows who talks to who and in what order.

State Diagram: Shows how one object changes over time.Think: Conversations vs. Transformations.

88
New cards

What does a sequence diagram show?

The order of messages between parts of a system (like a comic strip).Focuses on communication and timing.

89
New cards

What are participants in a sequence diagram?

Objects, users, or systems that send and receive messages.Examples: Customer, Website, Payment System, Database.

90
New cards

What are the main message types in sequence diagrams?

Solid arrow: Send message (wait for response)

Dashed arrow: Return message

Loop arrow: Object talks to itself

91
New cards

What's the difference between an activity diagram and a sequence diagram?

Activity = Flow of tasks

Sequence = Flow of messages between partsExample: Activity shows steps in login; Sequence shows how User, Website, and Database talk to complete login.

92
New cards

What does a state diagram show?

The life cycle of one object — how it moves from one condition to another.Each state shows what the object is doing.

93
New cards

What are transitions in a state diagram?

Arrows showing what causes a change.Example: "Go Online" moves driver from Offline → Available.

94
New cards

What are the three activities within a state?

Entry: Happens once when entering

Do: Ongoing while inside

Exit: Happens once when leaving

95
New cards

Example of a State Diagram (Driver App)?

States: Offline → Online → Ride Accepted → Passenger Pickup → In Transit → Trip Complete → Back to OnlineShows how driver and system move through each step.

96
New cards

When should you use Sequence vs. State diagrams?

Sequence: To show message order and communication

State: To show how an object changes over timeUse both for complete time-based behavior.

97
New cards

Sequence

Object Conversations (who talks when)

98
New cards

State

Object Lifecycles (how things change)Together, they explain system behavior over time.