dido:public:ra:1.4_req:2_nonfunc:30_usability:satisfaction
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:2_nonfunc:30_usability:satisfaction [2020/11/20 19:01] nick created |
dido:public:ra:1.4_req:2_nonfunc:30_usability:satisfaction [2022/02/24 13:52] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Satisfaction Metrics ====== | + | ====== 4.3.6.3 Attitude / Satisfaction Metrics ====== |
| [[dido:public:ra:1.4_req:2_nonfunc:30_usability| Return to Top]] | [[dido:public:ra:1.4_req:2_nonfunc:30_usability| Return to Top]] | ||
| - | Usability Metrics are generally done using through standardized questions designed to capture a the user's sentiments about the application, product or system. The survey's pose questions to the users and provide a scale of acceptability they user choses in assessing a particular attribute. The most common scale is based on the Likert Scales originally proposed in 1032 (( | + | ===== About ===== |
| + | [[dido:public:ra:xapend:xapend.a_glossary:u:usability|Usability]] Metrics are generally done through standardized questions designed to capture a the user's sentiments about the [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]], product or system. The survey's pose questions to the users and provide a scale of acceptability the user chooses in assessing a particular attribute. The most common scale is based on the Likert Scales originally proposed in 1032 (( | ||
| Saul McLeod, __Likert Scale Definition, Examples and Analysis __, Simply Psychology, 2019, Accessed 20 November 2020, | Saul McLeod, __Likert Scale Definition, Examples and Analysis __, Simply Psychology, 2019, Accessed 20 November 2020, | ||
| [[https://www.simplypsychology.org/likert-scale.html]] | [[https://www.simplypsychology.org/likert-scale.html]] | ||
| Line 13: | Line 14: | ||
| ^ Agreement ^ Strongly Disagree ^ Disagree ^ Undecided ^ Agree ^ Strongly Agree ^ | ^ Agreement ^ Strongly Disagree ^ Disagree ^ Undecided ^ Agree ^ Strongly Agree ^ | ||
| ^ Frequency ^ Never ^ Rarely ^ Sometimes ^ Often ^ Always ^ | ^ Frequency ^ Never ^ Rarely ^ Sometimes ^ Often ^ Always ^ | ||
| - | ^ Importance ^ Unimportant ^ Important ^ Moderately Important ^ Important ^ Very Important ^ | + | ^ Importance ^ Unimportant ^ Slightly Important ^ Moderately Important ^ Important ^ Very Important ^ |
| ^ Quality ^ Very Poor ^ Poor ^ Fair ^ Good ^ Excellent ^ | ^ Quality ^ Very Poor ^ Poor ^ Fair ^ Good ^ Excellent ^ | ||
| ^ Likelihood ^ Almost Never True ^ Usually Not True ^ Occasionally True ^ Usually True ^ Almost Always True ^ | ^ Likelihood ^ Almost Never True ^ Usually Not True ^ Occasionally True ^ Usually True ^ Almost Always True ^ | ||
| - | ^ //Score//| 1 | 3 | 3 | 4 | 5 | | + | ^ //Score//| 1 | 2 | 3 | 4 | 5 | |
| <caption>The Lickert Scale</caption> | <caption>The Lickert Scale</caption> | ||
| </figure> | </figure> | ||
| There are two ways that user satisfaction can be measured: | There are two ways that user satisfaction can be measured: | ||
| - | * **Task Level Satisfaction** - The Task Level Satisfaction is made at the end of each task attempted by the user. Note, a task may be attempted but it may not be completed. Therefore, it is important o record not just the attitude or sentiment about the task, but also the status of the task when the user takes the survey. | + | * **Task Level Satisfaction** - The Task Level Satisfaction is made at the end of each task attempted by the user. Note, a task may be attempted but it may not be completed. Therefore, it is important to record not just the attitude or sentiment about the task, but also the status of the task when the user takes the survey. |
| - | * **Test Level Satisfaction** - Similar to the **Task Level Satisfaction**, but Test Level Satisfaction is conducted at the end of a Test which can be comprised of multiple tasks. Therefore, in order to properly assess the Test Level, an evaluation of the Task assessments also needs to be made. For example, a test assessment might be low because some of the tasks were assessed as poor. | + | * **Test Level Satisfaction** - Similar to the **Task Level Satisfaction**, Test Level Satisfaction is conducted at the end of a Test which can be comprised of multiple tasks. Therefore, in order to properly assess the Test Level, an evaluation of the Task assessments also needs to be made. For example, a test assessment might be low because some of the tasks were assessed as poor. |
| ISO also provides some guidance in how to assess User Satisfaction. | ISO also provides some guidance in how to assess User Satisfaction. | ||
| Line 32: | Line 33: | ||
| * **Note:** For more information, see: [[https://blog.ansi.org/2018/07/customer-satisfaction-iso-10002-quality/#gref]] | * **Note:** For more information, see: [[https://blog.ansi.org/2018/07/customer-satisfaction-iso-10002-quality/#gref]] | ||
| + | |||
| + | ===== DIDO Specifics ===== | ||
| + | [[dido:public:ra:1.4_req:2_nonfunc:30_usability:satisfaction | Return to Top]] | ||
| + | |||
| + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA </color></wrap> | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
| + | |||
dido/public/ra/1.4_req/2_nonfunc/30_usability/satisfaction.1605916916.txt.gz · Last modified: 2020/11/20 19:01 by nick
