Business Process Modeling with Levels of Abstraction A Survey of Practitioners with Experience

The success of a software project depends on the quality of the software requirements specifications. Business process models are frequently used for eliciting software requirements; therefore, it is critical to produce high-quality business process models. To achieve this, the use of multiple levels of abstraction has been suggested in the literature as a modeling strategy. This paper presents the findings from a survey of experienced practitioners in order to test a set of propositions to address some of the issues with this strategy. The findings show, among other things, that practitioners need to represent business processes at the strategic, tactical and operational levels of abstraction. The survey findings also provide useful insights for selecting a business process modeling notation.

[1]  Marta Indulska,et al.  How good is BPMN really? Insights from theory and practice , 2006, ECIS.

[2]  Marta Indulska,et al.  Do Process Modelling Techniques Get Better? A Comparative Ontological Analysis of BPMN , 2005 .

[3]  Alain Abran,et al.  Guide to the Software Engineering Body of Knowledge : 2004 Version , 2005 .

[4]  Marta Indulska,et al.  Using ontology for the representational analysis of process modelling techniques , 2009, Int. J. Bus. Process. Integr. Manag..

[5]  Michael Rosemann,et al.  Exploring proposed ontological issues of ARIS with different categories of modellers , 2004 .

[6]  Mark von Rosing,et al.  Business Process Model and Notation - BPMN , 2015, The Complete Business Process Handbook, Vol. I.

[7]  Robert M. Davison,et al.  Principles of canonical action research , 2004, Inf. Syst. J..

[8]  Carlos Monsalve,et al.  Requirements elicitation using BPM notations: focusing on the strategic level representation , 2011 .

[9]  Shari Lawrence Pfleeger,et al.  Personal Opinion Surveys , 2008, Guide to Advanced Empirical Software Engineering.

[10]  Marta Indulska,et al.  How do practitioners use conceptual modeling in practice? , 2006, Data Knowl. Eng..

[11]  Michael Rosemann,et al.  A success model for Business process modeling: Findings from A multiple case study , 2004, PACIS.

[12]  Alain Abran,et al.  BPM and requirements elicitation at multiple levels of abstraction : a review , 2011 .

[13]  Alain Abran,et al.  Representing Unique Stakeholder Perspectives in BPM Notations , 2010, 2010 Eighth ACIS International Conference on Software Engineering Research, Management and Applications.

[14]  Michael Rosemann,et al.  Ontological Analysis of Integrated Process Models: testing hypotheses , 2001, Australas. J. Inf. Syst..

[15]  Marta Indulska,et al.  Business Process Modeling- A Comparative Analysis , 2009, J. Assoc. Inf. Syst..

[16]  D. Dillman,et al.  How to conduct your own survey , 1994 .

[17]  Michael Rosemann,et al.  Perceived Ontological Weaknesses Of Process Modeling Techniques : Further Evidence , 2002, ECIS.

[18]  T.C. Lethbridge,et al.  Guide to the Software Engineering Body of Knowledge (SWEBOK) and the Software Engineering Education Knowledge (SEEK) - a preliminary mapping , 2001, 10th International Workshop on Software Technology and Engineering Practice.