Порівняння методів
Переглядайте обрані методи поруч; рядки з відмінностями підсвічено.
| Тестування дерева× | Евристична оцінка× | |
|---|---|---|
| Галузь | Взаємодія людини з комп'ютером | Взаємодія людини з комп'ютером |
| Родина | Hypothesis test | Hypothesis test |
| Рік появи≠ | 2000s | 1990 |
| Автор методу≠ | Usability Professionals | Jakob Nielsen and Rolf Molich |
| Тип≠ | Task-based testing of navigation structures | Expert-based inspection using established design principles |
| Основоположне джерело≠ | Tullis, T., Fleischman, S., McNulty, M., Ciccone, C., & Bergel, M. (2002). An empirical comparison of lab and remote usability testing of web sites. In Proceedings of the Usability Professionals Association Annual Conference. link ↗ | Nielsen, J. (1994). Heuristic evaluation of user interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 249–256). link ↗ |
| Інші назви≠ | Reverse Card Sort, Card Sorting Validation | HE, Expert Evaluation, Nielsen's Heuristics |
| Пов'язані | 4 | 4 |
| Підсумок≠ | Tree Testing is a quantitative, task-based validation method for evaluating information architecture and navigation structures. Users are presented with a text-only representation of a website or app hierarchy (a tree) and asked to locate specific items or complete tasks by clicking through the structure. Unlike card sorting, which reveals user mental models during design, tree testing validates whether a proposed structure allows users to find items efficiently. The method captures success rate, time-to-completion, and paths taken, providing metrics for comparing navigation designs. | 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. |
| ScholarGateНабір даних ↗ |
|
|