Interactive Software Component Coupling Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current interactive software development faces challenges in managing complexity, ensuring interoperability, and supporting diverse interaction modalities due to the limitations of traditional programming languages and existing software patterns, which lead to increased software complexity, decreased interoperability, and difficulties in certification and tool design.

Innovation Solution

A recursive architecture for interactive software that enables homogeneity, complexity management, and interoperability among components, supporting all usual control structures and allowing for the creation of new control structures, by defining couplings between interactive components to enable defined interactions between the software and its environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional programming languages and existing software patterns are used for interactive software development, then software can be developed using conventional methods, but software complexity increases and interoperability decreases

Engineering Contradiction:
Improvesoftware development easeVSAvoidsoftware complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent segments interactive software into discrete, composable components with well-defined interfaces. Each component encapsulates specific functionality (e.g., input handling, display rendering, logic processing) and can be independently developed, tested, and reused. This segmentation reduces overall software complexity by breaking down monolithic systems into manageable units while maintaining ease of development through component assembly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent establishes universal interfaces and communication protocols that enable components to serve multiple functions across different applications. Standardized event handlers, data exchange formats, and coupling mechanisms allow the same component to be reused in various contexts, reducing development effort while maintaining manageable complexity through consistency.

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

2Ease of manufacture

If traditional programming languages and existing software patterns are used for interactive software development, then software can be developed using conventional methods, but interoperability among components decreases

Engineering Contradiction:
Improvesoftware development easeVSAvoidinteroperability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent defines universal interfaces and standardized communication protocols that enable components from different sources to work together seamlessly. Components adhere to common contracts for event handling, data exchange, and coupling, ensuring interoperability across diverse software ecosystems while maintaining ease of development through consistent patterns.

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

Solution Approach 2:

The patent introduces intermediary layers such as event buses, message queues, and adapter components that facilitate communication between heterogeneous systems. These intermediaries translate between different component interfaces and communication styles, enabling interoperability without requiring changes to the components themselves, thus preserving development ease while enhancing versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If diverse interaction modalities are supported, then software can handle multiple input methods, but software complexity increases

Engineering Contradiction:
Improveinteraction modality supportVSAvoidsoftware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments interaction handling into specialized input components that encapsulate specific modality logic (e.g., touch input handlers, voice recognition interfaces, gesture detectors). Each input component independently processes its specific modality and converts inputs into standardized events, allowing diverse interaction support without increasing overall system complexity through modular organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal event model and processing pipeline that handles multiple interaction modalities through consistent mechanisms. Different input types (touch, voice, gesture, keyboard) are normalized into common event structures that can be processed by the same downstream components, enabling versatile interaction support while maintaining manageable complexity through uniform handling.

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

4Ease of manufacture

If components are made interchangeable and reusable, then software development is simplified, but ensuring proper coupling and activation between components becomes more challenging

Engineering Contradiction:
Improvecomponent reusabilityVSAvoidcoupling management complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent establishes universal coupling interfaces and activation protocols that enable interchangeable components to be assembled like building blocks. Standardized connection points, matching interfaces, and automated coupling detection allow components to be reused across different applications without manual configuration, simplifying development while managing complexity through consistency.

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

Solution Approach 2:

The patent implements feedback mechanisms that automatically detect and verify proper coupling between components. When components are assembled, the system checks interface compatibility, activates appropriate connection logic, and provides runtime verification that coupling is correct. This automated feedback reduces the complexity of managing interchangeable components by eliminating manual configuration errors.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11194050B2Processing unit, software and method for controlling interactive components
Publication Date: 2021.12.07 ECOLE NATIONALE DE LAVIATION CIVILE
  • US11194050B2 patent drawing
  • US11194050B2 patent drawing
  • US11194050B2 patent drawing

AI summary

The invention relates to the development, control and execution of interactive software. An interactive component of the invention is configured to enable a defined interaction between the interactive digital system and an environment of the interactive digital system. It comprises a first subcomponent, defining a coupling between a second interactive component and a third interactive component. Said first subcomponent is configured, when executed by the interactive digital system, to generate an activation of the third interactive component conditional upon an activation of the second interactive component, said activation enabling the defined interaction.