Error Rate | Error Density | ERs 6 Months | ERs 1 Year | ERs 2 Year

Error Rate
Handle: Error Rate
Description: The number of changes due to error. If a module is changed due to an error report (as opposed to a change request), then it receives a one up count. It cannot receive more than a one up for a given error report.
Observation: By csh, awk and Perl scripts on programs that have associated file or module changes with the error reports.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is one error - one count.
Range: Above 0.
Usage: To identify the number of changes due to an error report.
Relationship: It's a measure of quality.
Threshold: None.
Validation: It is what it is by definition.

+ Top

Error Density
Handle: Error Density
Description: ER/KLOC
Observation: By csh, awk and Perl scripts on programs that have associated file or module changes with the error reports.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is ER/KLOC.
Range: Unlimited.
Usage: To show if a design element is generating more errors than it should.
Relationship: It is a measure of chronic problems from the standpoint it being beyond threshold combined with on-going generation of error reports related to the design element.
Threshold: It varies by language 13.7 for C; 17 for Ada; 13.7 is also used for C++ because no threshold has been identified. It appears to be nearer 15.
Validation: Capers Jones identifies 13.7 and 17 in his book, Software Quality.

+ Top

Error Reports in Six Months
Handle: PRs in 6 Mths.
Description: Number of PRs
Observation: The number of defects logged in a tracking system for each design object.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count
Range: Unlimited.
Usage: To show if a design element is generating more errors than it should.
Relationship: It is a measure of chronic problems from the standpoint it being beyond threshold combined with on-going generation of error reports related to the design element.
Threshold: No known threshold
Validation: None Known

+ Top

Error Reports in One Year
Handle: PRs in 1 Yr.
Description: Number of PRs
Observation: The number of defects logged in a tracking system for each design object.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count
Range: Unlimited.
Usage: To show if a design element is generating more errors than it should.
Relationship: It is a measure of chronic problems from the standpoint it being beyond threshold combined with on-going generation of error reports related to the design element.
Threshold: No known threshold
Validation: None Known

+ Top

Error Reports in Two Years
Handle: PRs in 2 Yrs
Description: Number of PRs
Observation: The number of defects logged in a tracking system for each design object.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count
Range: Unlimited.
Usage: To show if a design element is generating more errors than it should.
Relationship: It is a measure of chronic problems from the standpoint it being beyond threshold combined with on-going generation of error reports related to the design element.
Threshold: No known threshold
Validation: None Known

+ Top