SYSML12 — Section: 11.3.1.1 Activity in bdd

The semantics of composition between activities refers to synchronous calls. What happens if the activity is called asynchronously? Is it possible to show that activity in the bdd, too? What is the relationship to the calling activity?

Resolution:
Asynchronous calls start a new execution of the called behavior, but there is
usually no link between the new execution and the calling execution (the caller
invokes, but after that doesn't communicate with the called behavior execution).
If this is needed for some applications, the caller execution can instantiate the
called activity as a class/block, and link the new instance (the new called
execution) to the caller execution via an association. This association would be
composite if the called execution is started synchronously, and non-composite if
it is started asynchronously (using StartObjectBehaviorAction in both cases).
This seems like too much detail of UML to cover in the SysML spec for an
uncommon usage scenario. The filer agrees to close with no change.
Disposition: Closed, no change