Custom Code Maintenance Scoring via Metadata Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business systems face challenges in managing and maintaining custom code modules, as they often lack awareness of their existence, ownership, and integration into lifecycle maintenance programs, leading to unsupported and unmanaged code that poses risks to system stability and support.

Innovation Solution

A method is introduced that involves receiving metadata about custom code modules, applying rules from a template to calculate a score representing the degree of maintenance, using a score calculator module to assess transparency, ownership, and integration, and providing the score to a user interface, thereby enhancing awareness and management of custom code within the business system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom code modules are developed by end-users or third parties, then system flexibility and adaptability improve, but awareness of code existence and ownership deteriorates

Engineering Contradiction:
Improvesystem flexibilityVSAvoidawareness of code existence
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system automatically queries the custom code library to obtain metadata about custom code modules and provides feedback to users through a user interface, enabling awareness of code existence, location, and ownership without requiring manual tracking

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The score calculator module automatically calculates maintenance scores based on retrieved metadata and applies rules from a rules template, eliminating the need for manual assessment and providing self-service monitoring of code maintenance status

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If custom code modules are integrated into the business system, then functionality improves, but integration into lifecycle maintenance program deteriorates

Engineering Contradiction:
Improvecode integrationVSAvoidlifecycle maintenance integration
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system retrieves metadata including integration information from the custom code library and provides feedback through calculated maintenance scores, enabling automatic assessment of whether code is integrated into the lifecycle maintenance program

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the state of maintenance assessment from manual to automated by calculating numerical scores based on metadata parameters such as owner assignment, integration status, and maintenance program inclusion

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If manual tracking of custom code is performed, then ownership awareness improves, but time consumption increases

Engineering Contradiction:
Improveownership awarenessVSAvoidtime for code tracking
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The score calculator module automatically retrieves metadata from the custom code library, applies rules from a rules template, and calculates maintenance scores without manual intervention, eliminating time-consuming tracking while maintaining comprehensive ownership awareness

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual tracking mechanisms with automated computational processes that query databases, process metadata, and generate scores through algorithmic evaluation of maintenance criteria

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS8707262B2Code scoring
Publication Date: 2014.04.22 SAP SE
  • US8707262B2 patent drawing
  • US8707262B2 patent drawing
  • US8707262B2 patent drawing

AI summary

Methods and apparatus, including computer program products, are provided for code scoring. In one aspect, there is provided a computer-implemented method. The method may include receiving metadata including information representative of at least one custom code module used in a business system; receiving at least one rule from a rules template; and calculating, based on the received metadata and the received at least one rule, a score representative of whether the at least one custom code module is maintained. Related apparatus, systems, methods, and articles are also described.