Prototyping Lecture #4 - February 5th, 2008 213: User Interface Design and Development.

Slides:



Advertisements
Similar presentations
Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Advertisements

Design, prototyping and construction
Rapid Prototyping Dimensions and terminology Non-computer methods
Web E’s goal is for you to understand how to create an initial interaction design and how to evaluate that design by studying a sample. Web F’s goal is.
Human Computer Interaction
What is Design? Professor: Tapan Parikh TA: Eun Kyoung Choe
Prototyping. Introduction Low-fidelity prototyping High-fidelity prototyping Compromises in prototyping From design to implementation.
1 Why prototype? “…the value of prototypes resides less in the models themselves than in the interactions they invite.” Michael Schrage – Serious Play.
Scenarios and Personas Professor: Tapan Parikh TA: Eun Kyoung Choe
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
ISP 666 Week 6 Prototyping. Design a Solution From task to system From abstract to concrete Task Models UI Presentation evaluation Conceptual Model System.
COMP5047 – Design Prototyping and storyboards Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies Acknowledgement:
Prototyping Professor: Tapan Parikh TA: Eun Kyoung Choe
CS147 - Terry Winograd - 1 Lecture 9 – Prototyping Terry Winograd CS147 - Introduction to Human-Computer Interaction Design Computer Science Department.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
2/23/991 Low-fidelity Prototyping & Storyboarding SIMS 213, Spring ‘99 Professor James Landay, EECS Dept. February 23, 1999.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2007.
HCI revision lecture. Main points Understanding Applying knowledge Knowing key points Knowing relationship between things If you’ve done the group project.
Web Design cs414 spring Announcements Project status due Friday (submit pdf)
Spring /6.831 User Interface Design and Implementation1 Lecture 6: User-Centered Design GR1 (project proposal & analysis) released today, due.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
High-Fidelity Prototyping
Human Computer Interaction & Usability Prototyping Design & Prototyping HCI Prototyping.
Principles of User Centred Design Howell Istance.
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 (
1 DENIM: An Informal Web Site Design Tool Inspired by Observations of Practice CS 376 – Research Topics in HCI 11/01/2005 Tony Tulathimutte.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
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.
HCI Prototyping Chapter 6 Prototyping. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “prototyping” –Explain the.
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Storyboarding 1. Purpose of Storyboarding  To gain an early reaction from users on the concepts proposed for the application.  They are an effective.
UML & Prototyping. What is a prototype? A prototype is a small-scale model. It can be (among other things): a series of screen sketches a storyboard,
CSCD 487/587 Human Computer Interface Winter 2013 Lecture 17 Prototypes and Design.
COMP5047 – Design Prototyping and storyboards Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies Acknowledgements:
Fall 2002CS/PSY Rapid Prototyping Sketches, Storyboards, Mock-Ups and Scenarios Agenda Dimensions and terminology Non-computer methods Computer methods.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
1 Lecture 16 Prototyping Software Engineering. 2 Outline Definitions Uses of prototyping in the design process Prototyping approaches Prototyping “technologies”
Prototyping CSCI 4800 Spring 2007 Kraemer. Learning Goals Understand the uses of different types of prototypes for different kinds of designs and be able.
Prototyping. What is a prototype? In other design fields a prototype is a small- scale model: a miniature car a miniature building or town.
University of Washington HCDE 518 & INDE 545 Lo-Fidelity Prototyping HCDE 518 & INDE 545 Winter 2012 With credit to Jake Wobbrock, Dave Hendry, Andy Ko,
—————————————————————————————————————————— Design of Interactive Computational Media Sep.-Dec © , Ronald M. Baecker Slide 8.1 The Design.
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.
Software Engineering User Interface Design Slide 1 User Interface Design.
Prototyping 1. Design Document How express your design ideas. How express your design ideas. Key notions Key notions Cheap, FastCheap, Fast Flexibility.
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
1 Paper (low-fidelity) Prototypes. 2 When we are designing When we are thinking about design We are visualizing the interface inside our head (imaginary)
Prototyping. REVIEW : Why a prototype? Helps with: –Screen layouts and information display –Work flow, task design –Technical issues –Difficult, controversial,
Begin Class with More Studio. Introduction to Prototyping.
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. Today Wednesday Running A Paper Prototyping Session Paper Prototyping Video: Paper.
Overview Prototyping Construction Conceptual design Physical design Generating prototypes Tool support.
Creating a Google Drive Presentation By Ms. Rogers & Ms. Heskett.
Requirements gathering Storyboarding Prototyping
Design, prototyping and construction(Chapter 11).
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.
Stanford hci group / cs October 2007 An Overview of Design Process Scott Klemmer tas: Marcello Bastea-Forte, Joel Brandt,
Digital Media & Interaction Design LECTURE 4+5. Lecture 4+5 Draw requirement + Prototyping.
Prototyping & Design CS 352.
Recall The Team Skills Analyzing the Problem (with 5 steps)
Introduction to Prototyping
Prototyping.
Design, prototyping and construction
Design, prototyping and construction
Presentation transcript:

Prototyping Lecture #4 - February 5th, : User Interface Design and Development

Today’s Outline 1)Low-fidelity techniques 2)High-fidelity techniques 3)Role of a Prototype

Design Prototype Evaluate

Design Iteration The goal is to test as many ideas as possible Formative as opposed to summative evaluation - especially with early stage prototypes

Low-Fidelity Prototypes Provide an early, concrete representation of a design idea Provide hands-on experience for all stakeholders (design teams, users, customers, etc.) Everyone understands their limitations Can be made cheaply, and can be fun to make and use

