requirement-usage-only-one-subject

Available in: SysML

This checks that requirement usages have at most one owned or inherited subject.

Note that the first subject will redefine all other inherited subjects automatically through the implicit step parameters redefinition.

Specification

A RequirementUsage must have at most one feature_membership that is a SubjectMembership.

Example

requirement r {
    subject s;
    subject s2; // error
}

Remove the additional subject:

requirement r {
    subject s; // ok
}

s implicitly redefines an inherited standard subject Requirements::RequirementCheck::subj.