SysML 2.1b1 RTF Avatar
  1. OMG Issue

SYSML21 — Problem with library model for perform actions as transition effect actions

Open Closed All
  • Key: SYSML21-716
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:
    1. In the textual notation for a TransitionUsage, the effectAction is parsed as either an empty ActionUsage, a PerformActionUsage, an AcceptActionUsage or a SendActionUsage (see the production EffectBehaviorUsage in 8.2.2.18 States Textual Notation).
    2. A PerformAction is required to be non-composite (see the validation constraint validatePerformActionUsageReference in 8.3.17.14 PerformActionUsage).
    3. An effectAction of a TransitionUsage is required to subset the library usage Actions::TransitionAction::effect (see the semantic constraint checkTransitionUsageTransitionFeatureSpecialization in 8.3.18.9 TransitionUsage).
    4. The feature TransitionAction::effect is a composite ActionUsage (see the normative Systems Library model Actions.sysml). When the effectAction is a PerformAction, this conflicts with the requirement for a PerformAction to not be composite.

      Note also that TransitionAction::effect redefines the feature TransitionPeformance::effect from KerML, which is not composite. So there is not really any need for TransitionAction::effect to be composite.
  • Reported: SysML 2.0 — Thu, 29 Oct 2026 22:12 GMT
  • Updated: Fri, 30 Oct 2026 21:15 GMT