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

Hall of Fame/Shame Presentations

Homework Revisited

Project: Req’s Analysis revisited

Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders, field studies Usability specifications Activity scenarios Interaction scenarios iterative analysis of usability claims and re-design metaphors, information technology, HCI theory, guidelines formative evaluation 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 and Requirements Analysis

Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders, field studies Usability specifications Activity scenarios Interaction scenarios iterative analysis of usability claims and re-design metaphors, information technology, HCI theory, guidelines formative evaluation DESIGN ANALYZE PROTOTYPE & EVALUATE Functionality Look and feel

product data browsing searching ordering payment customer data SYSTEM FUNCTIONALITY LOOK & FEEL icons links menus layout navigation labels 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: 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. user control Individual vs group needs

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

Designer’s Model User’s Mental Model Cashier Systematic, logical, comprehensive Ad hoc, informal, incomplete The Web Cart +-+- Metaphors bridge the gap

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 – Reqs analysis review? Soccer mom: Shopping cart: + - Shelves/Aisles: + -

Metaphors for Grocery Shopping?

New activity scenario? Online grocery Soccer mom story:

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

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…

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.

The Morphological Box  Identify dimensions of the design space  Enumerate all possible solutions PBJ sandwich, on whole wheat, with butter

Grocery Shopping – design dimensions?

Grocery Shopping – design dimensions Online vs. Store Browse vs. Search Deliver vs. Pickup

Morph. Box for Grocery Shopping onlinestore Browse llbeankroegers Search Ebay, Pizza by phone Mcdonalds location navigation Possible new ways to grocery shop?

Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders, field studies Usability specifications Activity scenarios Interaction scenarios iterative analysis of usability claims and re-design metaphors, information technology, HCI theory, guidelines formative evaluation DESIGN ANALYZE PROTOTYPE & EVALUATE

Execution Action plan System goal Last month’s budget... ? Interpretation Perception Making sense GULF OF EVALUATION GULF OF EXECUTION Stages of Action in HCI Information design Interaction design Human- computer interaction Task goal

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?