Sparx Systems Forum
Enterprise Architect => Uml Process => Topic started by: beginner on June 16, 2010, 09:18:04 pm
-
Here's another one for the UML gurus. I wonder why Sparx has introduced Advanced/Custom properties. Aren't these just tagged values? E.g. for action pins the custom properties are used for in/out. Ports (from SysML) make use of a tagged value. What is the logic behind this?
The disadvantage of custom properties is on the hand: you have to perform complicated click operations while tagged values are always visible in the docked window.
b.
-
Apparently they have introduced the "custom properties" to be more flexible.
I think most of the custom properties are actually regular properties from a UML point of view. I guess it was just easier to add a custom property then to add a regular one.
Geert
-
Likely the custom dialogue is easier to customize than the regular. However, why not using tagged values for the purpose. These are nothing else but "custom properties", aren't they?
b.
-
Would that make it a bit complicated?
Because that would mean that standard UML attributes are being mixed with tagged values, which are bound to a profile.
Geert
-
I don't mean the standard attributes. Only those you get from context Advanced/Custom Properties. They are not standard anyway, are they?
b.
-
Actually they are, that's what I meant.
For example the "isderived" attribute of an association is stored in the custom properties, while that is a standard UML attribute.
Geert
-
I see. Thanks, Geert.
b.