UAF 1.3b1 RTF Avatar
  1. OMG Issue

UAF13 — UAF::*ControlFlow not possible from most UML::ActivityNodes

Open Closed All
  • Key: UAF13-17
  • Status: closed  
  • Source: Department of Navy ( Mr. James Ciarcia)
  • Summary:

    By constraining UAF ControlFlows to just the associated viewpoint Actions as sources and targets we are preventing users from using the full range of UML::ActivityNodes that they could use in Process Views. Significally, ControlNodes, such as the Initial,Fork,Join,Merge,Final Nodes are all excluded but of major importance to good description and visualization.
    Recommendation:
    1) Either elevate UAF::*ActivityAction up to UML::ActivityNode and specifically add UML::InterruptingActivityRegion.interruptingEdge
    2)or remove .source and .target constraints on UAF::ControlFlows
  • Reported: UAF 1.2 — Wed, 19 Jan 2022 17:12 GMT
  • Disposition: Deferred — UAF 1.3b1
  • Disposition Summary:

    UAF RTF 1.3 scope is limited to Mission Engineering only

    Out of scope for 1.3
  • Updated: Mon, 24 Mar 2025 13:35 GMT