In situational method engineering (SME), there are two core intentions that method engineers look for: 1) a set method engineering goal that is the kind of method needed and 2) a method allowing him to satisfy this goal. This chapter can capture method engineering's goal using a generic process model (GPM) that guides the method engineering in the definition of his project method engineering goal and in the selection approach that best allows him to achieve it. The authors wish to move to functional method engineering so as to explore the context of method engineering/situational method engineering more fully based on functional and non-functional method situation. The implications of the approach on CAME tool design are considered and illustrated through a running example.
TopIntroduction
Method Engineering, ME is the discipline of developing information systems development methods. Initially, it was thought that a universal method (Saeki M. & Wenyin K., 1994) that was capable of addressing the needs of all information system development projects could be defined. However, this view was rejected (Hoef, Rob, Rolf & Vincent 1997), (Karlsson F. & Ågerfalk P J, 2004). Since project needs vary with projects and projects vary in their characteristics, development of methods may require specific adaptations (Anat & Iris, 2011). Therefore, an engineering technique for this is required. The area of Situational Method Engineering, SME was developed to build methods for specific development situations. Situational Method Engineering, SME, assumes the existence of a method base from which method components could be retrieved and assembled to form the desired method (Xavier, Jolita, Anna, Alberto, David, Jesús, Sergi, Marc, Norbert, Alberto, Angelo, 2018).
The assembly process has been illustrated in (Brinkkemper, Saeki & Harmsen 1998) where state chart and object models have been assembled together to form a new method.
Ralyte (Ralyté, Rébecca & Rolland, 2003) proposed a two-step goal oriented SME process: first, a method engineering, ME, goal is established, second, assembly based method engineering task is carried out by eliciting ME intentions. Prakash (Prakash, Srivastava, Gupta & Arora, 2007) proposed a three stage SME process: intention matching, architecture matching, and method implementation matching.
The situation of SME can be conceptualized in many ways, as descriptors (Rolland & Prakash, 1996), contingency factors (Slooten & Brinkkemper, 1993; Lemmen & Punter, 1994; Swede & Vliet 1994; Slooten 1995), project factors (Harmsen, Brinkkemper, Han Oei, 1994), situation factors (Harmsen, Lubbers I. & Wijers 1995), context type (Deneckere, Elena & Bruno 2010) and project type (Bucher, Klesse, Kurpjuweit &Winter 2007), (Bucher & Winter 2008). Table I summarizes the proposals made by different authors for the notion of a situation.