SBD: Activity DesignCS 3724 - HCIChris North

Usability Engineering - Chapter 3

Hall of Fame/Shame Presentations

• http://courses.cs.vt.edu/~cs3724/fall2006/schedule.html

HW#1 Revisited

Problem scenarios

summativeevaluation

Information scenarios

claims about current practice

analysis ofstakeholders,field studies

Usability specifications

Activityscenarios

Interaction scenarios

iterativeanalysis ofusability claims andre-design

metaphors,informationtechnology,HCI theory,guidelines

formativeevaluation

DESIGN

ANALYZE

PROTOTYPE & EVALUATE

Summaries: stakeholder, task, and artifact analyses, general themes

Root concept: vision, rationale,assumptions, stakeholders

Problem scenarios:illustrate and put into context the tasks and themes discovered in

the field studies

Claims analysis:find and incorporate features of practice

that have key implications for use

Field studies: workplace observations,recordings, interviews, artifacts

SBD andRequirementsAnalysis

Problem scenarios

summativeevaluation

Information scenarios

claims about current practice

analysis ofstakeholders,field studies

Usability specifications

Activityscenarios

Interaction scenarios

iterativeanalysis ofusability claims andre-design

metaphors,informationtechnology,HCI theory,guidelines

formativeevaluation

DESIGN

ANALYZE

PROTOTYPE & EVALUATE

Functionality

Look and feel

product data

browsing

searching

ordering

payment

customer data

SYSTEM

FUNCTIONALITY

LOOK & FEEL

iconslinks

menus

layout

navigationlabels

fields

security

feedback

The Two Faces of HCI Design

Activity Design

Information & Interaction

Design

Problem scenarios: work from current practice to build new ideas

Activity design scenarios:transform current activities to

use new design ideas

SBD: Activity Design

• Transform old activities to new activities that use technology

• Focus on system “what”,not “how” (why?)“conceptual design”, “task-level

design”

• Focus on improvements• Iterative

Goal: work from problems and opportunities of problem domain to envision new activities

Problem scenarios: work from current practice to build new

Activity design scenarios:transform current activities to

use new design ideas

Claims analysis: identify, illustrate, and document design features with key implications

Activity design space:

brainstorm implications of metaphors and

technology

Problem claims: look for design

ideas that address negatives, but keep positives

HCI knowledge

about activity design

SBD:ActivityDesign

+/-

+/-

Envisioning new activities

• Effectiveness: meets users’ needs• Innovative technology vs. tried-and-true• Generality vs. specific tasks

• Comprehension: understandable, predictable

• Mental models• Metaphors

• Satisfaction: accomplishment, motivating• Automation vs. control • Individual vs group needs

Designer’s Model User’s Mental Model

Cashier

Systematic, logical,comprehensive

Ad hoc, informal, incomplete

The Web

Cart

+ -

Metaphors bridge the gap

Activity design process

1. Design alternatives• Focus on fixing -’s, preserving +’s• Informal methods:

– Brainstorm– Try metaphors– Apply technologies– Explore “what if”s, Be creative, out of the box

• Systematic methods:– Identify design space -- Morphological Box

2. Rework scenarios with new design ideas• Participatory design• Coherence, completeness

3. Track claims• +/-, rationale

4. Iterate

The Morphological Box

Identify dimensions of the design space

Enumerate all possible solutions

PBJ sandwich, on whole wheat, no butter

Brainstorming

Developed in response to “group think” Basic rules:

Someone keeps list so everyone can see No idea is too wild No evaluation Silence does not mean “DONE”

Fun and “light weight”

Grocery shopping?

• Soccer mom:•

• Shopping cart:•

• Shelves/Aisles:•

metaphors

•

new scenario

• Online grocery?• Soccer mom:

•

The Morphological Box

Identify dimensions of the design space

Enumerate all possible solutions

PBJ sandwich, on whole wheat, no butter

Grocery shopping?

•

Problem scenarios

summativeevaluation

Information scenarios

claims about current practice

analysis ofstakeholders,field studies

Usability specifications

Activityscenarios

Interaction scenarios

iterativeanalysis ofusability claims andre-design

metaphors,informationtechnology,HCI theory,guidelines

formativeevaluation

DESIGN

ANALYZE

PROTOTYPE & EVALUATE

Execution

Action plan

Systemgoal

Last month’sbudget... ?

Interpretation

PerceptionMakingsense

GULF OFEVALUATION

GULF OFEXECUTION

Stages of Action in HCIInformationdesign

Interactiondesign

Human-computer

interaction

Taskgoal

Homework #2

• Due Thurs• Study Usability Case library

• Garden.com• Requirements analysis

• Create an HTA for planning a garden• Use existing analysis – stuff you didn’t know• Add own/friends’ knowledge• Hierarchical decomposition• Be thorough

Project Step 2 – Reqmts Analysis

• Due next Thurs• Do the UE process

• Identify stakeholders• Observe, interview, survey• Analyze data• Develop representations

• Users• Problem scenarios• Claims • What’s the REAL problem? Remember

Glenn Fink!