2006
DOI: 10.1007/11841760_17
|View full text |Cite
|
Sign up to set email alerts
|

On Representing, Purging, and Utilizing Change Logs in Process Management Systems

Abstract: Abstract. In recent years adaptive process management technolgy has emerged in order to increase the flexibility of business process implementations and to support process changes at different levels. Usually, respective systems log comprehensive information about changes, which can then be used for different purposes including process traceability, change reuse and process recovery. Therefore the adequate and efficient representation of change logs is a crucial task for adaptive process management systems. In… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
19
0

Year Published

2006
2006
2018
2018

Publication Types

Select...
7
3

Relationship

7
3

Authors

Journals

citations
Cited by 53 publications
(19 citation statements)
references
References 13 publications
0
19
0
Order By: Relevance
“…Traceability and Analysis of Changes (Change Feature F4). For adaptation patterns, applied changes have to be stored in a change log as change patterns or primitives [55]. Regarding patterns for changes in predefined regions, an execution log is usually sufficient to enable traceability (Design Choice F4 [1]).…”
Section: Other Change Support Featuresmentioning
confidence: 99%
“…Traceability and Analysis of Changes (Change Feature F4). For adaptation patterns, applied changes have to be stored in a change log as change patterns or primitives [55]. Regarding patterns for changes in predefined regions, an execution log is usually sufficient to enable traceability (Design Choice F4 [1]).…”
Section: Other Change Support Featuresmentioning
confidence: 99%
“…This section describes refactoring techniques, which become applicable when process models are executed by PAISs and historic data on process instances is available in execution or change logs [85,66]. These logs can be analyzed and mined to discover potential refactoring options.…”
Section: Refactorings For Model Evolutionmentioning
confidence: 99%
“…In AristaFlow, schema evolution is based on the same adaptation patterns as used for process modeling and ad-hoc changes [5]. Thereby, pattern semantics is utilized to cope with conflicting changes at the type and instance level, to increase the number of migratable process instances, and to efficiently represent applied changes [19][20][21]. Note that similar concepts exist for evolving service compositions [22].…”
Section: Supporting Process Changes Along the Process Life Cyclementioning
confidence: 99%