Top Banner
SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3
35

SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Dec 27, 2015

Download

Documents

Marilynn Rogers
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

SBD: Activity DesignCS 3724 - HCIChris North

Usability Engineering - Chapter 3

Page 2: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Hall of Fame/Shame Presentations

Page 3: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Homework Revisited

Page 4: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Project: Req’s Analysis revisited

Page 5: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Activity design

• Conceptual models– Abstract objects– Abstract operations

Page 6: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

e.g. communication

• Phone: voice, sync, 2 way, remote, 1-1, immediate, – Metaphor: Face to face

• Cell text• IM: text, sync• Email: text/files, stored, editable, 1

way, async, 1-M, impersonal, not interupting, ignore– Metaphor: snail mail

Page 7: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

e.g. project metaphors

• Find needle in haystack• Reading a book, creating mystery

novel, choose your own• Identifying trends, e.g fashion, stock• Multiple Puzzle

– Sorting out pieces, categorizing– Border, framework– Pick focus area, unique– Filling in gaps– Show it off

Page 8: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

e.g. more project ideas

• Browsing the web• Googling, hits• To-do lists• Notes in margin, textbook• Piling, filing, folders• Timelines, calendars

Page 9: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

e.g. project claims

• Search box– + narrows list of files– + flexible, can type any keyword– - searching in wrong files– - irrelevant optoins– - no stemming (“flower(s)”)– - no organization of hits list– - copy&paste, mispelling

• Piling:– + focus the searches within piles– - must pre-sort piles

• Browsing the web:– + select the hyperlink, no retyping or copy&paste– - less flexible– + shows us what is ‘searchable’, avoid 0 hit query

• Googling– + give hints about similar searches

Page 10: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.
Page 11: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 12: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 13: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 14: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 15: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 16: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

+/-

+/-

Page 17: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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. user control • Individual vs group needs

Page 18: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 19: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

The Morphological Box

Identify dimensions of the design space

Enumerate all possible solutions

PBJ sandwich, on whole wheat, no butter

Page 20: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Designer’s Model User’s Mental Model

Cashier

Systematic, logical,comprehensive

Ad hoc, informal, incomplete

The Web

Cart

+ -

Metaphors bridge the gap

Page 21: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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”

Page 22: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Grocery shopping – Reqs analysis review?

• Soccer mom:•

• Shopping cart:• + • -

• Shelves/Aisles:• + • -

Page 23: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Metaphors for Grocery Shopping?

Page 24: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

New activity scenario?

• Online grocery• Soccer mom story:

Page 25: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Grocery shopping – Reqs analysis review

• Soccer mom:• Screaming kids• Large quantity• search strategy, lists• Browsing strategy?• weekly repeats

• Large Shopping cart:• + 1 slot for 1 kid• + Pile stuff, big stuff underneath• - >1 kid? • - must push, heavy

• Shelves• + see lots of stuff fast• - hard to find stuff• - lots of walking

Page 26: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Metaphors for grocery shopping

• Pizza delivery• + stay home• - no browsing

• Cookbook• + meal oriented• - no customization?

• Vending machine• Menu for search stuff• + Automating retrieval of items• - get top item only, can’t pick unbruised fruit…

Page 27: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

New activity scenario

• Online grocery• Soccer mom story:

• Puts screaming kids outside• Repeating purchases using order template • Search for items quickly• Gets helpful linked recommendations: beer +

diapers• How does she Browse? Online

coupons/specials…• Items get packed for her and delivered to her

door (or maybe she picks up, they load into her van for her)

• But She notices some items are not correct.

Page 28: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

The Morphological Box

Identify dimensions of the design space

Enumerate all possible solutions

PBJ sandwich, on whole wheat, with butter

Page 29: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Grocery Shopping – design dimensions?

Page 30: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Grocery Shopping – design dimensions

• Online vs. Store• Browse vs. Search• Deliver vs. Pickup•

Page 31: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Morph. Box for Grocery Shopping

online store

Browse llbean kroegers

Search Ebay, Pizza by phone

Mcdonalds

location

navigation

Possible new ways to grocery shop?

Page 32: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 33: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

Execution

Action plan

Systemgoal

Last month’sbudget... ?

Interpretation

PerceptionMakingsense

GULF OFEVALUATION

GULF OFEXECUTION

Stages of Action in HCIInformationdesign

Interactiondesign

Human-computer

interaction

Taskgoal

Page 34: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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

Page 35: SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3.

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?