SysML 2.0b3 FTF Avatar
  1. OMG Issue

SYSML2_ — ObjectFlow mappings limited to non-streaming parameters

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

    Clause 7.7.3.3.17 (CommonActivityEdgeSuccessionAsUsage_Mapping), Description says

    The mapping class provides a common mapping of a UML4SysML::ActivityEdge to a SysMLv2 SucessionAsUsage.

    Clause 7.7.3.3.35 (ObjectFlow_Mapping), Description, says

    A UML4SysML::ObjectFlowFlow without a guard condition is mapped to a SysMLv2SuccessionFlowConnectionUsage.

    This seems to say all ActivityEdges, including ObjectFlows are mapped to v2 Successions, is that right? This prevents mapping of object flows from/to streaming parameters, which enable actions to provide output and take input while they are executing, with object flows between the respective pins potentially defining guards to filter which items move across which object flows, per UML 2.5, Clause 15.2.3.3 (Activity Edges), second paragraph.

    The above isn't mentioned, AFAICT, in the various "not mapped" tables, and the term "stream" doesn't appear anywhere in the Transformation specification.

  • Reported: SysML 2.0b2 — Tue, 30 Jul 2024 15:41 GMT
  • Updated: Tue, 30 Jul 2024 15:45 GMT