HCI Midterm Review: Quizzes and Lecture Notes

Which of the following is NOT one of the design perspectives suggested by the authors? A. Emotional perspective B. Interaction perspective C. User perspective D. Ecological perspective

C

Design-Informing Models

1. Artifacts that drive, inform, and inspire design 2. Turn contextual data into actionable items to guide design 3. Elements to consider or take into account in design 4. Most models can be used to describe the current situation and/or the envisioned situation

Two main parts of CA

1. Identification, organization and interpretation: building a flow model and synthesizing work activity notes. 2. Data consolidation and communication: building a WAAD from the work activity notes and walk throughs of all these work products

Requirements extraction process

1. Walkthrough: WAAD for needs and requirements 2. Deduct: switch from inductive to deductive reasoning, what interaction requirements is implied by each work activity note in the WAAD 3. Categorize: create a requirements template to record all needs in categories. Use WAAD's hierarchy to create the

A cardinal sin in ideation is to: A. Mix critiquing into idea creation B. Come up with too many ideas C. Use a dedicated work space D. Ignore job titles and status

A

The textbook argues that we should design so that: A. The primary persona is very happy and the rest of the selected personas are not unhappy B. The primary persona is not unhappy C. All of the selected personas are very happy D. The entire user class is very happy

A

What is NOT one of the benefits of using personas in design? A. It allows to disregard designing for other user classes B. It relieves the struggle to design for conflicting needs and goals C. It creates empathy between designers and the user D. It controls the instinct to design for all cases and problems

A

What is the best way to combine the UX and SE lifecycles? A. Have the two cycles work collaboratively and in parallel B. Have the two cycles work independently in parallel C. Have the two cycles work in series with iterative feedback going back and forth D. There is no way to effectively combine the two due to their totally different scope

A

Which of these is NOT typically covered in a system concept statement? A. What is the target hardware? B. What is the design vision? C. What will the system do? D. Who are the system users?

A

What is a flow model

A "big picture" diagram of work domain. Shows interconnections among components of work domain. Work flow among components and information flow among components. Components include key work roles and machine roles. Shows how things get done in domain and how entities communicate

Affordances

A property of an object or a system that furnishes something to its users.

What of these statements are true regarding design sketches and low-fidelity prototypes? (select all that apply) A. Prototyping is used to get the design right vs getting the right design use of sketching B. Design sketches can be used for exploration of ideas while prototypes are used for evaluation purposes C. Both design sketches and low-fidelity prototypes can be equally used for both ideation and evaluation purposes D. Sketching is used to get the design right vs getting the right design use of prototyping

A, B

What are the main difference(s) in orientation between the UX and SE approaches? (select all that apply) A. Technological constraints vs User satisfaction B. Code vs Design quality C. Functional vs User requirements D. User vs Business goals

A, B, C

How would you best describe your relationship to the user during contextual inquiry? (pick all that apply) A. The user is the expert and you are the observer B. You are the expert guiding the user C. You are both observers offering no opinion about the system/product D. You are a co-investigator along with the user

A, D

Work Activity Affinity Diagram (WAAD)

An affinity diagram is a way to sort data into categories and subcategories when you dont know in advance what these will be. The data determine the categories, not preconceived notions.

Metaphors

Analogies for communication and explanations, explain unfamiliar using familiar conventional knowledge. Use what users already know about existing system or phenomena

Ideation

Applied to design thinking, active, fast-moving collaborative group process for forming design ideas, where you start your conceptual design

Which type of model is a story about particular people doing work in existing contexts? A. Usage scenario B. Work roles C. Persona D. Step-by-step task interaction model

A

What are the two primary activities in contextual inquiry? A. Surveys and interviews B. Observation and interviews C. Observation and surveys D. Focus groups and individual interviews

B

Which type of mental model is more likely to be incomplete and incorrect? A. Developer's mental model B. Client's mental model C. User's mental model D. Designer's mental model

