Welcome to Modeltron, the elements of systems modeling.
All tagged Activity Diagram
There is a nuanced difference between an Activity Final Node and a Flow Final Node on a SysML Activity diagram. The Activity Final Node, when reached, terminates the execution of the entire Activity. When the Flow Final Node is reached, all tokens (either Control or Object Tokens) are consumed, but Activity execution continues.
Activity Parameters may be bundled together into Parameter Sets. Only one Input Parameter Set may hold tokens and only one Output Parameter Set may hold tokens on an Activity, although a single Activity Parameter may belong to more than one Parameter Set.
The «nobuffer» and «ovewrwrite» stereotypes can be applied to object nodes to model whether incoming tokens are discarded if a token is already present or overwrite the existing token in the object node.
If an Object Node is typed by a Block which possesses a state machine, then an Object Node, Activity Parameter, or Action Pin typed by that Block can require that the State Machine exist in a certain state before an Object Token may be passed.
