Abstract: Static analysis of a code base is expanded beyond finding faults to also find code instances where a particular fault could have occurred but did not. A conformance count reflects code portions that satisfy a specified coding rule per static analysis, and a nonconformance count reflects code portions that do not satisfy the coding rule. Various metrics computed from the conformance count and nonconformance count drive software development quality assessments. For example, bugs or bug categories may be prioritized for developer attention, static analysis tools are evaluated based on the metrics, to reduce noise by eliminating low-value bug alerts. Particular areas of expertise of developers and developer groups are objectively identified. Source code editors are enhanced to provide specific recommendations in context. Other quality enhancements are also provided.

Abstract: Static analysis of a code base is expanded beyond finding faults to also find code instances where a particular fault could have occurred but did not. A conformance count reflects code portions that satisfy a specified coding rule per static analysis, and a nonconformance count reflects code portions that do not satisfy the coding rule. Various metrics computed from the conformance count and nonconformance count drive software development quality assessments. For example, bugs or bug categories may be prioritized for developer attention, static analysis tools are evaluated based on the metrics, to reduce noise by eliminating low-value bug alerts. Particular areas of expertise of developers and developer groups are objectively identified. Source code editors are enhanced to provide specific recommendations in context. Other quality enhancements are also provided.