©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10 Wednesday Group Discussion

©2001 Southern Illinois University, Edwardsville All rights reserved. Where We Are At Where 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 work You 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

©2001 Southern Illinois University, Edwardsville All rights reserved. Consolidation 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.

©2001 Southern Illinois University, Edwardsville All rights reserved. The 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

©2001 Southern Illinois University, Edwardsville All rights reserved. Affinity Diagram Example Time Management Track Class Assignments 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 Do Lists Looked at calendar U2 after each task to decide what to do next Printed a weekly U2 to do list from PDA Made a daily to U3 do list every morning

©2001 Southern Illinois University, Edwardsville All rights reserved. Affinity Diagram Built bottom-up Reveals scope of issues Group session drives consensus about the meaning of the data Use post-it’s

©2001 Southern Illinois University, Edwardsville All rights reserved. The Design War Room Walking the Wall Immersing yourself in the data Beyer & Holtzblat (1998), Contextual Design, Morgan Kaufmann, Page:204

©2001 Southern Illinois University, Edwardsville All rights reserved. Consolidating 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

©2001 Southern Illinois University, Edwardsville All rights reserved. Consolidating 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 stepU5U4 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 stepU5U4 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

©2001 Southern Illinois University, Edwardsville All rights reserved. A Consolidated Sequence Model General Activity LabelGoal of ActivitiesAbstract Step ActivityIntentAbstract step Find out about problemLearn about problems quickly Discover problems before users do Provide quick response Trigger: Find out about problem –Automated procedure –Someone reports problem Go to problem locationMake it possible to do a diagnosis and take action Go to the place where the problem can be solved Diagnose problemFind 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 ProblemFix problem at onceDecide if I can fix it: Attempt fit See if fix worked Try to figure out why fix didn’t work Call on helpGet 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 Beyer & Holtzblat (1998), Contextual Design, Morgan Kaufmann, Page:177

©2001 Southern Illinois University, Edwardsville All rights reserved. Consolidating 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

©2001 Southern Illinois University, Edwardsville All rights reserved. A Consolidated Artifact Model Beyer & Holtzblat (1998), Contextual Design, Morgan Kaufmann, Page:183