Applying the principle of separation of concerns to business process design

Functional decomposition breaks down a business process into a set of progressively more detailed activities. It facilitates the modular design of a system, the reuse of its parts and also contributes to increasing its comprehensibility. But achieving these qualities requires a business process to be decomposed consistently. Separation of concerns is the principle of separating a system into distinct features with a minimum of overlapping. This paper proposes using this principle to consistently decompose a business process into its constituent activities. An activity is modelled as a collaboration between role types that are played by entities. The decomposition method successively separates the overlapping roles until an activity is specified by the collaboration of an orthogonal set of role types. This method facilitates the consistent decomposition and design of a business process and the unambiguous identification of its atomic activities.

[1]  Antonia Albani,et al.  Identifying Business Components on the Basis of an Enterprise Ontology , 2006 .

[2]  Alan R. Hevner,et al.  Design Science in Information Systems Research , 2004, MIS Q..

[3]  Boudewijn F. van Dongen,et al.  Business process mining: An industrial application , 2007, Inf. Syst..

[4]  Salvatore T. March,et al.  Design and natural science research on information technology , 1995, Decis. Support Syst..

[5]  Nicola Guarino,et al.  An Ontology of Meta-Level Categories , 1994, KR.

[6]  José M. Tribolet,et al.  A role-based enterprise architecture framework , 2009, SAC '09.

[7]  Robert Rosenbaum,et al.  Supply chain excellence : a handbook for dramatic improvement using the SCOR model , 2007 .

[8]  Michael Uschold,et al.  The Enterprise Ontology , 1998, The Knowledge Engineering Review.

[9]  Jon Espen Ingvaldsen,et al.  Model-Based Business Process Mining , 2005, Inf. Syst. Manag..

[10]  Peter Huber,et al.  Hierarchies in coloured Petri nets , 1991, Applications and Theory of Petri Nets.

[11]  Subrata Dasgupta Design Theory and Computer Science: The Nature of Design Problems , 1991 .

[12]  Agnes Koschmider,et al.  Recommendation Based Process Modeling Support: Method and User Experience , 2008, ER.

[13]  George M. Giaglis,et al.  A Taxonomy of Business Process Modeling and Information Systems Modeling Techniques , 2001 .

[14]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[15]  José M. Tribolet,et al.  Using Business Transactions to Analyse the Consistency of Business Process Models , 2012, 2012 45th Hawaii International Conference on System Sciences.

[16]  Boudewijn F. van Dongen,et al.  Process Mining and Verification of Properties: An Approach Based on Temporal Logic , 2005, OTM Conferences.

[17]  Robert Winter,et al.  Method construction - a core approach to organizational engineering , 2005, SAC '05.

[18]  Luigi Pontieri,et al.  An Ontology-Driven Process Modeling Framework , 2004, DEXA.

[19]  Ivo Vondrák,et al.  Business Process Modeling , 2007, Encyclopedia of Database Systems.

[20]  J. Brocke,et al.  Handbook on Business Process Management 1 , 2010 .

[21]  Wolfgang Reisig,et al.  Lectures on Petri Nets I: Basic Models , 1996, Lecture Notes in Computer Science.

[22]  Jan L. G. Dietz,et al.  Enterprise ontology - theory and methodology , 2006 .

[23]  John F. Sowa,et al.  Conceptual Structures: Information Processing in Mind and Machine , 1983 .

[24]  Rob Davis,et al.  ARIS Design Platform: Getting Started with BPM , 2007 .

[25]  Herbert Weber,et al.  Modularity in Data Base System Design: A Software Engineering View of Data Base Systems , 1978, VLDB Surveys.

[26]  Wil M. P. van der Aalst,et al.  A configurable reference modelling language , 2007, Inf. Syst..