dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness
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:effectiveness [2021/06/11 14:49] char |
dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness [2021/08/18 10:52] (current) murphy |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness| Return to Top]] | [[dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness| Return to Top]] | ||
| - | Another way to understand an application or system efficiency from a usability perspective is to count the errors instead of counting the success of completing tasks. Every error can have more consequences requiring more work to "undo" thus negatively impacting Effectiveness and efficiency. | + | Another way to understand an [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] or system efficiency from a [[dido:public:ra:xapend:xapend.a_glossary:u:usability|usability]] perspective is to count the errors instead of counting the success of completing tasks. Every error can have more consequences requiring more work to "undo" thus negatively impacting Effectiveness and efficiency. |
| The following is a partial list that users can make while completing tasks(( | The following is a partial list that users can make while completing tasks(( | ||
| Jeff Sauro, __10 Essential Usability Metrics__, Measuring U, 30 November 2011, Accessed 19 November 2020, | Jeff Sauro, __10 Essential Usability Metrics__, Measuring U, 30 November 2011, Accessed 19 November 2020, | ||
dido/public/ra/1.4_req/2_nonfunc/30_usability/effectiveness.1623437369.txt.gz · Last modified: 2021/06/11 14:49 by char
