Event Orchestration for Software Maintenance Complexity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software applications become increasingly complex and costly to maintain due to custom business logic being dispersed and duplicated across multiple layers and applications, making it time-consuming and expensive to enhance and modify business rules and processes.

Innovation Solution

The automated generation of reusable user interface event handling routines from business and design requirements, allowing these routines to exist independently from user interface components, enabling multiple applications to share common event handling services and allowing business rule modifications without updating user interface code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If custom code is embedded within graphical user interface components, then the application can be developed with integrated business logic, but the code cannot be reused across other applications and platforms, increasing complexity and maintenance cost

Engineering Contradiction:
ImproveApplication development easeVSAvoidApplication complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent extracts custom business logic from graphical user interface components and places it in separate event handling routines. This allows the business logic to be reused across multiple applications and platforms while the GUI components remain platform-specific. The separation enables independent development and maintenance of business rules without affecting UI code.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the application into distinct layers: platform-specific GUI components and platform-independent event handling routines containing business logic. This segmentation allows each layer to be developed, maintained, and reused independently, reducing overall application complexity and maintenance costs.

Inventive Principle:
Principle #1Segmentation

2Stability of the object's composition

If custom code is embedded within graphical user interface components, then the application can be developed as a unified structure, but modifications to business rules require updating user interface code, increasing maintenance time and expense

Engineering Contradiction:
ImproveApplication structure stabilityVSAvoidMaintenance ease
Core Design Contradiction:
Stability of the object's compositionVSEase of repair

Solution Approach 1:

By extracting business logic from GUI components into separate event handling routines, the patent enables independent modification of business rules without affecting UI code. This maintains structural stability while significantly improving maintenance ease, as business logic changes can be made in isolation.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If multiple data sources and interdependent components are utilized, then the application can handle complex business requirements, but the application becomes increasingly complex and costly to maintain

Engineering Contradiction:
ImproveBusiness requirements adaptabilityVSAvoidApplication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments complex business logic into modular event handling routines that can be independently managed. Each routine handles specific business rules and can be developed, tested, and maintained separately, reducing overall application complexity while maintaining the ability to handle complex requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates platform-independent event handling routines that can be reused across multiple applications and platforms. This universality reduces complexity by eliminating duplication of business logic while maintaining adaptability to different business requirements through configuration rather than code changes.

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

Data Source

PatentUS9898262B2User interface event orchestration
Publication Date: 2018.02.20 JPMORGAN CHASE BANK NA
  • US9898262B2 patent drawing
  • US9898262B2 patent drawing
  • US9898262B2 patent drawing

AI summary

Methods, systems and computer program products for user interface event orchestration are provided. A computer-implemented method may include defining a business domain object, associating the business domain object with a user interface component type, defining a rule for an event of the user interface component type, generating an event handling routine providing the defined rule in a programming language, and associating the generated event handling routine with a user interface component of an application interface.