C

What is HCI

HCI is the study of designing effective interactive systems for human use. Understanding how interactive technologies affect the lives of individuals, groups and societies

Cognitive Affordance

Help users think and learn and understand

UX guidelines: Learnability

How easily can a user learn to navigate the interface

UX guidelines: Efficiency

How easily can users perform tasks

UX guidelines: Errors

How quickly can users recover from errors

Design perspectives: Ecological

How system/product works within its external environment. How its used in its context. How it interacts with people and systems around

UX guidelines: Memorabilty

How well can a returning user recall the interface

Synthesizing work activity notes

Identify (tag each work activity note with a source ID), make (compact, concise, easy to read), simplify (make each work activity note a simple declarative point)

User's Mental Model

Internal explanation user has build about how system works. Partial explanations rather than a complete picture. A product of many different inputs, cultural conventions, system conceptual design (knowledge in the world), informal, incomplete

Origin of Contextual Inquiry

Roots in ethnography (writing about people)

Design Perspectives: Emotional

about aesthetics and joy of use. emotional impact and value sensitive aspects, social and cultural implications

What is the textbook's definition of "work domain?" A. The set of activities that people undertake to accomplish goals B. The entire context of work and work practice in the target usage environment C. Comprised of sensory, cognitive, and physical actions made by users in the course of carrying out the work practice D. The pattern of established actions, approaches, routines, conventions, and procedures followed and observed in the customary performance of a particular job

B

Which of these is NOT an example of a work artifact? A. Screenshot of computer system B. Design idea (sketch) C. Photo of a bulletin board D. Maintenance request form

B

Which of these is NOT one of the major activities in the Wheel? A. Evaluate B. Architect C. Analyze D. Design

B: Architect

Which of these UX team roles would be associated primarily with the task of verifying and refining interaction design? A. User researcher B. Usability analyst C. Subject matter expert D. Interaction designer

B: Usability analyst

A series of sketches of mobile screens with specific options being selected is an example of conceptual design from the __________. A. Ecological perspective B. Emotional perspective C. Interaction perspective D. User perspective

C

Contextual inquiry is primarily about understanding which of the following? A. Design changes that would improve effectiveness B. What users want C. Existing work practice D. The most efficient way to complete a task

C

Design-informing models describe: A. Envisioned work practice B. Current work practice C. Both current and envisioned work practice

C

How are typically UX designers treated when software engineers are the product architects, according to the authors? A. They are equal contributors to the design and production process B. They are not part of the process at all C. They are brought near the end mostly for visual and cosmetic changes D. They are consulted early on and never again

C

The principal role of a sketch during ideation is to serve as: A. One frame in a storyboard B. Documentation of a design C. A medium to support a conversation among design team members D. A prototype that can be evaluated

C

What are the foundations for success in SE-UX development? A. Coordination, synchronization, constraint checking, and risk management B. Coordination, facilitation, adaptation, and synchronization C. Coordination, collaboration/communication, dependency & constraint enforcement, and synchronization (change management) D. Coordination, communication/collaboration, adaptation, and iteration

C

What are we primarily trying to model during the contextual inquiry stage? A. None of these B. The envisioned system and work practice C. The existing system and work practice D. Both of these

C

Where do organizations with a predominant software engineering culture fall short of? A. They spend too much time in development B. They spend too much money on tech innovation C. They neglect to listen to the users throughout the lifecycle D. They are disconnected from organizational and business constraints

C

With which of these statements about iteration in UX would the textbook authors disagree? A. Iteration should begin early in the process B. Iteration is almost always necessary C. Iteration allows you to be less careful with the initial design D. Iteration does not have to be expensive.

C

User Models: Social Model

Communal aspects of workplace, philosophy, ambiance, and environmental factors, norms of behavior, mind-sets, feelings, attitudes, influences, pressures, concerns of individuals in specific work roles, captured in social model diagram

