Scenario-Based Usability Engineering Chris North cs3724: HCI.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

CSCI 4163 / CSCI 6610, Winter 2014 Human-Computer Interaction web.cs.dal.ca/~hawkey/4163 Dr. Kirstie Hawkey,
Claims Analysis: Example ‘Hall of Fame/Shame’ Presentation Chris North CS 3724: Intro to HCI.
User Interface Design Notes p7 T120B pavasario sem.
From requirements to design
Department of Computer Science
CS CS 5150 Software Engineering Lecture 12 Usability 2.
Empirical Methods in Human- Computer Interaction.
IS 425 Enterprise Information LECTURE 4 Winter
CS 3724 Introduction to HCI Dr. Scott McCrickard McBryde 623
IS 425 Enterprise Information I LECTURE 4 Autumn  2004 Norma Sutcliffe.
CS 5764 Information Visualization Dr. Chris North.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Design Process …and the project.
© Lethbridge/Laganière 2001 Chapter 7: Focusing on Users and Their Tasks1 7.1 User Centred Design (UCD) Software development should focus on the needs.
Analytical Evaluations 2. Field Studies
Chapter 13: Designing the User Interface
CS 235: User Interface Design January 22 Class Meeting
CS 3724: Introduction to Human Computer Interaction Chris North Jason Lee Szu-Chia Lu.
Human Computer Interaction & Usability Prototyping Design & Prototyping HCI Prototyping.
CS110/CS119 Introduction to Computing (Java)
SBD: Activity Design Chris North CS 3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Evaluation: Controlled Experiments Chris North cs3724: HCI.
Information Design and Visualization
Principles of User Centred Design Howell Istance.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Guidelines and Prototypes CS774 Human Computer Interaction Spring 2004.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
CS 235: User Interface Design August 25 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
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.
Design Chris North cs3724: HCI. Quiz What are the 3 steps in producing a UI?
Today Thursday Introduction to HCI and Contextual Design Course Introduction CS 321 Human-Computer Interaction Jerry B. Weinberg Reading: CD: Chapter.
Formative Evaluation cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
SBD: Interaction Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
INTRO TO USABILITY Lecture 12. What is Usability?  Usability addresses the relationship between tools and their users. In order for a tool to be effective,
Usability Testing Chris North cs3724: HCI. Presentations karen molye, steve kovalak Vote: UI Hall of Fame/Shame?
SBD: Analyzing Requirements Chris North CS 3724: HCI.
Scenario-Based Usability Engineering 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.
Scenario-Based Usability Engineering Chris North CS 3724: HCI.
Dr. H. Rex Hartson Fall 2003 Introduction to the Course Copyright © 2003 H. Rex Hartson and Deborah Hix. CS5714 Usability Engineering.
Presentations Project Teams (practice presenting together) 5% of grade 5 minutes STRICTLY ENFORCED 3-4 PowerPoint slides – to Kibum, bring on CD,
Early Design Process Chris North cs3724: HCI. Presentations mohamed hassoun, aaron dalton Vote: UI Hall of Fame/Shame?
EVALUATION PROfessional network of Master’s degrees in Informatics as a Second Competence – PROMIS ( TEMPUS FR-TEMPUS-JPCR)
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Course Introduction Wednesday Introduction.
SBD: Information Design
SBD: Activity Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Cs3724: Introduction to HCI Dr. Chris North GTA: Purvi Saraiya.
CS 3724 Lecture 2: Scenario-Based Design Section 2 CRN MW 2:30-3: McB.
CS 5714 Usability Engineering Dr. Scott McCrickard McBryde 623
SBD: Analyzing Requirements Chris North cs3724: HCI.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
SBD: Interaction Design Chris North CS 3724: HCI.
Scenario-Based Usability Engineering 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.
Presentations Project Teams (practice presenting together) 5% of grade 5 minutes STRICTLY ENFORCED 3-4 PowerPoint slides – to Jacob, bring on CD,
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
cs3724: Introduction to HCI
SBD: Analyzing Requirements
SBD: Analyzing Requirements
Scenario-Based Usability Engineering
Information Design and Visualization
Formative Evaluation cs3724: HCI.
Presentation transcript:

Scenario-Based Usability Engineering Chris North cs3724: HCI

Homework #0: UI Analysis See website Pick a movie of your choice Task: find a convenient playing time and location Use 3 different systems: TELL Write down the time it takes you for each Bring your times to class on Thursday

Homework #0 Qualitative discussion Usability problems, errors, access, alternate tasks, … Quantitative discussion Data averages, min, max Data visualization Statistics, t-tests, …

Myth The user interface is tacked on at the end of the project

The Changing Face of Computer Use 1960’s 1970’s 1980’s 1990’s Professional programmers, “software psychology” Business professionals, mainframes, command-line Large, diverse user groups, “the computer for the rest of us” World Wide Web and more, information access & overload Ubiquitous computing, diversity in task, device, …

Newton vs. Palm Newton Palm

User Interface Metrics Ease of learning Ease of use User satisfaction Not “user friendly”

Tradeoffs Optimization? Examples Identify tradeoffs Choose based on design goals Track tradeoffs for rationale

Using “Scenarios” Marissa was not satisfied with her class today on gravitation and planetary motion. She is not certain whether smaller planets always move faster or how a larger or denser sun would alter the possibilities for solar systems. She stays after class to speak with Ms. Gould, but she isn’t able to pose these questions clearly, so Ms. Gould suggests that she re-read the text and promises more discussion tomorrow. Stories about people and their needs, activities A problem scenario describing current situation:

Marissa, a 10th-grade physics student, is studying gravity and its role in planetary motion. She goes to the virtual science lab and navigates to the gravity room. In the gravity room, she discovers two other students, Randy and David, already working with the Alternate Reality Kit, which allows students to alter various physical parameters (such as the universal gravitational constant) and then observe effects in a simulation world. The three students, each of whom is from a different school in the county, discuss possible experiments by typing messages from their respective personal computers. Together they build and analyze several solar systems, eventually focusing on the question of how comets can disrupt otherwise stable systems. They capture data from their experiments and display it with several visualization tools, then write a brief report of their experiments, sending it for comments to Don, another student in Marissa’s class, and Mr. Arkins, Randy’s physics teacher. A design scenario describing our initial vision:

Scenario Elements Setting Actors (people, users) Task goals (what I want to achieve) Plans (how I will accomplish it) Actions (do it) Events (system response) Evaluation(is that what I wanted?)

Advantages of Scenarios

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

Iterative Fuzzy -> clear

Iterative Fuzzy -> clear

Iterative Sometimes “design is radically transformational”

Summary Measurable Metrics! Tradeoffs Scenarios, elements Scenario-based UE process Iterative assignment: Download & install java sdk1.4, Borland JBuilder Read Ch 2

Presentations Groups of 2 5 minutes, 2-3 slides Pick UI of your choice (software or real-world) UI critique Scenarios/tasks Good Bad Redesign ideas? Vote: UI Hall of Fame/Shame

Fast Food Drive-Thru Menus Scenarios: College student hungry Get food, get out. FAST! Often: sandwich, fries, drink Typically: Not sure what I want Sometimes: Know what I want Passengers want food too Limited budget

The Good All in one view Organized by categories Tabular format: left alligned, prices alligned Combo meals (high frequency) Get price before proceeding Some: feedback on order Need picture!

The Bad See menu too late Passengers cant see menu Passengers must order thru driver Winter: brrrrr… Small Redesign ideas: More menus back in line Menu on both sides of car Microphone on both sides Radical: cell phone, in-car UI

The Ugly I can’t understand a word they say They cant hear me over my ’87 VW