Author Topic: Make metaclasses and stereotypes selectable in profile model  (Read 5141 times)

Uffe

  • EA Practitioner
  • ***
  • Posts: 1669
  • Karma: +112/-11
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Hello,

There are two very similar metaconstraint relationships; «metarelationship» and «stereotyped relationship». In both of these, you must specify the metaclass / stereotype as free text.
This is stupid.

They should be selectable from dropdown lists or selector dialogs, as is the case when you create a new metaclass or add stereotypes to toolboxes using the profile helper.


/Uffe
My theories are always correct, just apply them to the right reality.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 7268
  • Karma: +166/-115
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Make metaclasses and stereotypes selectable in profile model
« Reply #1 on: June 23, 2020, 10:26:36 am »
Definitely wot 'e sed!

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 7232
  • Karma: +83/-10
    • View Profile
Re: Make metaclasses and stereotypes selectable in profile model
« Reply #2 on: June 29, 2020, 09:52:11 am »
Yes, it would be nice. In terms of the metaclass it could be a simple hard coded list. umlRole could be too, but ideally it would take into account the type for the source.

It's not so simple for the stereotype, which can be a stereotype in that package or an externally defined stereotype that may not even be available in the source model. Unfortunately, there's no tag type in EA that behaves even remotely similar.
Eve

support@sparxsystems.com