SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 17, 2006.

Slides:



Advertisements
Similar presentations
Preparing Students for Online Learning
Advertisements

IS214 Recap. IS214 Understanding Users and Their Work –User and task analysis –Ethnographic methods –Site visits: observation, interviews –Contextual.
Prof. James A. Landay University of Washington Spring 2012 Introduction & Course Overview CSE 441 – Advanced HCI March 27, 2012.
CPSC 481 Foundations and Principles of Human Computer Interaction
Department of Computer Science
Saul Greenberg CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
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)
Electronic Communications Usability Primer.
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.
General information CSE 230 : Introduction to Software Engineering
213: User Interface Design & Development Professor: Tapan Parikh TA: Eun Kyoung Choe
SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 18, 2005.
IEEM Human-Computer Systems Dr. Vincent Duffy - IEEM Week 13 - Working in Groups May 4, ieem.ust.hk/dfaculty/duffy/552
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 Feb 13, 2001.
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.
10th Workshop "Software Engineering Education and Reverse Engineering" Ivanjica, Serbia, 5-12 September 2010 First experience in teaching HCI course Dusanka.
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 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.
Evaluation in HCI Angela Kessell Oct. 13, Evaluation Heuristic Evaluation Measuring API Usability Methodology Matters: Doing Research in the Behavioral.
CS 3724: Introduction to Human Computer Interaction Chris North Jason Lee Szu-Chia Lu.
WRITING EFFECTIVE S. Before writing the Make a plan! Think about the purpose of the Think about the person who will read the and.
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.
CS 4720 Usability and Accessibility CS 4720 – Web & Mobile Systems.
Prof. Barbara Bernal NEW Office in J 126 Office Hours: M 4pm - 5:30 PM Class Lecture: M 6 PM - 8:30 in J133 Weekly Web Lecture between Tuesday to Sunday.
Usability Evaluation June 8, Why do we need to do usability evaluation?
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
COMP 465W Software Engineering Fall Components of the Course The three main components of this course are: The study of software engineering as.
1 Project Information and Acceptance Testing Integrating Your Code Final Code Submission Acceptance Testing Other Advice and Reminders.
CS 3120 USER INTERFACE DESIGN, IMPLEMENTATION AND EVALUATION (UIDIE) Dr. Ben Schafer
17-Dec-03 Intro to CIT 594 ~matuszek/cit594.html.
B. Prabhakaran1 Multimedia Systems Textbook Any/Most Multimedia Related Books Reference Papers: Appropriate reference papers discussed in class from time.
COURSE INTRODUCTION BUSINESS ENGLISH 2. Lecturer: BOGLARKA KISS KULENOVIĆ Office hours: Tuesday: 10:00 – 12:00 1 more hour to be set for meetings Room:
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
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.
Testing External Survey Automatic Credit Granting Shepherd University Department of Psychology.
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.
Prof. James A. Landay University of Washington Winter 2009 Introduction & Course Overview CSE 441 – Advanced HCI January 6, 2009.
CS 3724: Introduction to Human Computer Interaction Chris North Regis Kopper.
SFnight SFnight 213 project Overview Special Challenges Heuristic Evaluation Results of the Pilot Study Formal Usability Study Demo of Current Design Last.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #20.
CS 575 Spring 2012 Lecture Bapa Rao.
Discount Evaluation User Interface Design. Startup Weekend Wellington CALLING ALL DESIGNERS, DEVELOPERS AND IDEAS FOLK: Startup Weekend returns to Wellington.
CS 3120 USER INTERFACE DESIGN, IMPLEMENTATION AND EVALUATION (UIDIE)
Research Topics in Human-Computer Interaction
CS305, HW1, Spring 2008 Evaluation Assignment
Software Usability Course notes for CSI University of Ottawa
Presentation transcript:

SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 17, 2006

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?.”

More Formal Refs Electronic voting system usability issues BB Bederson, B Lee, RM Sherman, PS Herrnson, RG., CHI The Unconsidered Ballot : How Design Affects Voting Behavior. SK Roth - Visible Language, eric.ed.gov Visible Language, 28, Disenfranchised by Design : Voting Systems and the Election Process, SK Roth - Information Design Journal, Misvotes, undervotes and overvotes: The 2000 presidential election in Florida,- A Agresti, B Presnell - Statistical Science, 2002 – Law and Data: The Butterfly Ballot Episode, HE Brady, MC Herron, WR Mebane, JS Sekhon, KW … - PS: Political Science and Politics,

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. …”

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 TA: –Andrew Fiore Please sign up on list –Use my.sims.berkeley.edu – with the one line Subscribe is213 –Note that you can only to the list successfully from the address(es) you sign up with. Office hours: –Will be twice a week –No need to make appointments, just come –I will the class if I can’t be there

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

WARNING: THIS CLASS IS A LOT OF WORK!!!!

Project / Assignments Schedule 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) Lo-Fi prototype and test (8 th week) Individual Assignment (9 th week) Midterm (10 th week) [Spring Break] First interactive prototype (11 th week) Class presentation (11 th week) Project heuristic evaluation (12th week) Second interactive prototype (13th week) Usability test (15 th week) Class presentations (15 th week) Third prototype and project writeup (Finals week)

Administrivia Grading: –Individual assignment: 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 Start thinking about projects and team members Look at previous years’ projects – – – –