SYSML2_ — There is no checkSatisfyRequirementUsageSpecialization constraint

SatisfyRequirementUsage subsets Requirements::notSatisfiedRequirementChecks or Requirements::satisfiedRequirementChecks in pilot implementation.

checkSatisfyRequirementUsageSpecialization constraint should be defined in the specification.

Correct the semantics for SatisfyRequirementUsage

The normative Systems Model Library file Requirements.sysml contains the following:

	abstract requirement satisfiedRequirementChecks :> requirementChecks, assertedConstraintChecks {
		doc
		/*
		 * satisfiedRequirementChecks is the subset of requirementChecks for Requirements asserted to be satisfied.
		 */
	}

	abstract requirement notSatisfiedRequirementChecks: RequirementCheck[0..*] :> requirementChecks, negatedConstraintChecks {
		doc
		/*
		 * notSatisfiedRequirementChecks is the subset of requirementChecks for Requirements asserted to be not satisfied.
		 */
	}

It was, indeed, intended that these be the base usages for SatisfyRequirementUsages. However, the specification was not updated to reflect this.

This resolution corrects that omission. It also fixes incorrect references to assertedConstraints and negatedConstraints in the abstract syntax and semantics for AssertConstraintUsage, changing then to assertedConstraintChecks and negatedConstraintChecks, respectively.