Dynamic Case Model Structure via Fragment References
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing case management systems lack the ability to dynamically control the structure of case models, leading to inefficiencies and inflexibility in managing complex projects and collaborations.
Innovation Solution
The implementation of case fragments allows for the creation of case model definitions that reference these fragments, enabling dynamic control over the structure of case models. This approach allows multiple case model definitions to share and reuse common fragments, facilitating more flexible and efficient case management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If case model definitions are statically defined without fragments, then the system structure is simple and easy to manage, but the system lacks flexibility and adaptability in managing complex projects
Solution Approach 1:
The case model definition is segmented into reusable fragments that can be independently defined, stored, and referenced. Each fragment represents a modular portion of the case model structure, allowing the system to build complex case models by assembling multiple fragments rather than defining everything monolithically. This segmentation enables flexibility while managing complexity through modularity.
Solution Approach 2:
Case fragments are designed to be universal and reusable across multiple case model definitions. A single fragment can be referenced by multiple different case models, allowing the same structural pattern or data organization to be applied universally across different case types. This universality reduces redundancy and improves adaptability without proportionally increasing system complexity.
2Productivity
If case model definitions are dynamically updated with fragment references, then the efficiency and reusability improve, but the difficulty of managing and resolving fragment references increases
Solution Approach 1:
The system introduces an intermediary fragment reference resolution mechanism that mediates between case model definitions and the actual fragment implementations. This intermediary layer handles the complexity of reference resolution, version matching, and dependency management, shielding users from the underlying complexity while enabling efficient dynamic updates and reusability.
Solution Approach 2:
Instead of directly embedding complex fragment definitions throughout the system, the invention uses lightweight references or pointers to fragments. These references act as copies that point to the actual fragment definitions stored centrally. When fragments need to be updated or reused, the reference mechanism allows efficient copying of structural patterns without duplicating the entire fragment definition, reducing management difficulty.
3Loss of time
If multiple case model definitions share common fragments, then the loss of time for creating new case models decreases, but the loss of information about fragment dependencies increases
Solution Approach 1:
The system implements feedback mechanisms that track and manage fragment dependencies across multiple case model definitions. When fragments are updated or modified, the system automatically detects which case models depend on those fragments and propagates the necessary information. This feedback loop ensures that dependency information is maintained and updated automatically, preventing information loss while enabling rapid case model creation through fragment sharing.
Data Source
AI summary
Case fragment management includes obtaining a case model definition for a case, and generating a case model from the case model definition. Generating the case model includes obtaining a case fragment expression, executing the case fragment expression using data gathered from a data source to obtain a case fragment identifier, selecting, from multiple case fragments, a case fragment corresponding to the case fragment identifier, and populating the case model with the case fragment. Case fragment management also includes storing the case model.