requirement-usage-types

Available in: SysML

This checks that requirement usages are only typed by a single requirement definition.

Subsumes constraint-usage-types.

Specification

While not formally described in chapter 8, it is given in chapter 7.21.2:

A requirement usage must be defined by a single requirement definition.

Example

part def P;
requirement def R1;
requirement def R2;
requirement r1 : P; // error: A requirement usage must be defined by a single requirement definition
requirement r2 : R1, R2; // error: A requirement usage must be defined by a single requirement definition

Fix this by removing specializations that directly or indirectly contribute to invalid types:

part def P;
requirement r1; // ok

or specialize only a single requirement definition:

requirement def R1;
requirement r2 : R1; // ok

---

All validation rules