In this example, a repeatability assessment is used to illustrate the idea, and it also applies to reproducibility. The fact is that many samples are needed to detect differences in an analysis of the attribute, and if the number of samples is doubled from 50 to 100, the test does not become much more sensitive. Of course, the difference that needs to be identified depends on the situation and the level of risk that the analyst is prepared to bear in the decision, but the reality is that in 50 scenarios, it is difficult for an analyst to think that there is a statistical difference in the reproducibility of two examiners with match rates of 96 percent and 86 percent. With 100 scenarios, the analyst will not be able to see any difference between 96% and 88%. Like any measurement system, the accuracy and accuracy of the database must be understood before the information is used (or at least during use) to make decisions. At first glance, it appears that the apparent starting point begins with an analysis of the attribute (or attribute-Gage-R-R). That may not be a very good idea. Despite these difficulties, performing an attribute analysis on bug tracking systems is not a waste of time. In fact, it is (or may be) an extremely informative, valuable and necessary exercise. The analysis of attributes should only be applied with caution and with a certain focus.
However, a bug tracking system is not an ongoing payment. The assigned values are correct or not; There is no (or should not) grey area. If codes, locations and degrees of gravity are defined effectively, there is only one attribute for each of these categories for a particular error. 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. Repeatability and reproducibility are components of accuracy in an analysis of the attribute measurement system, and it is advisable to first determine if there is a precision problem. This means that before designing an attribute contract analysis and selecting the appropriate scenarios, an analyst should urgently consider monitoring the database to determine if past events have been properly coded. Analytically, this technique is a wonderful idea. But in practice, the technique can be difficult to execute judiciously.
First, there is always the question of sample size.