Persistent Classes

[zyx]

Hello,

    There is a way to show a class is a persistent class? I mean graphically, I know that in the class properties I can set it is persistent.

[qwerty]

Where in the class properties can you set persistence?

q.

[zyx]

Well, I click in the class, then in details, there is a combo entitled persistence where you can set your class to be persistent or transient.

[qwerty]

Uhh, that was too obvious... I guess that except for writing a shape script there is no standard way. Instead you could consider to use a <<persistent>> stereotype instead of this property. This property is most likely some UML heritage. The recent 2.5 spec does not tell anything about such a property.

q.

[zyx]

Well, I thought about it, but there is no such stereotype available, so I must to create a new one, correct? I know EA allows you to digit a stereotype that is not in the list, but is it correct? I read that to create new stereotypes we need to create a new UML profile... Or is there a profile with this kind of stereotypes? I think it is very probable...

[qwerty]

You can create any stereotype at wish (as you do with class names). That is their intention. Using them with MDG is a more strict way to prevent people to go astray and add stereotypes in dozens. EA security also has an option to restrict adding stereotypes for single users/groups. If that is not enabled, your users can already introduce stereotypes (also by accidentally misspelling them).

q.

[Eve]

I know EA allows you to digit a stereotype that is not in the list, but is it correct? I read that to create new stereotypes we need to create a new UML profile...

From a strict UML point of view, all stereotypes come from profiles and all tagged values come from stereotypes. EA is more flexible, but these free stereotypes can be considered as part of an implicitly defined profile.

[qwerty]

I never thought about that. Actually p. 278 of UML 2.5 states

A stereotype must be contained, directly or indirectly, in a profile.

I concur with Simon's statement that EA provides this implicit (dynamic) profile. Especially when reading p. 251 where they write

There is no simple answer for when to create a new metamodel, when to create a new profile, and when to create both

which qualifies the earlier statement

when defining a UML profile, the profile’s stereotypes are defined to extend the UML classes in the normative version of the UML

q.