Issue 17529: Requirements should be disallowed from typing other elements (sysml-rtf) Source: Raytheon (Mr. Frederick A. Steiner, fsteiner(at)raytheon.com) Nature: Clarification Severity: Minor Summary: The concept of Requirement, as intended in the original SysML specification, included the notion that textual requirements only have meaning in their original context. Requirements thus should not provide a source of inheritance. This precludes their use as classifiers for typing other Requirements or any other model elements. The 5 constraints listed at the end of section 16.3.2.3 are currently insufficient to enforce this concept. Recommend adding a 6th constraint, precluding a class stereotyped by <<requirement>> from typing any other model element. Resolution: Revised Text: Actions taken: July 26, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 26 Jul 2012 11:44:11 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Rick Steiner Employer: Raytheon mailFrom: fsteiner@raytheon.com Terms_Agreement: I agree Specification: SysML 1.3 Section: 16.3.2.3 FormalNumber: formal/2012-06-01 Version: 1.3 Doc_Year: 2012 Doc_Month: June Doc_Day: Day Page: 148 Title: Requirements should be disallowed from typing other elements Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: The concept of Requirement, as intended in the original SysML specification, included the notion that textual requirements only have meaning in their original context. Requirements thus should not provide a source of inheritance. This precludes their use as classifiers for typing other Requirements or any other model elements. The 5 constraints listed at the end of section 16.3.2.3 are currently insufficient to enforce this concept. Recommend adding a 6th constraint, precluding a class stereotyped by <> from typing any other model element.