SYSML14 — Requirements should be disallowed from typing other elements

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.

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