Is Property a Stereotype

[Thomas Mercer-Hursh]

If one creates an Attribute for a Component, one of the available Stereotypes listed in the drop down is Property, but in the list of Stereotypes, there is no entry for Property.

Magic?

It seems to work to define a stereotype for an Attribute, but there are not examples and it doesn't seem to be shown anywhere.

[Paolo F Cantoni]

If one creates an Attribute for a Component, one of the available Stereotypes listed in the drop down is Property, but in the list of Stereotypes, there is no entry for Property.

Magic?

It seems to work to define a stereotype for an Attribute, but there are not examples and it doesn't seem to be shown anywhere.

EA works by Magic...

That's why many of the bugs can't be fixed...

Paolo

[«Midnight»]

0.02 CAD, if I may...

UML recognizes the the stereotype; so does EA.

EA also provides features for code engineering. Among these is the ability to 'signal' [my word] EA that a given attribute should be accompanied by a relate property.

At the higher levels of an MDA or Zachman paradigm the earlier interpretation would be appropriate. At the lower - or language dependent - levels the second might be what you need. EA seems to assume you are working close to the metal; it pops up a dialog for the language you are using. [It seems to assume the default, but appears to let you supersede that.] The end result is that EA creates appropriate entries for the necessary method(s).

I don't think EA 'remembers' what the link though. Perhaps I am wrong on this. You might want to test whether EA applies    a stereotype if you check Property. You should also check whether EA goes back through previously created methods if you change the 'attributes' of an Attribute.

David

[Thomas Mercer-Hursh]

No discount on that 0.02 CAD anymore ... if anything you get change back!

In my current example, the base object is a Component, which annoyingly doesn't have a link direct to attributes, but one can still bring up attributes on the right click menu in the project browser.  There is not property check box there, but Property is available as a stereotype.  If I add a new stereotype with base of Attribute (not in the drop down, but is accepted) it does show up there as well.  I.e., it seems to work, but it seems a bit non-orthogonal that Property isn't in the list of stereotypes.

[«Midnight»]

So true Thomas,

Remember that the «property» stereotype and the Property check box in EA are two different (but subtly related) things. One is a standard UML stereotype, the other is a 'command' to EA to set up appropriate property methods (get and set) in a language-dependent way.

David

[Thomas Mercer-Hursh]

And, how unfortunate that they are separate things.  Property itself, may or may not cause me any grief when I get to MDA since ABL has properties it it may be straightforward.  But, it sure is annoying to be stuck using table and column instead of being able to extend those stereotypes to cover aspects specific to the OpenEdge database.