SBD Activity Design CS 3724 HCI Chris North
SBD: Activity Design CS 3724 - HCI Chris North Usability Engineering - Chapter 3
Hall of Fame/Shame Presentations • http: //courses. cs. vt. edu/~cs 3724/fall 2006/schedule. html
HW#1 Revisited
ANALYZE analysis of stakeholders, field studies Problem scenarios claims about current practice DESIGN metaphors, information technology, HCI theory, guidelines Activity scenarios Information scenarios iterative analysis of usability claims and re-design Interaction scenarios PROTOTYPE & EVALUATE summative evaluation Usability specifications formative evaluation
Root concept: vision, rationale, assumptions, stakeholders SBD and Requirements Analysis Field studies: workplace observations, recordings, interviews, artifacts Summaries: stakeholder, task, and artifact analyses, general themes 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
ANALYZE analysis of stakeholders, field studies Problem scenarios claims about current practice DESIGN metaphors, information technology, HCI theory, guidelines Activity Functionality scenarios Information scenarios Look and feel iterative analysis of usability claims and re-design Interaction scenarios PROTOTYPE & EVALUATE summative evaluation Usability specifications formative evaluation
EM LITY T S SY IONA CT N FU customer data Activity Design The Two Faces of HCI Design ordering product data searching browsing payment Information & Interaction Design LOOK & FEEL icons security links menus layout navigation labels fields feedback
SBD: Activity Design Goal: work from problems and opportunities of problem domain to envision new activities • Transform old activities to new Problem scenarios: work from current practice to build new ideas activities that use technology • Focus on system “what”, not “how” (why? ) “conceptual design”, “task-level design” • Focus on improvements • Iterative Activity design scenarios: transform current activities to use new design ideas
Problem claims: look for design ideas that address negatives, but keep positives +/- SBD: Activity Design Problem scenarios: work from current practice to build new Activity design space: brainstorm implications of metaphors and technology Activity design scenarios: transform current activities to use new design ideas Claims analysis: identify, illustrate, and document design features with key implications +/- HCI knowledge about activity design
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
Metaphors bridge the gap + - User’s Mental Model Designer’s Model The Web Cart Cashier Systematic, logical, comprehensive Ad hoc, informal, incomplete
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? •
ANALYZE analysis of stakeholders, field studies Problem scenarios claims about current practice DESIGN metaphors, information technology, HCI theory, guidelines Activity scenarios Information scenarios iterative analysis of usability claims and re-design Interaction scenarios PROTOTYPE & EVALUATE summative evaluation Usability specifications formative evaluation
Stages of Action in HCI Information design Interpretation Making sense GULF OF EVALUATION Perception Last month’s budget. . . ? Humancomputer interaction Task goal Interaction design System goal GULF OF EXECUTION Action plan Execution
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!
- Slides: 24