Issue 18410: Constraint [5] should include specializations of Requirement (sysml-rtf) Source: Atego (Mr. Phillip Astle, phil.astle(at)atego.com) Nature: Enhancement Severity: Significant Summary: Constraint [5] states: "A nested classifier of a class stereotyped by «requirement» must also be stereotyped by «requirement»." This would seem to stop Requirements from owning Classes stereotyped by specializations of Requirements (for example, ExtendedRequirement from D.2.2 Stereotypes), which seems too limiting. I'd suggest this is reworded to: "A nested classifier of a class stereotyped by «requirement» must also be stereotyped by «requirement» or one of its specializations" Resolution: Revised Text: Actions taken: February 5, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 05 Feb 2013 05:21:56 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Phil Astle Employer: Atego mailFrom: phil.astle@atego.com Terms_Agreement: I agree Specification: OMG Systems Modeling Language (OMG SysML.) Section: 16.3.2.3 Requirement FormalNumber: formal/2012-06-01 Version: 1.3 Doc_Year: 2012 Doc_Month: June Doc_Day: 01 Page: 148 Title: Constraint [5] should include specializations of Requirement. Nature: Enhancement Severity: Significant CODE: 3TMw8 B1: Report Issue Description: Constraint [5] states: "A nested classifier of a class stereotyped by «requirement» must also be stereotyped by «requirement»." This would seem to stop Requirements from owning Classes stereotyped by specializations of Requirements (for example, ExtendedRequirement from D.2.2 Stereotypes), which seems too limiting. I'd suggest this is reworded to: "A nested classifier of a class stereotyped by «requirement» must also be stereotyped by «requirement» or one of its specializations"