Unity criteria for Business Process Modelling

Software Engineering has a recurrent problem in relation to Business Process Modelling (BPM): there is no agreement with regards to business process modularity. We claim that this results from a lack of theoretical underpinnings on the matter. This paper goes deeply into this issue by unfolding the notion of modularity: modularisation has an engineering intention that depends on the field where it is applied, and it relies on information hiding and encapsulation mechanisms. Unity criteria provide guidance for encapsulation. An important contribution of the paper is to provide unity criteria for BPM. These criteria are mainly underpinned by systemic principles and Communication Theory. The resulting unity criteria allow to clearly differentiate between problem space and solution space in BPM. The argumentations are illustrated with explanatory examples and figures. Also, a historical review of unity criteria in Software Engineering and Requirements Engineering is offered.

[1]  Edward Yourdon,et al.  Modern structured analysis , 1989 .

[2]  Ivar Jacobson,et al.  Use cases – Yesterday, today, and tomorrow , 2004, Software & Systems Modeling.

[3]  Roel Wieringa,et al.  Design methods for reactive systems - Yourdon, Statemate, and the UML , 2003 .

[4]  David Lorge Parnas,et al.  A technique for software module specification with examples , 1972, CACM.

[5]  Liu Jie,et al.  An Empirical Study of Flexible Business Process Based on Modularity System Theory , 2008, 2008 The Third International Multi-Conference on Computing in the Global Information Technology (iccgi 2008).

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

[7]  Gordon S. Blair,et al.  Object-oriented languages, systems and applications , 1991 .

[8]  Monique Snoeck,et al.  Consistency by Construction: The Case of MERODE , 2003, ER.

[9]  Maria Lapata.  The Semantics of Relationships: An Interdisciplinary Perspective , 2003 .

[10]  I. M. Bochenski.  The problem of universals , 1956 .

[11]  Mario Gerardo Piattini Velthuis.  Definición de una metodología de desarrollo para bases de datos orientadas al objeto fundamentadas en extensiones del modelo relacional , 1994 .

[12]  Oscar Pastor,et al.  Conceptual Alignment of Software Production Methods , 2007 .

[13]  Janis A. Bubenko,et al.  Enterprise Modelling: Improving the Quality of Requirements Specifications , 1994 .

[14]  Jim Gray,et al.  The Transaction Concept: Virtues and Limitations (Invited Paper) , 1981, VLDB.

[15]  John Mylopoulos,et al.  A language facility for designing database-intensive applications , 1989 .

[16]  Roel Wieringa,et al.  A survey of structured and object-oriented software specification methods and techniques , 1998, CSUR.

[17]  Cláudia Maria Lima Werner,et al.  Info Cases: Integrating Use Cases and Domain Models , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[18]  Sang Joon Kim,et al.  A Mathematical Theory of Communication , 2006 .

[19]  Colin Runciman,et al.  Perfect hash functions made parallel-Lazy functional programming on a distributed multiprocessor , 1993, [1993] Proceedings of the Twenty-sixth Hawaii International Conference on System Sciences.

[20]  Oscar Pastor,et al.  Towards a Communicational Perspective for Enterprise Information Systems Modelling , 2008, PoEM.

[21]  Aldo Gangemi,et al.  Ontological Analysis for the Unification of Biology , 2002, AMIA.

[22]  D. A Jardine,et al.  Concepts and terminology for the conceptual schema and the information base , 1984 .

[23]  Jan Willem Wieland,et al.  What Problem of Universals? , 2008, Philosophica.

[24]  Nicola Guarino,et al.  Dwq : Esprit Long Term Research Project, No 22469 Part-whole Relations in Object-centered Systems: an Overview Part-whole Relations in Object-centered Systems: an Overview , 2022 .

[25]  Aldo Dagnino,et al.  Deriving Goals from a Use-Case Based Requirements Specification , 2001, Requirements Engineering.

[26]  Ritu Agarwal,et al.  Comprehending Object and Process Models: An Empirical Study , 1999, IEEE Trans. Software Eng..

[27]  Börje Langefors,et al.  Theoretical analysis of information systems , 1973 .

[28]  Juan Sánchez,et al.  BPMN-Based Specification of Task Descriptions: Approach and Lessons Learnt , 2009, REFSQ.

[29]  Nicola Guarino,et al.  Identity and Subsumption , 2002 .

[30]  Alistair Cockburn,et al.  Structuring Use Cases with Goals , 2000 .

[31]  Michael Jesse Chonoles,et al.  UML 2 For Dummies , 2003 .

[32]  S. A. Yuditskii.  Behavioral Models of Business Systems , 2003 .

[33]  Guttorm Sindre,et al.  On the purpose of object-oriented analysis , 1993, OOPSLA '93.

[34]  John Mylopoulos,et al.  A language facility for designing database-intensive applications , 1980, TODS.

[35]  Clinton O. Longenecker,et al.  Why organizations fail: the view from the front‐line , 1999 .

[36]  F. E..  A Relational Model of Data Large Shared Data Banks , 2000 .

[37]  Glenford J. Myers,et al.  Structured Design , 1999, IBM Syst. J..

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

[39]  Niklaus Wirth,et al.  Program development by stepwise refinement , 1971, CACM.

[40]  Urs Andelfinger,et al.  Conceptions are Social Constructs - towards a Solid Foundation of the FRISCO Approach , 2000, ISCO.

[41]  Jeffrey Parsons,et al.  How UML is used , 2006, CACM.

[42]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[43]  Aldo Gangemi,et al.  Understanding systematic conceptual structures in polysemous medical terms , 2000, AMIA.

[44]  Colette Rolland,et al.  Concepts for Design of an Information System Conceptual Schema and its Utilization in the REMORA Project , 1978, VLDB.

[45]  Jan Mendling,et al.  Modularity in Process Models: Review and Effects , 2008, BPM.

[46]  Jean-Baptiste Lully,et al.  The collected works , 1996 .