Legacy FORTRAN Migration via Dependency Structure Matrix
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy FORTRAN systems face challenges due to lack of documentation, outdated software design, disparate programming styles, and a shortage of skilled programmers familiar with the language, making maintenance, migration, and modernization difficult.
Innovation Solution
A method and system for migrating non-object-oriented applications to object-oriented platforms by parsing the application, generating a dependency structure matrix (DSM) representation, performing analysis to create a modular framework, and mapping it to an object-oriented code skeleton, facilitating translation from FORTRAN to an object-oriented language like JAVA.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automated dependency analysis and code transformation tools are used to migrate legacy FORTRAN systems, then productivity and modernization capability are improved, but device complexity and implementation difficulty increase
Solution Approach 1:
The patent introduces an intermediary dependency analysis system that acts as a mediator between legacy FORTRAN code and modern object-oriented platforms. This intermediary automatically extracts dependencies, generates dependency structure matrices, and facilitates transformation without requiring direct complex interactions between the legacy system and modern platform, thereby improving productivity while managing complexity.
Solution Approach 2:
The patent replaces manual mechanical processes of code analysis and transformation with automated computational tools. Instead of manually analyzing dependencies and rewriting code, the system uses automated dependency extraction algorithms and code transformation engines to perform these tasks, significantly improving migration efficiency while the automation handles the complexity.
2Ease of operation
If manual analysis and transformation methods are used for legacy systems, then system complexity is reduced and ease of operation is improved, but productivity and migration efficiency deteriorate
Solution Approach 1:
The patent implements self-service capabilities where the dependency analysis system automatically performs code parsing, dependency extraction, and transformation planning without requiring extensive manual intervention. The system serves itself by autonomously analyzing the legacy codebase and generating migration plans, maintaining operational simplicity while dramatically improving migration efficiency through automation.
3Manufacturing precision
If comprehensive dependency analysis is performed on legacy code, then manufacturing precision and code transformation accuracy are improved, but loss of time and analysis duration increase
Solution Approach 1:
The patent performs preliminary dependency analysis and code examination before the actual transformation process. By pre-identifying all dependencies, data flows, and structural relationships in the legacy FORTRAN code, the system prepares a comprehensive transformation plan that ensures high accuracy during execution. This preliminary action prevents rework and ensures precise transformation while optimizing overall time investment.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods, systems, and computer-readable media are described herein for migrating a non-object-oriented application to an object-oriented platform. The non-object-oriented application may be received. The non-object-oriented application may be parsed into elements of the non-object-oriented application. A design structure matrix (DSM) representation (110) of the elements may be generated. A final object model (126) may be generated based on the DSM representation (110). The final object model (126) may be mapped to a code skeleton representation (128) of an object-oriented development environment.