1 / 18

Heuristic Evaluation and Discount Usability Engineering

Heuristic Evaluation and Discount Usability Engineering. Taken from the writings of Jakob Nielsen – inventor of both. Heuristic Evaluation. Context – part of iterative design Goal – find usability problems Who – small set of evaluators

sheparda
Télécharger la présentation

Heuristic Evaluation and Discount 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. Heuristic Evaluation and Discount Usability Engineering Taken from the writings of Jakob Nielsen – inventor of both

  2. Heuristic Evaluation • Context – part of iterative design • Goal – find usability problems • Who – small set of evaluators • How – study interface in detail, compare to small set of principles

  3. Ten Usability Heuristics • Visibility of system status • Match between system and the real world • User control and freedom • Consistency and standards • Error prevention • Recognition rather than recall • Flexibility and efficiency of use • Aesthetic and minimalist design • Help users recognize, diagnose, and recover from errors • Help and documentation

  4. How to Conduct a Heuristic Evaluation • More than one evaluator to be effective. • Each evaluator inspects the interface by themselves • General heuristics may be supplemented • Results can be oral or written • Evaluator spends 1-2 hours with interface • Evaluator goes through interface > 1 time • Evaluators may follow typical usage scenarios • Interface can be paper

  5. Different Evaluators Find Different Problems

  6. Number of Evaluators

  7. Heuristic Evaluation Results • List of usability problems • With principle violated • With severity • NOT fixes • May have debriefing later to aid fixing • Discount usability

  8. Usability Problem Location • Single Location • Two/Several Locations • Overall Structure • Something Missing

  9. Severity • Help focus repair efforts • Help judge system readiness • Factors in Severity: • Frequency • Impact • Persistence • Market impact • Scale severity to a number • May wait on severity

  10. H.E. Complementary w/ Usability Testing • Each will find problems that the other will miss • H.E. Weakness – finding domain specific problems • Don’t H.E. and Usability Test same prototype version

  11. Discount Usability Engineering • “It is not necessary to change the fundamental way that projects are planned or managed in order to derive substantial benefits from usability inspection” • 6% of project budget on usability • 18% of respondents used usability evaluation methods the way they were taught

  12. More Discount Usability Engineering • Cost projection to focus on usability may be reduced • “Insisting on only the best methods may result in having no methods used at all” • 35% of respondents used 3-6 users for usability testing • Nielsen and others suggest 50-1 ROI

  13. Elements of Discount Usability Engineering • Scenarios • Simplified Thinking Aloud • Heuristic Evaluation

  14. Scenarios • Take prototyping to extreme – reduce functionality AND number of features • Small, can afford to change frequently • Get quick and frequent feedback from users • Compatible with interface design methods

  15. Simplified Thinking Aloud • Bring in some users, give them tasks, have them think out loud • Fewer users in user testing

  16. Heuristic Evaluation • Fewer principles etc to apply • Compare interface to previous version or competitor • Ensure tasks are parallel • “Within Subjects” recommended • Counter balance order

  17. Stages of Views of Usability in Organizations • Usability does not matter. • Usability is important, but good interfaces can surely be designed by the regular development staff as part of their general system design. • The desire to have the interface blessed by the magic wand of a usability engineer. • GUI/WWW panic strikes, causing a sudden desire to learn about user interface issues. • Discount usability engineering sporadically used. • Discount usability engineering systematically used. • Usability group and/or usability lab founded. • Usability permeates lifecycle.

  18. End Nielsen insert for Chapt 4

More Related