-
Key: SYSML2_-111
-
Status: closed
-
Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
-
Summary:
In SysML v1, an output value of an action that is an input value of more than one action, is often modeled by an object flow and fork node which create object tokens pointing to the value.
The mapping of ObjectFlow in combination with ForkNodes is not covered yet by the transformation.
-
Reported: SysML 2.0b1 — Mon, 24 Jul 2023 13:16 GMT
-
Disposition: Resolved — SysML 2.0b4
-
Disposition Summary:
Map to special fork and join actions if corresponding SysML v1 nodes are connected with object flows
Map to special action usages defined by ForkAction resp. JoinAction that flow things like SysML v1 object flow, but always as succession flows, even for v1 object flows that do not have the semantics of v2 successions which handle the SysML v1 object flow semantics.
A fork node is mapped to:
fork sysMLv1ForkNode { in ref inputObject1; out ref outputObject1 = inputObject1; out ref outputObject2 = inputObject1; }
And a join node is mapped to:
join sysMLv1JoinNode { in ref inputObject1; in ref inputObject2; out ref outputObject1 = (inputObject1, inputObject2); }
If isCombineDuplicate is false, a join node is mapped to:
join sysMLv1JoinNode { in ref inputObject1; in ref inputObject2; out ref outputObject1 nonunique = (inputObject1, inputObject2); }
-
Updated: Sat, 19 Jul 2025 19:26 GMT
-
Attachments:
- sysmlv2-111-proposal.jpg 181 kB (image/jpeg)
SYSML2_ — Mapping of ObjectFlows with ForkNodes
- Key: SYSML2_-111
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF 2