Final Review 490JL. What’s on the Final? Everything. Lecture Slides Assignments/Project Readings Discussion Section Worth 20 %

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Chapter 11 Designing the User Interface
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
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)
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
UI Standards & Tools Khushroo Shaikh.
Stanford hci group / cs376 Research Topics in Human-Computer Interaction Design Tools 01 November 2005.
Class 6 LBSC 690 Information Technology Human Computer Interaction and Usability.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Douglas K. van Duyne James A. Landay Jason I. Hong Using Design Patterns to Create Customer-Centered Web Sites.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
1 Web Design Process & Patterns. 2 Outline Review Web design process Motivation for design patterns Web design patterns Home page pattern.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
1 Web Site Design Customer Centered Design Principles Patterns and Processes Dr. Carl Rebman.
1 User Centered Design and Evaluation. 2 Overview My evaluation experience Why involve users at all? What is a user-centered approach? Evaluation strategies.
Introduction to HCI Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development January 21, 1999.
HCI revision lecture. Main points Understanding Applying knowledge Knowing key points Knowing relationship between things If you’ve done the group project.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Chapter 13: Designing the User Interface
Review an existing website Usability in Design. to begin with.. Meeting Organization’s objectives and your Usability goals Meeting User’s Needs Complying.
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Web Design and Patterns CMPT 281. Outline Motivation: customer-centred design Web design introduction Design patterns.
1 440 Midterm Review Midterm in-class Tuesday, Nov 6.
Human Computer Interaction & Usability Prototyping Design & Prototyping HCI Prototyping.
Principles of User Centred Design Howell Istance.
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
Guidelines and Prototypes CS774 Human Computer Interaction Spring 2004.
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 Luke Vink Cornell Tech Spring 2014 May 14, 2014 HCI+DESIGN: USER INTERFACE DESIGN + PROTOTYPING + EVALUATION Cornell Tech HCI+Design.
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 for Interaction Rui Filipe Antunes
Overview of the rest of the semester Building on Assignment 1 Using iterative prototyping.
CS CS 5150 Software Engineering Lecture 11 Usability 1.
Chapter 3: Managing Design Processes
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
SEG3120 User Interfaces Design and Implementation
User Interface Structure Design Chapter 11. Key Definitions The user interface defines how the system will interact with external entities The system.
Slide 1 Chapter 11 User Interface Structure Design Chapter 11 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman.
INFORMATION X INFO425: Systems Design Chapter 14 Designing the user interface.
COMPSCI 345 / SOFTENG 350 Review for mid-semester test AProf Beryl Plimmer.
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
User Interfaces 4 BTECH: IT WIKI PAGE:
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
Midterm Review Francis Li CS160 Midterm Review October 9, 2000.
Final Review 490F. What’s on the Final? Everything Lecture Slides Assignments/Project Readings Discussion Section Worth 25 % Bias toward topics covered.
EVALUATION PROfessional network of Master’s degrees in Informatics as a Second Competence – PROMIS ( TEMPUS FR-TEMPUS-JPCR)
Conceptual Design Dr. Dania Bilal IS588 Spring 2008.
Creating & Building the Web Site Week 8. Objectives Planning web site development Initiation of the project Analysis for web site development Designing.
Importance of user interface design – Useful, useable, used Three golden rules – Place the user in control – Reduce the user’s memory load – Make the.
Prof. James A. Landay Richard Davis Kate Everitt University of Washington Autumn 2004 UW Undergraduate HCI Projects A CSE 490jl Overview December 9, 2004.
Stanford hci group / cs376 Research Topics in Human-Computer Interaction Design Tools Ron B. Yeh 26 October 2004.
1 CS 490JL Midterm Review Midterm in-class Tuesday, October 26 With thanks to Wai-Ling Ho-Ching.
Information Architecture & Design Week 9 Schedule - Web Research Papers Due Now - Questions about Metaphors and Icons with Labels - Design 2- the Web -
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 13 Usability 1.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
Prof. James A. Landay University of Washington Autumn 2004 Design Patterns for the Web #1 October 21, 2004.
SE 431 Human Computer Interactions Jamal Nasir. How to design & build good UIs UI Development process Usability goals User-centered design Design discovery.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
Prof. James A. Landay University of Washington Spring 2008 Web Interface Design, Prototyping, and Implementation Ubicomp Design Pre-Patterns May 29, 2008.
Midterm in-class Tuesday, Nov 6
Prototyping.
Design, prototyping and construction
Formative Evaluation cs3724: HCI.
Design, prototyping and construction
Presentation transcript:

