dido:public:ra:1.4_req:2_nonfunc:30_usability
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:2_nonfunc:30_usability [2020/11/20 18:59] nick ↷ Links adapted because of a move operation |
dido:public:ra:1.4_req:2_nonfunc:30_usability [2021/08/06 17:08] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 4.2.10 Usability ====== | + | ====== 4.3.6 Usability ====== |
| [[dido:public:ra:1.4_req:2_nonfunc| Return to Non-Functional Requirements]] | [[dido:public:ra:1.4_req:2_nonfunc| Return to Non-Functional Requirements]] | ||
| ===== About ===== | ===== About ===== | ||
| - | [[dido:public:ra:1.4_req:2_nonfunc:30_usability| Return to Top]] | ||
| - | |||
| [[dido:public:ra:xapend:xapend.a_glossary:u:usability]] is defined by [[dido:public:ra:xapend:xapend.b_stds:tech:iso:square_sys_model]] as the degree to which a product or system can be used by [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder]] (i.e., specified users) to achieve specified [[dido:public:ra:xapend:xapend.a_glossary:g:goal | goals]] within a specified context. | [[dido:public:ra:xapend:xapend.a_glossary:u:usability]] is defined by [[dido:public:ra:xapend:xapend.b_stds:tech:iso:square_sys_model]] as the degree to which a product or system can be used by [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder]] (i.e., specified users) to achieve specified [[dido:public:ra:xapend:xapend.a_glossary:g:goal | goals]] within a specified context. | ||
| - | ==== Goals ==== | + | ==== Goals ==== |
| - | The goals are(( | + | The goals of usability are(( |
| Justin Mifsud, __Usability Metrics – A Guide To Quantify The Usability Of Any System__, Accessed 18 November 2020, [[https://usabilitygeek.com/usability-metrics-a-guide-to-quantify-system-usability/]] | Justin Mifsud, __Usability Metrics – A Guide To Quantify The Usability Of Any System__, Accessed 18 November 2020, [[https://usabilitygeek.com/usability-metrics-a-guide-to-quantify-system-usability/]] | ||
| )): | )): | ||
| Line 16: | Line 14: | ||
| - **Satisfaction** - The comfort and acceptability of use. | - **Satisfaction** - The comfort and acceptability of use. | ||
| - | * **Note:** See also | + | ==== Sub-Characteristics ==== |
| - | + | ||
| - | ==== Sub-Characteristics ==== | + | |
| This characteristic is composed of the following sub-characteristics(( | This characteristic is composed of the following sub-characteristics(( | ||
| [[dido:public:ra:xapend:xapend.a_glossary:i:iso]], __Usability__, ISO25000, Accessed: 17 November 2020, | [[dido:public:ra:xapend:xapend.a_glossary:i:iso]], __Usability__, ISO25000, Accessed: 17 November 2020, | ||
| Line 28: | Line 24: | ||
| * //**[[dido:public:ra:xapend:xapend.a_glossary:l:learnability]]** - Degree to which a product or system can be used by specified users to achieve specified goals of learning to use the product or system with effectiveness, efficiency, freedom from risk and satisfaction in a specified context of use.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | * //**[[dido:public:ra:xapend:xapend.a_glossary:l:learnability]]** - Degree to which a product or system can be used by specified users to achieve specified goals of learning to use the product or system with effectiveness, efficiency, freedom from risk and satisfaction in a specified context of use.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | ||
| * //**[[dido:public:ra:xapend:xapend.a_glossary:o:operability]]** - Degree to which a product or system has attributes that make it easy to operate and control.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | * //**[[dido:public:ra:xapend:xapend.a_glossary:o:operability]]** - Degree to which a product or system has attributes that make it easy to operate and control.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | ||
| - | * //**[[dido:public:ra:xapend:xapend.a_glossary:u:user_error_protection]]** - Degree to which a system protects users against making errors.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | + | * //**[[dido:public:ra:xapend:xapend.a_glossary:u:uerror_protection]]** - Degree to which a system protects users against making errors.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] |
| - | * //**[[dido:public:ra:xapend:xapend.a_glossary:u:user_interface_aesthetics]]** - Degree to which a user interface enables pleasing and satisfying interaction for the user.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | + | * //**[[dido:public:ra:xapend:xapend.a_glossary:u:interface_aesthetics]]** - Degree to which a user [[dido:public:ra:xapend:xapend.a_glossary:i:interface|interface]] enables pleasing and satisfying interaction for the user.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] |
| * //**[[dido:public:ra:xapend:xapend.a_glossary:a:accessibility]]** - Degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | * //**[[dido:public:ra:xapend:xapend.a_glossary:a:accessibility]]** - Degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use.//[[dido:public:ra:1.4_req:2_nonfunc:30_usability#fn__1| (1)]] | ||
| Line 38: | Line 34: | ||
| * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:ergonomics]] | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:ergonomics]] | ||
| - | ===== Metrics ===== | + | ==== 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 the Top]] |
| Usability as a characteristic is often considered a subjective quality and left to "interpretation", however, there are metrics which use to quantify these sub-characteristics. Before we delve into the definition of the specific metrics, it is important to understand why we need metrics rather than just rely on intuitive evaluations. | Usability as a characteristic is often considered a subjective quality and left to "interpretation", however, there are metrics which use to quantify these sub-characteristics. Before we delve into the definition of the specific metrics, it is important to understand why we need metrics rather than just rely on intuitive evaluations. | ||
| - | A core reason to collect Usability Metrics is to provide a data about stakeholder's understanding about a product's usability rather than the developer's understanding of usability. When the two understandings (i.e., interpretations) converge everyone is happy and a way forward can result. That result may be to either continue in the same direction or to have a reassessment of the user's needs. | + | A core reason to collect Usability Metrics is to provide data about a stakeholder's understanding of a product's usability rather than the developer's understanding of usability. When the two understandings (i.e., interpretations) converge everyone is happy resulting in a way forward. That result may be to either continue in the same direction or to have a reassessment of the user's needs. |
| The metrics must quantify that the system meets the [[dido:public:ra:1.4_req:2_nonfunc:30_usability#goals| goals]] of the overall system: | The metrics must quantify that the system meets the [[dido:public:ra:1.4_req:2_nonfunc:30_usability#goals| goals]] of the overall system: | ||
| Line 53: | Line 49: | ||
| * [[dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness]] | * [[dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness]] | ||
| - | * [[ddido:public:ra:1.4_req:2_nonfunc:30_usability:efficiency]] | + | * [[dido:public:ra:1.4_req:2_nonfunc:30_usability:efficiency]] |
| - | * [[dido:public:ra:1.4_req:2_nonfunc:20_usability:satisfaction]] | + | * [[dido:public:ra:1.4_req:2_nonfunc:30_usability:satisfaction]] |
| - | + | ||
| - | + | ||
| - | + | ||
| - | ==== Satisfaction Metrics ==== | + | |
| - | [[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 (( | + | |
| - | Saul McLeod, __Likert Scale Definition, Examples and Analysis __, Simply Psychology, 2019, Accessed 20 November 2020, | + | |
| - | [[https://www.simplypsychology.org/likert-scale.html]] | + | |
| - | )). | + | |
| - | + | ||
| - | Figure {{ref>likertScale}} gives a few of the Scales that Lickert defined. There are more available [[https://www.simplypsychology.org/likert-scale-examples.jpg| here]]: | + | |
| - | + | ||
| - | <figure likertScale> | + | |
| - | ^ Scale ^ Attitude / Sentiment ||||| | + | |
| - | ^ Agreement ^ Strongly Disagree ^ Disagree ^ Undecided ^ Agree ^ Strongly Agree ^ | + | |
| - | ^ Frequency ^ Never ^ Rarely ^ Sometimes ^ Often ^ Always ^ | + | |
| - | ^ Importance ^ Unimportant ^ Important ^ Moderately Important ^ Important ^ Very Important ^ | + | |
| - | ^ Quality ^ Very Poor ^ Poor ^ Fair ^ Good ^ Excellent ^ | + | |
| - | ^ Likelihood ^ Almost Never True ^ Usually Not True ^ Occasionally True ^ Usually True ^ Almost Always True ^ | + | |
| - | ^ //Score//| 1 | 3 | 3 | 4 | 5 | | + | |
| - | <caption>The Lickert Scale</caption> | + | |
| - | </figure> | + | |
| - | + | ||
| - | 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. | + | |
| - | * **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. | + | |
| - | + | ||
| - | ISO also provides some guidance in how to assess User Satisfaction. | + | |
| - | See: | + | |
| - | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:customer_satisfaction]] | + | |
| - | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:customer_complaints]] | + | |
| - | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:customer_dispute]] | + | |
| - | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:quality_monitor_and_measure]] | + | |
| - | + | ||
| - | * **Note:** For more information, see: [[https://blog.ansi.org/2018/07/customer-satisfaction-iso-10002-quality/#gref]] | + | |
| - | + | ||
| - | ==== DDS Specifics Metrics ==== | + | |
| - | [[dido:public:ra:1.4_req:2_nonfunc:30_usability| Return to Top]] | + | |
| + | ===== DIDO Specifics ===== | ||
| + | [[dido:public:ra:1.4_req:2_nonfunc:30_usability| Return to the Top]] | ||
| + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA </color></wrap> | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| Line 103: | Line 63: | ||
| ~~DISCUSSION:on|Outstanding Issues~~ | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| ~~DISCUSSION:off~~ | ~~DISCUSSION:off~~ | ||
| - | |||
| - | |||
| - | |||
dido/public/ra/1.4_req/2_nonfunc/30_usability.1605916750.txt.gz · Last modified: 2020/11/20 18:59 by nick
