Difference between revisions of "XCSG:Node"
From AtlasWiki
(→Specification) |
(→Specification) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
An XCSG Node represents an entity or state in the software being modeled. | An XCSG Node represents an entity or state in the software being modeled. | ||
− | All nodes have names, which should be a brief, human-friendly text string representing the node. For nodes representing named software entities, the name will be its name in that [[namespace]]. | + | All nodes have names, which should be a brief, human-friendly text string representing the node. For nodes representing named software entities, the name will be its name in that [[namespace]]. |
For other nodes, it will be a brief, human-friendly representation of the type of the node, but need not uniquely identify it. For example, an appropriate name for both the subtraction and negation operators is "-", which makes sense as the label of such a node in a data flow graph. | For other nodes, it will be a brief, human-friendly representation of the type of the node, but need not uniquely identify it. For example, an appropriate name for both the subtraction and negation operators is "-", which makes sense as the label of such a node in a data flow graph. | ||
+ | |||
+ | Nodes also have a source correspondence attribute, which indicates their origin. | ||
==Specification== | ==Specification== | ||
Line 12: | Line 14: | ||
{{Attribute | {{Attribute | ||
− | | name = | + | | name = sourceCorrespondence |
− | | description = | + | | description = An object describing the origin of the element, such as source file and offset range. |
− | + | ||
}} | }} |
Latest revision as of 15:22, 21 May 2014
An XCSG Node represents an entity or state in the software being modeled.
All nodes have names, which should be a brief, human-friendly text string representing the node. For nodes representing named software entities, the name will be its name in that namespace.
For other nodes, it will be a brief, human-friendly representation of the type of the node, but need not uniquely identify it. For example, an appropriate name for both the subtraction and negation operators is "-", which makes sense as the label of such a node in a data flow graph.
Nodes also have a source correspondence attribute, which indicates their origin.
Specification
Metaclass | Node |
---|---|
Extends | ModelElement |
Description | Represents an entity or state in the software being modeled. |
Direct Subkinds | ControlFlow (Node), ControlFlowBlock, DataFlow (Node), Function, Library, Namespace, Project, C:TranslationUnit, Type, TypeAlias, UnrecognizedElement, Variable |
---|
All Superkinds | ModelElement |
---|
Known Possible In Edges | |||
---|---|---|---|
In Edge | Predecessor | Multiplicity | Description |
Contains | Node | 1 | Indicates that the predecessor contains the successor in a sense specified by the specific type of Contains edge. |
Known Possible Out Edges | |||
---|---|---|---|
Out Edge | Successor | Multiplicity | Description |
Contains | Node | ✱ | Indicates that the predecessor contains the successor in a sense specified by the specific type of Contains edge. |
Attribute | sourceCorrespondence |
---|---|
Description | An object describing the origin of the element, such as source file and offset range. |
Required | Yes |