Legacy Application Increment Analysis Using Resource Graphs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches to modernizing legacy software systems are manual, costly, and lack automated incremental analysis capabilities, relying heavily on expert knowledge and failing to allow users to specify design constraints and objectives for incremental modernization.

Innovation Solution

A computer-implemented method and system for automated increment analysis of legacy applications, which identifies and generates service increments based on specified constraints and objectives, using code analysis to determine resource subsets and generate resource graphs, enabling incremental modernization with minimal dependencies and adherence to logical boundaries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual approaches are used for modernizing legacy software systems, then expert knowledge can be applied to ensure correctness, but the process becomes costly and time-consuming

Engineering Contradiction:
Improvemodernization correctnessVSAvoidmodernization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs automated analysis of legacy applications, automatically identifying service boundaries, resources, and dependencies without requiring continuous manual expert intervention. The automated increment analysis engine processes application code, metadata, and configuration files to generate modernization recommendations autonomously

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Manual expert analysis is replaced with an automated computational system that uses static analysis, graph processing, and algorithmic approaches to identify modernization opportunities. The system substitutes human mechanical analysis with automated software-based analysis engines

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

2Extent of automation

If static analysis tools are used for legacy system modernization, then some automation is achieved, but the analysis capabilities remain limited and lack incremental analysis functionality

Engineering Contradiction:
Improveanalysis automationVSAvoidanalysis capability
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The system segments the legacy application into discrete services, resources, and dependencies using graph-based modeling. Each component is analyzed independently and then recombined to form comprehensive modernization plans, enabling both automation and detailed analysis capability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The analysis system is designed to be dynamic and configurable, allowing users to specify different service properties, constraints, and objectives. The system can adapt its analysis approach based on user-defined parameters and generate different types of increment analyses depending on the modernization goals

Inventive Principle:
Principle #15Dynamics

3Reliability

If comprehensive analysis of all applications is performed, then complete modernization coverage is achieved, but the complexity and cost increase significantly

Engineering Contradiction:
Improvemodernization coverageVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables partial analysis by allowing users to focus on specific services, resources, or application subsets. The increment analysis can be performed on selected portions of the legacy system rather than requiring analysis of the entire system, reducing complexity while maintaining coverage where needed

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The legacy system is divided into manageable services and resources, allowing the analysis to be performed in smaller, less complex units. Each service can be analyzed independently, and results can be aggregated to achieve comprehensive coverage without analyzing everything simultaneously

Inventive Principle:
Principle #1Segmentation

4Productivity

If incremental modernization is implemented, then risk is reduced and progress is measurable, but identifying appropriate increments requires complex analysis

Engineering Contradiction:
Improvemodernization progressVSAvoidanalysis complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an automated increment analysis engine that acts as an intermediary between the legacy system and the modernization process. This engine automatically identifies suitable service increments based on user-defined properties and constraints, eliminating the need for manual identification of increment boundaries

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The complex manual process of identifying appropriate service increments is replaced with automated computational analysis. The system uses graph processing, constraint satisfaction, and optimization algorithms to automatically determine which services constitute appropriate increments for modernization

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

Data Source

PatentUS12632305B2Incremental analysis of legacy applications
Publication Date: 2026.05.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12632305B2 patent drawing
  • US12632305B2 patent drawing
  • US12632305B2 patent drawing

AI summary

A method, system, and computer program product for automated increment analysis of legacy applications are provided. The method receives a set of service properties for a service to be generated from a set of applications. The set of applications are associated with a set of resources. A subset of resources are determined based on the set of service properties. The subset of resources are to be included in the service. A resource graph of the subset of resources is generated based on the subset of resources and the set of service properties. The method generates a service increment including at least a portion of the subset of resources based on the resource graph and the set of service properties.