If the test is planned and designed effectively, it can reveal enough information about the causes of the accuracy problems to justify a decision not to use attribute analysis at all. In cases where the trial does not provide sufficient information, the analysis of the attribute agreement allows for a more detailed review to inform the introduction of training changes and error correction in the measurement system. Second, the evaluation of the attribute agreement should be applied and the detailed results of the audit should provide a number of information that will help to understand how evaluation can be the best way to be organized. The accuracy of a measurement system is analyzed by segmenting into two main elements: repeatability (the ability of a particular evaluator to assign the same value or attribute several times under the same conditions) and reproducibility (the ability of several assessors to agree on a set of circumstances). In the case of an attribute measurement system, repeatability or reproducibility problems necessarily pose precision problems. In addition, if global accuracy, repeatability and reproducibility are known, distortions can also be detected in situations where decisions are always wrong. Attribute analysis can be an excellent tool for detecting the causes of inaccuracies in a bug tracking system, but it must be used with great care, reflection and minimal complexity, should it ever be used. The best way to do this is to first monitor the database and then use the results of that audit to perform a targeted and optimized analysis of repeatability and reproducibility. First, the analyst should determine that there is indeed attribute data. One can assume that the assignment of a code – that is, the division of a code into a category – is a decision that characterizes the error with an attribute. Either a category is correctly assigned to an error, or it is not. Similarly, the appropriate source location is either attributed to the defect or not.
These are “yes” or “no” and “correct allocation” or “wrong allocation” answers. This part is pretty simple. Once it is established that the bug tracking system is a system for measuring attributes, the next step is to examine the concepts of accuracy and accuracy that relate to the situation. First, it helps to understand that accuracy and precision are terms borrowed from the world of continuous (or variable) gags. For example, it is desirable that the speedometer in a car can carefully read the right speed over a range of speeds (z.B. 25 mph, 40 mph, 55 mph and 70 mph), regardless of the drive. The absence of distortion over a range of values over time can generally be described as accuracy (Bias can be considered wrong on average).