Elsevier

Information Systems

Volume 38, Issue 8, November 2013, Pages 1046-1069
Information Systems

Version management for business process schema evolution

https://doi.org/10.1016/j.is.2013.03.006Get rights and content

Highlights

  • A versioning approach to specify process schema evolutions and versions in version space.

  • Analysis on process evolution dependency and conflicts.

  • A version preserving graph model to capture and update process changes in schema space.

  • Algorithms to dynamically retrieve the process schema of any version from the VPG.

  • Implement a proof-of-concept prototype.

Abstract

The current business environment changes rapidly, dictated by user requirements and market opportunities. Organisations are therefore driven to continuously adapt their business processes to new conditions. Thus, management of business process schema evolution, particularly process version control, is in great demand to capture the dynamics of business process schema changes. This paper aims to facilitate version control for business process schema evolution, with an emphasis on version compatibility, co-existence of multiple versions and dynamic version shifts. A multi-level versioning approach is established to specify dependency between business process schema evolutions, and a novel version preserving graph model is proposed to record business process schema evolutions. A set of business process schema updating operations is devised to support the entire set of process change patterns. By maintaining sufficient and necessary schema and version information, our approach provides comprehensive support for navigating process instance executions of different and changing versions, and deriving the process schema of a certain version. A prototype is also implemented for the proof-of-concept purpose.

Introduction

In the current business globalisation setting, varying market opportunities have been described as “change has become the only certainty” [1]. In such a turbulent environment, organisations have to adapt their business processes to emerging opportunities and changes continuously [2], [3], in order to survive and thrive. Driven by this urgent de-mand, organisations are seeking new technologies to help manage their dynamic, expanding and changing business processes [4], [5].

Technically, these requirements call for support on process schema evolution, process instance updating, and version control, inter alia. In particular, the capability for updating running process instances to the latest schema version, and modifying the process schema without suspending running instances is highly sought after [6]. In practice, this requirement is further complicated by temporary and concurrent process schema evolutions, since they result in many business process schema versions and their business process instances. As such, innovative version management solutions are in demand to harmonise the co-existence of business processes and instances belonging to different versions.

In our previous work [7], we tackled the handover of running instances from an old process schema to a new schema, i.e., between only two process schema versions, with other colleagues. In this paper we concentrate on management of multiple process schema versions and version shifts. A multi-level evolution diagram is proposed to specify process schema evolutions and their dependencies, while a version preserving graph is defined to record process schema evolutions. This approach allows dynamic process schema evolutions and co-existence of diverse process schema versions, and supports the entire set of classical process change patterns [8], [9]. Particularly, our approach contributes to the current process version management by:

  • (1)

    Proposing a process versioning approach to specify the process schema evolutions and versions in the version space.

  • (2)

    Establishing a novel version preserving graph (VPG) model to capture sufficient and necessary process schema evolution information and update the process schema on the fly, in the schema space.

  • (3)

    Defining a set of updating operations to support dynamic process schema evolutions following various process change patterns.

  • (4)

    Supporting extracting process schemas of different versions and navigating process instances of changing process schema versions in a dynamic manner.

  • (5)

    Implementing a proof-of-concept prototype.

The remainder of this paper is organised as follows: Section 2 addresses the version issues in business process schema evolutions with a motivating example, and analyses the requirements for process schema version management with a study of process schema evolution strategies and patterns. Section 3 defines the notion of process schema and introduces a multi-level versioning approach to specify the dependency between process schema evolution and process schema versions. Section 4 proposes a version preserving graph (VPG) model, and explains how to record process schema changes in a version preserving graph with a set of process schema updating operations. Section 5 discusses process instance navigation and process schema retrieval with the VPG model, and introduces the implemented prototype. Section 6 lists the work related to business process change management, and discusses the advantages and limitations of our approach. Conclusion remarks and future work are in Section 7.

The reported work in this paper is based on our previous research on process schema evolutions [10], with significant extensions on process schema version designation, process schema evolution analysis, supports to classical process change patterns, model justification and prototype implementation.

Section snippets

Motivating example

Business process adaptation and evolution are becoming more common and frequent. Here, we use a manufacturing scenario as a motivating example to illustrate how process schemas evolve. A factory has multiple pipelines of the same type, two of which are pipeline A and pipeline B as shown in Fig. 1. At the beginning, each pipeline follows the same production process schema, which is marked as version 0. The production process includes activities “schedule production”, “produce using work centre

Process schema and version representation for business process change management

