DYNAMITE: DYNAMIc Task nEts for software process management

Abstract. The agile workflow technology deals with flexible workflow adaptation and overriding, in case of foreseen as well as unforeseen changes and problems in the operating business environment. One key issue that an agile workflow system should address is Business Process (BP) monitoring. This consists in properly highlighting and organizing non-compliances and adaptations with respect to the default process schema. Such an activity can be the starting point for other very critical tasks, such as quality assessment and process reengineering.In this paper, we introduce an automated support to BP monitoring, which exploits the Case-based Reasoning (CBR) methodology. CBR is particularly well suited for managing exceptional situations, and has been proposed in the literature for process change reuse and workflow adaptation support. Our work extends these functionalities by retrieving traces of process execution similar to the current one, which can then be automatically clustered. Retrieval and clustering results can provide support both to end users, in the process instance execution phase, and to process engineers, in (formal) process quality evaluation and long term process schema redefinition. Our approach in practice is illustrated by means of a case study in the field of stroke management.

show abstract

“…new laws, reengineering efforts) as well as to unanticipated exceptions and problems in the operating environment (e.g. emergencies) [6].…”

Section: Introductionmentioning

confidence: 99%

A Case-Based Approach to Business Process Monitoring

Montani

Leonardi

2010

Artificial Intelligence in Theory and Practice III

View full text Add to dashboard Cite

show abstract

“…Both scenarios can be found, for example, in hospital and engineering environments [49,80]. Besides state-related correctness properties instance-specific changes pose several challenging issues.…”

Section: Changes Of Single Process Instancesmentioning

confidence: 99%

“…In particular, change predictability influences the way how process instances are adapted during runtime. Regarding evolving processes, for example, necessary changes and their scope are often known at buildtime [49,75,80]. Consequently, respective adaptations can be pre-planned and automated.…”

Section: Changes Of Single Process Instancesmentioning

confidence: 99%

“…We provide a short categorization of adaptive research process engines which includes Chautauqua [40], WASA 2 [136], Breeze [104], and ADEPT [88]. In addition, we consider the respective approaches followed by AgentWork [80], EPOS [75], and DYNAMITE [49] as well as the flexibility support offered by commercial process management tools.…”

Section: Change Scenarios and Their Realization In Existing Approachesmentioning

confidence: 99%

“…Application-specific support for automatic process changes is provided by AgentWork [80,81], DYNAMITE [49], and EPOS [75], but may be realizable on top of adaptive PMS like WASA 2 , ADEPT, or InConcert as well. The overall aim is to reduce error-prone and costly manual process adaptations.…”

Section: Approaches Supporting Pre-planned Instance Changesmentioning

confidence: 99%

See 2 more Smart Citations

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

Advanced workflow management technologies

Bolcer¹,

Taylor

1998

Softw. Process: Improve. Pract.

View full text Add to dashboard Cite

DYNAMITE: DYNAMIc Task nEts for software process management

Cited by 53 publications

References 12 publications

A Case-Based Approach to Business Process Monitoring

A Case-Based Approach to Business Process Monitoring

Schema Evolution in Process Management Systems

Advanced workflow management technologies

Contact Info

Product

Resources

About