Designer's Mental Model

Conceptualization of the envisioned system- how it is organized and what it does and how it works. Created from what is learned in contextual inquiry and analysis. Transformed into design by ideation and sketching. If a designer has never established a mental model, users will experience vagueness and misconceptions. Systematic, logical, comprehensive

Usage Models: Flow Model

Considered the most important model type. Scope is the entire work practice. Bird's-eye vie of entire workflow. Nodes for entire entities. Arcs for flow of work or information. Include non-human entities.

Building the Work Activity Affinity Diagram

Create clusters by work roles, clusters to groups, create a hierarchy, WAAD walkthrough

In the process described in the book, what is the immediate source of interaction requirements? A. Consensus among team members B. Contextual inquiry C. The client D. The WAAD

D

The main role of a conceptual design is to: A. Provide requirements to interaction designers B. Evolve into the final system implementation C. Evaluate the user experience of the system D. Connect the designer's mental model to the user's mental model

D

The placement of kitchen stove buttons in the same arrangement as the cooktop elements layout is an example of good: A. Consistency B. Feedback C. Constraints D. Natural mappings

D

What term means "characteristics of user interface objects and interaction design features that help users perform tasks?" A. Conceptual designs B. Metaphors C. Design patterns D. Affordances

D

Which HCI paradigm would be likely to lead to designs for placement of car controls to react quickly to emergency driving situations? A. Phenomenology paradigm B. Design thinking paradigm C. Engineering paradigm D. Human information processing paradigm

D

Which is NOT part of the user work activity data gathering process? A. Gather raw user work activity data and artifacts B. Observe and interview users while they work C. Ask users about the structure of their work practice D. Inquire users' opinion about the envisioned system

D

Which of the following is NOT a type of User Model? A. User classes B. Work roles C. Social model D. Artifact model

D

Which of the following is NOT part of a typical requirements statement? A. Rationale B. Name of major feature or category C. Source node ID D. How the requirement should be realized in the design

D

Which of the following is something that is NOT typically included in a storyboard? A. Sketches of devices and screens B. Physical user actions C. Cognitive user actions as "thought balloons" D. Screen layout and color choices

D

Which type of affordance helps users know what to do or what will happen? A. Physical affordance B. Functional affordance C. Sensory affordance D. Cognitive affordance

D

Which type of model helps you understand communal aspects of the users' workplace? A. Flow model B. Information object model C. Hierarchical task analysis D. Social model

D

User Models: User Classes

Description of characteristics of people who might take on a work role

Design sketches vs low-fidelity prototypes

Design sketches: goal--- support ideation to find a great design solution, experimenting, exploring, being creative, getting the right design for design. Low-fidelity prototypes: goal---support iterative refinement of a given design, following UX process, getting the design right, for UX engineering

UX guidelines: Satisfaction

Do users enjoy using the interface and the results

Sketching an initial flow model

Draw nodes of diagram to represent work roles, label nodes with work role names, add additional labeled nodes for other entities, anything involved in flow of work practice, add arcs indicating information work flow, label arcs with what information flows, include flow outside system and label with flow channel

Good work activity notes descriptors:

Each note should contain just one concept, idea or fact, break a long work activity note into shorter ones, each with only one main point, make each note complete and self-standing, disambiguate pronouns and references to context and refer to work roles rather than individual people, avoid repetition of same information in multiple place

Design Thinking

Emphasis in interaction is about making meaning and emotional aspects

UX Guidelines: Usability

Learnability (how easily can a user learn to navigate the interface). Flexibility (how many ways can a user interact with the system). Robustness (how well are we supporting users when they face errors).

Usability and Accessibility

Learnability, effectiveness, efficiency, productivity, ease of use, retainability, HOW

System Concept Statement

Mission statement for a new system to be developed. Explains system to outsiders (understandable). Needs to be short (concise), must be iterated and refined

