Detecting and Resolving Process Model Differences in the Absence of a Change Log

Küster, Jochen M.; Gerth, Christian; Förster, Alexander; Engels, Gregor

doi:10.1007/978-3-540-85758-7_19

Cited by 124 publications

(59 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In related work, there exist measures that can be used to determine the level of similarity between processes (Dijkman et al, 2011) and to identify differences between processes (Küster et al, 2008). These measures could also be used to measure the extent to which harmonization has been achieved, because more similar process variants can be assumed to be more harmonized.…”

Section: Application Consolidation Process Harmonization and Relatedmentioning

confidence: 99%

Measures of process harmonization

Romero

Dijkman

Grefen

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

Context: Many large organizations juggle an application portfolio that contains different applications that fulfill similar tasks in the organization. In an effort to reduce operating costs, they are attempting to consolidate such applications. Before consolidating applications, the work that is done with these applications must be harmonized. This is also known as process harmonization. Objective:The increased interest in process harmonization calls for measures to quantify the extent to which processes have been harmonized. These measures should also uncover the factors that are of interest when harmonizing processes. Currently, such measures do not exist. Therefore, this study develops and validates a measurement model to quantify the level of process harmonization in an organization. Method:The measurement model was developed by means of a literature study and structured interviews. Subsequently, it was validated through a survey, using factor analysis and correlations with known related constructs. Results:As a result, a valid and reliable measurement model was developed. The factors that are found to constitute process harmonization are: the technical design of the business process and its data, the resources that execute the process, and the information systems that are used in the process.In addition, strong correlations were found between process harmonization and process standardization and between process complexity and process harmonization. Conclusion:The measurement model can be used by practitioners, because it shows them the factors that must be taken into account when harmonizing processes, and because it provides them with a means to quantify the extent to which they succeeded in harmonizing their processes. At the same time, it can be used by researchers to conduct further empirical research in the area of process harmonization.

show abstract

Section: Application Consolidation Process Harmonization and Relatedmentioning

confidence: 99%

Measures of process harmonization

Romero

Dijkman

Grefen

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Difference Detection: For the detection of differences between different process model versions, we apply an approach that results in a reconstructed change log consisting of compound change operations [6] that comprise several related elementary changes, e.g. the joint insertion of a fork and a join node that form a complete parallel fragment.…”

Section: Framework For Business Processmentioning

confidence: 99%

“…In previous work [6,5,3,4,2], we have developed a framework for process model change management that addresses these activities. Our framework is based on an intermediate representation and can be used to merge process models in different modeling languages, e.g.…”

Section: Introductionmentioning

confidence: 99%

Towards Rich Change Management for Business Process Models

Gerth¹,

Luckey²

2012

Softwaretechnik-Trends

Self Cite

View full text Add to dashboard Cite

Business process models play an important role in the development of large IT systems, since they are easy to understand by all project stakeholders. High-level process models may be created by domain experts, which are stepwise refined in later development phases until they become executable. To establish such model-driven development (MDD) approaches in praxis, a comprehensive tool support of the complete model life cycle is necessary including model change management in particular. In this position paper, we give an overview of our framework for change management of business process models. This framework allows to merge process models in different modeling languages and considers the execution semantics of process models during comparison. Based on these results, we derive further research challenges with the aim to obtain a rich change management solution for business process models.

show abstract

“…Since our process models are design-time artifacts, this work is complimentary to ours. At design-time, Küster et al [22,21,14] propose a method for merging two versions of the same process model based on the application of change operations which can be automatically identified without the need for a change log. Similar to our approach, this solution relies on the decomposition of process models into SESE fragments.…”

Section: Concurrency Controlmentioning

confidence: 99%

Fragment-Based Version Management for Repositories of Business Process Models

Ekanayake

Rosa

Hofstede

et al. 2011

On the Move to Meaningful Internet Systems: OTM 2011

View full text Add to dashboard Cite

Abstract. As organizations reach higher levels of Business Process Management maturity, they tend to accumulate large collections of process models. These repositories may contain thousands of activities and be managed by different stakeholders with varying skills and responsibilities. However, while being of great value, these repositories induce high management costs. Thus, it becomes essential to keep track of the various model versions as they may mutually overlap, supersede one another and evolve over time. We propose an innovative versioning model, and associated storage structure, specifically designed to maximize sharing across process models and process model versions, reduce conflicts in concurrent edits and automatically handle controlled change propagation. The focal point of this technique is to version single process model fragments, rather than entire process models. Indeed empirical evidence shows that real-life process model repositories have numerous duplicate fragments. Experiments on two industrial datasets confirm the usefulness of our technique.

show abstract

Detecting and Resolving Process Model Differences in the Absence of a Change Log

Cited by 124 publications

References 13 publications

Measures of process harmonization

Measures of process harmonization

Towards Rich Change Management for Business Process Models

Fragment-Based Version Management for Repositories of Business Process Models

Contact Info

Product

Resources

About