Business process schema evolution management relies on the recording of process schema evolutions in both schema space and version space, as discussed in Section 2. Correspondingly, this section is to introduce the definition of process schema, process schema evolution types and relations, and a version numbering mechanism, respectively.

Version control in business process change management

The versioning approach discussed in Section 3 solves the issue of representing process schema versions and evolutions in the version space. In this section, a novel graph model is proposed to store and maintain the structural changes to a process schema in the schema space.

Run-time version management

Run-time process schema version management tackles three main issues, i.e., process instance navigation, process schema retrieval and process instance data migration. Our previous work [7] has already addressed the last issue and this paper concentrates on the first two issues with the proposed process version control approach. With respect to process instance navigation and process schema retrieval, exclusive relation and evolution IDs play an important role in determining process components

Related work

Business process version management is closely related to workflow evolution research. Casati et al. [28] presented a workflow modification language (WFML) to support business process schema evolutions. They also devised three main policies, viz., abort, flush and progressive, to manage case evolution. WFML defines a set of declaration primitives and flow primitives for the changes of workflow variables and flow structures. Chiu, Li, and Karlapalem applied the extended object-oriented

Conclusions and future work

This paper discussed version management issues in the context of business process schema evolution. A versioning method was proposed to represent different business process schema evolutions and the dependencies between them. A novel version preserving graph model was proposed to capture dynamic modifications to a business process schema via a set of updating operations. Strategies for extracting a business process schema of a given version from a version preserving graph were also discussed,

References (44)

  • X. Zhao et al.

    Aligning collaborative business processes: an organisation-oriented perspective

    IEEE Transactions on Systems, Man and Cybernetics: Part A

    (2009)
  • X. Zhao et al.

    Steering dynamic collaborations between business processes

    IEEE Transactions on Systems, Man and Cybernetics: Part A

    (2010)
  • C. Liu et al.

    Challenges and opportunities in collaborative business process management

    Information System Frontiers

    (2009)
  • C. Liu, M.E. Orlowska, H. Li, Automating Handover in Dynamic Workflow Environments, in: 10th International Conference...
  • B. Weber, S. Rinderle, M. Reichert, Change patterns and change support features in process-aware information systems,...
  • X. Zhao, C. Liu, Version management in the business process change context, in: Proceedings of the 5th International...
  • K. Ploesser, J. Recker, M. Rosemann, Towards a classification and lifecycle of business process change, in: Proceedings...
  • S. Rinderle-Ma, M. Reichert, B. Weber, On the formal semantics of change patterns in process-aware information systems,...
  • D. Delen et al.

    Successful business process transformation at J.D. Edwards

    Business Process Transformation—Advances in Management Information Systems

    (2007)
  • P. Harmon

    Business Processs Change—A Guide for Business Management and BPM and Six Sigma Professionals

    (2007)
  • A.P. Massey et al.

    Transforming the new product development process: leveraging and managing knowledge

    Busienss Process Transformation—Advances in Management Information Systems

    (2007)
  • M. Kirchmer et al.

    Business Process Change Management: ARIS in Practice

    (2003)
  • Cited by (23)

    • Grouping of business processes models based on an incremental clustering algorithm using fuzzy similarity and multimodal search

      2017, Expert Systems with Applications
      Citation Excerpt :

      Business Processes (BP) Models group procedures and interrelated activities in organizational structures that work together to accomplish a business objective. BP may be related to product manufacturing, services provisioning, goods procurement, inventory management, among other activities (Rajnoha, Sujová, & Dobrovič, 2012; Reijers, Mans, & van der Toorn, 2009; Zhao & Liu, 2013). Furthermore, BP models include information about shared data, process participants and how these participants interact (Schlegel, Vidačković, Dusch, & Seiger, 2012; Vukšić, Bach, & Popovič, 2013).

    • Impact analysis and change propagation in service-oriented enterprises: A systematic review

      2015, Information Systems
      Citation Excerpt :

      Therefore, process flexibility and change are deemed of crucial concern in the Business Process Management (BPM) domain [15]. Adaptive business process management systems [67] and version management of business processes [92] are relevant areas of change management in this regard; however, our focus is specifically on impact analysis and propagation of business process changes. From Service Oriented Architecture (SOA) point of view, services are also subject to constant changes and modifications.

    • A version and context-based approach to easily model flexible collaborative processes

      2020, Collaborative Convergence and Virtual Teamwork for Organizational Transformation
    • A framework for evaluating migration strategies of evolving business processes

      2020, International Journal of Business Process Integration and Management
    • A context-based approach for modelling and querying versions of BPMN processes

      2020, International Journal of Business Process Integration and Management
    View all citing articles on Scopus
    View full text