Usage Models: Step by step task interaction model

More direct and less story oriented sequence, contains detailed description of task performance observed in users or as told by users. Includes temporal ordering of actions and activities. Not complete task specifications. Mostly linear paths but can add branching if necessary. Can gather great understanding from one task path.

UX Components: Content Strategy

Planning, development, and management of content

UX Components: User interface

Space supporting the interaction between the user and the system

UX Components: Information Architecture

Structural design of shared information environments

What is Contextual Analysis

Systematic analysis of contextual user work activity data for the purpose of understanding work context for new system to be designed.

Where do personas work best

Systems with relatively simple work domains, not good for complex work domains

Usage Models: Hierarchical Task Inventory

Tasks broken down into subtasks and steps. Show what user tasks and actions are possible. To guide overall design. Use as checklist for keeping track of task coverage in design. Hierarchical tree structure of tasks. Does not represent temporal ordering.

UX Components: Functionality

The quality or state of being functional (what) features

What is CI and what are the best practices in CI

UX lifecycle activity to gather detailed descriptions of customer or user work practice. Best practices include interviews, and observations, learning about user behaviors, learning about user attitudes, involving users in the design process

Goal of Contextual Inquiry

Understand customer's work practice. Work, work practice, work domain. Understanding work activities and underlying rationale. Goal is to Improve work practice and construct and/or improve system designs to support it.

User Models: Work Roles

Work Roles: Correspond to duties, functions, work activities, system usage or not, internal or external to organization. Sub-Roles: more specific description based on specific goals. Mediated work roles: not direct system users but play part in usage context.

Work Environment Models: Physical model

captures roles, activities, and artifacts of other models of a physical setting. Shows physical dimensions of work spaces, shows workstations, placement and paths of movement of people.

Contextual inquiry -----> _____________ ------> __________ -----> _______________ -----> ______________

contextual analysis, needs and requirements, design informing models, design

CI is about learning the ________ __________ for the work your system is going to be designed to support

current practice

Contextual inquiry and analysis DO NOT result in ________

design

Requirements inform __________

design

WAAD Guidelines

do not act on designer instincts, compartmentalize clusters by work roles. note groups should be 5-12, label groups to identify themes

What is CI NOT?

doing a survey, holding a focus group, assuming you know your users because you keep an eye on your stats.

Collecting work activity data

dont ask users what they want or need, you focus is to create empathy, focus on user tasks and information flows

Do NOT include information from _____ _______ in work activity notes

flow model

Physical Affordance

help users do something physically

Design perspectives: Interaction

how users operate the system or product, task and intention view where user and system come together. involves sensory and cognitive and physical actions

Two modes of thinking:

idea creation and critiquing

Steps of data interpretation

identify key work roles, build initial flow model, synthesize work activity notes, gather domain artifacts, identify missing data or gaps, decide on goals, tasks, and actions, update the flow model, extract more work activity notes, update list of artifacts, and record design ideas/insights

Interview DONTs

never say "usually" when asking a question, dont try to sell your system / product

User personas

not an actual user, more than a stakeholder, pretend user or hypothetical archetype, offer concreteness, personal engagement, ideal for sharing a design vision, story and description of specific person. Personas help us focus on designing literally for a single person. Liberates designers from having to sort through all conflicting details. Rich persona: relevant, believable, specific, precise, personality, life surrounded with artifacts. Sticky persona (memorable): not just in design meetings, create posters, coffee mugs, shirts

_____________ and ____________ bridge the gap between CI/CA and design

requirements and DIMs

What are requirements

requirements means interaction design requirements in this class

Contextual analysis does NOT directly yield _____________- or _____________

requirements or design

A physical model can be used to understand how the placement of objects, equipment, and people can help or hinder work in a shared space. True False

true

Metaphors are an important tool that can be used to create a good conceptual design. True False

true

current system < user (expert) < ______

work domain