Hierarchical Versioning for Stable Business Process Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software lifecycle management approaches fail to provide stable linking and patchability of business processes, leading to unpredictable behavior and increased costs due to redundant resource allocation and frequent modifications in business process management systems.
Innovation Solution
A system and method that employs hierarchical versioning of business process models, generating a dependency graph to manage artifact dependencies, compute unique version identifiers, and allow transparent patching of sub-workflows and tasks, ensuring deterministic execution and lean resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional software lifecycle management approaches are used, then business process modifications can be made, but stable linking and patchability are not provided leading to unpredictable behavior
Solution Approach 1:
The patent segments the business process model into multiple independent artifacts (workflows, data mappings, tasks, texts, data types) that can be versioned separately. Each artifact has its own version identifier, allowing granular control over which components are modified and how changes propagate through the system. This segmentation enables stable linking by maintaining version relationships between parent and child artifacts while allowing independent modification of individual components.
Solution Approach 2:
The patent implements a hierarchical versioning structure where parent artifacts contain references to child artifacts, and each level has its own version identifier. The version identifier of a parent artifact incorporates the version identifiers of its referenced child artifacts, creating a nested versioning relationship. This allows changes at any level to be tracked and propagated appropriately, providing both stability for running instances and flexibility for modifications.
2Adaptability or versatility
If artifacts are modified frequently to improve adaptability, then business processes can adapt to changes, but resource consumption increases due to redundant allocations
Solution Approach 1:
The patent applies local quality by allowing different artifacts to have different versioning characteristics based on their modification frequency and importance. Frequently modified artifacts (like workflows) can be versioned independently, while stable artifacts (like data types) maintain their version identifiers without requiring frequent updates. This localized approach to versioning reduces redundant resource allocation while maintaining the necessary adaptability.
Solution Approach 2:
The patent creates a universal versioning framework that works across all artifact types (workflows, data mappings, tasks, texts, data types) through a common hierarchical structure. The version identifier system serves multiple functions: tracking changes, maintaining stable links, enabling patchability, and reducing resource consumption. This multi-functional approach allows the system to handle diverse artifact modification needs through a single coherent mechanism.
3Duration of action of moving object
If running process instances have long lifecycles, then business processes can complete complex tasks, but patching becomes difficult without affecting stable execution
Solution Approach 1:
The patent prepares for future modifications by establishing stable version links between parent and child artifacts before changes are needed. The hierarchical versioning structure pre-defines how changes will propagate, so when patching is required, the system can automatically determine which instances need to be updated and which should continue running with their original versions. This preliminary structuring enables seamless patching of long-running processes.
Solution Approach 2:
The version identifier acts as an intermediary between the artifact definition and the running process instances. It mediates the relationship between stable execution requirements and modification needs by providing a clear version reference that can be updated without disrupting running instances. The hierarchical versioning system allows the intermediary to manage change propagation selectively, enabling patchability while maintaining execution stability.
Data Source
AI summary
A system, method and computer program product is presented for versioning a business process model. The business process model is decomposed into a number of artifacts. A hierarchical dependency graph is generated for the number of artifacts to produce, for each artifact, a set of referencing artifacts and a set of referenced artifacts. The set of referenced artifacts are compiled by creating a runtime format and computing a unique version identifier for each referenced artifacts, and the unique version identifier for each referenced artifact is incorporated into a version identifier of each associated referencing artifact from the set of referencing artifacts. At least one of the referenced artifacts is modified to produce a new version of the associated referencing artifact.