Data Model Database for Cross-Language Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data dictionaries face challenges in managing complex data structures and interrelationships across multiple entities in large-scale software efforts, particularly in environments using disparate languages and models, leading to difficulties in interoperability, versioning, and data type reuse.
Innovation Solution
A data model database is introduced, featuring symbol, concrete, and carrier data types, which allows for cross-model, cross-language, and cross-format comparison and utilization, enabling efficient management of data types and their dependencies through a structured framework that includes symbol data types with language-agnostic fields, concrete data types with constraints, and carrier data types specific to each language, facilitating conversions and dependency chain analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional data dictionaries are used to manage data types across multiple entities, then manual entry and cross-referencing can be performed, but interoperability management becomes difficult and manual effort increases
Solution Approach 1:
The patent introduces an intermediary system that automatically manages data type relationships across disparate models and languages. This intermediary layer translates and correlates data types between different data dictionaries without requiring manual cross-referencing, thereby improving interoperability management while reducing manual effort.
Solution Approach 2:
The patent replaces the mechanical manual process of entry and cross-referencing with an automated computational system. The system automatically discovers, correlates, and manages data type relationships across multiple entities, eliminating the need for manual intervention and significantly reducing operational effort.
2Stability of the object's composition
If data dictionaries are updated in real-time during simultaneous development efforts, then versioning can be maintained, but changes are difficult to propagate and consistency is lost
Solution Approach 1:
The patent implements a feedback mechanism that automatically detects changes in data types and propagates them across all relevant data dictionaries and entities. The system monitors for modifications and triggers automated updates to maintain versioning consistency, ensuring that changes are propagated efficiently without manual intervention.
Solution Approach 2:
The patent performs preliminary actions by pre-establishing the relationships and dependencies between data types across multiple entities. This allows the system to automatically manage versioning and propagate changes efficiently, as the structural framework is already in place to handle updates without manual intervention.
3Adaptability or versatility
If anonymous data types are used to facilitate reuse between models, then flexibility is improved, but data type reuse becomes laborious and potentially risky
Solution Approach 1:
The patent creates universal data type representations that can be reused across multiple models and languages. By establishing a unified framework for data type definitions, the system enables flexible reuse without the complexities and risks associated with anonymous types, as the universal representations maintain explicit identities and relationships.
Data Source
AI summary
Systems and methods utilize a data model database which includes a plurality of symbol data types. Each of the plurality of symbol data types have one or more symbol data fields. The data model database further includes a plurality of concrete data types. Each of the concrete data types have one or more language-agnostic concrete fields associated with each of the one or more symbol data fields. Each of the one or more language-agnostic concrete fields apply one or more concrete constraints to each of the corresponding symbol data fields. The data model database further includes a plurality of carrier data types. The plurality of carrier data types having one or more language-specific carrier fields associated with each of the one or more language-agnostic concrete fields. Each of the one or more language-specific carrier fields apply one or more carrier constraints to each of the corresponding language-agnostic concrete fields.


