Overriding References Resolve Hierarchical Component Conflicts

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In complex integrated systems, conflicts arise due to multiple components referencing different versions of the same reusable component, leading to management challenges in hierarchical component design and development.

Innovation Solution

A computer-implemented method and system that uses overriding references to replace descendant components with an overriding component associated with an ancestor component, resolving conflicts by preempting differing versions within the logical component hierarchy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple components reference different versions of the same reusable component, then design flexibility and component reusability are improved, but version conflicts and management complexity increase

Engineering Contradiction:

Improvecomponent reusabilityVSAvoidhierarchy management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary conflict detection by analyzing the logical component hierarchy before finalizing component versions. It identifies all descendant components referencing the same reusable component and detects version conflicts in advance, allowing the system to resolve conflicts proactively rather than reactively during implementation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary conflict resolution mechanism that acts as a mediator between multiple components with conflicting version references. This intermediary system automatically selects and applies a resolution strategy (such as using the version from the highest-level ancestor component) to harmonize version discrepancies without requiring manual intervention.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the same reusable component is referenced by multiple components within a product, then design efficiency is improved, but version conflicts increase

Engineering Contradiction:

Improvedesign efficiencyVSAvoidversion consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system implements feedback by continuously monitoring component references throughout the hierarchy and automatically detecting version conflicts. When a conflict is detected, the system provides feedback about the inconsistent versions and applies resolution logic to ensure all references point to a consistent version, thereby maintaining reliability while preserving design efficiency.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent applies homogeneity by ensuring that all descendant components referencing the same reusable component ultimately resolve to a single, consistent version. This is achieved by propagating version information from ancestor components down the hierarchy, making all references homogeneous and eliminating version discrepancies.

Inventive Principle:

Principle #33Homogeneity

3Loss of time

If hierarchical references are used to link components to reusable components, then design time is reduced, but conflict detection difficulty increases

Engineering Contradiction:

Improvedesign timeVSAvoidconflict detection difficulty

Core Design Contradiction:

Loss of timeVSDifficulty of detecting and measuring

Solution Approach 1:

The system segments the conflict detection process into distinct phases: first, it segments the hierarchy traversal to efficiently navigate from ancestor to descendant components; second, it segments conflict detection to specifically identify version mismatches; and third, it segments resolution application. This segmentation makes the complex detection process manageable and automated.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent replaces manual conflict detection mechanisms with an automated computer-implemented system. Instead of manually tracing hierarchical references and checking versions, the system automatically traverses the logical component hierarchy, compares version identifiers, and detects conflicts programmatically, significantly reducing the difficulty of detection.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10127261B2Methods and systems for resolving conflicts in hierarchically-referenced data

Publication Date: 2018.11.13 DASSAULT SYSTEMS AMERICAS CORP

AI summary

In one aspect, a computer-implemented method for managing conflicts in a logical component hierarchy is provided. The logical component hierarchy includes an ancestor component and a descendant component associated with the ancestor component. The method uses a computer device in communication with a memory. The method includes determining, by the computer device, a requirement to replace the descendant component, within the logical component hierarchy, with an overriding component. The overriding component is associated with the ancestor component by an overriding reference. The method also includes replacing the descendant component with the overriding component within the logical component hierarchy.