Prof. James A. Landay University of Washington Autumn 2008 Low-fi Prototyping November 4, 2008.

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Rapid Prototyping Dimensions and terminology Non-computer methods
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Feb 23, 2006.
DENIM: Finding a Tighter Fit with Web Design Practice James Lin, Mark W. Newman, Jason I. Hong, James A. Landay April 6, 2000 CHI 2000, The Hague
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 24, 2004.
ISP 666 Week 6 Prototyping. Design a Solution From task to system From abstract to concrete Task Models UI Presentation evaluation Conceptual Model System.
Paper Prototyping A tool for iterative design Wai Yong Low.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Feb 20, 2003.
Prototyping Professor: Tapan Parikh TA: Eun Kyoung Choe
SIMS 213: User Interface Design & Development Marti Hearst Tues Feb 20, 2001.
Design Process: Implement Low Fidelity Prototyping Christine Robson & Bryan Tsao September 27, 2007.
SIMS 202 Information Organization and Retrieval Prof. Marti Hearst and Prof. Ray Larson UC Berkeley SIMS Tues/Thurs 9:30-11:00am Fall 2000.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Feb 21, 2002.
2/23/991 Low-fidelity Prototyping & Storyboarding SIMS 213, Spring ‘99 Professor James Landay, EECS Dept. February 23, 1999.
Rapid Prototyping Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development February 25, 1999.
I213: User Interface Design & Development Marti Hearst Thurs, Feb 22, 2007.
Prototyping Material Drawn from: James Landay, Berkeley Univ. John Kelleher, IT Sligo.
Prof. James A. Landay University of Washington Autumn 2006 Rapid Prototyping November 16, 2006.
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
Prof. James A. Landay University of Washington Autumn 2012 USER INTERFACE DESIGN + PROTOTYPING + EVALUATION Early Stage Prototyping.
Design, prototyping and construction Readings: ID-book, Chap. 11 (through 11.3) Also, Prototyping for Tiny Fingers
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Low-fi Prototyping. CSE490f - Autumn 2006User Interface Design, Prototyping, and Evaluation2 Hall of Fame or Shame? Password dialog in Eudora Pro for.
1 Low-fidelity Prototyping. 2 Interface Hall of Shame or Fame? PowerBuilder List of objects with associated properties.
DMS 546/446 INTERFACE DESIGN AL LARSEN – SPRING 2008 PAPER PROTOTYPING Lecture draws from multiple sources, including: Jakob Nielsen, Shawn Medero (
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
HCI 특론 (2010 Spring) Low-fi Prototyping. 2 Interface Hall of Shame or Fame? Amtrak Web Site.
Prof. James A. Landay Computer Science Department Stanford University Spring 2015 CS 377 E : ENGELBART ’ S UNFINISHED LEGACY : DESIGNING SOLUTIONS TO GLOBAL.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
June 2004 User Interface Design, Prototyping, and Evaluation 1 Outline Low-fi prototyping Wizard of Oz technique Informal UI prototyping tools Hi-fi prototyping.
COMP5047 – Design Prototyping and storyboards Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies Acknowledgements:
Rapid Prototyping. 2 Hall of Fame or Shame? 3 Hall of Shame.
CS298: HCI Design Clinics Paper Prototyping 03/01/10 Berkel ey UNIVERSITY OF CALIFORNIA.
Prof. James A. Landay University of Washington Autumn 2008 Rapid Prototyping November 10, 2008.
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,
Usability When you design the userinterface to a computer system, you decide which screens the system will show, what exactly will be in each screen and.
Prof. James A. Landay University of Washington Autumn 2008 Video Prototyping October 14, 2008.
Prototyping. What is a prototype? In other design fields a prototype is a small- scale model: a miniature car a miniature building or town.
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
1 Human Computer Interaction Week 7 Prototyping. 2 Introduction Prototyping is a design technique where users can be involved in testing design ideas.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Running A Paper Prototyping Session CS 321 Human-Computer Interaction.
Prof. James A. Landay University of Washington Autumn 2007 Video Prototyping October 16, 2007.
Prototyping. REVIEW : Why a prototype? Helps with: –Screen layouts and information display –Work flow, task design –Technical issues –Difficult, controversial,
Prof. James A. Landay University of Washington Autumn 2007 Rapid Prototyping November 13, 2007.
Prof. James A. Landay University of Washington Spring 2008 Web Interface Design, Prototyping, and Implementation Low-fi Prototyping April 24, 2008.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Wednesday Running A Paper Prototyping Session Paper Prototyping Video: Paper.
Paper Prototyping Source: Paper Prototyping a method of brainstorming, designing, creating, testing, refining and communicating.
Low-fidelity Prototyping. Outline Low-fidelity prototyping Wizard of OZ technique Informal user interfaces Sketching user interfaces electronically Informal.
Prof. James A. Landay Richard Davis Kate Everitt University of Washington Autumn 2004 UW Undergraduate HCI Projects A CSE 490jl Overview December 9, 2004.
Prof. James A. Landay University of Washington CSE 440 USER INTERFACE DESIGN + PROTOTYPING + EVALUATION February 14, 2013 Early Stage Prototyping.
Prof. James A. Landay University of Washington Autumn 2007 Low-fi Prototyping October 25, 2007.
HCI 특론 (2007 Fall) Low-fi Prototyping. 2 Hall of Fame or Shame? Password dialog in Eudora Pro for Mac.
Low-fi Prototyping. CSE490f - Autumn 2006User Interface Design, Prototyping, and Evaluation2 Hall of Fame or Shame? Password dialog in Eudora Pro for.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday CS 321 Human-Computer Interaction Paper Prototyping Video: Paper Prototyping.
Prof. James A. Landay University of Washington Winter 2009 Introduction & Course Overview CSE 441 – Advanced HCI January 6, 2009.
Prof. James A. Landay University of Washington Winter 2007 Video Prototyping January 22, 2007.
 refers to the overall experience a user has with a product. This experience doesn’t stop at the use of the product but starts with the advertising and.
Design for usability E6: Human Factors Design IB Technology.
Rapid Prototyping Only got through Topiary. Split into two lectures.
Low-fi Prototyping November 2, 2006
Prototyping.
Introduction to Prototyping
Low-fidelity Prototyping
Prototyping.
Rapid Prototyping Sketches, Storyboards, Mock-Ups and Scenarios
Low-fidelity Prototyping
Early Stage (lo-fi & med-fi) Prototyping
Presentation transcript:

Prof. James A. Landay University of Washington Autumn 2008 Low-fi Prototyping November 4, 2008

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation2 Interface Hall of Shame or Fame? Amtrak Web Site

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation3 Interface Hall of Fame/Shame! Amtrak Web Site Good –tells you what’s wrong –gets your attention Bad –doesn't label where to fix –tells you that you made an error, because you didn’t know their codes

Prof. James A. Landay University of Washington Autumn 2008 Low-fi Prototyping November 4, 2008

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation5 Outline Review midterm course survey Low-fi prototyping Wizard of Oz technique Informal UI prototyping tools Go over Low-fi assignment (#6)

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation6 Midterm Course Survey Things you like! Teaching with examples Slides & other materials online Interactive lectures –especially on candy days Project work focuses on lecture material Readings tied to lectures

Midterm Course Survey Areas to Improve In class workshop with early feedback & help –we have one this Thursday, one after the midterm, and one at the end of course, but it sound like in the future I should have another one earlier (after ESM/TA?) Better communication about non-graded parts of course –e.g., web site. Usually in final presentation grade. We will create a web site grading FAQ and present this earlier in course next time Emphasize and define key points, terms, concepts earlier –too late now, but can I get examples for future? Pre-work/troubleshoot technical aspects before course –we did pre-work phone/ESM, but it IS research software. Prefer avoiding? Clarify grading criteria –Try to pretty explicit on each assignment. Examples would help me know where you need more. Remember, there is not a “right” or “best” answer as in a math or programming course. CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation7

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation8 Fidelity in Prototyping Fidelity refers to the level of detail High fidelity? –prototypes look like the final product Low fidelity? –artists renditions with many details missing

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation9 Why Use Low-fi Prototypes? Traditional methods take too long –sketches  prototype  evaluate  iterate Can instead simulate the prototype –sketches  evaluate  iterate –sketches act as prototypes designer “plays computer” other design team members observe & record Kindergarten implementation skills –allows non-programmers to participate

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation10 Hi-fi Prototypes Warp Perceptions of the tester/reviewer –representation communicates “finished” comments focus on color, fonts, & alignment Time –encourage precision specifying details takes more time Creativity –lose track of the big picture

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation11 The Basic Materials Large, heavy, white paper (11 x 17) 5x8 in. index cards Post-its Tape, stick glue, correction tape Pens & markers (many colors & sizes) Overhead transparencies Scissors, X-acto knives, etc.

from “Prototyping for Tiny Fingers” by Rettig 12CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation

CSE440 - Autumn User Interface Design, Prototyping, and Evaluation

ESP CSE440 - Autumn User Interface Design, Prototyping, and Evaluation

April 24, CSE 490 L - Spring 2008

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation16 Constructing the Model Set a deadline –don’t think too long - build it! Draw a window frame on large paper Put different screen regions on cards –anything that moves, changes, appears/disappears Ready response for any user action –e.g., have those pull-down menus already made Use photocopier to make many versions

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation17 Constructing the Model

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation18 Constructing the Model

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation19 Constructing the Model

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation20 Constructing the Model

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation21 Constructing the Model

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation22 Preparing for a Test Select your “customers” –understand background of intended users –use a questionnaire to get the people you need –don’t use friends or family I think existing “customers” are OK (Rettig disagrees) Prepare scenarios that are –typical of the product during actual use –make prototype support these (small, yet broad) Practice to avoid “bugs”

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation23 Conducting a Test Four testers (minimum) –greeter – puts users at ease & gets data –facilitator – only team member who speaks gives instructions & encourages thoughts, opinions –computer – knows application logic & controls it always simulates the response, w/o explanation –observers – take notes & recommendations Typical session is 1 hour –preparation, the test, debriefing Read the Gommol paper (1 page) for details on conducting a test

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation24 Conducting a Test

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation25 Evaluating Results Sort & prioritize observations –what was important? –lots of problems in the same area? Create a written report on findings –gives agenda for meeting on design changes Make changes & iterate

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation26 Advantages of Low-fi Prototyping Takes only a few hours –no expensive equipment needed Can test multiple alternatives –fast iterations number of iterations is tied to final quality Almost all interaction can be faked

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation27 Wizard of Oz Technique Faking the interaction. Comes from? –the film “The Wizard of OZ” “the man behind the curtain” Long tradition in computer industry –e.g., prototype of a PC w/ a VAX behind the curtain Much more important for hard to implement features –speech & handwriting recognition

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation28 Problems with Low-fi Prototypes “Computer” inherently buggy Slow compared to real app –timings not accurate Hard to implement some functionality –pulldowns, feedback, drag, viz … Won’t look like final product –sometimes hard to recognize widgets End-users can’t use by themselves –not in context of user’s work environment

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation29 Informal UI Prototyping Tools Support advantages of low-fi paper prototypes –brainstorming consider different ideas rapidly do not require specification of details –incomplete designs need not cover all cases, just illustrate important examples Add advantages of electronic tools –evolve easily –support for “design memory” –transition to other electronic tools –allow end-user interaction

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation30 Summary Low-fi testing allows us to quickly iterate –get feedback from users & change right away Informal prototyping tools bridge the gap between paper & high-fi tools

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation31 Further Reading Prototyping Books –Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces, by Carolyn Snyder, Morgan Kaufmann, 2003Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces Articles –“Prototyping for Tiny Fingers” by Marc Rettig, in Communications of the ACM, 1994“Prototyping for Tiny Fingers” –“Using Paper Prototypes to Manage Risk” by Carolyn Snyder, Paper Prototypes to Manage Risk” –“The Perils of Prototyping” by Alan Cooper,“The Perils of Prototyping” Web Sites –dub Group web site, for DENIM & SUEDE downloads, Group –InfoDesign Toolkit, Toolkithttp://

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation32 Lo-fi Prototyping Assignment Due: Thur. 11/13 Presentation by new team member Get industry mentor involved –you are not required to do everything they say, simply to give you a resource Make sure to use new participants Two good reports from CSE 440, Au07 –What’s HappeningWhat’s Happening –TripMeTripMe Questions?

CSE440 - Autumn 2008User Interface Design, Prototyping, and Evaluation33 Next Time In class work on project Come to class and I will move around between the teams giving feedback