Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!

NoBuffer::1_not_overwrite The «nobuffer» and «overwrite» stereotypes cannot be applied to the same element at the same time

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
UML keywords
ObjectNode
ActivityNode::outgoing
InputPin
Action::/input
SysML keywords
«noBuffer»
NoBuffer
Overwrite
«overwrite»
Full quote
1_not_overwrite

The «nobuffer» and «overwrite» stereotypes cannot be applied to the same element at the same time.

     Overwrite.allInstances().base_ObjectNode->excludes(self.base_ObjectNode)
Next snippet
Related snippets
When the «nobuffer» stereotype is applied to object nodes, tokens arriving at the node are discarded if they are refused by outgoing edges, or refused by actions for object nodes that are input pins.
This is typically used with fast or continuously flowing data values, to prevent buffer overrun, or to model transient values, such as electrical signals.
For object nodes that are the target of continuous flows, «nobuffer» and «overwrite» have the same effect.
The stereotype does not override UML token offering semantics; it just indicates what happens to the token when it is accepted. When the stereotype is not applied, the semantics are as in UML, specifically, tokens arriving at an object node ...
Related snippets (backlinks)
Visit also
Visit also (backlinks)