1 / 53

CS305, HCI in Software Development (formerly Usability Engineering)

CS305, HCI in Software Development (formerly Usability Engineering). Course Introduction Fall 2008. There must be a problem because…. What’s the Course About?. In one sentence: Human-computer interaction (HCI) and user-centered design in the context of SW engineering

baylee
Télécharger la présentation

CS305, HCI in Software Development (formerly Usability Engineering)

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. CS305, HCI in Software Development(formerly Usability Engineering) Course Introduction Fall 2008

  2. There must be a problem because…

  3. What’s the Course About? • In one sentence: • Human-computer interaction (HCI) and user-centered design in the context of SW engineering • Note the target audience: • Students who may be involved in SW development • HCI is important to others: HW designers and engineers, Web designers, psychologists, etc. • But CS305 targets SW development

  4. What is HCI? • More soon… • Human-Computer interface • Where people “meet” or come together with machines or computer-based systems • Physical interface (e.g. buttons, screens, menus, etc.) • Logical interface • The model a system presents a user • Set of tasks available and how they’re organized

  5. From the SIGCHI Website • HCI is… • An inter-disciplinary discipline (engineering, CS, psychology, graphic design, ergonomics, etc.) • Concerned with design, evaluation, and implementation • Addresses people’s needs, capabilities, limitations

  6. SIGCHI curriculum definition site Human-computer interaction is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them.

  7. What is an interface? ?

  8. Evolution of HCI ‘interfaces’ • 50s - Interface at the hardware level for engineers - switch panels • 60-70s - interface at the programming level - COBOL, FORTRAN • 70-90s - Interface at the terminal level - command languages • 80s - Interface at the interaction dialogue level - GUIs, multimedia • 90s - Interface at the work setting - networked systems, groupware • 00s - Interface becomes pervasive • RF tags, Bluetooth technology, mobile devices, consumer electronics, interactive screens, embedded technology, information appliances

  9. HCI: Wide Range of Concerns • Make an interactive system be useful for a task, and support that task effectively • Easy to use, easy to learn, avoid errors • Must understand users, understand users’ tasks • Create a usable logical interface • A user’s conceptual model of the system • Overall design of how we interact • Physical and low-level design • Physical interface: buttons, keys, screens • SW interface: menus, screens, colors • Evaluating usability • During development, after completion

  10. High-level Terms • HCI, CHI • Usability • User-centered Design • An approach to design (SW, Web, other) that involves the user a great deal, in many phases • Interaction Design (ID) • Something different than HCI? Maybe. • Our current textbook is an an “ID” text

  11. Usability • A definition from ISO standard 9241 • The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use. • Effectiveness: • accuracy and completeness in achieving goals • Efficiency: • resources expended… • Satisfaction: • comfort, acceptability (happiness, pleasure)

  12. Discussion • Effectiveness, efficiency and satisfaction: • Are all of these equally important? • All the time?

  13. What is User-Centered Design? • An approach to UI development and system development. • Focuses on understanding: • Users, and • Their goals and tasks, and • The environment (physical, organizational, social) • Pay attention to these throughout development

  14. ISO on User-centered Design • ISO 13407 describes human-centered design processes for interactive systems • Principles of human-centered design: • Active involvement of users • Appropriate allocation of function between user and system • Iteration of design solutions • Multidisciplinary design teams

  15. ISO on User-centered Design (2) • Essential activities in human-centered design: • Understand and specify the context of use • Specify the user and organizational requirements • Produce design solutions (prototypes) • Evaluate designs with users against requirements

  16. Are You Experienced? (in UC Design, I mean) • Think about a significantly complex software project you’ve been involved in • Work, research, CS340, etc. • Did it seem like an example of user-centered design? • How did it, or how did it not?

  17. What is interaction design? • Designing interactive products to support people in their everyday and working lives • Sharp, Rogers and Preece (2002) • The design of spaces for human communication and interaction • Winograd (1997)

  18. Goals of interaction design • Develop usable products • Usability means easy to learn, effective to use and provide an enjoyable experience • Involve users in the design process

  19. Unclear about what ID is? • Not surprising! • We’ll read: • What is Interaction Design and What Does It Mean to Information Designers? by Craig Marion • http://www.chesco.com/~cmarion/PCD/WhatIsInteractionDesign.html • and • From Computing Machinery to Interaction Design by Terry Winograd • http://hci.stanford.edu/%7Ewinograd/acm97.html

  20. From HCI to Interaction Design • Human-computer interaction(HCI) is:“concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them” (ACM SIGCHI, 1992, p.6) • Interaction design (ID) is: “the design of spaces for human communication and interaction” (Winograd, 1997) • One distinction: more application areas, more technologies and more issues to consider when designing ‘interfaces’

  21. Relationship between ID, HCI and other fields Academic disciplines (e.g. computer science, psychology) Design practices (e.g. graphic design) Interaction Design Interdisciplinary fields (e.g HCI, CSCW)

  22. Relationship between ID, HCI and other fields • Academic disciplines contributing to ID: • Psychology • Social Sciences • Computing Sciences • Engineering • Ergonomics • Informatics

  23. Relationship between ID, HCI and other fields • Design practices contributing to ID: • Graphic design • Product design • Artist-design • Industrial design • Film industry

  24. Relationship between ID, HCI and other fields • Interdisciplinary fields that ‘do’ interaction design: • HCI • Human Factors • Cognitive Engineering • Cognitive Ergonomics • Computer Supported Co-operative Work • Information Systems

  25. What do professionals do in the HCI or ID business? • interaction designers - ?? • usability engineers - ?? • web designers – (we know this one!) • information architects - ?? • user experience designers - ??

  26. What do professionals do in the HCI or ID business? • interaction designers - people involved in the design of all the interactive aspects of a product • usability engineers - people who focus on evaluating products, using usability methods and principles • web designers - people who develop and create the visual design of websites, such as layouts • information architects - people who come up with ideas of how to plan and structure interactive products • user experience designers - people who do all the above but who may also carry out field studies to inform the design of products

  27. Reminder: What is involved in the process of UC/ID design • Identify needs and establish requirements • Develop alternative designs • Build interactive prototypes that can be communicated and assessed • Evaluate what is being built throughout the process(This is what you’ll do this semester!)

  28. Class Activity • Think-Pair-Share: • Pairs write down differences • Pairs merge results • Instructor calls on pairs to share answers • Question: • Think about a hard-to-use software product (or computer-based system). • In what way does it have poor usability? • General problems • Specific examples

  29. Bad Interfaces, Fall 08 • Cell phone voice mail • No visual, hard to bring up a message • Lots of steps • Cognos database system • Vague names of product types • Slow to query the entire DB • Computer repair DB • Couldn’t search by last name • Advanced music keyboards with touchscreen • Lots of taps, many steps, slows down group

  30. Signature pads • Can’t read signature, defeats the real point • Rate my professor .com • Hard to find professor, must search by last name • Search buttons in opposite corners • Info ordered oddly

  31. Eclipse • Small project, hard to get started, long time to setup. Especially for beginners. • Lots of functions. Can we better balance lots of power and intuitiveness • vi • Self-checkout • Slow you down to listen and respond to voice

  32. Activity (Mini-Homework) • Do this on your own on in pairs • Go find two examples of problems in the GUIs of software apps or the UI of a interactive device (not Web pages) • Problem must illustrate a violation of one of the design principles or usability guidelines (taught next Monday!) • Describe the problems in these terms • We’ll collect these write-ups from you and put them on the Web • Be ready to “post” on Collab wiki page before class next Fri.

  33. Bad Interfaces, Spr 08 • SMOK • Zooming hard, not intuitive • Do it too much, overlap, too much scrolling • Sometimes right-click, other times do something else • Some commands buried • Default when adding component bad, things overlap, • Things you need to find not labeled well • Too much zooming, search to find things • Add tings and file is lost • Components/things easily deleted by mistake • Failed to always load file correctly • Demands advance planning, otherwise hard to change things later • Hard to distinguish arrows between components where there are many

  34. Excel • Copy and paste from Word puts stuff in just one cell • Hard to change details in graphs • Wizard great, but hard to see how to customize • 2D graphs • Print formatting • Steep learning curve • Hard for beginners needing advanced features • Click on cell, selects all, and you may delete it when you mean to edit it • Formulas: hard to follow which cells are referenced • Floating point accuracy

  35. Fake iPod • Different buttons are used to select at different times • Mistake takes you back to beginning instead of back one • Can’t define order of songs when playing

  36. ISIS • Type in year/semester: use odd format • Could default to “logical” semester • Doesn’t have all info in it to be good • Need COD which isn’t there • Waitlist isn’t well integrated • Availability: closed at certain times (?) • Can’t press enter to login in, must click • Also, tab order isn’t logical • Must return back to main menu always, even when there’s a logical other window you want to do • Can’t use Backspace/Back to go back • Close window causes it to chide you • Audit have this request/wait/return option • Seems unfriendly, unresponsive • Timer period too short since you have to use >1 system • Refresh -- F5 logs you out

  37. Examples of non-usable systems • Kroger’s self-checkout • Use of the scale is confusing, not enough room for stuff • Slow scanners, not as efficient as you’d hope • Slow to scan/place/wait, so takes longer • Default fix is “get cashier”, no other suggestions • Poor error recovery • Why can’t I swipe student ID? Didn’t check if you were a student once • Ableton-Live or similar recording/audio software • doesn’t look like standard Windows program, so hard to find GUI controls • might look cool but makes it less efficient

  38. Games that used keyboard commands only and used card-board cut-out • Chem151 HW checker program • Can’t backtrack in the steps you have to do • Crashes a lot • Didn’t accept numeric answers missing x.0 • No feedback on why • UVa’s Webmail • Ugly to look at, not pleasing • hard to keep mail organized in folders • Must explicitly copy and move • Slow • Useless spam filter • Must log into webmail/toolkit even when you’ve logged into a machine • Filters out mail headers / not clear you can control this • Indents messages in a thread, but if too deep you don’t see enough of the message

  39. Mathcad • hard to learn at first • hard to keep track of variable / whole thing fails because of one small error / not good at explaining source of errors • use of arrow-keys vs. space-bar to move things in an equation • expected arrow keys to work • 4+ different versions of the equals-sign / hard to distinguish on the screen • new version can’t read files from other versions • hard to remember after not using it for a while (lots of tricks needed, hard to remember)

  40. ISIS • pops up a window, pop-up blocker problems • can’t use browser’s back button • gives course instructor number instead of name • must enter schedule-number instead of clicking on course ID and number • Must use semester as a code, and if you get this wrong it’s confusing what’s wrong • Interface has pictures/images for links, not the conventional under-lined links • not integrated into COD, so must copy info over from COD to ISIS • Kicks you off too quickly • Too often overloaded, too many users • Unavailability at certain hours / don’t know when it’s unavailable / status not visible easily • Links on main page are too similar • SSN number use

  41. Spring 06: Examples of non-usable systems • Eclipse • Hard learning curve, bad for beginners • Too many windows, confusing layout, too much going on (advanced options) • Mathcad • Interface not intuitive • Not monkey-proof (let’s you make mistakes that crash it, make it unstable) • Saving didn’t always work well • Mouse scrolling caused program to crash

  42. Main UVa website • Cluttered, too much stuff • Random, not organized • Things you need small, hard to find – must search for • [User-base…] • Grad school application sites • Multiple systems, not standard • Important info not clear, not consistent (deadlines) • Geometer’s Sketchpad • Hard to figure out how to use (sit down, can’t figure out what to do). Need to read instruction book. Bad help

More Related