Methoden vergleichen
Prüfen Sie die ausgewählten Methoden nebeneinander; abweichende Zeilen sind hervorgehoben.
| AttrakDiff/UEQ× | Kano-Modell× | |
|---|---|---|
| Fachgebiet | Mensch-Computer-Interaktion | Mensch-Computer-Interaktion |
| Familie | Hypothesis test | Hypothesis test |
| Entstehungsjahr≠ | 2003 | 1984 |
| Urheber≠ | Marc Hassenzahl (AttrakDiff), Martin Schrepp (UEQ) | Noriaki Kano |
| Typ≠ | Questionnaire measuring pragmatic and hedonic quality dimensions | Two-dimensional model categorizing product/service features by satisfaction impact |
| Wegweisende Quelle≠ | Hassenzahl, M. (2003). The thing and I: Understanding the relationship between user and product. In M. A. Blythe, K. Overbeeke, A. F. Monk, & P. C. Wright (Eds.), Funology (pp. 31–42). Kluwer Academic Publishers. DOI ↗ | Kano, N., Seraku, N., Takahashi, F., & Tsjui, S. (1984). Attractive quality and must-be quality. Journal of the Japanese Society for Quality Control, 14(2), 147–156. link ↗ |
| Aliasnamen≠ | Hedonic Quality Assessment, Pragmatic vs. Hedonic, UEQ | Kano Analysis, Attractive-Performance-Basic Model |
| Verwandt≠ | 4 | 3 |
| Zusammenfassung≠ | AttrakDiff and the User Experience Questionnaire (UEQ) are assessment instruments for measuring user experience across multiple dimensions. AttrakDiff, developed by Marc Hassenzahl, evaluates the tension between pragmatic quality (functionality, usability, does the system do what I need?) and hedonic quality (beauty, emotional engagement, does it delight me?). The UEQ, developed by Schrepp and colleagues, extends this framework with additional dimensions including efficiency, perspicuity, stimulation, and novelty. Both instruments provide quantitative post-use assessment, complementing task-based usability testing with holistic experience evaluation. | The Kano Model is a framework for categorizing product or service features based on their impact on customer satisfaction. Developed by Noriaki Kano, this model distinguishes three types of features: basic (must-have) features that satisfy minimally but cause significant dissatisfaction if absent; performance features that increase satisfaction proportionally with their level; and attractive (delightful) features that exceed expectations and generate disproportionate satisfaction. By classifying features using the Kano Model, product teams prioritize development efforts, balance risk and innovation, and design experiences that delight rather than merely satisfy. |
| ScholarGateDatensatz ↗ |
|
|