KERML — Validation constraints are missing in the SysML abstract syntax

The following validation constraints are implied by textual descriptions in the specification, but are missing in the abstract syntax. They should be added, along with appropriate OCL.

8.3.17.2 ExhibitStateUsage

1. validateExhibitStateUsageReference – If an ExhibitStateUsage has an ownedReferenceSubsetting, then its referencedFeature must be a StateActionUsage.

8.3.19.2 AssertConstraintUsage

2. validateAssertConstraintUsageReference – If an AssertConstraintUsage has an ownedReferenceSubsetting, then its referencedFeature must be a ConstraintUsage.

8.3.20.10 SatisfyRequirementUsage

4. validateSatisfyRequirementUsageReference – If a SatisfyRequirementUsage has an ownedReferenceSubsetting, then its referencedFeature must be a RequirementUsage.

8.3.24.2 IncludeUseCaseUsage

5. validateIncludeUseCaseUsageReference – If an IncludeUseCaseUsage has an ownedReferenceSubsetting, then its referencedFeature must be a UseCaseUsage.

Transferred to SysML v2 FTF

This issue was created under the KerML FTF by mistake. It has been transferred to the SysML v2 FTF (SYSML2-28).