Studied by 0 people
Looks like no one added any tags here yet for you.
Human-Centered Design
An approach to system design that focuses on users' needs, requirements, and social context.
goal of HCD
Create products and systems that are useful, usable, and meaningful to the intended users.
Key principle of HCD
Involve users throughout the design process
6 core elements of HCD
understand, define, ideate, prototype, test, iterate
benefits of HCD
Improved user satisfaction and adoption rates, Reduced development costs by addressing issues early, Enhanced accessibility and inclusivity, Increased product effectiveness and efficiency, Better alignment with users' real-world needs and contexts, Fostering innovation through deep user understanding
Affordances
Perceived possibilities for action in an environment growth an object. Coined by psychologist James J. Gibson in 1977
Features
Specific attributes or functions of a product, Defined by designers and developers, Focus on product capabilities, Intentionally created and implemented
Signifiers
perceivable indicators that communicate how to usesomething; Introduced by Don Norman to clarify the concept of affordances
User Feedback in HCD
information provided by users about their experience with a product or system encompasses:• User opinions, complaints, and suggestions• Behavioral data from user interactions• Performance metrics in task completion
Conceptual Models
simplified mental representation that a user forms to understand and interact with a system or product.
Mapping
The relationship between the elements oftwo sets of things
Symbolic Systems in HCD
structured representations that use symbols, notations, and diagrams to model complex real-world systems, processes, or concepts in a simplified and standardized manner.
UML
Standardized visual language used in software engineering to create diagrams that represent the structure, behavior, and interactions of a software system
Double Diamond Model
Provides a visual representation of the design process, emphasizing the iterative nature of design thinking. comprised of 4 phases: Discover, define, develop, deliver
HCD Process
made up of 4 activities: observation, idea generation, prototyping, testing
Observation
Involves carefully watching and listening to users in their natural environments to gain deep,unbiased insights into their behaviors, needs, and challenges.
Prototyping
involves creating early, tangible representations of ideas to explore, test, and refine potential solutions.
Testing
Evaluating prototypes or concepts with actual users to gatherfeedback, validate assumptions, and refine solutions
Model
simplified representation or abstraction of asystem or concept
Systems
actual set of interrelatedcomponents working together to achieve aspecific purpose. It's the real-worldimplementation of what the model represents.
Views
specific perspective representation of a model or system, focusing on particular aspects or concerns. It is a way of looking at or presenting the model or system.
Class Diagram
shows the different objects (classes) in a system, their attributes, their operations, and relationships among them
Component Diagram
High-level blueprint or map of a software system. It shows the major parts (components) of a system and how they connect or interact with each other. Think of it as a simplified view of how different pieces of software fit together to make a complete system.
Deployment Diagram
map that shows how the different parts of a software systemare distributed across the physical hardware. It illustrates where each piece of software runs andhow these pieces connect to each other in the real world.
Use Case Diagram
visual story that shows how different users interact with asystem to accomplish various tasks. It's a way to illustrate what a system does from theuser's point of view, without getting into the technical details of how it does it.
State Diagram
map that shows the differentconditions or situations (states) an object or system can be in, and how it moves between thesestates in response to various events or actions.
Activity Diagram
A flowchart that shows the step-by-step flow of actions in a process or system. A visual way to describe how activities are coordinated to provide a service or how the flow of events goes in a use case or business process.
Sequence Diagram
story that shows how different parts of a system interact with each other over timeto complete a specific task or scenario.
CSCW
Computer Supported Cooperative Work: The study and practice of how technology can help people work together more effectively, especially when they're not in the same place or working at the same time.
Social Technical Gap In Action
A concept in CSCW that refers to the divide between what we know we must support socially and what we can support technically.
The Disparity
situations where the individuals or groups who invest time and effort into using or maintaining a collaborative system are not necessarily the same ones who derive the primary benefits from it.
Structural Things
nouns of UML models• Static parts of a model, representing elements that are either conceptual or physical
Behavioral Things
Dynamic parts of UML models• The verbs of a model represent behavior over time and space
Interaction
Contains a set of messages exchanged among a set of objects within a particular context to accomplish a specific purpose
State machine
behavior that specifies thesequences of states an object or aninteraction goes through during itslifetime in response to events,together with its responses to thoseevents
Grouping things
organized parts of UML models• The boxes into which a model can be decomposed. only one kind packages
Package
general-purpose mechanism for organizing elements into groups
Annotational Things
Explanatory parts of UML models comments applied to describe, illuminate, and remark about any element in a model, there is one kind of note
Structural Diagrams
class, deployment, and component diagrams
Association
simple relationship between two classes. Forexample, a Driver drives a Car.
Aggregation
stronger relationship. It's like a "has-a"relationship. For example, a Department has Employees.
Composition
similar to aggregation, but stronger. It's a"owns-a" relationship. For example, a House owns Rooms
Inheritance
"is-a" relationship. It is how we represent that one class is a type of another class.
Realization/Implementation
This is used when a class implements an interface. An interface is like a contract that says what methods a class must have. For example, if we have a Vehicle interface, a Car might implement it
Dynamic Diagrams
they show how things change and interact over time..
