1 / 69

Introduction & Course Overview CS490jl

Introduction & Course Overview CS490jl. September 30, 2004. UI Hall of Fame or Hall of Shame?. Hall of Shame!. Does not help the user accomplish their task why did they come to the site? Takes too long most visitors will just leave & never come back

Download Presentation

Introduction & Course Overview CS490jl

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Introduction & Course Overview CS490jl September 30, 2004

  2. UI Hall of Fame or Hall of Shame? User Interface Design, Prototyping, and Evaluation

  3. Hall of Shame! • Does not help the user accomplish their task • why did they come to the site? • Takes too long • most visitors will just leave & never come back • May be valid for entertainment, art, or branding sites User Interface Design, Prototyping, and Evaluation

  4. Hall of Fame or Shame? • Page setup for printing in IE5 User Interface Design, Prototyping, and Evaluation

  5. Hall of Shame! • Page setup for printing in IE5 • Problems • codes for header & footer information • requires recall! • want recognition • no equivalent GUI • help is the way to find out, but not obvious User Interface Design, Prototyping, and Evaluation

  6. Introduction & Course Overview CS490jl September 30, 2004

  7. Outline • Who are we? • HCI introduction • Course overview & schedule • Introductions User Interface Design, Prototyping, and Evaluation

  8. Who are we? • James Landay • Associate Professor in Computer Science at the University of Washington (formerly professor in EECS at UC Berkeley) • Ph.D. in CS from Carnegie Mellon ‘96 • HCI w/ focus on informal input (pens, speech, etc.), Web design (tools, patterns, etc.), & Ubiquitous Computing • founded NetRaker, leader in Web experience management • Now subsidiary of KeyNote Systems • Co-authored The Design of Sites with D. van Duyne & J. Hong • Director of Intel Research Seattle (ubicomp lab) • Kate Everitt • Ph.D. student in CSE • BSc in Computing & Info Science from Queen’s University • MS in CS from UC Berkeley • HCI w/ focus on computer support cooperative work User Interface Design, Prototyping, and Evaluation

  9. Who are we? • Richard Davis • Ph.D. student in CS at UC Berkeley • BS & MS in EECS from MIT • lots of industry experience (Virtual Ink, Boris F/X, Mathworks, Intel) • HCI w/ focus on pen-based user interfaces (animation) User Interface Design, Prototyping, and Evaluation

  10. Human-Computer Interaction (HCI) • Human • the end-user of a program • the others in the organization • Computer • the machine the program runs on • often split between clients & servers • Interaction • the user tells the computer what they want • the computer communicates results User Interface Design, Prototyping, and Evaluation

  11. Organizational & Social Issues Tasks Design Technology Humans HCI Approach to UI Design User Interface Design, Prototyping, and Evaluation

  12. Organizational & Social Issues Tasks Design Technology Humans Factors Influence Each Other “People change their knowledge as they perform, i.e., they learn” User Interface Design, Prototyping, and Evaluation

  13. User Interfaces (UIs) • Part of application that allows people • to interact with computer • to carry out their task • User vs. Customer vs. Client • user is a term only used by 2 industries -> bad! • customer –person who will use the product you build • client – the person/company who is paying you to build it HCI = design, prototyping, evaluation, & implementation of UIs User Interface Design, Prototyping, and Evaluation

  14. Why is HCI Important? • Major part of work for “real” programs • approximately 50% • Bad user interfaces cost • money • 5% satisfaction -> up to 85%profits • finding problems early makes them easier to fix • reputation of organization (e.g., brand loyalty) • lives (Therac-25) • User interfaces hard to get right • people are unpredictable • intuition of designers often wrong User Interface Design, Prototyping, and Evaluation

  15. Who Builds UIs? • A team of specialists (ideally) • graphic designers • interaction / interface designers • information architects • technical writers • marketers • test engineers • usability engineers • software engineers • users User Interface Design, Prototyping, and Evaluation

  16. How to Design and Build UIs • UI Development process • Usability goals • User-centered design • Task analysis & contextual inquiry • Rapid prototyping • Evaluation • Programming User Interface Design, Prototyping, and Evaluation

  17. User Interface Development Process Customers, Products, Business, Marketing Customers, Products, Business, Marketing Customers, Products, Business, Marketing Design Discovery Design Exploration Evaluate Execute Customers: - Roles (Who) - Tasks (What) - Context (Stories) Marketing: - Business Priorities - Messages Technology: - Products - Architecture Design: - Leading/competing technologies Work together to realize the design in detail. Evaluate with Customers Storyboard Review & Iterate Design Definition: - Design Problem Statement - Targeted User Roles (Who) - Targeted User Tasks (What) - Design Direction Statements Specification: Hi Fidelity, Refined Design - Based on customer feedback - Foundation in product reality - Refined Design description Proposal: Demos/ Lo Fi Prototypes (How) based on slide by Sara Redpath, IBM & Thyra Trauch, Tivoli User Interface Design, Prototyping, and Evaluation

  18. Design Prototype Evaluate Iteration At every stage! User Interface Design, Prototyping, and Evaluation

  19. Design • Design is driven by requirements • what the artifact is for • not how it is to be implemented • e.g., PDA not as important as “mobile” app. • A design represents the artifact • for UIs these representations include (?) • screen sketches or storyboards • flow diagrams/outline showingtask structure • executable prototypes • representations simplify Write essay start word processor write outline fill out outline Start word processor find word processor icon double click on icon Write outline write down high-level ideas . . . User Interface Design, Prototyping, and Evaluation

  20. Web Design Representations Site Maps Storyboards Schematics Mock-ups User Interface Design, Prototyping, and Evaluation

  21. Usability According to the ISO:The effectiveness, efficiency, and satisfaction with which specified users achieve specified goals in particular environments • This does not mean you have to create a “dry” design or something that is only good for novices – it all depends on your goals User Interface Design, Prototyping, and Evaluation

  22. Learnable faster the 2nd time & so on Memorable from session to session Flexible multiple ways to accomplish tasks Efficient perform tasks quickly Robust minimal error rates good feedback so user can recover Pleasing high user satisfaction Fun Usability Goals • Set goals early & later use to measure progress • Goals often have tradeoffs, so prioritize • Example goals User Interface Design, Prototyping, and Evaluation

  23. User-centered Design “Know thy User” • Cognitive abilities • perception • physical manipulation • memory • Organizational / job abilities • Keep users involved throughout • developers working with target users • think of the world in users terms • understanding work process • not technology-centered/feature driven User Interface Design, Prototyping, and Evaluation

  24. ? Task Analysis & Contextual Inquiry • Observe existing work practices • Create examples and scenarios of actual use • “Try-out”new ideas before building software User Interface Design, Prototyping, and Evaluation

  25. Fantasy Basketball Rapid Prototyping • Build a mock-up of design so you can test • Low fidelity techniques • paper sketches • cut, copy, paste • Interactive prototyping tools • HTML, Visual Basic, HyperCard, Director, Flash, DENIM, etc. • UI builders • Visual Studio .NET, JBuilder… User Interface Design, Prototyping, and Evaluation

  26. ESP Evaluation • Test with real users (participants) • w/ interactive prototype • low-fi with paper “computer” • Build models • GOMS • Low-cost techniques • expert evaluation • walkthroughs • online testing User Interface Design, Prototyping, and Evaluation

  27. Programming • Toolkits • UI Builders • Event models • Input / Output models • etc. User Interface Design, Prototyping, and Evaluation

  28. Goals of the Course • 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 • Understand where technology is going & what UIs of the future might be like User Interface Design, Prototyping, and Evaluation

  29. Course Format • Interactive lectures • Semester long project & homeworks • Readings • All material is online • slides, exercises, readings, schedule • http://www.cs.washington.edu/cs490jl • Have fun & participate! User Interface Design, Prototyping, and Evaluation

  30. How CSE490jl Fits into CS Curriculum • Most courses for learning technology • compilers, operating systems, databases, etc. • CSE490jl concerned w/design & evaluation • assume you can program/learn new languages • technology as a tool to evaluate via prototyping • skills will become very important upon graduation • complex systems, large teams • don’t look for large immediate impact in other CS courses User Interface Design, Prototyping, and Evaluation

  31. Project Description • Each of you will propose an interface idea • fixing something you don’t like or a new idea • Groups • 4 students to a group • work with students w/ different skills/interests • groups meet with teaching staff every 2 weeks • Cumulative • apply several HCI methods to a single interface User Interface Design, Prototyping, and Evaluation

  32. Project Process Overview • Project proposal (individual) due Tuesday • Break-up into groups next Thursday • Project task analysis & “sketches” • i.e., rough proposals that can & will change • Low fidelity prototyping & testing • Build 1st interactive prototype • In class presentations & critiques • Heuristic evaluations (individual) User Interface Design, Prototyping, and Evaluation

  33. Project Process Overview (cont.) • Heuristic evaluation summary • Build 2nd interactive prototype • In lab demo & critiques • Customer testing of 2nd prototype • In class presentation & critiques • Not enough time for 3rd prototype User Interface Design, Prototyping, and Evaluation

  34. Project Examples • Research notebook • threads of ideas • multiple views • secure time stamps User Interface Design, Prototyping, and Evaluation

  35. Research Notebook User Interface Design, Prototyping, and Evaluation

  36. Project Examples (cont.) • SiteSketch • web page design • sketch-based User Interface Design, Prototyping, and Evaluation

  37. SiteSketch User Interface Design, Prototyping, and Evaluation

  38. Project Examples (cont.) • CD Jukebox User Interface Design, Prototyping, and Evaluation

  39. CD JukeBox User Interface Design, Prototyping, and Evaluation

  40. Project Examples (cont.) • Clothes Shopper • online shopping • knows your prefs & sizes User Interface Design, Prototyping, and Evaluation

  41. Clothes Shopper User Interface Design, Prototyping, and Evaluation

  42. Project Examples (cont.) • Electronic book reader • take advantage of all the online texts on the net User Interface Design, Prototyping, and Evaluation

  43. Electronic Book Reader User Interface Design, Prototyping, and Evaluation

  44. Project Examples (cont.) • Nutrition tracker User Interface Design, Prototyping, and Evaluation

  45. Nutrition Tracker User Interface Design, Prototyping, and Evaluation

  46. Project Examples (cont.) • cUIzine • recipe tool for the home User Interface Design, Prototyping, and Evaluation

  47. cUIzine User Interface Design, Prototyping, and Evaluation

  48. Project Examples (cont.) • Tech support help desk • avoid using the phone for getting help User Interface Design, Prototyping, and Evaluation

  49. Project Examples (cont.) • Apartment finder • kinda obvious!!! :) User Interface Design, Prototyping, and Evaluation

  50. Apartment Finder User Interface Design, Prototyping, and Evaluation

More Related