COBOL Reference Architecture Legacy Extension

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Developers face challenges in modifying legacy COBOL applications to add new functionality without rewriting the existing code, as they lack tools to easily reuse COBOL functionality across different interactive types and ensure consistency.

Innovation Solution

The COBOL Reference Architecture (CRA) system uses a transactional workflow driver (TWD) to visualize legacy applications, identify extender components, and generate target application processing vectors, enabling the extension of legacy applications with new functionality that is consistent and interchangeable across various computing environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers modify legacy COBOL applications to add new functionality, then new functionality is integrated, but code complexity and modification difficulty increase

Engineering Contradiction:

Improvenew functionality integrationVSAvoidcode complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the legacy COBOL application into modular components using object-oriented techniques. Classes and objects are introduced to divide the monolithic codebase into reusable, manageable units, reducing overall complexity while enabling new functionality to be added as separate modules rather than scattered modifications throughout the legacy code.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (wrapper classes and adapter patterns) between the legacy COBOL code and new functionality. This intermediary allows new features to be integrated without directly modifying the legacy code, maintaining its integrity while enabling adaptability through the mediating layer that handles communication and data transformation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If developers rewrite legacy COBOL applications to add new functionality, then functionality can be enhanced, but development time and resources increase

Engineering Contradiction:

Improvefunctionality enhancementVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by creating a systematic framework of classes, interfaces, and design patterns before adding new functionality. This preliminary object-oriented structure is established once, then new features can be rapidly added by implementing existing interfaces or extending existing classes, significantly reducing subsequent development time compared to ad-hoc modifications.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent creates universal, reusable components through object-oriented design that can serve multiple functions. A single class or module can be instantiated and configured to provide different functionalities, reducing the need to write new code for each enhancement and thereby reducing overall development time while maintaining versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of manufacture

If developers use traditional COBOL techniques to add functionality, then legacy code can be modified, but consistency and interchangeability across interactive types decrease

Engineering Contradiction:

Improveease of modificationVSAvoidinterchangeability across interactive types

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements universal interfaces and base classes that define standardized behavior across different interactive types (e.g., web, mobile, batch). All COBOL components implement these common interfaces, ensuring consistency in how they are used regardless of the interactive type. This allows the same component to be interchangeably used across different deployment scenarios without modification.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces dynamic configuration and runtime binding capabilities that allow the system to adapt to different interactive types without recompiling or reconfiguring the core logic. Components can be dynamically instantiated and bound to different interfaces based on runtime requirements, enhancing interchangeability while maintaining ease of modification through the flexible object-oriented structure.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentEP2685376B1COBOL reference architecture

Publication Date: 2017.10.11 ACCENTURE GLOBAL SERVICES LTD

Figure 1
Figure 2
Figure 3

AI summary

The COBOL reference architecture (CRA) system and the transactional workflow driver (TWD) provide an efficient and effective way to extend an existing application using modern architecture techniques without rewriting the existing application. The (CRA) system and TWD provide a way to generate new and interchangeable COBOL language functionality for multiple interactive types (e.g., transaction servers and/or transaction managers) running in various computing environments, including: a WebSphere message queue (MQ) transaction server; a Customer Information Control System (CICS) transaction server; an Information Management System (IMS) transaction server; and a batch transaction manager.