SysML 2.0b3 FTF Avatar
  1. OMG Issue

SYSML2_ — TransitionUsage requires binding to succession with mandatory end multiplicities

  • Key: SYSML2_-129
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 7.13.3 (Bindings as Usages) says

    The end features of a binding always have multiplicity [1..1].

    and Clause (TransitionUsage) includes a constraint requiring a (1 to 1) binding between its succession and transitionLink:

    A TransitionUsage must have an ownedMember that is a BindingConnector between its succession and the
    inherited Feature TransitionPerformances::TransitionPerformance::transitionLink.
    ownedMember->selectByKind(BindingConnector)->exists(b |
    b.relatedFeatures->includes(succession) and

    with similar text in (Transition Usages). A succession will typically have fewer values than its transition usage, because the succession won't be traversed for every value (occurrence) of its source feature, while its transition usage will have the same number of values as the source feature, conflicting with the 1-1 end multiplicities. Compare to the modeling pattern in KerML Clause (Transition Performances Overview), excerpted in KERML-157.

  • Reported: SysML 2.0b1 — Fri, 25 Aug 2023 19:22 GMT
  • Updated: Wed, 10 Apr 2024 00:41 GMT