Final Review 490JL

What’s on the Final? Everything. Lecture Slides Assignments/Project Readings Discussion Section Worth 20 %

What is HCI? Design Organizational & Social Issues Technology Humans Tasks

What is HCI? Design Organizational & Social Issues Technology Humans Tasks LearningNew Tasks

Iteration at Every Stage Design Prototype Evaluate

Goals of the course 1) Learn to design, prototype, & evaluate UIs the needs & tasks of prospective users cognitive/perceptual constraints that affect design technology & techniques used to prototype UIs techniques for evaluating a user interface design importance of iterative design for usability technology used to prototype & implement UI code how to work together on a team project communicate your results to a group key to your future success 2) Understand where technology is going & what UIs of the future might be like

Intro, Design Discovery Intro Design triangle Usability Metrics Task Analysis Questions *** Tasks Contextual Inquiry Context, Apprentice Model

Conceptual Models & Interface Metaphors Design Concepts Affordances Conceptual Models (Design, Customer) Visibility Metaphors Consistency Teams vs. Groups Commitment, common goals, mix of skills, agreement, mission statements etc… Also, remember the reading The Discipline of Teams!

Human Abilities Human Perception Color sensitivity & physical human eye Hue, Lightness, Saturation Model Human Processor Fitt’s law LTM, STM 100ms

Lo-Fi Prototyping Lo-fi Prototyping Advantages: Speed Cost Quickly iterate Focus on interaction rather than details Conducting a test Wizard of Oz Informal prototyping tools

Heuristic Evaluation Pros Fast +Cheap Gets major problems Cons: Not as in depth as User Testing False Positives Need trained evaluators Phases Training Evaluation (x2) Severity Rating Debriefing Diminishing returns when adding evaluators (sweet spot 3-5) Have evaluators independently rate severity Alternate with user testing

Design Patterns Design patterns communicate common design problems and solutions Prevent “reinvention” Not too general & not too specific Use a solution “a million times over, without ever doing it the same way twice” Web Design Patterns Above the Fold Shopping Cart Location Bread Crumbs Up-selling/Cross-selling Visibility Action Button …

Rapid Prototyping Difference from Lo-Fi? Problems with Lo-Fi? Computer “buggy” Timings Affordances/Doesn’t look like final version Unrealistic / Hard to recognize widgets Not in context of user’s work Some things hard to simulate (dragging/highlights) Advantages of Prototyping Tools? Faster than code

Visual Design Typography Grid Systems Small Multiples Color Spaces RGB vs. HSV (a.k.a. HLS) Use color properly – not for ordering!

Model View Controller Model View Controller

Toolkits Computer Graphics Stroke Model, Pixel Model, Region Model Fonts –Serif/Sans Serif Image depth, Aliasing Coordinate Systems Toolkits Sequential Event Driven When would you use each? Interactor Tree Definitions Dispatching events: bottom-most, top-most Latency problems with networked window systems

Advanced User Testing User testing is important Don’t know how good a UI is until people use it Evaluators may know too much or too little Hard to predict what people will do User testing takes time & effort Problems finding representative users Early testing can be done on low-fi mock-ups real tasks & representative participants Be ethical & treat your participants well

