Evaluation of Correctness Criteria for Dynamic Workflow Changes

Today's process-aware information systems tend to either support business processes or provide flexibility. Classical workflow management systems offer good process support as long as the processes are structured and do not require much flexibility. Information systems that allow for flexibility have a tendency to lack process-related support. If systems offer guidance, then they are typically also inclined to "enforce guidelines" and are perceived as inflexible. Moreover, implementing flexible systems is far from trivial. This paper will show that using a more declarative approach can assist in a better balance between flexibility and support. This is demonstrated by presenting the Declare framework that aims to take care of the full spectrum of flexibility while at the same time supports the user using recommendations and other process-mining-based diagnostics.

show abstract

“…This taxonomy is based on [43]. See also [5,9,23,26,33,39,42,47] for other classifications of flexibility.…”

Section: Flexibilitymentioning

confidence: 99%

“…See [5,9,23,26,33,39,42,43,47] for various taxonomies/classifications of workflow flexibility. The taxonomy in this paper is based on [43].…”

Section: Related Workmentioning

confidence: 99%

Declarative workflows: Balancing between flexibility and support

Aalst

Pesic

Schonenberg

2009

Comp. Sci. Res. Dev.

382

315

View full text Add to dashboard Cite

show abstract

“…Correctness of changes. The ultimate ambition of any change framework must be to ensure correctness of dynamic changes (Rinderle, Reichert, & Dadam, 2003). First, structural and behavioral sound ness of the modified process schema should be guaranteed independent from whe ther the change is applied at instance level or not.…”

Section: Requirementsmentioning

confidence: 99%

Enabling Adaptive Process-Aware Information Systems with ADEPT2

Reichert¹,

Dadam²

Handbook of Research on Business Process Modeling

Self Cite

View full text Add to dashboard Cite

In dynamic environments it must be possible to quickly implement new busi ness processes, to enable ad-hoc deviations from the defined business processes on-demand (e.g., by dynamically adding, deleting or moving process activities), and to support dynamic pro cess evolution (i.e., to propagate process schema chan ges to already running process instances). These fundamental requirements must be met without affecting process consistency and robustness of the process-aware information system. In this chapter the authors describe how these challenges have been addressed in the ADEPT2 process management system. Their overall vision is to provide a next generation technology for the support of dynamic processes, which enables full process lifecycle management and which can be applied to a variety of application domains.

show abstract

“…In the literature process type and instance changes have been an important research topic for several years [1,26,37,39,67,96,98,104,118,136]. However, there are only few adaptive PMS which support both kinds of changes in one system [65,88,100,101,136].…”

Section: Vision and Big Picturementioning

confidence: 99%

“…As discussed in Section 2 both kinds of changes have been an important research topic in the process management literature [118,1,26,37,39,67,104,88,96,136] for several years. However, there are only few adaptive PMS which support both kinds of changes in one system [65,136].…”

Section: Chapter 5 Migrating Biased Process Instancesmentioning

confidence: 99%

Schema Evolution in Process Management Systems

SpringerReference

View full text Add to dashboard Cite

Continuously arising new trends in information technology and developments at the (e-business) market let companies crave for automated business process support. Process management systems offer the promising possibility to (electronically) define, control, and monitor business processes. However, if this technology shall be applicable in practice it must be possible to change running business processes even at runtime. Basically, such process changes can take place at two levels -the process type level and the process instance level. If a process type is modified a new version of the respective process type schema is created. Then, at minimum, the process instances running according to the old process type schema version must be able to finish without being disturbed. However, this simple versioning approach is only sufficient for short-running business processes. For long-running ones like, for example, car leasing contracts or medical treatment processes which may last from 3 up to 5 years, it must be possible to apply the process type changes to the collection of running process instances as well but without causing inconsistencies or errors in the sequel. Apart from process schema evolution and change propagation a flexible process management system must also enable instance-specific (ad-hoc) changes, for example, if exceptional situations occur. If then a process type change takes place the challenging question arises how to adequately deal with the interplay of process type and process instance changes.

show abstract

Evaluation of Correctness Criteria for Dynamic Workflow Changes

Cited by 58 publications

References 14 publications

Declarative workflows: Balancing between flexibility and support

Declarative workflows: Balancing between flexibility and support

Enabling Adaptive Process-Aware Information Systems with ADEPT2

Schema Evolution in Process Management Systems

Contact Info

Product

Resources

About