Uporedite metode

	NASA-TLX	Kognitivni hod
Oblast	Interakcija čoveka i računara	Interakcija čoveka i računara
Porodica	Hypothesis test	Hypothesis test
Godina nastanka	1988	1990
Tvorac	Sandra Hart and Lowell Staveland	Clayton Lewis, Peter Polson, Cathleen Wharton, John Rieman
Tip	Multi-dimensional post-task questionnaire for measuring subjective mental workload	Evaluative walkthrough examining how users learn to use an interface
Temeljni izvor	Hart, S. G., & Staveland, L. E. (1988). Development of NASA-TLX (Task Load Index): Results of empirical and theoretical research. In P. A. Hancock & N. Meshkati (Eds.), Human Mental Workload (pp. 139–183). Elsevier.	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).
Drugi nazivi	Task Load Index, TLX, NASA-TLX	Cognitive Walkthrough, CW Analysis
Srodne	4	4
Sažetak	The NASA Task Load Index (TLX) is a multi-dimensional subjective workload assessment tool developed at NASA Ames Research Center by Sandra Hart and Lowell Staveland in the 1980s. TLX measures perceived mental workload across six dimensions—mental demand, physical demand, temporal demand, performance, effort, and frustration—allowing researchers and practitioners to understand the cognitive and affective burden of tasks and interfaces. The instrument is widely used in human factors, cognitive engineering, and HCI to identify task bottlenecks and evaluate system designs.	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.