Hierarchical Code Quality Evaluation Metrics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software development using hierarchical structures faces challenges in identifying design problems and evaluating the quality of codebases across various levels, making it difficult to ensure the quality of codebases.

Innovation Solution

A method and system for evaluating codebase quality using a hierarchical structure with metrics and indicators defined at each level, allowing for the calculation and normalization of metrics, and the combination of indicators to provide a comprehensive evaluation of code quality across multiple levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Shape

If hierarchical structure is used for software development, then software organization is improved, but difficulty in identifying design problems and evaluating code quality increases

Engineering Contradiction:
Improvesoftware organizationVSAvoiddesign problem identification
Core Design Contradiction:
ShapeVSDifficulty of detecting and measuring

Solution Approach 1:

The patent divides the codebase evaluation into multiple hierarchical levels (package level, class level, method level), with each level having its own specific metrics and indicators. This segmentation allows targeted analysis at each level while maintaining the overall hierarchical structure, making it easier to identify design problems at specific levels without losing the organizational benefits of the hierarchy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediate evaluation layers including metrics calculation, indicator determination, and index generation between the hierarchical structure and the final quality assessment. These intermediaries transform complex code data into meaningful quality indicators at each level, facilitating problem identification while preserving the hierarchical organization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Shape

If hierarchical structure is used for software development, then software organization is improved, but codebase quality evaluation capability deteriorates

Engineering Contradiction:
Improvesoftware organizationVSAvoidcodebase quality evaluation
Core Design Contradiction:
ShapeVSMeasurement precision

Solution Approach 1:

The patent implements level-specific metrics and indicators for each hierarchical level (package, class, method), allowing precise quality measurement at each level rather than applying a single evaluation method to the entire codebase. This segmentation enables accurate local assessment while maintaining hierarchical organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a vertical evaluation dimension to the existing horizontal hierarchical structure by introducing multiple evaluation layers (metrics → indicators → indices) at each level. This multi-dimensional approach enhances measurement precision without disrupting the organizational hierarchy.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8473907B1Computer programming adaptive analysis
Publication Date: 2013.06.25 BLACK DUCK SOFTWARE INC
  • US8473907B1 patent drawing
  • US8473907B1 patent drawing
  • US8473907B1 patent drawing

AI summary

A method and apparatus for evaluating quality of a codebase is provided. The evaluation is provided by developing metrics, indicators, and indices for all levels of a codebase to provide indicators of quality and to enable identification of code blocks that need to be improved.