User Tools

Site Tools


dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness [2021/01/15 16:46]
ian
dido:public:ra:1.4_req:2_nonfunc:30_usability:effectiveness [2021/06/11 14:49]
char
Line 1: Line 1:
-====== 4.2.6.1 Effectiveness Metrics ======+====== 4.3.6.1 Effectiveness Metrics ======
 [[dido:​public:​ra:​1.4_req:​2_nonfunc:​30_usability| Return to Usability]] [[dido:​public:​ra:​1.4_req:​2_nonfunc:​30_usability| Return to Usability]]
  
 ===== About ===== ===== About =====
-[[dido:​public:​ra:​1.4_req:​2_nonfunc:​30_usability:​effectiveness | Return to Top]] 
- 
 There are two ways to calculate effectiveness:​ There are two ways to calculate effectiveness:​
  
Line 18: Line 16:
 **Mathematically:​** **Mathematically:​**
  
-<​m>​Effectiveness = {sum{user=1}{numberOfTesters}{Completed Tasks by user} / sum{user=1}{numberOfTesters} {Total Tasks assigned to user}} * 100%</​m>​ +<color white>​o</​color> ​<​m>​Effectiveness = {sum{user=1}{numberOfTesters}{Completed Tasks by user} / sum{user=1}{numberOfTesters} {Total Tasks assigned to user}} * 100%</​m> ​\\ 
- +\\ 
 +\\ 
 +\\ 
 +\\
 Here is an example where the system uses 10 tasks and all the tasks are completed by 5 users. The results are: Here is an example where the system uses 10 tasks and all the tasks are completed by 5 users. The results are:
  
Line 51: Line 51:
 Recording each instance of an error along with a description can help refine the system to prevent these errors in the future. For example, “user entered last name in the first name field”. ​ Recording each instance of an error along with a description can help refine the system to prevent these errors in the future. For example, “user entered last name in the first name field”. ​
  
-In many ways, this metric can be considered similar to the Task Complete Rate metric but instead of counting completed tasks the errors are counted. Note, many there can be many errors required to complete ​a single task. For example, a data entry form required for one task can have errors associated with each field. Each of these errors can have a negative impact on the overall efficiency. ​+In many ways, this metric can be considered similar to the Task Complete Rate metric but instead of counting completed tasks the errors are counted. 
 +Note, many errors ​can occur in accomplishing ​a single task. For example, a data entry form required for one task can have errors associated with each field. Each of these errors can have a negative impact on the overall efficiency. ​
  
 Another enhancement to this metric wold be to assign a weight to the error. For example, data entry errors are less dramatic and important than unintended actions. Therefore, unintended actions would receive a higher weighting than data entry. Another enhancement to this metric wold be to assign a weight to the error. For example, data entry errors are less dramatic and important than unintended actions. Therefore, unintended actions would receive a higher weighting than data entry.
Line 58: Line 59:
 [[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]]
  
-<color #FF0000><todo>TBD</todo></color>+  : <wrap hi><color redTo be added/​expanded in future revisions of the DIDO RA </color></wrap 
  
 /​**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- /​**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
dido/public/ra/1.4_req/2_nonfunc/30_usability/effectiveness.txt · Last modified: 2021/08/18 10:52 by murphy