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

When a DataStoreNode accepts an object token, if that token contains an object with the same identity as an object contained in a token already held by the node, then the duplicate object token shall not be placed on the DataStoreNode.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
SysML1.7: ISSUE: Claim that 'Datastore already has an overwrite semantics' is inconsistent w.r.t. UML2.5.1
SysMLv1: Cameo Simulation Toolkit: Activity Diagram simulation: Tokens in a DataStoreNode [with mini video]
Source
Unified Modeling Language 2.5.1
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
RULE
UML keywords
Activity
token
object token
DataStoreNode
token offer
identity
Full quote
When a DataStoreNode accepts an object token, if that token contains an object with the same identity as an object contained in a token already held by the node, then the duplicate object token shall not be placed on the DataStoreNode.
Next snippet
Unlike a regular CentralBufferNode, a DataStoreNode contains objects uniquely.
The selection and transformation Behaviors on outgoing ObjectFlows can be used to get information out of a DataStoreNode as if a query were being performed.
Related snippets
15.4.3.4 Data Store Nodes - A DataStoreNode is a CentralBufferNode that holds its object tokens persistently while its activity is executing.
Related snippets (backlinks)
(Datastore already has an overwrite semantics)
Visit also
Visit also (backlinks)