방법 비교
선택한 방법을 나란히 검토하세요. 서로 다른 행은 강조 표시됩니다.
| 다원적 워크스루× | 휴리스틱 평가× | |
|---|---|---|
| 분야 | 인간-컴퓨터 상호작용 | 인간-컴퓨터 상호작용 |
| 계열 | Hypothesis test | Hypothesis test |
| 기원 연도≠ | 1992 | 1990 |
| 창시자≠ | Randolph G. Bias | Jakob Nielsen and Rolf Molich |
| 유형≠ | User-centered walkthrough with mixed stakeholders | Expert-based inspection using established design principles |
| 원전≠ | Bias, R. G. (1994). The pluralistic walkthrough: Coordinating technology and pedagogy in software development. In J. Nielsen & R. L. Mack (Eds.), Usability Inspection Methods (pp. 63–76). John Wiley & Sons. ISBN: 0-471-01877-5 | Nielsen, J. (1994). Heuristic evaluation of user interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 249–256). link ↗ |
| 별칭≠ | Pluralistic Usability Walkthrough, PW | HE, Expert Evaluation, Nielsen's Heuristics |
| 관련 | 4 | 4 |
| 요약≠ | The Pluralistic Walkthrough is a usability inspection method that brings together users, developers, and usability specialists to walk through an interface and voice their reactions and concerns. Developed by Randolph Bias in 1992, this method combines elements of cognitive walkthroughs with user involvement, creating a collaborative evaluation setting that captures diverse perspectives. By including actual users in the evaluation session, the method bridges the gap between expert judgment and real-world user experience, uncovering unexpected insights and building stakeholder consensus around design improvements. | 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데이터셋 ↗ |
|
|