Execution Controller for Legacy Application Interface Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy applications often have outdated graphical user interfaces, making it difficult to communicate effectively with new applications that require updated interfaces while maintaining the useful services of the legacy applications, leading to issues with data synchronization and user navigation.

Innovation Solution

A computer-implemented method that provides a first graphical user interface for a second application using an execution controller to manage a stack of action scripts, allowing batch processing and data input, which maps display outputs and synchronizes the applications, enabling indirect upgrading of the legacy application's interface without reprogramming, and supports multi-user environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a new application is developed to reuse services of a legacy application with an updated graphical user interface, then the user interface is improved, but communication difficulties arise between the new application and the legacy application due to different execution contexts

Engineering Contradiction:
Improveuser interfaceVSAvoiddata communication
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an execution controller as an intermediary component that mediates communication between the new application and the legacy application. The execution controller receives navigation inputs from the new application, manages the execution context of the legacy application, and ensures proper data synchronization. This intermediary resolves the communication difficulties by providing a controlled interface that handles context differences between the two applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If batch processing is used to execute action scripts in the legacy application, then data synchronization is improved, but processing time increases

Engineering Contradiction:
Improvedata synchronizationVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-compiling navigation inputs into action scripts before execution. The execution controller prepares the sequence of operations in advance, storing them as structured action scripts that can be efficiently processed by the legacy application. This pre-preparation reduces execution time while maintaining data synchronization, as the scripts are ready to be processed in batch mode without requiring complex real-time computations.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If display outputs of the second application are mapped to the first application, then interface compatibility is improved, but complexity of mapping increases

Engineering Contradiction:
Improveinterface compatibilityVSAvoidmapping complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal mapping mechanism where the execution controller handles multiple types of display outputs and navigation inputs through a standardized interface. The mapping system is designed to be multi-functional, supporting various display formats and navigation methods while maintaining a consistent approach. This universality reduces mapping complexity by providing a single, flexible framework that can adapt to different scenarios without requiring separate mapping logic for each case.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP1906305B1Method and system for data preparation and communication between software applications
Publication Date: 2013.03.06 SAP SE
  • EP1906305B1 patent drawingFigure 1~2
  • EP1906305B1 patent drawingFigure 3
  • EP1906305B1 patent drawingFigure 4

AI summary

The invention relates to a computer implemented method of providing a first graphical user interface (106; 810) of a first application (104; 800) for a second application (112; 802), the method comprising: - receiving a navigation input at the first application (104; 800); - adding an action script to an ordered stack (830) of action scripts maintained by an execution controller, wherein the added action script corresponds to the navigation input; - providing the ordered stack (830) of action scripts to the second interface; - executing the ordered stack (830) of action scripts; - mapping a display output of the second application (112; 802) resulting from the execution of the ordered stack (830) to the next display output of the first application (104; 800).