10th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing

Research Article

Towards a Common Platform for the Support of Routine and Agile Business Processes

Download820 downloads
  • @INPROCEEDINGS{10.4108/icst.collaboratecom.2014.257269,
        author={Michael Zeising and Stefan Sch\o{}nig and Stefan Jablonski},
        title={Towards a Common Platform for the Support of Routine and Agile Business Processes},
        proceedings={10th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing},
        publisher={IEEE},
        proceedings_a={COLLABORATECOM},
        year={2014},
        month={11},
        keywords={business processes routine processes agile processes procedural modeling rule-based modeling cross-perspective modeling modalities workflow patterns process navigation cmmn},
        doi={10.4108/icst.collaboratecom.2014.257269}
    }
    
  • Michael Zeising
    Stefan Schönig
    Stefan Jablonski
    Year: 2014
    Towards a Common Platform for the Support of Routine and Agile Business Processes
    COLLABORATECOM
    IEEE
    DOI: 10.4108/icst.collaboratecom.2014.257269
Michael Zeising1,*, Stefan Schönig1, Stefan Jablonski1
  • 1: Universität Bayreuth
*Contact email: michael.zeising@uni-bayreuth.de

Abstract

The spectrum of an organization’s business processes ranges from routine processes with a well-defined flow to agile processes with a degree of uncertainty. The Process Navigation platform aims at supporting both types of processes as well as combinations of them. It offers execution support for traditional flow-oriented notations like BPMN as they are well-suited for the routine type of processes. Rule-based notations for agile processes like CMMN are on the way of getting established but still have a number of weaknesses. As a consequence, the platform’s agile part does not target one single notation but relies on a rule-based cross-perspective and modal intermediate language. CMMN models are then translated to the intermediate language for execution. The contribution of this paper is built up in three parts: first of all, the overall architecture of the execution platform is explained. In a second step, the intermediate language is evaluated on the basis of a comprehensive and acknowledged framework of business process requirements. And finally, the translation of CMMN to the intermediate language is described by means of an example.