Method Modifications in a Configuration Management Environment

Using configuration management (CM) within the method engineering discipline is a relatively new field of research (Greiffenberg, 2003; Saeki, 2006; Saeki & Oda, 2005). CM administrates revisions and variants of methods and provides a change process to control method modifications. Thus, method CM realizes the traceability of method changes, enables distributed method engineering and ensure a constantly high quality of engineered methods. In the past years, research focused on the development of appropriate method CM systems. The consequences of method modifications in such systems, however, have attained only little attention or were discussed only in a superficial way. As method modifications can lead to several problems (Weller & Esswein, 2006), it is important to know the consequences of such modifications to forecast the costs of a method change. Furthermore, this knowledge is useful to create or enhance appropriate CAME tools supporting (situational) method engineering. In this paper, we examine consequences of method modifications within configuration management. Thereby, we focus on the situational method engineering approach and the effects of method modifications on already instantiated models. We discuss critical modifications that lead to inconsistent models and analyze conditions for those problems.

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

[2]  Werner Esswein,et al.  Consequences of Meta-Model Modifications within Model Configuration Management , 2006, WoMM.

[3]  Pär J. Ågerfalk,et al.  Why Software Engineers Do Not Keep to the Principle of Separating Business Logic from Display: A Method Rationale Analysis , 2006, CAiSE.

[4]  Sjaak Brinkkemper,et al.  Situational method engineering for informational system project approaches , 1994, Methods and Associated Tools for the Information Systems Life Cycle.

[5]  Reidar Conradi,et al.  Version models for software configuration management , 1998, CSUR.

[6]  Oscar Dieste,et al.  CONCEPTUAL MODELING IN SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING: CONCEPTS, TECHNIQUES AND TRENDS , 2009 .

[7]  M. Saeki CAME : The First Step to Automated Method Engineering , 2003 .

[8]  Susanne Strahringer,et al.  Metamodellierung als Instrument des Methodenvergleichs: eine Evaluierung am Beispiel objektorientierter Analysemethoden , 1996 .

[9]  Reinhard Schütte,et al.  The Guidelines of Modeling - An Approach to Enhance the Quality in Information Models , 1998, ER.

[10]  Susan A. Dart,et al.  Concepts in configuration management systems , 1991, SCM '91.

[11]  Daniel Pfeiffer,et al.  A framework for comparing conceptual models , 2005, EMISA.

[12]  Joerg Evermann,et al.  Ontology based object-oriented domain modelling: fundamental concepts , 2005, Requirements Engineering.

[13]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[14]  Robert Braun,et al.  Configuration Management for Reference Models , 2007 .

[15]  Motoshi Saeki,et al.  A Conceptual Model of Version Control in Method Engineering Environment , 2005, CAiSE Short Paper Proceedings.

[16]  Andreas Zeller,et al.  Configuration management with version sets: a unified software versioning model and its applications , 1997 .

[17]  Ulrich Frank,et al.  Conceptual Modelling as the Core of the Information Systems Discipline - Perspectives and Epistemological Challenges , 1999 .

[18]  Jörg Becker,et al.  Configurative Process Modeling - Outlining an Approach to Increased Business Process Model Usability , 2004 .

[19]  Motoshi Saeki Configuration Management in a Method Engineering Context , 2006, CAiSE.

[20]  S. M. Thompson Configuration management — keeping it all together , 1997 .

[21]  Jacky Estublier Software configuration management: a roadmap , 2000, ICSE '00.

[22]  Andy Evans,et al.  Engineering Modelling Languages: A Precise Meta-Modelling Approach , 2002, FASE.

[23]  Oliver Thomas,et al.  Version Management for Reference Models: Design and Implementation , 2007 .

[24]  Matthias Jarke,et al.  ConceptBase: Managing Conceptual Models about Information Systems , 2006, Handbook on Architectures of Information Systems.

[25]  Steffen Greiffenberg,et al.  Methodenentwicklung in Wirtschaft und Verwaltung , 2004 .

[26]  Colette Rolland,et al.  Towards a Meta-tool for Change-Centric Method Engineering: A Typology of Generic Operators , 2004, CAiSE.

[27]  Ralf Kneuper,et al.  CMMI - Verbesserung von Softwareprozessen mit Capability Maturity Model Integration (2. Aufl.) , 2003 .

[28]  M. Rosemann,et al.  Vorbereitung der Prozessmodellierung , 2000 .

[29]  August-Wilhelm Scheer,et al.  ARIS - Business Process Modeling , 1998 .

[30]  Reidar Conradi,et al.  Impact of the research community on the field of software configuration management: summary of an impact project report , 2002, SOEN.

[31]  Pär J. Ågerfalk,et al.  Systems Development Method Rationale: A Conceptual Framework for Analysis , 2003, ICEIS.

[32]  Sjaak Brinkkemper,et al.  Assembly Techniques for Method Engineering , 1998, CAiSE.

[33]  Sjaak Brinkkemper,et al.  Method engineering: engineering of information systems development methods and tools , 1996, Inf. Softw. Technol..

[34]  Kalle Lyytinen,et al.  MetaEdit+: A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment , 1996, CAiSE.

[35]  Brian Fitzgerald,et al.  The use of systems development methodologies in practice: a field study , 1997, Inf. Syst. J..