Porównaj metody
Przeglądaj wybrane metody obok siebie; wiersze, które się różnią, są wyróżnione.
| Skala Użyteczności Systemu× | Kano Model× | |
|---|---|---|
| Dziedzina | Interakcja człowiek–komputer | Interakcja człowiek–komputer |
| Rodzina | Hypothesis test | Hypothesis test |
| Rok powstania≠ | 1986 | 1984 |
| Twórca≠ | John Brooke | Noriaki Kano |
| Typ≠ | Rapid, post-use questionnaire scale for measuring perceived usability | Two-dimensional model categorizing product/service features by satisfaction impact |
| Źródło pierwotne≠ | Brooke, J. (1986). System Usability Scale (SUS): A quick and dirty usability scale. In B. Shackel & S. J. Richardson (Eds.), Usability Evaluation in Industry (pp. 189–194). Taylor & Francis. ISBN: 0-85066-375-X | 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 ↗ |
| Inne nazwy | SUS, System Usability Score | Kano Analysis, Attractive-Performance-Basic Model |
| Pokrewne≠ | 4 | 3 |
| Podsumowanie≠ | The System Usability Scale (SUS) is a rapid, standardized 10-item questionnaire for measuring perceived system usability in a single summary score. Developed by John Brooke in 1986, SUS has become one of the most widely used post-use usability instruments in industry and research. The scale is administered after a user has interacted with a system, capturing perceived ease of use, learnability, error recovery, and overall satisfaction with a quick, economical assessment that correlates well with comprehensive usability testing. | 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. |
| ScholarGateZbiór danych ↗ |
|
|