Weak Dependency Workflow Model for Dynamic Task Insertion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Graph-based workflow models in commercial business process management systems lack flexibility, as they primarily use strong dependencies that do not allow for the insertion of additional tasks between linked tasks, limiting the ability to modify or adapt processes dynamically.
Innovation Solution
Introducing a weak dependency concept, represented graphically as a dashed line, which indicates that one or more tasks can be inserted between linked tasks, allowing for greater flexibility and modification of workflow models by decoupling immediate condition precedence requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If strong dependencies are used in workflow models to ensure strict task sequencing, then task execution reliability is improved, but workflow flexibility and adaptability deteriorate
Solution Approach 1:
The dependency relationship between tasks is segmented into two distinct types: strong dependencies (solid lines) that enforce strict sequencing for critical tasks, and weak dependencies (dashed lines) that allow flexible insertion of additional tasks. This segmentation allows the workflow model to simultaneously maintain reliability for essential task sequences while providing adaptability where task insertion is permitted.
Solution Approach 2:
The workflow model transitions from a static, rigid structure to a dynamic one by introducing weak dependencies that can accommodate runtime task insertions. The dashed line representation visually and functionally distinguishes these dynamic, flexible connections from the static, fixed strong dependencies, enabling the workflow to adapt to changing requirements while maintaining core execution integrity.
2Device complexity
If graphical workflow models use standard dependency representations, then model simplicity is maintained, but expressive functionality deteriorates
Solution Approach 1:
Different graphical representations are applied locally to different dependency types: solid lines represent strong dependencies with strict sequencing, while dashed lines represent weak dependencies allowing task insertion. This local differentiation enhances the expressive functionality of the graphical model without significantly increasing overall complexity, as it builds upon standard graphical conventions.
3Adaptability or versatility
If additional tasks can be inserted between linked tasks, then workflow adaptability is improved, but task execution precision and control deteriorate
Solution Approach 1:
The dependency structure is segmented into strong and weak types, where strong dependencies maintain precise control by preventing task insertion, and weak dependencies provide adaptability by allowing controlled insertions. This segmentation enables the system to maintain execution precision where needed while providing adaptability where permissible.
Solution Approach 2:
The weak dependency acts as an intermediary mechanism that mediates between the need for task insertion (adaptability) and the need for precise task sequencing (control). By introducing this intermediate dependency type, the system can accommodate task insertions while maintaining overall workflow control through the contrasting strong dependencies.
Data Source
AI summary
The subject matter disclosed herein provides methods and apparatus, including computer program products, for providing a weak dependency linking two tasks of a workflow of task. In one aspect, there is provided a computer-implemented method. The method receives, from a user interface, an indication representing a link between a first task and a second task. The link being a weak dependency linking the first and second task. The weak dependency representing that one or more tasks may be inserted between the first and second tasks. The first and second tasks including the link representing the weak dependency may be provided to the user interface. The link presented at the user interface to enable identification of the weak dependency. Related apparatus, systems, methods, and articles are also described.