Automated Master Schema Fragmentation and Update Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual process of fragmenting and merging large-scale inter-related schemas and reference models across multiple business focus areas is time-consuming, expensive, and prone to errors, hindering productivity and requiring significant specialist engineer input.

Innovation Solution

An automated system using semantic analysis and inference rules to fragment and update master schemas into sub-projects, monitoring changes, and distributing relevant updates across sub-projects, reducing the need for manual intervention and enabling continuous integration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual fragmentation and merging of master schema into sub-projects is performed, then schema development can be divided into discrete business focus areas, but the process becomes time-consuming and expensive

Engineering Contradiction:
Improveability to divide schema into discrete business focus areasVSAvoidtime required for manual fragmentation and merging
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies segmentation by automatically dividing the master schema into multiple sub-projects based on business focus areas. The system identifies and separates schema elements into discrete sub-projects that can be independently developed and maintained, eliminating the need for manual fragmentation while preserving the ability to work on specific business areas in parallel.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent replaces the manual mechanical process of schema fragmentation and merging with an automated computer-based system. The computer automatically performs schema analysis, fragmentation, change identification, and distribution of updates, substituting human engineering efforts with automated computational processes that significantly reduce time and cost.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Stability of the object's composition

If manual merging of sub-projects into master schema is performed, then completed developments can be integrated, but errors increase and productivity decreases

Engineering Contradiction:
Improveintegration of completed developments into master schemaVSAvoiderror rate in manual merging process
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where the system continuously monitors sub-projects for changes, automatically identifies modifications, and distributes relevant updates to other sub-projects and the master schema. This automated feedback loop ensures consistent integration without manual intervention, eliminating errors associated with manual merging while maintaining schema stability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-service by automatically detecting changes in sub-projects, determining which changes should be propagated, and distributing updates without human intervention. The automated system manages its own integration process, identifying conflicts and resolving them through predefined rules, thereby improving reliability and reducing errors.

Inventive Principle:
Principle #25Self-service

3Reliability

If specialist engineers perform manual schema maintenance, then schema integrity can be maintained, but expense and time requirements increase significantly

Engineering Contradiction:
Improveschema integrityVSAvoiddevelopment speed across multiple sub-projects
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent replaces specialist engineer manual work with automated computer-based systems that perform schema maintenance tasks. The computer automatically fragments schemas, monitors changes, validates integrity, and distributes updates, maintaining schema integrity through automated rule-based processes while dramatically increasing productivity by enabling parallel development across multiple sub-projects simultaneously.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces an automated intermediary system that acts as a mediator between sub-projects and the master schema. This intermediary automatically manages change propagation, validates schema integrity, and coordinates updates across multiple sub-projects, replacing the need for specialist engineers to manually maintain schema integrity while enabling faster development cycles.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If continuous integration is enabled across sub-projects, then productivity increases, but complexity of managing schema changes increases

Engineering Contradiction:
Improvesimultaneous development across sub-projectsVSAvoidcomplexity of managing schema changes
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements automated feedback mechanisms that continuously monitor sub-projects for changes and automatically distribute relevant updates to other sub-projects and the master schema. This feedback-driven approach enables continuous integration across multiple sub-projects simultaneously while managing complexity through automated change detection and propagation logic, eliminating the need for complex manual coordination.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10884997B2Maintaining a master schema
Publication Date: 2021.01.05 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10884997B2 patent drawing
  • US10884997B2 patent drawing
  • US10884997B2 patent drawing

AI summary

As disclosed herein a method, executed by a computer, includes accessing a master schema defining one or more reference models, the master schema comprising a plurality of model elements each model element thereof comprising an element name and an element definition and fragmenting the master schema to provide a plurality of sub-projects. The method further includes identifying a change in a sub-project model element, updating the master schema according to the identified change to the sub-project model element, and distributing the updated master schema changes to other sub-projects that include the changed model element. A computer system, and a computer program product corresponding to the method are also disclosed herein.