Book a Demo

Author Topic: Metaconstraint between different profiles  (Read 7352 times)

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Metaconstraint between different profiles
« on: May 18, 2021, 06:12:20 pm »
While I managed to create metaconstraints between elements of my own profile, I wonder how to do that between different profiles. Especially if I have own profile elements hookes up with standard UML elements. (Though I'm going on to mix several elixirs in the hope of the right pooof I appreaciate any hints here.)

q.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Metaconstraint between different profiles
« Reply #1 on: May 18, 2021, 06:38:13 pm »
Just add them as stereotype with their fully qualified name.

You can do that easily for build-in MDG's using the add metatype helper (but you are not a big fan of the helpers are you?)

Geert

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Metaconstraint between different profiles
« Reply #2 on: May 18, 2021, 06:50:22 pm »
I tried adding one that way, but it did not work. I'll poke around a bit more.

Yes, I don't like Clippy and its comrades. However, I will have a look. Probably I have to recover from current pains a bit more before doing so.

q.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Metaconstraint between different profiles
« Reply #3 on: May 18, 2021, 07:14:30 pm »
Ah, got it. It's possible to draw the constraint to the metaclass. So rather to UML::ActivityInitial I use the extending metaclass. Probably that would allow any profile extending it being the source. Well, I can sort of live with that. It's EA, still.

q.

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Metaconstraint between different profiles
« Reply #4 on: May 20, 2021, 07:36:39 am »
Just add them as stereotype with their fully qualified name.

...and set to abstract
The Sparx Team
[email protected]

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Metaconstraint between different profiles
« Reply #5 on: May 20, 2021, 08:42:48 am »
Hu, abstract. I never would have found that by myself. Thanks! I'll give that a try.

q.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Metaconstraint between different profiles
« Reply #6 on: May 26, 2021, 08:28:03 pm »
So i fought that windmill. It still swings its arms :-(

I added a FQN stereo to my profile and made it abstract. From this stereotype I drew a stereotyped relationship to one of my stereotypes. Once exported, the XML does not show any difference. Does Not Work.

q.

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Metaconstraint between different profiles
« Reply #7 on: May 27, 2021, 07:47:59 am »
So i fought that windmill. It still swings its arms :-(

I added a FQN stereo to my profile and made it abstract. From this stereotype I drew a stereotyped relationship to one of my stereotypes. Once exported, the XML does not show any difference. Does Not Work.

q.

The abstract external stereotype needs to be the target of whatever constraint you are creating, not the source. You are adding constraints to your own stereotypes, not the external ones.
The Sparx Team
[email protected]

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Metaconstraint between different profiles
« Reply #8 on: May 27, 2021, 06:41:36 pm »
Hmm, I'm puzzled. I assumed the arrow to give the direction as to which a connector can be created and hence the _Meaning* attributes to be pulled out. With your advice that would prove to be incorrect. But then, how would I tell which way to read forward and backward??

q.

P.S. I confirm that the above works. But now it only offers the connector the wrong way around. I want it to go from the external stereo to my own.
« Last Edit: May 27, 2021, 06:44:38 pm by qwerty »

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Metaconstraint between different profiles
« Reply #9 on: May 27, 2021, 07:15:28 pm »
Hmm, I'm puzzled. I assumed the arrow to give the direction as to which a connector can be created and hence the _Meaning* attributes to be pulled out. With your advice that would prove to be incorrect. But then, how would I tell which way to read forward and backward??

q.

P.S. I confirm that the above works. But now it only offers the connector the wrong way around. I want it to go from the external stereo to my own.
We use stereotyped relationship for that.  We create a stereotype with the FQN of the external and then use the stereotyped relationship to it from the internal one.

Paolo
« Last Edit: May 27, 2021, 09:39:34 pm by Paolo F Cantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Metaconstraint between different profiles
« Reply #10 on: May 27, 2021, 08:47:32 pm »
Seems pretty obvious :-[

Thanks!

q.