Issue 11284: Section: 14.11 and B.4 (spem2-ftf) Source: International Business Machines (Dr. Peter Haumer, phaumer@us.ibm.com) Nature: Revision Severity: Significant Summary: Inconsistent overrides for Extends: User of the SPEM 2.0 implementations EPF Composer and Rational Method Composer complained about an inconsistency in semantics define for the Extends relationship in Section 14.11 (p.136) and Appendix B.4 (p.179). The inconsistency relates to the fact that for to-one relationships and attribute values the extending element can override the inherited values whereas for to-many relationships values of the extending element would be appended to the list of inherited elements. The users preferred to have complete override semantics here as well. In other words, if the extending element would define its own to-many relationship instances the inherited relationships would be completely overridden. If the extending element needed relationships from its base element then users could add them back in manually, which is perceived as a more flexibility solution for using this relationship. Resolution: - Updated semantics definition for Extends in Section 14.11 and updated Appendix B.4 Revised Text: - Updated sentences in Section 14.11: "The result of interpretation is that the special element has the same properties as the based-on has, but might override the inherited properties with its own values." "0..n-association instances: Association instances defined for the based-on Variability Element are inherited to the special Variability Element. If the special Variability Element defines its own association instances, then the inherited ones are ignored." [Note, Framemaker did not create a change bar here for this text change as the text is position inside a nested table, which the tool does not seem to support for change bars.] - Updated sentence in Section B.1: "Extends: Only defines inheritance for the extending element. The base remains untouched. The extending element can override inherited attribute values and association instances by defining their own. If no new values are defined for the extending element it will inherit these values from the base element." - Updated text in Section B.4: "The result of interpretation is that the special element has the same properties that the based-on has, but might define its own overrides." "Outgoing to-many associations of the base element are inherited to the extending element if the extending element does not define its own association instances." Disposition: Resolved Actions taken: August 17, 2007: received issue January 15, 2008: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 17 Aug 2007 14:39:00 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Peter Haumer Company: IBM mailFrom: phaumer@us.ibm.com Notification: No Specification: Software Process Engineering Metamodel Specification Section: 14.11 and B.4 FormalNumber: ptc/07-03-03 Version: 2.0 RevisionDate: March/12/2007 Page: 136, 179 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Description Inconsistent overrides for Extends: User of the SPEM 2.0 implementations EPF Composer and Rational Method Composer complained about an inconsistency in semantics define for the Extends relationship in Section 14.11 (p.136) and Appendix B.4 (p.179). The inconsistency relates to the fact that for to-one relationships and attribute values the extending element can override the inherited values whereas for to-many relationships values of the extending element would be appended to the list of inherited elements. The users preferred to have complete override semantics here as well. In other words, if the extending element would define its own to-many relationship instances the inherited relationships would be completely overridden. If the extending element needed relationships from its base element then users could add them back in manually, which is perceived as a more flexibility solution for using this relationship.