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

Slides:



Advertisements
Similar presentations
Chapter 5 Development and Evolution of User Interface
Advertisements

Requirements gathering
Chapter 11 Designing the User Interface
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
CS305: HCI in SW Development Evaluation (Return to…)
From requirements to design
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #18.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
Identifying needs and establishing requirements Chapter 7b.
An evaluation framework
Day 9 Navigation Heuristic evaluation. Objectives  Look at some simple rules on navigation  Introduction to Heuristic Evaluation.
A New Paradigm for E-Groceries IS 485, Professor Matt Thatcher.
Information architecture Summary Natalia Shatokhina CS575 Spring 2010.
HEC Lausanne > HCI > March 2005 Scenario-Based Design of Interactive Software Université de Lausanne Ecole des Hautes Etudes Commerciales (HEC) Introduction.
Chapter 13: Designing the User Interface
CS 3724: Introduction to Human Computer Interaction Chris North Jason Lee Szu-Chia Lu.
Web Design and Patterns CMPT 281. Outline Motivation: customer-centred design Web design introduction Design patterns.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
SBD: Activity Design Chris North CS 3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Information Design and Visualization
Tietojärjestelmien peruskurssi Systeemisuunnittelu ja prototyyppimenetelmä Malin Brännback.
Evaluation Framework Prevention vs. Intervention CHONG POH WAN 21 JUNE 2011.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
SBD: Interaction Design Chris North CS 3724: HCI.
HCI Prototyping Chapter 6 Prototyping. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “prototyping” –Explain the.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
 What is involved in Interaction Design? › What is a user-centered approach? › Four basic activities  Some practical issues › Who are the users? › What.
Formative Evaluation cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Chapter 6: NavigationCopyright © 2004 by Prentice Hall 6. Navigation Design Site-level navigation: making it easy for the user to get around the site Page-level.
Scenario-Based Usability Engineering Chris North cs3724: HCI.
SBD: Interaction Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Level 2 Prepared by: RHR First Prepared on: Nov 23, 2006 Last Modified on: Quality checked by: MOH Copyright 2004 Asia Pacific Institute of Information.
User interface design and human computer interaction Xiangming Mu.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
CS 3724 Introduction to Human Computer Interaction Section 2 CRN MW 2:30-3: McB.
SBD: Analyzing Requirements Chris North CS 3724: HCI.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
January 24-25, 2013 Igsummit.weebly.com Playing to build great projects from unknown needs Jorge Zavala Chief Disruptive Officer Kinnevo San Jose, CA
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.
Human Computer Interaction
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
Early Design Process Chris North cs3724: HCI. Presentations mohamed hassoun, aaron dalton Vote: UI Hall of Fame/Shame?
SBD: Information Design
SBD: Activity Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Information Architecture & Design Week 9 Schedule - Web Research Papers Due Now - Questions about Metaphors and Icons with Labels - Design 2- the Web -
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Contextual Inquiry & Intro to Ethnography Introduction to HCI & Contextual.
SBD: Analyzing Requirements Chris North cs3724: HCI.
Supporting the design of interactive systems a perspective on supporting people’s work Hans de Graaff 27 april 2000.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
SBD: Interaction Design Chris North CS 3724: HCI.
CS 3724: Introduction to Human Computer Interaction Chris North Regis Kopper.
CS 3724 Usability Engineering Section 2 CRN MW 2:30-3: McB.
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
CS 3724 Introduction to Human Computer Interaction Section 1 CRN TuTh 5:00-6: McB.
Elaboration popo.
INF385G: Topic Discussion Huang, S. C.
Muneo Kitajima Human-Computer Interaction Group
Design Thinking.
Introduction to Human Computer Interaction
CS 522: Human-Computer Interaction Usability and HCI Topics
SBD: Analyzing Requirements
SBD: Analyzing Requirements
Information Design and Visualization
Formative Evaluation cs3724: HCI.
Presentation transcript:

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

Hall of Fame/Shame Presentations

HW#1 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. control Individual vs group needs

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

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:

Grocery shopping? Soccer mom: Screaming kids Browsing strategy search strategy weekly repeats Shopping cart: + 1 slot for 1 kid + Pile stuff, big stuff underneath - >1 kid? - push Shelves + see lots of stuff fast - hard to find stuff - lots of walking

metaphors Pizza delivery + stay home - no browsing Cookbook + meal oriented - customization? Vending machine Menu for search stuff + Automating retrieval - literacy?

new scenario Online grocery? Soccer mom: Puts screaming kids outside Repeating purchases, template Search items quickly Linked recommendations: beer + diapers Browsing?

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

Grocery shopping?

Grocery Shopping? Online vs. Store Browse vs. Search Deliver vs. Pickup

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? Remember Glenn Fink!