Abstract
Abstract Workflow management systems usually interpret a workflow definition rigidly. However, there are real life situations where users should be allowed to deviate from the prescribed static workflow definition for various reasons, including lack of information and unavailability of the required resources. To flexibilize workflow execution, this paper first proposes mechanisms that allow execution to proceed in the presence of incomplete information, by adopting presuppositions, and in the presence of negative information, by suggesting execution alternatives. Then, the paper presents an architecture for a workflow system, driven by ontologies that capture semantic relationships between workflows and resources. The architecture includes a component which uses matching techniques to find alternatives for workflows and resources.
Highlights
Workflow management systems have received considerable attention lately, motivated by their wide spectrum of applications
We propose in this paper: (i) a mechanism to handle presuppositions, that uses default values which allow execution to proceed in the presence of incomplete information; (ii) a mechanism for choosing alternatives to subworkflows and resources, thereby allowing workflow execution to proceed when the predefined resource is unavailable
We described in this paper two mechanisms to flexibilize the execution of workflow instances: a mechanism to handle presuppositions that allows workflow execution to proceed in the presence of incomplete information, and a mechanism for choosing alternative subworkflows or resources, in the presence of negative information or when an abstract definition is reached
Summary
Workflow management systems have received considerable attention lately, motivated by their wide spectrum of applications. We propose in this paper: (i) a mechanism to handle presuppositions, that uses default values which allow execution to proceed in the presence of incomplete information; (ii) a mechanism for choosing alternatives to subworkflows and resources, thereby allowing workflow execution to proceed when the predefined resource is unavailable. In some sense, these mechanisms implement a component substitution strategy, applied to workflow execution, where subworkflows and resources play the role of components [3].
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
