Enterprise Data Integration Tool for Shared Database Imbalance Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise architecture modeling techniques face challenges in integrating shared databases due to data imbalances, where data produced by one system is not consumed by others, leading to system errors and resource wastage, and vice versa, making it difficult to identify and correct these issues manually within complex ICD documents.
Innovation Solution
A method is introduced to construct an interim model of an enterprise, analyze data producers and consumers, and generate maps to identify data imbalances, allowing for the integration of shared databases by revising the model to ensure data produced is consumed and vice versa, using tools like UML modeling and validation tools to create integrated models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual examination of ICD documents is used to identify data imbalances, then integration accuracy can be improved, but the time and effort required increases significantly
Solution Approach 1:
The patent replaces manual mechanical examination of ICD documents with automated computational analysis. The system uses software tools to automatically parse ICD documents, generate producer/consumer maps, and identify data imbalances, substituting human manual analysis with automated information processing mechanisms.
Solution Approach 2:
The patent introduces intermediary tools and methods between the ICD documents and the analysis process. These intermediaries include automated parsing tools, data mapping generators, and exception report creators that facilitate the transition from raw documents to integrated enterprise models without requiring direct manual examination.
2Adaptability or versatility
If direct connections are made between systems to support new products, then system functionality is improved, but system complexity and vulnerability increase
Solution Approach 1:
The patent uses EAI technologies and shared databases as intermediaries between systems. Instead of direct point-to-point connections, systems communicate through standardized interfaces and shared data repositories, reducing the complexity web of direct connections while maintaining system functionality and adaptability.
Solution Approach 2:
The patent implements universal integration mechanisms through shared databases and standardized data access layers that serve multiple systems simultaneously. This multi-functional approach allows different systems to access and interact with the same data resources without requiring unique integration pathways for each system pair.
3Adaptability or versatility
If incremental stacking of software systems is performed, then system capabilities are expanded, but integration maintenance effort increases
Solution Approach 1:
The patent introduces EAI technologies and shared databases as intermediary layers that manage integrations between incrementally added systems. These intermediaries absorb the complexity of integration maintenance, allowing new systems to be added without proportionally increasing the maintenance burden on existing integrations.
Solution Approach 2:
The patent segments the integration architecture into distinct layers including presentation layer, application layer, and data access layer. This segmentation allows incremental system additions to be isolated to specific layers, reducing the ripple effect and maintenance effort across the entire system architecture.
4Adaptability or versatility
If data producing operations are added without corresponding consuming operations, then data availability is improved, but system errors increase
Solution Approach 1:
The patent implements feedback mechanisms through automated validation tools that analyze producer/consumer relationships in the enterprise model. These tools generate exception reports identifying data imbalances where data is produced without corresponding consumption or vice versa, providing feedback that allows designers to correct errors before system implementation.
Solution Approach 2:
The patent performs preliminary analysis of data producer/consumer relationships during the modeling phase before actual system implementation. By identifying and correcting data imbalance exceptions in advance through automated tools, the system prevents errors from propagating to the implemented system, ensuring both data availability and reliability.
Data Source
AI summary
A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool for analyzing calls, contained in the constructed model, between applications of the integrated enterprise and a database shared thereby. The call analysis tool identifies data attribute imbalances in calls between the applications of the integrated enterprise and the shared database. Data attribute imbalances result if the calls attempt to consume data which was never produced or if the calls produce data which is never consumed. The call analysis tool also generates producer/consumer maps of the data attributes used in the model, producer exception reports which identify data attributes which are consumed but never produced and consumer exception reports which identify data attributes which are produced but never consumed.