KerML 1.0b3 FTF Avatar
  1. OMG Issue

KERML_ — TransitionPerformance modeling pattern more general than needed, not aligned with SysML::TransitionUsage

  • Key: KERML_-41
  • Status: open  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Clause 9.2.10.1 (Transition Performances Overview) requires two connectors typed by associations, to constrain transitionLink and transitionLinkSource:

    The Succession constrained by a TransitionPerformance is specified by a Connector between the Succession and its transitionStep, a unique Step typed by TransitionPerformance or a specialization of it, of the same Behavior as the Succession. This connector is
    • typed by an Association defined to give a value to the transitionLink of TransitionPerformances,
    • has connector end multiplicity 0..1 on the Succession end and 1 on the TransitionPerformance Step end.

    The transitionStep above is also connected to the Succession's sourceFeature, because conditions on the Succession depend on each Occurrence of its sourceFeature separately, which TransitionPerformances identify as their transitionLinkSource. This connector is
    • typed by an Association defined to give a value to the transitionLinkSource of TransitionPerformances.
    • with connector end multiplicity 1 on both ends.

    but

    • succession could subset transitionStep.transitionLink (equivalent to a binding with optional multiplicity on succession end)
    • bind succession's sourceFeature and its transitionStep.transitionLinkSource (1 to 1 end multiplicities)

    giving the desired result without introducing new associations for each transitionStep. This would also align it with SysML's modeling pattern specified in TransitionUsage::checkTransitionUsageSuccessionBindingConnector and checkTransitionUsageSourceBindingConnector (after the latter is corrected as proposed in SYSML2-397).

  • Reported: KerML 1.0a1 — Fri, 25 Aug 2023 19:16 GMT
  • Updated: Tue, 9 Apr 2024 23:30 GMT