©2001 southern illinois university, edwardsville all rights reserved. cs 321 human-computer...

©2001 Southern Illinois University, Edwardsville All rights reserved.

CS 321 Human-Computer InteractionCS 321 Human-Computer Interaction

TodayToday

Consolidation

Reading:CD Ch.s 8, 9, & 10

WednesdayWednesday Group Discussion


Where We Are AtWhere We Are AtWhere We Are GoingWhere We Are Going

Contextual Inquiry – Ethnographic Techniques to collect raw data

Work Models – Interpretation Sessions to create a shared understanding of the work and user’s

mental models of the workYou are here Consolidation – Process of Induction to create a sense of

the whole user population from the individual users

Visioning – Brainstorming solutions

User Environment Design – System Blueprint and Interface Specification

Prototype – Application with sufficient detail for usability testing


ConsolidationConsolidation

From facts we learn about individuals, we need to draw conclusions about the general population

• Deduction vs. Induction

What do the individuals say about common work structures, strategies, intent, issues, and problems.


The Affinity DiagramThe Affinity Diagram

Organizes individual notes into a hierarchy of common issues

How-To• In a group session each member has their field notes and a pad

of post-its• One note is put-up and others look for similar notes that seem to

go with it• Interview notes are placed together if they have an “affinity” –

similar issues, intent, problems• Notes are given a group name that states the issue which binds

them together


Affinity Diagram ExampleAffinity Diagram Example

TimeManagement

Track ClassAssignments

Entered class U1 assignments into PDA

Wrote class U3 assignments on pocket calendar

Wrote class U2 assignments on hand and transferred to calendar at end of day

To DoLists

Looked at calendar U2after each task to decide what to do next

Printed a weekly U2to do list from PDA

Made a daily to U3do list every morning


Affinity DiagramAffinity Diagram

Built bottom-up

Reveals scope of issues

Group session drives consensus about the meaning of the data

Use post-it’s


The Design War RoomThe Design War Room

Walking the Wall Immersing yourself in the data

Beyer & Holtzblat (1998), Contextual Design, Morgan Kaufmann, Page:204


Consolidating Flow ModelsConsolidating Flow Models

Reveals the patterns of communication

Focuses the application by recognizing the line of communication it should support

How-To

• From individual flow models identify common roles Collection of responsibilities organized to accomplish a

goal or set of goals

• Name each role and list responsibilities

• Draw communication lines between roles


Consolidating Sequence ModelsConsolidating Sequence Models

Reveal common activities, goals, and strategies How-To

• Identify common activities and match triggers• Write an abstract step that states the work done• Match sequence activities and write abstract steps

• Step back through the consolidated sequence model and list the intent of each step or sequence

Beyer & Holtzblat (1998), Contextual Design, Morgan Kaufmann, Pages: 173, 174

Abstract step U5 U4

•Go to the place where the problem can be solved (physically or logically

•Log onto failing system to search for problem

•Go into lab to look at equipment

Figure 9.11 Going to deal with a a problem pg 173

Abstract step U5 U4

•Trigger: Find out about problem

–Automated procedure–Someone reports problem

•Trigger: Watcher sends mail that the All-in-1 (A1) mail system isn't working

•Trigger: Person walks into office to report problem; can’t access files on another machine

Figure 9.10 Alternate triggers pg 174


A Consolidated Sequence ModelA Consolidated Sequence ModelGeneral Activity Label Goal of Activities Abstract Step

Activity Intent Abstract step

Find out about problem •Learn about problems quickly

•Discover problems before users do

•Provide quick response

•Trigger: Find out about problem

–Automated procedure

–Someone reports problem

Go to problem location •Make it possible to do a diagnosis and take action

•Go to the place where the problem can be solved

Diagnose problem •Find cause of problem

•Decide who has been affected

•Decide if any additional action should be taken to notify people of status

•Make sure I don’t do things I’m not suppose to

•Execute commands and tests in suspect system to identify anomalous behavior

•Determine cause of symptoms

•Estimate impact of problem

•Decide whether I can fix the problem

Fix Problem •Fix problem at once •Decide if I can fix it:

•Attempt fit

•See if fix worked

•Try to figure out why fix didn’t work

Call on help •Get the people involved who have the authority of the knowledge to fix the problems

•Ensure problem gets fixes, even if not my job

•Decide I can’t fix it, call on help

Figure 9.14 A consolidated sequence model



Consolidating the Artifact ModelConsolidating the Artifact Model

Reveals common organizing themes and concepts that people use to pattern their work

How-To

• Group artifacts of similar types

• Identify common parts

• Draw common structure, usage, and intent

• Note variations


A Consolidated Artifact ModelA Consolidated Artifact Model


©2001 southern illinois university, edwardsville all rights reserved. cs 321 human-computer...

Documents

southern illinois university

morning slide

group discussion slide

common activities

individual notes

class u2 assignments

common work structures

usability testing slide