The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #15.

Slides:



Advertisements
Similar presentations
Chapter 14: Usability testing and field studies
Advertisements

Task-Centered User Interface Design who are the users? what are the tasks? plagiarize! iterative design –rough descriptions, mock-ups, prototypes test.
CS305: HCI in SW Development Evaluation (Return to…)
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #4.
Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #21.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #18.
213: User Interface Design & Development Professor: Tapan Parikh TA: Eun Kyoung Choe
User Interface Testing. Hall of Fame or Hall of Shame?  java.sun.com.
Evaluation Methodologies
Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #3.
© 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.
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
» Teaching an online class, what takes up most of your time?
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
ESM Interface Re-Design HCI Undergraduate Project Team Bei Yang Derek Parham Wenyao Ho.
Requirements II: Task Analysis. Objectives By the end of the class, you will be able to… Write detailed task descriptions to inform design. Create scenarios.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Part 1-Intro; Part 2- Req; Part 3- Design  Chapter 20 Why evaluate the usability of user interface designs?  Chapter 21 Deciding on what you need to.
Human Computer Interaction
Usability Testing intro.12.ppt CS 121 “Ordering Chaos” “Mike” Michael A. Erlinger.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Usability testing. Goals & questions focus on how well users perform tasks with the product. – typical users – doing typical tasks. Comparison of products.
What is Usability? Usability Is a measure of how easy it is to use something: –How easy will the use of the software be for a typical user to understand,
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
Usability Testing Chapter 6. Reliability Can you repeat the test?
1 ISE 412 Usability Testing Purpose of usability testing:  evaluate users’ experience with the interface  identify specific problems in the interface.
Usability Testing: Role Playing as an Illustration Defining experimental tasks Recording stuff Identifying problems  changes Leading to A6 Presented by.
Chapter 8 Usability Specification Techniques Hix & Hartson.
Introduction To Engineering Bike Lab 1 – 4 Report Agenda: Lab Report Format Team Writing Outline Lab 1 Report.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #16.
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.
Lab Report Format: Steps of the Scientific Method.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #14.
IR 202 Research Methods This course aims to introduce students what is social research, what are the different types of research and the research process.
Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough CS352.
By Godwin Alemoh. What is usability testing Usability testing: is the process of carrying out experiments to find out specific information about a design.
June 5, 2007Mohamad Eid Usability Testing Chapter 8.
Prof. James A. Landay University of Washington Autumn 2006 User Testing November 30, 2006.
Usability Evaluation or, “I can’t figure this out...do I still get the donuts?”
UCI Library Website Chris Lee Archana Vaidyanathan Duncan Tsai Karen Quan.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #13.
Huddle Social Event Discovery Nadav Manager Brandon Design Joe User Testing Mike Development.
Day 1 & 2. Agenda  Logistics  About the Class  About Me  About You.
Learning Management System
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #20.
Day 8 Usability testing.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #11.
Avalon Science and Engineering Fair 2015 Let’s Get Started Science and Engineering Fair packets will go home this week. All 2 nd, 3 rd, 4 th and 5 th.
Do Now **Please put your phone in the caddy 
Information System Design Info-440
TIM 58 Chapter 3: Requirements Determination
Information System Design Info-440
Usability Evaluation, part 2
Informatics 121 Software Design I
SY DE 542 User Testing March 7, 2005 R. Chow
Information System Design Info-440
things to know and review…
Evaluation (cont.): Empirical Studies
Information System Design Info-440
User Testing November 27, 2007.
CS305, HW1, Spring 2008 Evaluation Assignment
Information System Design Info-440
HCI – Lesson 7 USABILITY Homework Prof. Garzotto.
Evaluation (cont.): Empirical Studies: The Thinkaloud
Presentation transcript:

The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #15

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 2 Agenda Usability testing –Video example –Assignment #4 –Continue with principles Lab –Bring your paper prototypes, notes & ideas

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 3 Admin Announcements –Will schedule some kind of Visio lab It will be very collaborative We’ll teach each other

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 4 Upcoming Next week –Read Nielsen, Chapters 5 & 6 –Heuristic evaluations Prototyping project –Bring prototypes to lab –1 st iteration of prototype (25 Nov) Quiz #4 –25 November –Chapter #6 only Assignment #4 –December 4

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 5 Review Usability –Purposes? Science Design Social Video excerpt –What did you learn?

The Information School of the University of Washington Video

The Information School of the University of Washington Assignment #4

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 8 Four parts Part I: –Heuristic evaluation Part II: –Task analysis Part III: –Task performance estimate Part IV: –Usability evaluation

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 9 Deliverable A usability report –Outline is given in assignment Target audience –Product design team, which includes business people, engineers, visual designer, and information architect Overall objective: –Understand the efficiency of finding movie times online

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 10 Part III: Objective Derive an estimate for how long it takes to discover movie times using: –Telephone –News paper

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 11 User goal Find the playing times for movie, M, at University District, Seattle, Washington, between 6-9pm on Thursday Movies are: –M1: 8 mile –M2: Harry Potter

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 12 Newspaper: Procedure Select newspaper Start state: –Newspaper folded/closed End state: –You find the exact time ‘Reset’ Newspaper

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 13 Telephone: Procedure Use this number: –Xxx Start state –Phone on hook End state –You find the exact time ‘Reset’ the phone

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 14 Data collection Each person in the class will generate this table: User IDTrialMethodTime Dgh-mem1news40 Dgh-mem2news67 Dgh-mem2tele40 Dgh-mem1tele67

