SPEM 1.1 NO IDEA Avatar
  1. OMG Issue

SPEM11 — definition of what constitutes a development method

  • Key: SPEM11-3
  • Legacy Issue Number: 14075
  • Status: open  
  • Source: The Marlo Group ( Wayne Jenkins)
  • Summary:

    think it is crucial that the definition of what constitutes a development method is added to this specification. Observe that many concepts within the document define aspects of a method (e.g. method plug-in, method content, method configuration, etc) but at no stage is the concept of a method defined. The reason I think this is important is that the concept of "enactment" (seen in section 16) should be applied to a method rather than a process. For example, when I enact a development method I create a code repository and processes for its use — I do not just enact the processes. To support this model Figure 6.1 could change the configuration statement to "Configure a cohesive method customized for my project needs". The reason I need this alteration is that I am using the TOGAF method plug-in with the Eclipse Practice Framework. Here, the enactment of the TOGAF method for an organisation requires the creation of an architecture repository (in direct analogy to a code repository above). The current SPEM conceptual model does not seem to adequately cover this scenario

  • Reported: SPEM 1.1 — Mon, 13 Jul 2009 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT