Change Patterns Detection and Traceability Impact Analysis of Business Process Models

  • Watcharin Uronkarn
  • Twittie SenivongseEmail author


Business analysts define business process models for describing a series of tasks to produce services or products to serve business goals. Hence business process models represent business requirements for development of the software that enables automation of the business processes. When tasks in a business process are changed, such changes also trigger changes in the artifacts that have been produced during development of the related software. Analysis of an impact a business process change has on the software is useful for the software project manager and the system analyst to plan the effort to change the artifacts, including the software itself, accordingly. This paper presents a traceability impact analysis using traceability information of the old version of the business process model and its related software artifacts. The impact analysis is based on different patterns of business process changes that are made to the old business process model to create a new version of the model. Detection algorithms are used to identify various patterns of process structure changes so that business process tasks that are changed and software artifacts that would be impacted by the changes can be reported. The paper also discusses a supporting tool and its evaluation.


Business process Business process model Change detection Change impact analysis Change patterns Traceability 


  1. 1.
    Object Management Group, Business process model and notation (BPMN) (Online). Available:
  2. 2.
    F.A.C. Pinheiro, J.A. Goguen, An object-oriented tool for tracing requirements, in IEEE Software, Mar 1996, pp. 52–64Google Scholar
  3. 3.
    S.A. Bohner, R.S. Arnold, Software Change Impact Analysis (IEEE Computer Society Press, Los Alamitos, 1996)Google Scholar
  4. 4.
    W. Uronkarn, T. Senivongse, Change pattern-driven traceability of business processes, in Proceedings of the International MultiConference of Engineers and Computer Scientists 2014, IMECS 2014, 12–14 Mar 2014, Hong Kong. Lecture Notes in Engineering and Computer Science, pp. 601–606Google Scholar
  5. 5.
    B. Piprani, M. Borg, J. Chabot, É. Chartrand, An adaptable ORM metamodel to support traceability of business requirements across system development life cycle phases, in Proceedings of on the Move to Meaningful Internet Systems: OTM 2008 Workshops. Lecture Notes in Computer Science, vol. 5333, pp. 728–737 (2008)Google Scholar
  6. 6.
    IBM: Mapping business process diagrams to UML use case diagrams (online). Available:
  7. 7.
    Y. Wang, J. Yang, W. Zhao, Change impact analysis for service based business processes, in Proceedings of IEEE International Conference on Service-Oriented Computing and Applications, SOCA 2010, 13–15 Dec 2010, Australia, pp. 1–8Google Scholar
  8. 8.
    H. Xiao, J. Guo, Y. Zou, Supporting change impact analysis for service oriented business applications, in Proceedings of International Workshop on Systems Development in SOA Environments, SDSOA 2007, 20–26 May 2007, Minneapolis, 6 ppGoogle Scholar
  9. 9.
    R. Dijkman, A classification of differences between similar business processes, in Proceedings of 11th IEEE International Conference on Enterprise Distributed Object Computing Conference, EDOC 2007, 15–19 Oct 2007, Annapolis, pp. 37–47Google Scholar

Copyright information

© Springer Science+Business Media Dordrecht 2015

Authors and Affiliations

  1. 1.Department of Computer Engineering, Faculty of EngineeringChulalongkorn UniversityBangkokThailand

Personalised recommendations