Representing Unique Stakeholder Perspectives in BPM Notations

Evidence shows that proposals for new modeling notations emerge and evolution of current ones are becoming more complex, often in an attempt to satisfy the many different modeling perspectives required by each stakeholder. This paper presents a method to identify the specific notation construct requirements, at multiple levels of abstraction, which satisfy the needs of a stakeholder when performing a specific task. Initially the focus is on two different stakeholders: software engineers (SE) and business analysts(BA), and one specific software engineering activity: requirements eliciting and analysis. The specific body of knowledge of the two stakeholders (Software Engineering Book of Knowledge (SWEBOK) for the SE, and Business Analysis Body of Knowledge (BABOK) for the BA) are used to identify each stakeholder specific notation construct requirements, at multiple levels of abstraction, in order to propose a simplification of their notation and constructs set. This paper presents solution avenues to simplify business process modeling notations by identifying the specific constructs preferred by different stakeholders.

[1]  Jon Atle Gulla,et al.  Modelling with APM in ERP projects , 2001 .

[2]  Ron Weber,et al.  On the deep structure of information systems , 1995, Inf. Syst. J..

[3]  Valeria De Antonellis,et al.  A Disciplined Approach to Office Analysis , 1990, IEEE Trans. Software Eng..

[4]  A Straw,et al.  Guide to the Software Engineering Body of Knowledge , 1998 .

[5]  Jan L. G. Dietz,et al.  The Benefit of Enterprise Ontology in Identifying Business Components , 2006, IFIP TC8 WCC ISS.

[6]  Activité ad‐hoc Types de tâches.  Introduction to BPMN , 2004 .

[7]  A. Spanyi.  Business Process Management is a Team Sport: Play it to Win! , 2003 .

[8]  Geert Poels,et al.  Mapping semantically enriched Formal Tropos to business process models , 2009, SAC '09.

[9]  Philippe Dumas,et al.  La méthode OSSAD : pour maîtriser les technologies de l'information , 1990 .

[10]  Raman Kazhamiakin,et al.  A framework for integrating business processes and business requirements , 2004, Proceedings. Eighth IEEE International Enterprise Distributed Object Computing Conference, 2004. EDOC 2004..

[11]  Magic Quadrant for Business Process Management Suites, 2007 , 2007 .

[12]  Jon Atle Gulla,et al.  On the challenges of business modeling in large-scale reengineering projects , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[13]  Eric Yu,et al.  Using Goals, Rules and Methods to Support Reasoning in Business Process Reengineering , 1996 .

[14]  Marc M. Lankhorst,et al.  Supporting viewpoint-oriented enterprise architecture , 2004, Proceedings. Eighth IEEE International Enterprise Distributed Object Computing Conference, 2004. EDOC 2004..

[15]  Amit P. Sheth,et al.  An overview of workflow management: From process modeling to workflow automation infrastructure , 1995, Distributed and Parallel Databases.

[16]  Christopher J. Pavlovski,et al.  Non-Functional Requirements in Business Process Modeling , 2008, APCCM.

[17]  Bill Curtis,et al.  Process modeling , 1992, CACM.

[18]  Michael Rosemann,et al.  Integrating multi-perspective views into ontological analysis , 2000, ICIS.

[19]  Michael Rosemann,et al.  Integrated Process Modeling: An Ontological Evaluation , 2000, Inf. Syst..

[20]  Beate List,et al.  A UML 2 Profile for Business Process Modelling , 2005, ER.

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

[22]  Jim Sinur.  Magic Quadrant for Business Process Management Suites , 2009 .

[23]  Hongyan Ma,et al.  Process-aware information systems: Bridging people and software through process technology , 2007, J. Assoc. Inf. Sci. Technol..

[24]  Jan Mendling,et al.  What Makes Process Models Understandable? , 2007, BPM.

[25]  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.

[26]  Peter Meso,et al.  Conceptualizing Systems for Understanding: An Empirical Test of Decomposition Principles in Object-Oriented Analysis , 2006, Inf. Syst. Res..

[27]  Hafedh Mili,et al.  Towards a Methodology for Representing and Classifying Business Processes , 2009, MCETECH.

[28]  Chung Yee Lee,et al.  Business process management: survey and methodology , 1995 .

