Linganisha mbinu
Pitia mbinu ulizochagua bega kwa bega; safu zinazotofautiana zinaangaziwa.
| KLM-GOMS× | Tathmini ya Virutubisho× | |
|---|---|---|
| Nyanja | Mwingiliano wa Binadamu na Kompyuta | Mwingiliano wa Binadamu na Kompyuta |
| Familia | Hypothesis test | Hypothesis test |
| Mwaka wa asili≠ | 1983 | 1990 |
| Mwanzilishi≠ | Stuart Card, Thomas Moran, Allen Newell | Jakob Nielsen and Rolf Molich |
| Aina≠ | Computational cognitive model for task execution time prediction | Expert-based inspection using established design principles |
| Chanzo asilia≠ | Card, S. K., Moran, T. P., & Newell, A. (1983). The Psychology of Human-Computer Interaction. Lawrence Erlbaum Associates. ISBN: 0898592437 | Nielsen, J. (1994). Heuristic evaluation of user interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 249–256). link ↗ |
| Majina mbadala≠ | GOMS Model, KLM | HE, Expert Evaluation, Nielsen's Heuristics |
| Zinazohusiana | 4 | 4 |
| Muhtasari≠ | 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. | 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. |
| ScholarGateSeti ya data ↗ |
|
|