Source: NIST ( Conrad Bock)
Clause 7.13.3 (Bindings as Usages) says
The end features of a binding always have multiplicity [1..1].
and Clause 22.214.171.124 (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.
with similar text in 126.96.36.199 (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 188.8.131.52 (Transition Performances Overview), excerpted in KERML-157.
Reported: SysML 2.0b1 — Fri, 25 Aug 2023 19:22 GMT
Updated: Tue, 29 Aug 2023 18:52 GMT