SBD: Activity Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,

Slides:



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

Chapter 11 Designing the User Interface
Systems Analysis and Design in a Changing World, Fourth Edition
User Interface Structure Design
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
CS305: HCI in SW Development Evaluation (Return to…)
User Interface Design Notes p7 T120B pavasario sem.
From requirements to design
Eventbook Satya Ram Twanabasu Eventbook What? An Android based Mobile App. using Social Networking APIs Who? Every mobile user specially.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #18.
User-centered Evaluation What is the purpose? –Determine if users can fulfill their goals, –Determine if users can complete tasks required to fulfill their.
IS 425 Enterprise Information LECTURE 4 Winter
Midterm Exam Review IS 485, Professor Matt Thatcher.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
Inspection Methods. Inspection methods Heuristic evaluation Guidelines review Consistency inspections Standards inspections Features inspection Cognitive.
1 CS 430 / INFO 430 Information Retrieval Lecture 24 Usability 2.
An evaluation framework
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
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.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
Chapter 13: Designing the User Interface
Chapter 14 Designing the User Interface
User Interface Design Process Lecture # 6. CS Structure  Understand the User Interface  Design the User Interface  Evaluate the User Interface.
Web Design and Patterns CMPT 281. Outline Motivation: customer-centred design Web design introduction Design patterns.
Human Interface Engineering1 Main Title, 60 pt., U/L case LS=.8 lines Introduction to Human Interface Engineering NTU Seminar Amy Ma HIE Global Director.
SBD: Activity Design Chris North CS 3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Information Design and Visualization
Evaluation Framework Prevention vs. Intervention CHONG POH WAN 21 JUNE 2011.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Chapter 11: An Evaluation Framework Group 4: Tony Masi, Sam Esswein, Brian Rood, & Chris Troisi.
1 The Web & Professional Communication English 3104.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Formative Evaluation cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
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.
User Interface Structure Design Chapter 11. Key Definitions The user interface defines how the system will interact with external entities The system.
Slide 1 Chapter 11 User Interface Structure Design Chapter 11 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman.
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.
Web Site Usability. Benefits of planning usability Increased user satisfaction, which translates directly to trust and brand loyalty Increased user productivity,
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
User interface design and human computer interaction Xiangming Mu.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
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.
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.
SBD: Information Design
User Interface Design Process Gabriel Spitz. Today  Understand the User Interface Design process  Gather info for designing a user interface for a vending.
SBD: Analyzing Requirements Chris North cs3724: HCI.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
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 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.
Introduction to Human Computer Interaction
SBD: Analyzing Requirements
SBD: Analyzing Requirements
Models, Metaphor, Paradigms
Formative Evaluation cs3724: HCI.
Presentation transcript:

SBD: Activity Design Chris North cs3724: HCI

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

Quiz What are the 5 steps of Requirement Analysis?

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

product data browsing searching ordering payment customer data USER ACTIVITIES = system functionality USER INTERFACE icons links menus layout navigation labels fields security feedback The Two Faces of HCI Design

SBD 1.Requirements analysis 2.Design: –Activity design –Information design –Interaction design

Problem scenarios: work from current practice to build new ideas Activity design scenarios: transform current activities to use new design ideas Activity Design Transform old activities to new activities that use technology Focus on system “what” not “how” “conceptual design”, “task-level design” Focus on improvements Iterative Goal: work from problems and opportunities of problem domain to envision new activities

Envisioning New Activities Effectiveness: meets needs Technology for technology’s sake? Generality vs. specific tasks Comprehension: understandable, predictable Mental models metaphors Satisfaction: accomplishment, motivating Automation? Social issues

Designer’s Model User’s Mental Model Cashier Systematic, logical, comprehensive Ad hoc, informal, incomplete The Web Cart

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 and Activity Design +/-

Activity Design Process 1.Design Space Brainstorm, creativity Metaphors, technology 2.Rework scenarios with new design ideas Particapatory design Coherence, completeness 3.Track claims +/-, rationale

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 + physical things + see lots of 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?