Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Attributes and data types
Attributes of feature types, object types, data types and union types shall have a name and a data type. This is stated in the General Feature Model in ISO19109 - Rules for application schema, and also in Annex E of ISO19136 -GML. Even though these standards relate to application schemas, the same rules apply to conceptual models. This is important for implementation of the models.
The data type shall either be one of the predefined types from ISO19103, from other standards or a local class defined in the UML model.
A common error in UML modelling is to assign an attribute type a name without linking the name back to a base class, (for example typing “GM_Point” into a datatype field is not the same as selecting it from the ISO 19107 base model). The model migth look correct in diagrams, but the missing connection will create errors in implementations and dependency checking.
In the attribute table (t_attribute) in Enterprise Architect, attributes shall have a ClassifierID that links it to a data type element. To make sure this link is correct, always select the data type from the model, instead of writing the name.
Unfortunately, there is no predefined functionality in Enterprise Architect for controlling that the attributes are connected to data types. But this can be done with searches or scripting. A sample script for checking data type connection can be found [here] (https://github.com/ISO-TC211/UML-Best-Practices/blob/master/Scripts/VBScript/VAL%20Data%20type%20references.vbs)