Patterns of Situational Method Engineering

Situational Method Engineering (SME) addresses the need for custom-built software development methodologies that are tailored to fit specific project situations. A process pattern is a description of a recurring development process fragment that can be used as a generic model or a building block for engineering development processes. Software development process patterns are extensively used in SME, mainly as process components assembled to form bespoke methodologies; however, the SME field itself has not been scrutinized as to the methodology development process fragments frequently encountered. Situational method engineering knowledge captured in the form of SME process patterns is not only useful for building and improving SME processes, but can also facilitate knowledge transfer among method engineers. We propose a set of SME process patterns obtained through studying existing method engineering approaches. The set of patterns is organized into a generic pattern-based framework for SME. The framework can be used for developing SME processes according to the specific requirements of method engineering projects; the resulting SME processes can then be enacted to yield custom-built, project-specific methodologies.

[1]  Robert de Simone,et al.  P2I: an innovative MDA methodology for embedded real-time system , 2005, 8th Euromicro Conference on Digital System Design (DSD'05).

[2]  Stuart Anderson,et al.  Requirements Evolution from Process to Product Oriented Management , 2001, PROFES.

[3]  Keng Siau,et al.  Information Modeling Methods and Methodologies , 2005, Advanced topics in database research.

[4]  Brian Henderson-Sellers,et al.  The open process framework : an introduction , 2002 .

[5]  Liming Zhu,et al.  Situational Method Quality , 2007, Situational Method Engineering.

[6]  Colette Rolland,et al.  An Assembly Process Model for Method Engineering , 2001, CAiSE.

[7]  Colette Rolland,et al.  Towards a Generic Model for Situational Method Engineering , 2003, CAiSE.

[8]  Jolita Ralyté,et al.  Requirements Definition for the Situational Method Engineering , 2002, Engineering Information Systems in the Internet Context.

[9]  Pär J. Ågerfalk,et al.  Method configuration: adapting to situational characteristics while creating reusable assets , 2004, Inf. Softw. Technol..

[10]  Naveen Prakash,et al.  Generic Models for Engineering Methods of Diverse Domains , 2002, CAiSE.

[11]  Richard F. Paige,et al.  Agile Formal Method Engineering , 2005, IFM.

[12]  J. N. Brinkkemper,et al.  Formalisation of information systems modelling , 1990 .

[13]  Richard F. Paige,et al.  Process-centered review of object oriented software development methodologies , 2008, CSUR.

[14]  Andreas Rausch,et al.  Modular Process Patterns Supporting an Evolutionary Software Development Process , 2001, PROFES.

[15]  Leon J. Osterweil,et al.  Software processes are software too , 1987, ISPW.

[16]  Claudio Gutierrez,et al.  Survey of graph database models , 2008, CSUR.

[17]  D. M. Hutton,et al.  Process Patterns: Building Large‐Scale Systems Using Object Technology , 1999 .

[18]  Colette Rolland,et al.  An Approach for Evolution-Driven Method Engineering , 2005, Information Modeling Methods and Methodologies.

[19]  Raman Ramsin,et al.  Process Patterns for Agile Methodologies , 2007, Situational Method Engineering.

[20]  A.E.K. Sahraoui,et al.  A Lightweight Workshop-Centric Situational Approach for the Early Stages of Requirements Elicitation in Software Development , 2005 .