SysML 2.1b1 RTF Avatar
  1. OMG Issue

SYSML21 — UseCaseUsage uses the Definition-only property ownedUseCase

Open Closed All
  • Key: SYSML21-714
  • Status: open  
  • Source: Diversitas Systems Engineering Ltd ( Geoffrey Tullener)
  • Summary: 
    UseCaseUsage::deriveUseCaseUsageIncludedUseCase: UseCaseUsage uses the Definition-only property ownedUseCase

Where:          SysML 2.0 (formal/2026-03-02), ยง8.3.25.4 UseCaseUsage, PDF p.413 (printed 381)
Published OCL:  includedUseCase = ownedUseCase->selectByKind(IncludeUseCaseUsage).useCaseIncluded
Correction proposed: includedUseCase = nestedUseCase->selectByKind(IncludeUseCaseUsage).useCaseIncluded
Proof of fault: ownedUseCase is a property of Definition; a UseCaseUsage is a Usage, so the name does not resolve.
Likely cause:   Copied from the Definition rule without adapting. Identical to the Definition rule, including the Definition-only property ownedUseCase. OMG fixed the same slip for ViewUsage (SYSML21-683).
Nearest rule:   UseCaseDefinition::deriveUseCaseDefinitionIncludedUseCase (SysML 2.0 PDF p.412 (printed 380)): includedUseCase = ownedUseCase->selectByKind(IncludeUseCaseUsage).useCaseIncluded
Basis of fix:   nestedUseCase is the Usage-side counterpart; OMG made the identical fix for ViewUsage (SYSML21-683).

    Provenance: found by deterministic checks of the OCL against the metamodel and OMG's reference implementation; the argument was reviewed and challenged by the reporter before filing. Further information on these methods is available on request.

    Not blocking: we are proceeding with the correction above in our own implementation.
  • Reported: SysML 2.0 — Tue, 27 Oct 2026 18:50 GMT
  • Updated: Fri, 30 Oct 2026 21:20 GMT