[29]  Ron Weber,et al.  Research Commentary: Information Systems and Conceptual Modeling - A Research Agenda , 2002, Inf. Syst. Res..

[30]  Beate List,et al.  An evaluation of conceptual business process modelling languages , 2006, SAC.

[31]  John M. Ward,et al.  Principles of Information Systems Management , 1995 .

[32]  Juan Sánchez,et al.  Business Process Modelling and Purpose Analysis for Requirements Analysis of Information Systems , 2008, CAiSE.

[33]  Reiko Heckel,et al.  Process Modeling Using UML , 2005, Process-Aware Information Systems.

[34]  Marta Indulska,et al.  Improving representational analysis: An example from the enterprise systems interoperability domain , 2006 .

[35]  Hans-Erik Eriksson,et al.  Business Modeling with UML , 2001 .

[36]  Ron Weber,et al.  An Ontological Model of an Information System , 1990, IEEE Trans. Software Eng..

[37]  Thomas R. Gulledge,et al.  Business process management: public sector implications , 2002, Bus. Process. Manag. J..

[38]  Heinrich C. Mayr,et al.  Business Process Modeling and Requirements Modeling , 2007, First International Conference on the Digital Society (ICDS'07).

[39]  Ron Weber,et al.  On the ontological expressiveness of information systems analysis and design grammars , 1993, Inf. Syst. J..

[40]  Jörg Becker,et al.  Guidelines of Business Process Modeling , 2000, Business Process Management.

[41]  Marc M. Lankhorst.  Enterprise Architecture at Work - Modelling, Communication and Analysis, 3rd Edition , 2005, The Enterprise Engineering Series.

[42]  M. Porter,et al.  How Information Gives You Competitive Advantage , 1985 .

[43]  John Mylopoulos,et al.  From E-R to "A-R" - Modelling Strategic Actor Relationships for Business Process Reengineering , 1994, Int. J. Cooperative Inf. Syst..

[44]  Enid Mumford,et al.  Reengineering the Corporation: A Manifesto for Business Revolution , 1995 .

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

[46]  Yijun Yu,et al.  Requirements-Driven Design and Configuration Management of Business Processes , 2007, BPM.

[47]  R. Kaplan,et al.  Using the balanced scorecard as a strategic management system , 1996 .

[48]  André Vasconcelos,et al.  A framework for modeling strategy, business processes and information systems , 2001, Proceedings Fifth IEEE International Enterprise Distributed Object Computing Conference.

[49]  Mario Pichler,et al.  Business Process-based Requirements Modeling and Management , 2006, 2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop).

[50]  Brian Henderson-Sellers,et al.  Ontological Evaluation of the UML Using the Bunge–Wand–Weber Model , 2002, Software and Systems Modeling.

[51]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .

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

[53]  Peter Gyngell,et al.  Process Innovation: Reengineering Work through Information Technology , 1994 .

[54]  S. T. Buckland,et al.  An Introduction to the Bootstrap. , 1994 .

[55]  Gregory D. Schumacher,et al.  IEEE Guide for Developing System Requirements Specifications , 1999 .

[56]  Marta Indulska,et al.  Extending the Scope of Representation Theory: A Review and Proposed Research Model , 2007 .

[57]  Howard Smith,et al.  Business Process Management: The Third Wave , 2003 .

[58]  Mohamed Zairi,et al.  Business process management: a boundaryless approach to modern competitiveness , 1997, Bus. Process. Manag. J..

[59]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[60]  Marta Indulska,et al.  Measuring Method Complexity : The Case of the Business Process Modeling Notation , 2009 .

[61]  D. Sinclair,et al.  Business process re‐engineering and process management , 1995 .

[62]  Niv Ahituv,et al.  Principles of information systems for management (2nd ed.) , 1986 .

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

[64]  Daniela E. Damian,et al.  Selecting Empirical Methods for Software Engineering Research , 2008, Guide to Advanced Empirical Software Engineering.

[65]  Michael zur Muehlen,et al.  Service Process Innovation: A Case Study of BPMN in Practice , 2008, Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008).

[66]  Onur Demirörs,et al.  Utilizing business process models for requirements elicitation , 2003, 2003 Proceedings 29th Euromicro Conference.

[67]  Peter Kawalek,et al.  Goal-based business process models: creation and evaluation , 1997, Bus. Process. Manag. J..