Persistent Object Instance Composition Across Disparate Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Extending enterprise resource planning (ERP) systems with new features from systems of engagement (SoEs) is challenging due to outdated languages, databases, and rigorous correctness requirements, making it difficult to deploy new features efficiently.
Innovation Solution
A method and system for composing persistent object instances that link resources across multiple disparate systems by associating each resource with a namespace-URL, providing a web-based object API, and designating a primary namespace-URL for each object instance, allowing access and management without modifying the underlying systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If ERP systems are extended with new features using traditional methods, then system functionality is improved, but deployment time and complexity increase significantly
Solution Approach 1:
The system segments ERP functionality into discrete, independently deployable feature modules. Each feature is encapsulated as a separate unit that can be developed, tested, and deployed independently, eliminating the need for comprehensive system re-deployment and reducing deployment time while maintaining full system functionality.
Solution Approach 2:
New features are nested within the existing ERP system architecture as embedded modules. These nested feature modules access and integrate with core ERP functionalities through defined interfaces, allowing new capabilities to be added without restructuring the entire system and minimizing deployment overhead.
2Adaptability or versatility
If ERP systems are extended with new features, then system adaptability is improved, but system complexity increases
Solution Approach 1:
The system divides complex ERP functionality into modular feature units with well-defined interfaces. This segmentation isolates complexity within individual modules while presenting a simplified interface to the rest of the system, allowing high adaptability without proportionally increasing overall system complexity.
Solution Approach 2:
The feature module architecture implements universal interfaces and standardized integration patterns that allow different feature modules to interact with the core ERP system and with each other through common mechanisms. This universality reduces the need for custom integration logic for each new feature, thereby limiting complexity growth despite increased adaptability.
3Reliability
If rigorous correctness requirements are maintained in ERP systems, then system reliability is improved, but feature deployment speed decreases
Solution Approach 1:
By segmenting the system into independent feature modules, correctness verification and testing can be performed on individual modules rather than the entire ERP system. This allows rapid validation of new features while maintaining overall system reliability through modular isolation, thereby increasing deployment speed without sacrificing reliability.
Solution Approach 2:
The system implements prior validation mechanisms including automated testing frameworks, interface contracts, and correctness proofs that are established before feature deployment. This beforehand cushioning ensures reliability requirements are met while enabling faster deployment by preventing errors early in the development process rather than requiring extensive post-deployment verification.
Data Source
AI summary
A system, method and computer program product for composing persistent object instances that link resources across multiple, disparate systems. An example method includes associating resources with namespace-URLs and object instances. One of the namespace-URLs is designated as primary namespace-URL. A web-based object API is provided through which the object instance can be accessed. The web-based object API uses the primary namespace-URL as an identifier of the object instance.