SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 18, 2005.

Slides:



Advertisements
Similar presentations
The IB MYP Design Cycle….
Advertisements

Assignment Tasks. CriteriaMarksMaximum Length Suggested finishing date Description of users and personas52 pages18 February Task analysis and scenarios52.
Preparing Students for Online Learning
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.
CPSC 481 Foundations and Principles of Human Computer Interaction
Department of Computer Science
1 Software Maintenance and Evolution CSSE 575: Session 1, Part 1 Course Introduction Steve Chenoweth Office Phone: (812) Cell: (937)
Semester in review. The Final May 7, 6:30pm – 9:45 pm Closed book, ONE PAGE OF NOTES Cumulative Similar format to midterm (probably about 25% longer)
Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.
Design Analysis of Everyday Objects IS 485, Professor Matt Thatcher.
Introduction to the Course Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development 19, 1999.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Feb 26, 2004.
213: User Interface Design & Development Professor: Tapan Parikh TA: Eun Kyoung Choe
CS 485/515 General course outline Design for people – theory and vocabulary Just enough psychology Task-centered procedure for user interface design. Tools.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 20, 2004.
Heuristic Evaluation IS 485, Professor Matt Thatcher.
Semester wrap-up …the final slides.. The Final  December 13, 3:30-4:45 pm  Closed book, one page of notes  Cumulative  Similar format and length to.
213: User Interface Design & Development Prof: Tapan Parikh TA: Deepti Chittamuru
Human-Computer Interaction John Kelleher IT Sligo.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 17, 2006.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 20, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
James Tam CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2007.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 27, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 22, 2002.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 26, 2006.
Introduction to HCI Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development January 21, 1999.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 29, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 23, 2003.
Guide to the Voting Action Planner Voting is the way we elect government officials, pass laws and decide on issues…
Palm Beach Ballot Problems Marti Hearst. The Palm Beach,FL Ballot November, 2000.
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
WRITING EFFECTIVE S. Before writing the Make a plan! Think about the purpose of the Think about the person who will read the and.
CS 6750 Human-Computer Interaction Fall 2009 Keith Edwards
Heuristic evaluation IS 403: User Interface Design Shaun Kane.
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
User Interface Design and Development (Introduction to Human Computer Interaction ) Nan Tu PhD Spring, 2007 Tsinghua University Department of Industrial.
INFO 330 Class Project Do it for real. Overview of the Class Project Scope – Approximately the same as the sample project – Standard starting place Marketing.
CS 4720 Usability and Accessibility CS 4720 – Web & Mobile Systems.
Usability Testing intro.12.ppt CS 121 “Ordering Chaos” “Mike” Michael A. Erlinger.
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
CS 3120 USER INTERFACE DESIGN, IMPLEMENTATION AND EVALUATION (UIDIE) Dr. Ben Schafer
Dana Nau: CMSC 722, AI Planning Licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License:
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
Human Computer Interaction Lecture /11 1.
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.
Project Deliverables CEN Engineering of Software 2.
User Interface Evaluation Cognitive Walkthrough Lecture #16.
Prototyping. REVIEW : Why a prototype? Helps with: –Screen layouts and information display –Work flow, task design –Technical issues –Difficult, controversial,
Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.
Usability Heuristics Avoid common design pitfalls by following principles of good design Nielsen proposes 10 heuristics, others propose more or less. Inspect.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
Prof. James A. Landay Richard Davis Kate Everitt University of Washington Autumn 2004 UW Undergraduate HCI Projects A CSE 490jl Overview December 9, 2004.
EasyChair Project Reviewer sign up and bidding Art Hsieh Jean Huang Norik Davtian Ryan Nissenbaum.
Project Deliverables CIS 4328 – Senior Project 2 And CEN Engineering of Software 2.
Prof. James A. Landay University of Washington Winter 2009 Introduction & Course Overview CSE 441 – Advanced HCI January 6, 2009.
Requirements Elicitation CSCI 5801: Software Engineering.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #20.
CS 575 Spring 2012 Lecture Bapa Rao.
Ten Usability Heuristics These are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of.
Discount Evaluation User Interface Design. Startup Weekend Wellington CALLING ALL DESIGNERS, DEVELOPERS AND IDEAS FOLK: Startup Weekend returns to Wellington.
SWE 205 Software Usability Analysis and Design
Alfred Kobsa University of California, Irvine
Research Topics in Human-Computer Interaction
CS305, HW1, Spring 2008 Evaluation Assignment
Software Usability Course notes for CSI University of Ottawa
CIS 4328 – Senior Project 2 And CEN Engineering of Software 2
SWE 632 User Interface Design and Development
Presentation transcript:

SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 18, 2005

Alternative names for this course User Interface Design, Prototyping, and Evaluation Human-computer Interaction

Why is HCI Important? It can determine who becomes president of the USA!

A Related Problem Evaluate the figures in a research paper

A Related Problem What’s wrong with this table? Redesign: add space between the columns.

Palm Beach Phone Book (a joke)

Problems The instructions are misleading –Use of the phrase “vote for group” is misleading Should say “vote for one” –Instructions only on lefthand side Implies righthand side is different The interleaving of holes is misleading –Only the president page has this layout –Other offices are one per page (with appropriate instructions) The sample ballot looks different –No holes – the source of the problem –Did not lead to complaints

Other Issues People vote infrequently –Have to re-learn the system each time Rushed, uncomfortable circumstances Palm Beach Demographics: Elderly

How to know if it will work? Test out the design! –Have real people use it! –Try to match the appropriate demographics –Even a few tries can turn up major problems

An Informal Usability Study Barbara Jacobowitz, CHI-WEB, Nov 10, 2000 “I was able to print 10 different sample ballots from various sources. Last night, I ran them all by my mother (81) and a group of her friends (70-something to 80's). All are bright, literate, and none are legally blind. They did reasonably well on 9 of the ballots. On one, 6 marked it incorrectly and didn't realize it, 2 did it correctly, but very slowly, and 2 had to ask me what to do. Guess which ballot it was?.” Summary of a more formal study of punch-card voting: –

Josephine Scott, CHI-Web, Nov 10, 2000 “I spent fifteen years making the voting process accessible and usable for all… Usability standards must be higher for voting than any other function for the most obvious reasons. Users--in this case, voters, share the need for the clearest of design and instruction to cast a vote properly. Many do not speak English well, or see well, or are able to decipher difficult design cognitively, but they may be able to make as informed a choice for president as our snobbish "experts" who don't see a problem. …

Josephine Scott, CHI-Web, Nov 10, 2000 “Bad design like this exacerbates the problem. The glib notion that "there is no problem because you can see the arrow" or that voters who made this mistake must be stupid shows a lack of compassion. Let me suggest that it is simple compassion for the user that informs usability expertise. …”

More evidence that the ballot is misleading (New York Times, Nov 9, 2000) Percent of ballots thrown out in Palm Beach County for "overvoting" on Presidential candidates: 4.1% (19,120) Percent of ballots thrown out in Palm Beach County for "overvoting" on Senatorial candidates: 0.8% (3,783) Percent of ballots thrown out in Sacramento County (CA) "overvoting" on Presidential candidates: 0.29% (1,147) Percentage of (unofficial) re-count votes in Gore's favor: 70% (2,520) Percentage of (unofficial) re-count votes in Bush's favor: 30% (1,063)

Blaming the User A huge step backwards: –Cokie Roberts (appearing on David Letterman) “stupidity is not an excuse” Well-designed user interfaces do not present situations in which it is easy to make mistakes Alan Cooper’s mantra: software should not humiliate the user In this class we assume: if the user does something “wrong,” it is usually the fault of the system designer

Administrivia Course TAs: –Jonathan Snydal –Andrew Fiore

Readings Do indicated readings before the class Required: –Course Reader University Copy 2425 Channing Way, Berkeley, CA –Jakob Nielsen’s Usability Engineering –Johnson’s GUI Bloopers –Norman’s The Design of Everyday Things –Cooper’s The Inmates are Running the Asylum

Course Schedule (Tentative) Intro to HCI UI Design Cycle, User-Centered Design Goals, Personas, Task Analysis, Scenarios Prototyping Design Techniques Heuristic Evaluation Cognitive Issues and Human Abilities Modes Midterm Usability Testing Research Topics

Project Schedule (Tentative) Note: there will also be individual assignments Dates shown are the week the item is due Project proposals (3 rd week) Project personas and goals (5 th week) Scenarios, tasks, and initial sketches (6 th week) Individual design practice (8 th week) Lo-Fi prototype and test (8 th week) Midterm (9 th week) First interactive prototype (10 th week) Class presentation (10 th week) Project heuristic evaluation (11th week) Second interactive prototype (12th week) Usability test (14th week) Class presentations (15 th week) Third prototype and project writeup (Finals week)

Administrivia Grading: –Individual assignment(s): 20% –Midterm: 30% –Project: Many milestone assignments – required, must be done on time, but not graded –will receive comments/feedback instead. Final project gets a grade at the end – counts 50%

Assignment Join the course list! (is213) –Mail to subscribe Start thinking about projects and team members Look at previous years’ projects – – – –