Salīdzināt metodes
Apskatiet izvēlētās metodes blakus; rindas, kas atšķiras, ir izceltas.
| KLM-GOMS× | Kognitīvā izstaigāšana× | |
|---|---|---|
| Nozare | Cilvēka un datora mijiedarbība | Cilvēka un datora mijiedarbība |
| Saime | Hypothesis test | Hypothesis test |
| Izcelsmes gads≠ | 1983 | 1990 |
| Autors≠ | Stuart Card, Thomas Moran, Allen Newell | Clayton Lewis, Peter Polson, Cathleen Wharton, John Rieman |
| Tips≠ | Computational cognitive model for task execution time prediction | Evaluative walkthrough examining how users learn to use an interface |
| Pirmavots≠ | Card, S. K., Moran, T. P., & Newell, A. (1983). The Psychology of Human-Computer Interaction. Lawrence Erlbaum Associates. ISBN: 0898592437 | Lewis, C., Polson, P. G., Wharton, C., & Rieman, J. (1990). Testing a walkthrough methodology for specifying and evaluating user interface designs. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 387–392). link ↗ |
| Citi nosaukumi | GOMS Model, KLM | Cognitive Walkthrough, CW Analysis |
| Saistītās | 4 | 4 |
| Kopsavilkums≠ | The Keystroke-Level Model (KLM), part of the Goals-Operators-Methods-Selection rules (GOMS) framework, is a computational method for predicting how long a user will take to accomplish a routine task using an interactive system. Developed by Card, Moran, and Newell in 1983, KLM decomposes user actions into primitive operators (keystrokes, mouse clicks, mental preparation, system response waits) with empirically derived execution times, enabling designers to estimate task performance without running user studies. | Cognitive Walkthrough is an inspection method for evaluating interface designs by simulating and analyzing how users will learn to use a system through exploration and trial. Developed by Clayton Lewis, Peter Polson, Cathleen Wharton, and John Rieman in 1990, this method is grounded in cognitive psychology and focuses specifically on learnability—whether first-time or occasional users can discover how to perform tasks without formal training. Evaluators role-play user actions, answer a set of critical questions about feedback and discovery at each step, and document usability problems. |
| ScholarGateDatu kopa ↗ |
|
|