Configurable Explicative Compiler for Legacy Code Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy code from older systems is often not readable or understandable by newer machine systems, making it challenging to migrate functionality effectively during system upgrades, as the code format and style become obsolete, and the functionality of older systems remains valuable but difficult to comprehend and utilize in newer systems.

Innovation Solution

A method involving a configurable explicative compiler that identifies functional elements in legacy source code, maps them to user-defined representations, and compiles the code into a person-readable language, allowing for the migration of legacy source code into targeted systems with maintained or improved functionality, using pseudocode, diagrams, and encapsulations to ensure uninterrupted operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If legacy source code is directly migrated to a newer system, then the functionality is preserved, but the code becomes unreadable and ununderstandable by the new system and practitioners

Engineering Contradiction:
Improvefunctionality preservationVSAvoidcode readability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary representation layer between legacy code and the target system. This intermediary format preserves the original legacy code while adding annotations and mappings that make the code understandable in the new system context, thus maintaining both functionality and readability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary analysis and annotation of legacy code before migration. By pre-identifying functional elements, data structures, and relationships, the system prepares the code in advance to ensure both functionality preservation and improved readability in the target system

Inventive Principle:
Principle #10Preliminary action

2Reliability

If legacy code format and style are maintained during migration, then the original functionality is preserved, but the code cannot be comprehended or utilized by newer systems

Engineering Contradiction:
Improveoriginal functionalityVSAvoidsystem compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent changes the parameters of code representation by adding metadata, annotations, and structural markers to the legacy code. These parameter changes enable the code to be interpreted by newer systems while preserving the original functionality and format

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a composite code structure that combines original legacy code with additional metadata and annotations. This composite format maintains the original functionality while adding layers of interpretability for modern systems

Inventive Principle:
Principle #40Composite materials

3Ease of operation

If legacy code is rewritten in a newer language or format, then readability and compatibility improve, but the original functionality may be lost or altered

Engineering Contradiction:
Improvecode comprehensionVSAvoidfunctionality accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates a copied representation of the legacy code that maintains the original functionality while adding interpretive layers. The intermediary format serves as a faithful copy that enhances readability without altering the underlying logic and behavior

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10324712B1Method and system of migrating legacy code for upgraded systems
Publication Date: 2019.06.18 NOLAN THOMAS A
  • US10324712B1 patent drawing
  • US10324712B1 patent drawing
  • US10324712B1 patent drawing

AI summary

A method of maintaining or improving functionality of legacy code for operation in a new machine system is disclosed. Reference code and documentation are leveraged to provide functionality of the machine system. The sections may be identified and presented as user defined representations (for example, pseudocode, diagrams, descriptive text, or encapsulations) so that the reference code may be migrated to a newer machine system and the sections may be re-written as necessary to make the sections of reference compatible with the new machine system.