Legacy Code Mining Tool for API Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy system functionalities are not directly compatible with modern program architectures, requiring resource-intensive and time-consuming recoding for integration, which is inefficient and cumbersome.

Innovation Solution

A system and method for mining software code to extract and convert legacy system functionalities into a compatible format, such as an API, using a mining tool that identifies, captures, and deploys modular functions from legacy systems to modern architectures without manual code rewriting, enabling seamless integration and reuse.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If legacy functionalities are directly integrated into modern systems, then compatibility is improved, but system complexity increases due to architectural incompatibility

Engineering Contradiction:
ImprovecompatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary conversion system that translates legacy functionalities into modern API formats. This mediator handles the architectural incompatibility by converting monolithic legacy code into modular API-compatible functions, allowing integration without direct compatibility requirements between legacy and modern systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments monolithic legacy functionalities into smaller, independently executable API functions. By dividing large legacy systems into modular components with specific interfaces, the system reduces complexity while maintaining adaptability to modern architectures.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If manual recoding is performed to integrate legacy functionalities, then compatibility is improved, but time consumption and resource usage increase

Engineering Contradiction:
ImprovecompatibilityVSAvoidintegration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements self-service automation where the conversion system automatically analyzes legacy code, identifies functional components, and generates API-compatible code without requiring manual recoding. This automated process significantly reduces integration time and resource consumption while maintaining compatibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary automated analysis and conversion of legacy functionalities before integration. By pre-processing legacy code to identify extractable functions and automatically generating API wrappers, the system eliminates time-consuming manual recoding steps.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If legacy code is recoded manually, then functionality compatibility is improved, but resource consumption increases

Engineering Contradiction:
Improvefunctionality compatibilityVSAvoidcomputational resources
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent replaces manual mechanical recoding processes with automated computational systems. The conversion tool uses algorithms to automatically analyze legacy code structure, identify functional boundaries, and generate compatible API code, substituting human effort with efficient automated processing.

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

4Adaptability or versatility

If legacy functionalities are extracted and converted, then reusability is improved, but conversion complexity increases

Engineering Contradiction:
ImprovereusabilityVSAvoidconversion complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent changes the interface parameters and structural parameters of legacy functionalities to match modern API standards. By systematically transforming code organization, function signatures, and interface definitions, the system enables reusability while managing conversion complexity through standardized transformation rules.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10996948B2Software code mining system for assimilating legacy system functionalities
Publication Date: 2021.05.04 BANK OF AMERICA CORP
  • US10996948B2 patent drawing
  • US10996948B2 patent drawing
  • US10996948B2 patent drawing

AI summary

A system, computer program product, and computer-implemented method for mining software code and assimilating legacy system functionalities are provided. Embodiments comprise a system configured for installing a mining tool on a first system having a first format, the mining tool being configured to continually capture code stored on the first system; identifying a function on the first system, wherein the function is configurable to be independently executable; pulling the function from the first system; converting the function from the first format to a second format; and deploying the function in the second format onto a second system, wherein the function is stored on the second system in the second format and configured to be called by a program.