Advanced User Testing (continued) Process data: what people are doing & why Thinking aloud Critical incidents Bottom line data: requires more participants to get statistically reliable results Difference between between & within groups? between groups: everyone participates in one condition within groups: everyone participates in multiple conditions

Action Analysis GOMS When to use? How to use it? GOMS: only gives performance for expert behavior Only works for goal directed tasks hard to create model, but still easier than user testing Does not address? … readability, memorability of icons, commands Automated usability faster than traditional techniques can involve more participants -> convincing data easier to do comparisons across sites tradeoff with losing observational data

From Section Speech UI’s Motivation Why they’re hard Speech Recognition / Production Errors Types of Error Strategies CSCW CSCW vs HCI Dimensions of Cooperation Coordination, Cooperation, Communication Toolkits

From Assignment Be familiar with: Contextual Inquiry Task Analysis Low Fidelity Prototyping Heuristic Evaluation Hall of Fame/Shame Usability Testing

Good Luck! Questions?

More Details

History of HCI Vannevar Bush As we may think: Predictions? Doug Englebart Inventions? Noun-Verb, Verb-Noun Augmenting human intellect

A Quick Topics List Know thy user & involve them in design answer questions before designing who, what, where, when, how often? users & data?, other tools? when things go wrong? Selecting tasks real tasks with reasonable functionality coverage complete, specific tasks of what user wants to do Contextual inquiry way to answer the task analysis questions interview & observe real users use the master-apprentice model to get them to teach you

Conceptual Models & Interface Metaphors Conceptual Model Mental representation of how object works & how interface controls affect it Mismatch? Affordances as Perceptual Clues Well-designed objects have affordances Metaphors Consistency Design Guidelines Provide good conceptual model Map interface controls to user’s model Make things visible Provide feedback Be consistent

Task Analysis Who is going to use the system? What tasks do they now perform? What tasks are desired? How are the tasks learned? Where are the tasks performed? What’s the relationship between user & data? What other tools does the user have? How do users communicate with each other? How often are the tasks performed? What are the time constraints on the tasks? What happens when things go wrong?

Web Design Patterns Designers create representations of sites at multiple levels of detail Web sites are iteratively refined at all levels of detail Site Maps, Storyboards, Schematics, Mock-ups Patterns: Site Branding Personal E-Commerce Obvious Links Above the Fold Location Bread Crumbs Personalized Recommendations/Recommendation Continuity Shopping Cart Up-selling/Cross-selling Visibility Action Button Quick Flow Checkout New account Process Funnel Order Summary Context Sensitive Help Navigation Bar Meaningful Error Messages Search Action Module

A Quick Topics List Rapid Prototyping Difference from Lo-Fi? Problems with Lo-Fi? Advantages of Tools?

Visual Design How do Serif fonts help the reader? serifs lead your eye along the line Grids help clarify & simply visual design by? reducing visual clutter improving consistency between items put things where people expect How do small multiples enable us to notice differences? only make changes (e.g., in color) for differences that matter How can color be problematic online? device may not be able to display color presentation is different on different devices (calibration) using color values for continuous scales (ok to use brightness)

Toolkit Details Computer Graphics Stroke Model, Pixel Model, Region Model Aliasing Coordinate Systems Event-Driven Programming communication from user to computer is done via “events” Clipping ? drawing only regions that are visible to the user Windowing systems special problem with networked WS? - latency Input events Main event loop used to dispatch events Interactor trees used for figuring out where to dispatch events Dispatching events: bottom-most, top-most Event focus

A Quick Topics List Model View Controller What do each of the parts do? Which two are often combined? Why? Toolkits Pixel model Stroke model Aliasing Coordinates: Device, Window, Physical, Model

A Quick Topics List Advanced User Testing Tasks Process, Bottom-line Data (dif? What good for what?) Between Groups, Within Groups Here is an example of a user test: Where are the flaws?