Workflows are a key part of Business Process Management, o ering the potential to automate\ud a number of business activities. Workflows are though constrained to their design,\ud i.e. workflow functionality does not extend outside its own specification. A relatively\ud small number of solutions to this inflexibility have been proposed. However, all\ud approaches so far are either at the orchestration level or are tightly-coupled with the workflow,\ud whereas we consider that the problem is at the business level and needs to be loosely\ud coupled from the workflow.\ud Significant value can be gained from separating core functionality in a workflow from\ud variability to that core process. Both can be defined separately and yet still corporately\ud execute to provide a variety of execution states that match the given context. Functionality\ud of the workflow can be supplied by Service Oriented Architecture.\ud Thus we define StPowla as a combination of workflows, policies and Service Oriented\ud Architecture. Workflows define the core business process, policies define the possible\ud variability of the processes and Service Oriented Architecture provides the underlying\ud functionality. We specifically present a set of reconfiguration functions that can be called\ud by policies on workflows and define each of these as graph transformation rules.\ud We provide an encoding from StPowla processes to SRML models, including core\ud workflow descriptions and variability, in order to make precise the relationship between\ud the constituent parts of StPowla. We apply the StPowla approach to an industrial case\ud study, provided by an industrial partner
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.