Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • n/a

    • This option chooses not to change the Core sizes for the scenario.

  • Low (20% Core Removed)

    • This option specifies that the number of files in this Area/Name combination that are part of a Core should be reduced by 20%. This requires a minimal effort of code design quality improvement, and will only yield decent improvement in overall defect density for codebases with extreme design quality challenges.

  • Moderate (60% Core Removed)

    • This option specifies that the number of files in this Area/Name combination that are part of a Core should be reduced by 60%. This requires a moderate effort of code design quality improvement, and should yield significant improvements in overall defect density for codebases with severe code design quality challenges.

  • High (100% Core Removed)

    • This option specifies that the number of files in this Area/Name combination that are part of a Core should be reduced by 100%, meaning all Emerging and Critical Cores will be completely removed. . This is the highest level of effort for refactoring code design quality, and should yield vast improvements in overall defect density for codebases with code design quality challenges.

Note that the ROI tool does not say how to reduce the size of a core. For one possibility on doing so, please see the Technical Health Improvement Plan, which is also described in the CodeMRI® Care User’s Guide, https://silverthread.atlassian.net/wiki/spaces/CKB/pages/961773820/CodeMRI+Care+User+s+Guide#CodeMRI%C2%AECareUser%27sGuide-ImprovingTechnicalHealth .

...