A strategy driven business process modelling approach

– Most of the process models concentrate on who does what, when, i.e. on the description of the operational performance of tasks. The goal driven approaches try to establish a close relationship between the “whys” and the “whats”. The former captures the strategic goals of the organisation whereas the latter tells us how they are achieved through tasks carried out by actors. In addition, managers do not naturally make the distinction between what to achieve (the goal) and the manner to achieve it (the strategy). This confusion often leads to the expression of manners as goals. In order to make clear the fundamental distinction between these two concerns and to master the complexity of process modelling, this paper seeks to propose a goal‐perspective, the map‐driven process modelling approach., – The map representation system conforms to goal models in the fact that it recognises the concept of a goal but departs from those by introducing the concept of strategy to attain a goal., – A business and its supporting system change in a concurrent way. In order to help the propagation of the intentional changes onto operational ones, we adopted the two levels hierarchical spiral process model. The intentional spiral deals with the production of the business process models using the map formalism and the operational one deals with the specifications of the supporting systems., – A business process is defined in terms of goals and strategies of reaching these goals. The approach allows choosing an appropriate level of details when analysing and redesigning business processes.

[1]  Colette Rolland,et al.  Meta-modelling for cooperative processes , 1999 .

[2]  Colette Rolland,et al.  Bridging the Gap Between Organisational Needs and ERP Functionality , 2000, Requirements Engineering.

[3]  Charles J. Fillmore,et al.  THE CASE FOR CASE. , 1967 .

[4]  Terry Winograd,et al.  The action workflow approach to workflow management technology , 1992, CSCW '92.

[5]  August-Wilhelm Scheer,et al.  Business Process Excellence: Aris in Practice , 2002 .

[6]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[7]  Jolita Ralyté,et al.  Ingénierie des méthodes à base de composants , 2001 .

[8]  Hans Eriksson,et al.  Business Modeling With UML: Business Patterns at Work , 2000 .

[9]  Jintae Lee,et al.  Extending the Potts and Bruns model for recording design rationale , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[10]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[11]  Colette Rolland,et al.  Eliciting gaps in requirements change , 2004, Requirements Engineering.

[12]  Nicolas Prat,et al.  Goal Formalisation and Classification for Requirements Engineering , 1996 .

[13]  Sergio Bandinelli,et al.  Process modeling in-the-large with SLANG , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[14]  Colette Rolland,et al.  A framework for generic patterns dedicated to the management of change in the electricity supply industry , 1998, Proceedings Ninth International Workshop on Database and Expert Systems Applications (Cat. No.98EX130).

[15]  Camille Salinesi,et al.  A method to analyse changes in the realisation of business intentions and strategies for information system adaptation , 2002, Proceedings. Sixth International Enterprise Distributed Object Computing.

[16]  Tok Wang Ling,et al.  Model-based support for business re-engineering , 1996, Inf. Softw. Technol..

[17]  Vasant Dhar,et al.  Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..

[18]  Carlo Ghezzi,et al.  A Survey and Assessment of Software Process Representation Formalisms , 1993, Int. J. Softw. Eng. Knowl. Eng..

[19]  Matthias Jarke,et al.  Requirements engineering in 2001: (virtually) managing a changing reality , 1994, Softw. Eng. J..

[20]  Amnon Naamad,et al.  Statemate: a working environment for the development of complex reactive systems , 1988, ICSE '88.

[21]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[22]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[23]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[24]  Colette Rolland,et al.  A multi-method for defining the organizational change , 2003, Inf. Softw. Technol..

[25]  Matthias Jarke,et al.  Scenario usage in system development: a report on current practice , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[26]  Geary A. Rummler,et al.  Improving Performance: How to Manage the White Space on the Organization Chart , 1990 .

[27]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[28]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[29]  Janis A. Bubenko,et al.  Facilitating "fuzzy to formal" requirements modelling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[30]  Colette Rolland,et al.  A unified framework for modeling cooperative design processes and cooperative business processes , 1998, Proceedings of the Thirty-First Hawaii International Conference on System Sciences.

[31]  Simon C. Dik,et al.  The theory of functional grammar , 1989 .

[32]  Michael Hammer,et al.  Reengineering Work: Don’t Automate, Obliterate , 1990 .

[33]  John M. Wilson,et al.  Business Processes: Modelling and Analysis for Re-engineering and Improvement , 1995 .

[34]  Stefan Decker,et al.  An Enterprise reference Scheme for Integrating Model Based Knowledge Engineering and Enterprise Modelling , 1997, EKAW.

[35]  Kees M. van Hee,et al.  Workflow Management: Models, Methods, and Systems , 2002, Cooperative information systems.

[36]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[37]  Colette Rolland,et al.  Fitting Business Models to System Functionality Exploring the Fitness Relationship , 2003, CAiSE.

[38]  James J. Alpigini,et al.  USING GRAMMAR-ORIENTED OBJECT DESIGN TO SEAMLESSLY MAP BUSINESS MODELS TO COMPONENT-BASED SOFTWARE ARCHITECTURES , 2001 .

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

[40]  David A. Marca,et al.  IDEFO - SADT Business Process and Enterprise Modelling , 1993 .

[41]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[42]  K. Siau,et al.  Intention Based Modelling of Organisational Change: An Experience Report , 1999 .

[43]  M. Hammer,et al.  REENGINEERING THE CORPORATION: A MANIFESTO FOR BUSINESS REVOLUTION , 1995 .

[44]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[45]  Desmond D'Souza,et al.  Objects, Components, and Frameworks with UML: The Catalysis Approach , 1998 .

[46]  Camille Salinesi,et al.  A Methodological Framework for Understanding IS Adaptation through Enterprise Change1 , 2002, OOIS.

[47]  Colette Rolland,et al.  Matching ERP system functionality to customer requirements , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.