Lo-Fi Techniques Scenarios Storyboards Design Sketch Paper Flipbook Cardboard / Foam Mock-up

Pre-history Previously, “user” features were described as functional requirements, and metrics of usability The system should provide the following ten user functions The X function should be executed by an average college-educated user in a maximum of ten seconds, with an acceptable error rate of 0.1%

Limitations Focus on quantitative, as opposed to qualitative, requirements - which are not always germane Is the time it takes to download a song the most important criterion for judging an online music store? It is also difficult to assess quantitative metrics until relatively late in the design process

Scenarios “Scenarios are stories about people and their activities” Focuses developers on the most important user activities that should be supported Does not focus on implementation Can either describe current practice, or a future hypothetical scenario

Example Scenario John wants to take notes while in class. Even though the slides will be posted online later, he wants to make sure he captures the most important points. Before the professor starts the lecture, he starts the note-taking application on his phone. The application automatically notes the current date, time and class. During the class he can press one of two buttons - to start recording audio or to take a picture. After recording, the application allows him to tag the recording with keywords. Later, when he is home, he can review his notes, synchronized with the powerpoint slides downloaded from the course web site. He can search by keyword, follow the lecture linearly, or sped up in time.

Elements of a Scenario Agents / Actors Setting Goals / Objectives Actions / Events

Example Scenario John wants to take notes while in class. Even though the slides will be posted online later, he wants to make sure he captures the most important points. Before the professor starts the lecture, he starts the note-taking application on his phone. The application automatically notes the current date, time and class. During the class he can press one of two buttons - to start recording audio or to take a picture. After recording, the application allows him to tag the recording with keywords. Later, when he is home, he can review his notes, synchronized with the powerpoint slides downloaded from the course web site. He can search by keyword, follow the lecture linearly, or sped up in time.

Example Scenario John wants to take notes while in class. Even though the slides will be posted online later, he wants to make sure he captures the most important points. Before the professor starts the lecture, he starts the note-taking application on his phone. The application automatically notes the current date, time and class. During the class he can press one of two buttons - to start recording audio or to take a picture. After recording, the application allows him to tag the recording with keywords. Later, when he is home, he can review his notes, synchronized with the powerpoint slides downloaded from the course web site. He can search by keyword, follow the lecture linearly, or sped up in time.

Ways to Present a Scenario Text paragraph Storyboard (Comic book) Video

Source:

Source:

Video Scenario Apple’s Knowledge Navigator (1987) Source: Apple Computer,

Lo-Fi Techniques Scenarios Storyboards Design Sketch Paper Flipbook Cardboard / Foam Mock-up

Slide from Jake Wobbrock

Two strips of paper Post-It® notes too

Slide from Jake Wobbrock

Materials for Lo-Fi Prototyping Large, heavy white paper Colored paper Thumbtacks Cardboard or foam core Index cards Tape or glue Pencils, pens, markers Overhead transparencies Scissors Exacto knife Slide from Jake Wobbrock

Hi-Fidelity Prototypes Provide increasing amounts of functionality and refinement Usually involve some amount of programming and interactivity Can provide functionality to be empirically tested with users Take more time and resources to build Users can be distracted by limitations

Tools for Hi-Fidelity Prototyping Powerpoint Flash Director Visual Basic Hypercard Photoshop D/HTML Video Phidgets Slide from Jake Wobbrock

Source: Kelly, Maureen. “Interactive Prototypes with PowerPoint”. (adapted from Scott Klemmer)

Source: Brunette, Kynthia, et. al. “Meeteetse”. Indiana University. Student Contest Entry. CHI 2005 (adapted from Scott Klemmer)

Source: IDEO (adapted from Scott Klemmer)

Slide from Jake Wobbrock

Source: Hisaab Project

32

33

34

Wizard of Oz Technique Human operator mimics advanced computational functionality –Speech recognition, gesture recognition, vision, etc. Allows for testing advanced functionality without full implementation

The Rights of a Prototype I am Disposable I am easy to Change I do not need to be Complete I do not need to be Updated Adapted from Scott Klemmer

Two Key Questions What do I want to Learn? What do I want to Communicate? Adapted from Scott Klemmer

Prototyping Techniques Scenario  Storyboard  Video Design Sketch  Screenshot Paper  Cardboard  Foam Mockups Wizard of Oz Interactive Prototypes Vision Experience Lo-Fi Hi-Fi

Kinds of Prototypes Role - “are built primarily to answer questions of what an artifact could do for a user” Look and Feel - “explore and demonstrate options for the concrete experience” Implementation - “experiments… to demonstrate to their organization the technical feasibility of the artifact” Integration - “verify that the design is complete and coherent, and to find synergy” Source: Houde and Hill, “What do Prototypes Prototype”

Cultures of Prototyping “Small, entrepreneurial companies tend to be prototype-driven” “Companies that manage a large installed base of users tend to be specification-driven” “Organizations intending to be innovative need to move from specification-driven prototypes to prototype-driven specifications" Source: Michael Schrage, “Cultures of Prototyping”

Testing Prototypes Heuristic Evaluation Focus Group Presentation Cognitive Walkthrough Think Aloud Usability Testing etc… more on this later!

For Next Time Assignment 1 - present your scenarios and personas in class on Feb 17th Assignment 2 will be posted soon Waitlisted students should be enrolled Guest lecture by Bill Buxton on Feb 10 - come prepared - attend his talk, read his writings, be ready to ask questions

Show and Tell Further reactions to the last lecture?