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
UML2 Types of Pins - metaclasses This content has been marked as discussing an ADVANCED topic! Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind UML Profile Diagram
Starting an Action that has a ValuePin - LIMITED SUPPORT Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind UML Activity Diagram
Starting an Action that has a ControlPin Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind UML Activity Diagram
Starting an Action that has an InputPin with multiplicity Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind UML Activity Diagram
The Action execution consumes input data on all InputPins on the Action up to the upper multiplicity for each InputPin. Source Unified Modeling Language 2.5.1
An Action may not put more values into an output in a single execution than the [upper] multiplicity of that OutputPin. Source Unified Modeling Language 2.5.1
The upper multiplicity determines the maximum number of values that can be consumed from an InputPin by a single execution of its Action. Source Unified Modeling Language 2.5.1
Starting an Action that has an InputPin Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind UML Activity Diagram
Association and Property - some cases Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:02: UML 101 for model-based systems engineering with SysML Slide kind UML Class Diagram
These multiplicities may be assumed if not shown on a diagram. To avoid confusion, any multiplicity other than the default should always be shown on a diagram. Source OMG Systems Modeling Language (SysML) 1.7beta1
A part or shared association has a default multiplicity of [0..1] on the black or white diamond end. A unidirectional association has a default multiplicity of 1 on its target end. Source OMG Systems Modeling Language (SysML) 1.7beta1
The semantics are undefined for adding a value that violates the upper multiplicity of the StructuralFeature, and for adding a new value to a StructuralFeature with isReadonly=true after initialization of the object that would have the value. Source Unified Modeling Language 2.5.1
