Dynamic Binding of Process Patterns in Method Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current method and process management frameworks require manual replication of capability patterns, leading to storage inefficiencies and the need for manual updates across multiple processes, as they lack compatibility and dynamic binding capabilities.
Innovation Solution
A data processing system and method for dynamic binding of capability patterns to multiple process patterns, allowing for referencing and extending capability patterns without replicating activities or method elements, using 'extends' relationships and variability elements to manage changes and additions across processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If capability patterns are manually replicated in each process, then processes can be constructed using existing patterns, but storage space increases and manual updates are required across multiple processes
Solution Approach 1:
The patent applies copying by creating lightweight references (handles) to capability patterns instead of full duplications. Each process contains only a reference identifier pointing to the master capability pattern definition, allowing rapid process assembly while minimizing storage requirements. The actual capability pattern content is stored once and shared across multiple processes through these references.
Solution Approach 2:
The capability pattern serves multiple functions simultaneously: it defines reusable process capabilities, provides a single source of truth for pattern definitions, and enables dynamic binding to multiple processes. This universal approach allows one capability pattern definition to support numerous processes without requiring separate copies in each process.
2Ease of manufacture
If capability patterns are manually replicated in each process, then processes can be constructed using existing patterns, but manual updates are required across multiple processes when patterns change
Solution Approach 1:
By copying only lightweight references rather than full capability pattern definitions, the system enables rapid process construction while eliminating the need for manual updates. When a capability pattern changes, the update automatically reflects in all processes that reference it, since they all point to the same master definition through their reference handles.
Solution Approach 2:
The system implements automatic feedback mechanisms where changes to capability patterns are dynamically propagated to all processes that reference them. This feedback loop ensures consistency across all processes without requiring manual intervention, as the system automatically detects and applies pattern updates to all referencing processes.
3Quantity of substance
If capability patterns are referenced without replication, then storage space is reduced, but compatibility across different process models must be maintained
Solution Approach 1:
The patent introduces an intermediary layer consisting of capability pattern references and binding mechanisms that mediate between different process models. This intermediary layer handles the complexity of compatibility requirements, allowing processes from different models to reference and extend capability patterns without direct coupling, thereby maintaining compatibility across diverse process models while using minimal storage.
Solution Approach 2:
The system employs dynamic binding where capability patterns can be flexibly associated with different processes at runtime. This dynamic approach allows the same capability pattern to be adapted to multiple process models through configurable bindings, enhancing versatility and compatibility without requiring static replication across all processes.
4Loss of time
If capability patterns are extended in processes without replication, then manual updating burden is reduced, but complexity of managing extensions increases
Solution Approach 1:
The patent segments the capability pattern system into distinct components: master capability pattern definitions, process-specific extensions, and binding relationships. This segmentation allows independent management of each component, reducing the complexity of managing extensions. Changes to base patterns and their extensions can be handled separately through structured inheritance mechanisms.
Solution Approach 2:
The system implements a nested structure where process-specific extensions are contained within the broader capability pattern framework. This nesting allows extensions to inherit from base capability patterns while maintaining their own specific definitions, creating a hierarchical management structure that reduces complexity through organized inheritance rather than flat, scattered modifications.
Data Source
AI summary
Embodiments of the present invention address deficiencies of the art in respect to method and process management, and provide a data processing system, method, and computer program product for dynamic binding of a capability pattern to multiple processes in a method architecture. In accordance with an embodiment of the present invention, a data processing system configured for dynamic binding of process patterns can include a method management tool. The method management tool can include program code enabled both to compose a capability pattern comprised of at least one activity defined by a plurality of nested and descriptors for source method elements, and to bind an extension activity to the capability pattern in a process model without replicating the activity of the capability pattern in the process pattern.