For automation interface information about a Data Store, see
Object node (automation interface). For automation interface purposes, a Data Store is an Object Node that has its Node Type set to Datastore Node.
A Data Store node is a central buffer node for non-transient information. A Data Store keeps all tokens that enter it, copying them when they are chosen to move downstream.
Create a Data Store through a Modeler pane or an Activity Diagram:
• In a Modeler pane, right-click an Activity or Structured Activity Node, point to New, point to Object Node, and then click Data Store.
• On an Activity Diagram, click the Data Store toolbar button, and then click in free space or inside an Activity Partition, Interruptible Activity Region or Structured Activity Node.
When used on an Activity Diagram, a Data Store's notation is as follows.
The View Options on an Activity Diagram allow you to show or hide the item type, that is, «Data Store». In addition, the view options allow you to dock a Data Store onto the boundary of an Activity Partition. The view options are set through the Object Node entry. See
Object node view options - activity diagram.
On an Activity Diagram, you can populate a Data Store's missing Activity Flows, Comments and Constraints: right-click the Data Store, point to Populate, and then click the appropriate command.
On a Class Diagram, you can show a Data Store as an Association between an Activity and a Class, that is, between the Activity that owns the Data Store and the Class that is that Data Store's type. To add this Association to a Class Diagram: right-click the Activity, point to Populate, and then click Associations. When shown on a Class Diagram, a Data Store's notation is as follows.
The View Options on a Class Diagram allows you to show or hide the name of the Data Store. The View options are set through the Association entry. See
Association view options - class diagram.
On a Class Diagram, you can populate a Data Store's missing Association symbols: right-click the Data Store, point to Populate, and then click Associations.
In the Dictionary pane, Data Stores are listed in the UML\Object Nodes folder.
In the Modeler panes, a short-cut symbol on the Data Store's icon indicates that the item is a
stub.
The following sections provide information about how a Data Store is used in the model. For more information about a property, item, model part or diagram, click it.
Structured Activity Node — Applies only when the Data Store is scoped directly to a Structured Activity Node.
Owns
Object Flow The Object Flow is owned jointly by Data Store and the associated item. The access permissions you have to an Object Flow are determined by the access permissions you have to its source item.
Dependency — The Dependency is owned jointly by the Data Store and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.
IO Flow — The IO Flow is owned jointly by the Data Store, the IO Flow's other linked item and the IO Flow's IO Item.
Data Store toolbar button, and then click in free space or inside an Activity Partition, Interruptible Activity Region or Structured Activity Node.
on the Data Store's icon indicates that the item is a
stub.
Structured Activity Node — Applies only when the Data Store is scoped directly to a Structured Activity Node.
Object Flow The Object Flow is owned jointly by Data Store and the associated item. The access permissions you have to an Object Flow are determined by the access permissions you have to its source item.
Dependency — The Dependency is owned jointly by the Data Store and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.
IO Flow — The IO Flow is owned jointly by the Data Store, the IO Flow's other linked item and the IO Flow's IO Item.
Atomic State — through the in states relationship.
Concurrent State — through the in states relationship.
Entry State —through the in states relationship.
Exit State — through the in states relationship.
Final State — through the in states relationship.
Fork State — through the in states relationship.
History State — through the in states relationship.
Initial State — through the in states relationship.
Join State — through the in states relationship.
Junction State — through the in states relationship.
Sequential State — through the in states relationship.
Stereotype — To make a Data Store valid for a Stereotype, set up Object Node a valid item type.
Submachine State — through the in states relationship.
Activity
Comment
Constraint
Activity Model
Activity Diagram
Class Diagram
Variant Diagram