Salīdzināt metodes
Apskatiet izvēlētās metodes blakus; rindas, kas atšķiras, ir izceltas.
| Hoiristiskā novērtēšana× | System Usability Scale× | |
|---|---|---|
| Nozare | Cilvēka un datora mijiedarbība | Cilvēka un datora mijiedarbība |
| Saime | Hypothesis test | Hypothesis test |
| Izcelsmes gads≠ | 1990 | 1986 |
| Autors≠ | Jakob Nielsen and Rolf Molich | John Brooke |
| Tips≠ | Expert-based inspection using established design principles | Rapid, post-use questionnaire scale for measuring perceived usability |
| Pirmavots≠ | Nielsen, J. (1994). Heuristic evaluation of user interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 249–256). link ↗ | Brooke, J. (1986). System Usability Scale (SUS): A quick and dirty usability scale. In B. Shackel & S. J. Richardson (Eds.), Usability Evaluation in Industry (pp. 189–194). Taylor & Francis. ISBN: 0-85066-375-X |
| Citi nosaukumi≠ | HE, Expert Evaluation, Nielsen's Heuristics | SUS, System Usability Score |
| Saistītās | 4 | 4 |
| Kopsavilkums≠ | Heuristic Evaluation is a usability inspection method in which small teams of expert evaluators examine an interface and judge its compliance with established usability principles (heuristics). Developed by Jakob Nielsen and Rolf Molich in 1990, this method is rapid and low-cost, identifying 60–90% of usability problems with as few as 3–5 evaluators. Nielsen's Ten Usability Heuristics—visibility of system status, match between system and real world, user control and freedom, consistency and standards, error prevention and recovery, recognition over recall, flexibility and efficiency, aesthetic and minimalist design, error recovery, and documentation—form the basis of most evaluations. | The System Usability Scale (SUS) is a rapid, standardized 10-item questionnaire for measuring perceived system usability in a single summary score. Developed by John Brooke in 1986, SUS has become one of the most widely used post-use usability instruments in industry and research. The scale is administered after a user has interacted with a system, capturing perceived ease of use, learnability, error recovery, and overall satisfaction with a quick, economical assessment that correlates well with comprehensive usability testing. |
| ScholarGateDatu kopa ↗ |
|
|