SysML Activity extension stereotypes - REFERENCE CARD Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 11:01: [STUB] Activity modelling extensions in SysML Slide kind UML Profile Diagram
The stereotype does not override UML token offering semantics, just indicates what happens to the token when it is accepted. When the stereotype is not applied, the semantics is as in UML, specifically, tokens arriving at object nodes do not replace ... Source OMG Systems Modeling Language (SysML) 1.6
For object nodes that are the target of continuous flows, «overwrite» and «nobuffer» have the same effect. Source OMG Systems Modeling Language (SysML) 1.6
The number of tokens replaced is equal to the weight of the incoming edge, which defaults to 1. Source OMG Systems Modeling Language (SysML) 1.6
Tokens arriving at a full object node with the Overwrite stereotype applied take up their positions in the ordering as normal, if any. The arriving tokens do not take the positions of the removed tokens. Source OMG Systems Modeling Language (SysML) 1.6
For upper bounds greater than one, the token removed is the one that has been in the object node the longest. For FIFO ordering, this is the token that is next to be selected, for LIFO it is the token that would be last to be selected. Source OMG Systems Modeling Language (SysML) 1.6
This is typically used on an input pin with an upper bound of 1 to ensure that stale data is overridden at an input pin. Source OMG Systems Modeling Language (SysML) 1.6
When the «overwrite» stereotype is applied to object nodes, a token arriving at a full object node removes one that is already there before being added (a full object node has as many tokens as allowed by its upper bound). Source OMG Systems Modeling Language (SysML) 1.6
NoBuffer::1_not_overwrite The «nobuffer» and «overwrite» stereotypes cannot be applied to the same element at the same time Source OMG Systems Modeling Language (SysML) 1.6
For object nodes that are the target of continuous flows, «nobuffer» and «overwrite» have the same effect. Source OMG Systems Modeling Language (SysML) 1.6
These two extensions are useful for ensuring that the most recent information is available to actions by indicating when old values should not be kept in object nodes, and for preventing fast or continuously flowing values from collecting ... Source OMG Systems Modeling Language (SysML) 1.6
Extension of object nodes, including pins, with the option for newly arriving values to replace values that are already in the object nodes (see Overwrite in Figure 11-8). Source OMG Systems Modeling Language (SysML) 1.6