Issue 14075: definition of what constitutes a development method (spem-rtf) Source: (, ) Nature: Enhancement Severity: Significant 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 Resolution: Revised Text: Actions taken: July 13, 2009: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 13 Jul 2009 23:50:14 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Wayne Jenkins Company: The Marlo Group mailFrom: wayne.jenkins@marlo.com.au Notification: Yes Specification: Software & Systems Process Engineering Meta-Model Specification Section: 6.2 FormalNumber: formal/2008-04-01 Version: 2.0 RevisionDate: April 2008 Page: 9-11 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729) Description I 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. Cheers, Wayne.