Unified Frontend Integration for Independent Computer Applications

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Integrating features of independently developed computer applications, such as issue tracking systems (ITS) and incident management systems (IMS), is computationally expensive and time-consuming, often resulting in inferior functionality due to the need for manual replication of features.

Innovation Solution

A unified frontend is provided by a primary computer application that communicates with secondary applications to create, update, and retrieve features, using unique object identifiers to maintain independent backend systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If features are manually replicated from one computer application to another, then integration functionality is achieved, but computational cost and development time increase significantly

Engineering Contradiction:

Improveintegration functionalityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses event data copying between independent computer applications through a consolidation system. Instead of manually replicating features, the system automatically copies event data structures and integrates them across applications, dramatically reducing development time while maintaining functionality.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The consolidation system acts as an intermediary between independent computer applications. It receives event data from multiple applications, consolidates them using a unified data structure, and distributes integrated events back to the applications, enabling feature integration without direct modification of the applications themselves.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If features are manually replicated from one computer application to another, then integration functionality is achieved, but computational resources are consumed excessively

Engineering Contradiction:

Improveintegration functionalityVSAvoidcomputational resources

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The system copies event data structures automatically rather than manually replicating entire feature sets. This selective copying approach consumes significantly fewer computational resources while achieving the same integration functionality.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The consolidation system extracts only the necessary event data from source applications rather than copying entire feature implementations. This extraction approach reduces computational overhead by processing only essential data elements needed for integration.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If two independently developed computer applications are integrated, then unified functionality is achieved, but technical compatibility issues arise

Engineering Contradiction:

Improveunified functionalityVSAvoidtechnical compatibility

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal consolidation system that can handle events from multiple different computer applications through a single unified data structure. This universal approach eliminates technical compatibility issues by providing a common interface that works across diverse applications without requiring application-specific integration code.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system changes the parameter representation of events by standardizing them into a unified data structure with consistent fields and formats. This parameter transformation allows incompatible applications to communicate effectively through the consolidation system, resolving technical compatibility issues through data standardization.

Inventive Principle:

Principle #35Parameter changes

4Ease of manufacture

If features are developed independently without regard for future integration, then application development is simpler, but future integration becomes complex and costly

Engineering Contradiction:

Improveapplication developmentVSAvoidfuture integration

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The consolidation system performs preliminary actions by establishing a universal integration framework before applications need to be integrated. Applications can continue to be developed independently with simpler architectures, while the consolidation system is pre-configured to handle their integration through standardized event data structures, making future integration straightforward and cost-effective.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250321810A1Systems and methods for integrating computer applications

Publication Date: 2025.10.16 ATLASSIAN PTY LTD

AI summary

Computer-implemented methods and systems for integrating computer applications are disclosed. One method includes querying a primary computer application for current state of a newly created object; receiving the current state of the object, and generating object data for a secondary computer application based on the current state of the object. The method further includes communicating an object creation request to a secondary computer application, the object creation request including the generated object data, receiving a secondary computer application object identifier from the secondary computer application upon creation of the object at the secondary computer application, and communicating the secondary computer application object identifier to the primary computer application for storing in a record of the object created at the primary computer application.