Integrated Code Inspection Framework with Cascading Check Variants

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Automated program code checking is time-consuming and often requires separate systems, leading to delays and increased costs due to the complexity of managing multiple checking processes, which can result in software development delays and the introduction of new errors.

Innovation Solution

An integrated code inspection framework that allows for the assignment of check variants to development objects within an integrated development environment (IDE), enabling one-click code inspection execution with user-specified rules, highlighting non-compliant code segments, and providing detailed error/warning details for early detection and correction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple separate automated checking processes are used to review program code, then code inspection coverage is improved, but system complexity and execution time increase

Engineering Contradiction:
Improvecode inspection coverageVSAvoidnumber of separate checking systems
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple separate automated checking processes into a single integrated code inspection system. The framework unifies various check types (static analysis, dynamic analysis, security scanning, etc.) into one cohesive platform that can execute multiple check variants simultaneously, reducing system complexity while maintaining comprehensive code inspection coverage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The integrated code inspection framework is designed as a universal system capable of performing multiple types of code checking functions through configurable check variants. A single system instance can execute different check rules and analysis methods on the same codebase, eliminating the need for multiple specialized separate systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If multiple separate automated checking processes are executed, then comprehensive code review is achieved, but development time and resource consumption increase

Engineering Contradiction:
Improvecode review completenessVSAvoidsoftware development speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The framework enables continuous code inspection by integrating checking processes into the development workflow. Code can be analyzed continuously as it is written or modified, rather than requiring sequential execution of separate checking processes. This continuous analysis maintains comprehensive review coverage while minimizing disruption to development speed.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system performs preliminary code analysis and provides feedback during the development process itself, before code is finalized or deployed. By conducting checks preliminarily and iteratively, developers can correct issues early without requiring multiple separate post-development checking cycles, thus maintaining both completeness and productivity.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If automated code checking is integrated into the development environment, then ease of operation is improved, but system complexity increases

Engineering Contradiction:
Improvecode inspection accessibilityVSAvoidintegration architecture
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The framework is designed to be self-configuring and automatically integrates with the development environment. Once installed, it automatically detects projects, configures appropriate check variants, and executes inspections without requiring complex manual setup or configuration by developers. This self-service capability provides ease of operation while managing integration complexity internally.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11354139B2Integrated code inspection framework and check variants
Publication Date: 2022.06.07 SAP SE
  • US11354139B2 patent drawing
  • US11354139B2 patent drawing
  • US11354139B2 patent drawing

AI summary

An integrated code inspection framework using check variants is provided herein. Integrated code inspection can include associating a check variant with a development object in a development project. Additionally, a check variant can be associated with a development project. A check variant associated with a development project can cascade to development objects in the development project. A check variant associated with a development object can cascade to related development objects, based on their hierarchical relationship. A check variant can be executed against a development object to identify code which triggers check rules of the check variant. The check variants executed can come from the development project or related development objects based on the cascade of check variants. Results of the code inspection via the check variants can be aggregated and displayed in a user interface, and integrated with the code of a development object.