The Information School of the University of Washington Part IV

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 16 Part IV: Main objective Determine which of three movie sites is the most usable The sites: –Yahoo: –Lycos: –MSN

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 17 User goal Find the playing times for movie, M, at University District, Seattle, Washington, between 6-9pm on Thursday Movies are: –M1: 8 mile –M2: Harry Potter

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 18 Experimental design Participant #1 –Complete goal for M1 –Complete goal for M2 Participant #2 –Complete goal for M2 –Complete goal for M1

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 19 Procedure Go to jump page – Have participant read task –Tell participant the movie & what site to use End state: –User tells you the time the movie is playing ‘Return’ to jump page

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 20 Part IV: Data collection Each person in the class will generate this table: User IDTrialMethodTime Dgh-P1m1Yahoo40 Dgh-P1m2Yahoo67 Dgh-P2m2Yahoo30 Dgh-P2m1Yahoo87

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 21 Everyone generates 8 records… User IDTrialMethodTime Dgh-mem1news40 Dgh-mem2news67 Dgh-mem2tele40 Dgh-mem1tele67 Dgh-P1m1Yahoo40 Dgh-P1m2Yahoo67 Dgh-P2m2Yahoo30 Dgh-P2m1Yahoo87

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 22 The GOAL: Class bar-chart (Avg. time to find movie info)

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 23 Select your site: Write your name on handout Yahoo MSN Lycos

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 24 Part I: Heuristic Evaluation Using Nielsen guidelines, carry out a heuristic evaluation of the movie site, M. Read chapter 5 of Nielsen

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 25 Part II: Task Analysis Suppose you are sitting on your couch and you decide "I want to go to a movie with my friend Joe". Develop a detailed task analysis for solving this goal. The goal is satisfied when you are sitting with Joe in the theatre.

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 26 Report format Executive summary –A maximum of two hundred words on what you did and what you learned The objective –Propose an objective for this assignment Heuristic evaluation –Present the heuristic evaluation Task analysis –Present the task analysis

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 27 Report format (cont) The participants –Describe briefly who the participants were The task –Describe the goal that you gave the participants and how you timed them Findings –Include the graph here, a discussion of it, and your conjectures about task completion times Issues and recommendations –List a maximum of three issues that you discovered and your recommendation for solving the issues

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 28 Report format (cont) Discussion of methods –Discuss what it was like to observe the users. Did anything surprise you? Did they change your understanding of the goal and tasks? How did the usability evaluation compare to the heuristic evaluation? References –If required Appendix A –Include a table showing the raw data

The Information School of the University of Washington Break

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 30 Reasons to test Develop understanding of user goals –Before beginning a project –You observe people working with systems –Goal: Identify tactics, strengths, weaknesses, etc. Competitive tests (X vs Y) –You believe a competitor is better than you –Determine which is more usable –Goal: Uncover best practices at competitor site

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 31 Reasons to test Alternative interfaces (X 1 Vs X 2) –You have two alternative versions of a UI –Goal: Determine which is the better direction Test-and-iterate –Iterative development process –Goal: You seek incremental improvement

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 32 Usability process 1.Decide on objectives 2.Decide on participant profile & develop scenario 3.Analyze system & make predictions 4.Decide on participant goals 5.Prompt participants to complete goals 6.Carefully observe 4-6 participants Identify critical incidents Measure performance (time, errors, etc.) 7.Debrief participants 8.Prioritize issues Team discussion Develop presentations, reports, etc.

The Information School of the University of Washington A huge number of details are important – We will consider only a few

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 34 Some details Human subject ethics Participants Creating good tasks Being a good moderator Think aloud protocols

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 35 Human subject ethics Guidelines –Acknowledge that that system is being tested, not the participant (remind repeatedly) –Tell the participant that she is free to leave at any time –Reveal who is watching & what is being recorded –Do not report results such that a participant is identified –Avoid telling the participant that he is making mistakes or doing things wrong –Acknowledge participants efforts but in a neutral fashion Bottom line: Treat people with great respect Read: Nielsen (pp ) *on quiz*

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 36 Participants Participant profile –Computer/net experience –Experience with system –Interests Example –You want to study an online teen magazine –Consider 15 year old girls who use IM Anyone else The most important decision to make

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 37 Creating good tasks Clear beginning and end states Easily stated Cover target areas of the system Consider –Find the 5-day weather forecast for Toronto –Here’s $ use eBay to buy something

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 38 Being a good moderator

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /20/2002) 39 Think aloud