Adaptive SBB Architecture Update Method

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies do not provide adaptive functionality for automatic updates of individual components within solution building block (SBB) architectures when changes occur, requiring manual intervention and inefficient integration processes.

Innovation Solution

A method for automatically updating SBB architectures by capturing metadata changes and generating new or updated building block architectures, which includes substituting or replacing components, and notifying administrators for manual changes, using a solution building block monitoring system (SBBMS) to manage dependencies and lifecycle management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual updates are performed for each component change in SBB architectures, then control and precision over changes are maintained, but time consumption and operational complexity increase significantly

Engineering Contradiction:
Improvecontrol precisionVSAvoidupdate time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs automatic updates of SBB architectures by detecting component changes and propagating them through dependency relationships without requiring manual intervention. The monitoring system continuously tracks component metadata and automatically triggers updates to dependent components, enabling the system to service itself and eliminating time-consuming manual update processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a feedback mechanism where component changes are detected and automatically propagated to dependent components through metadata relationships. The monitoring system continuously observes component states and triggers cascading updates based on detected changes, creating a closed-loop system that maintains architecture consistency automatically.

Inventive Principle:
Principle #23Feedback

2Productivity

If automatic update systems are implemented for SBB components, then update speed and productivity improve, but system complexity and detection difficulty increase

Engineering Contradiction:
Improveupdate efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system pre-establishes metadata relationships and dependency mappings between SBB components before runtime. By preparing the dependency graph and component relationships in advance, the system enables rapid automatic updates when changes occur, as the propagation paths are already known and configured, reducing the complexity of real-time decision-making.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If comprehensive metadata tracking is implemented across all SBB components, then update accuracy and reliability improve, but information processing overhead and system complexity increase

Engineering Contradiction:
Improveupdate reliabilityVSAvoidinformation overhead
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system extracts and isolates only the critical metadata elements required for update propagation, such as component dependencies and relationship types, from the full component information. By focusing on essential metadata rather than tracking all component attributes, the system maintains update reliability while minimizing information overhead and processing complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8805895B2Adaptive methodology for updating solution building block architectures and designs
Publication Date: 2014.08.12 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8805895B2 patent drawing
  • US8805895B2 patent drawing
  • US8805895B2 patent drawing

AI summary

Provided is a method for the adaptive updating of building block architectures and designs in the event of a change to a component of the building block architecture. When a specific component of the architecture, or SBB, is replaced or modified, the metadata associated with the new or modified component is placed in a building block repository. The system captures or recognizes the event and automatically makes updates to dependent components of the specific component. Such updates may include, but are not limited to, a substitution or replacement of one component with another, generally if the replacement component is a better fit in the solution architecture than the original component. A new or updated system architecture is generated to reflect the replaced and/or modified components and the associated metadata. In the alternative, the system notifies an administrator to make specific changes in components rather than implementing the changes automatically.