SysML 1.4 RTF Avatar
  1. OMG Issue

SYSML14 — Requirements should be disallowed from typing other elements

  • Key: SYSML14-19
  • Legacy Issue Number: 17529
  • Status: closed  
  • Source: University of Arizona ( Mr. Rick Steiner)
  • 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 are currently insufficient to enforce this concept.

    Recommend adding a 6th constraint, precluding a class stereotyped by <<requirement>> from typing any other model element.

  • Reported: SysML 1.3 — Thu, 26 Jul 2012 04:00 GMT
  • Disposition: Resolved — SysML 1.4
  • Disposition Summary:

    Add a 6th constraint to the text as recommended in the summary.

  • Updated: Fri, 6 Mar 2015 20:58 GMT