Grafted Model Network for Multi-App Data Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for sharing information between computer applications in networks lead to data inconsistencies and replication, lack of a single version of truth, and dependency on single software vendors, making it difficult to manage and upgrade systems effectively.
Innovation Solution
A grafted model network approach that creates and dynamically installs application projects with pre-defined and application-defined fields, allowing for a single version of truth and independent upgrades, while supporting the coexistence of multiple independent applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate databases are maintained by each computer application, then each application can store customized information, but data inconsistencies and replication occur across the network
Solution Approach 1:
The system segments data storage into two distinct layers: a centralized shared database for common data elements (maintaining data consistency) and application-specific database extensions for customized information (maintaining adaptability). Each application can define its own data elements while relying on the shared database for common elements, thus resolving the contradiction between customization and consistency.
Solution Approach 2:
The invention introduces an intermediary mechanism (the shared database with standardized data elements) that mediates between multiple application-specific databases. This intermediary ensures data consistency across applications while allowing each application to maintain its customized data structure, thereby resolving the contradiction between adaptability and reliability.
2Reliability
If ERP systems use a unified database, then a single version of the truth is achieved, but dependency on single software vendor and inability to upgrade independent applications occurs
Solution Approach 1:
The system segments the monolithic ERP database into a shared core database (providing single version of truth) and application-specific extensions (enabling independent upgrades). Each application can be upgraded independently by modifying its specific data elements without affecting the core shared database or other applications, thus resolving the contradiction between reliability and adaptability.
Solution Approach 2:
The invention introduces dynamic characteristics to the database architecture, allowing applications to be added, removed, or upgraded independently. The system dynamically adapts to changes in individual applications while maintaining the integrity of the shared database, enabling independent upgrades while preserving the single version of truth.
3Productivity
If information is copied or replicated between databases, then information can be shared between applications, but data inconsistencies and lack of single version of truth occur
Solution Approach 1:
The invention merges multiple application-specific databases with a shared database into a unified networked database system. Instead of copying data between separate databases, the system combines them into a single networked structure where data elements are centrally stored and accessed by multiple applications, thereby enabling information sharing while maintaining data consistency.
Data Source
AI summary
A computer program product and method for sharing information between multiple computer applications using a grafted model network. The method includes creating a first model having one or more pre-defined fields, defining one or more application-defined fields, associating the first model with the first application project, associating the one or more application-defined fields with the second application project, grafting the one or more application-defined fields to the first model, building the first and second application projects, and dynamically installing the first and second application projects on a software platform. Building the first application project comprises creating a first database table having one or more table columns corresponding to the pre-defined fields of the first model in a database. Building the second application project comprises adding one or more table columns to the first database table corresponding to the application-defined fields in the database. Dynamically installing the first application project enables the one or more table columns corresponding to the pre-defined fields of the first model to be accessed via the software platform by the first computer application upon execution on a computer, and dynamically installing the second application project enables the one or more table columns corresponding to the pre-defined fields of the first model and the application-defined fields to be accessed via the software platform by the second computer application upon execution on the computer.