Difference between revisions of "XCSG:ModelElement"
From AtlasWiki
(→Specification: Moving name attribute from Node to ModelElement) |
(→Specification: Added info on sourceCorrespondence) |
||
Line 12: | Line 12: | ||
| description = The name of the element within its [[Namespace]], or a brief, human-readable label. | | description = The name of the element within its [[Namespace]], or a brief, human-readable label. | ||
| type = String | | type = String | ||
+ | }} | ||
+ | |||
+ | {{Attribute | ||
+ | | name = sourceCorrespondence | ||
+ | | description = The location or locations in source code corresponding to the element. | ||
+ | | type = A SourceCorrespondence object or list of SourceCorrespondence objects. | ||
+ | | required = On nodes originating from source code. Edges (such as [[Call]] edges) that summarize multiple locations in source code contain lists of SourceCorrespondence objects indicating each location summarized. | ||
}} | }} |
Revision as of 17:40, 21 November 2014
An XCSG ModelElement is either a Node or Edge in an XCSG graph.
XCSG model elements have an id
attribute, which uniquely identifies that element; the id
attribute should enable those familiar with the analyzer which produced that node or edge to determine whether the graph already contains a node or edge representing a particular entity or relationship. No two model elements with equal IDs can exist in the same graph, to ensure each modeled element or relationship has a single representation in the graph.
Specification
Metaclass | ModelElement |
---|---|
Description | An abstraction drawn from the system being modeled. |
Direct Subkinds | Edge, Node |
---|
Attribute | name |
---|---|
Description | The name of the element within its Namespace, or a brief, human-readable label. |
Type | String |
Required | Yes |
Attribute | sourceCorrespondence |
---|---|
Description | The location or locations in source code corresponding to the element. |
Type | A SourceCorrespondence object or list of SourceCorrespondence objects. |
Required | On nodes originating from source code. Edges (such as Call edges) that summarize multiple locations in source code contain lists of SourceCorrespondence objects indicating each location summarized. |