Metamodel constraints and reversing built-in connectors

[Uffe]

Hello,


I've created two element stereotypes aaa and bbb, and a stereotyped connector ccc.
The metaclasses for aaa and bbb both have _HideUmlLinks True.
In ccc, I've specified a _MeaningBackwards as well as a _MeaningForwards.
I've added a stereotyped relationship connector from aaa to bbb, specifying ccc.

In a model, I can draw connectors in either direction between aaa and bbb elements. Drawing from bbb to aaa shows the backwards meaning in the quick linker menu, and results in a connector from aaa to bbb, as expected.

But if I replace my stereotyped relationship with a metarelationship and specify Realization, I can only draw connectors from aaa to bbb elements -- not the other way around.
Logically, the "realizes" relationship is reversible, and would in reverse be read "is realized by". But EA's metamodel prohibits this.

Why is this?

Is the UML Realization connector defined that way? Or is EA buggy?


/Uffe

[Eve]

Give it another name to use.

https://www.sparxsystems.com/enterprise_architect_user_guide/15.1/modeling/supportedattributes_2.html

_MeaningBackwards	A natural language meaning for a relationship when read from target to source. For example, a <<Flow>> relationship might have _MeaningBackwards set to 'Flows from'. Used in the Traceability window and elsewhere.
_MeaningForwards	A natural language meaning for a relationship when read from source to target. For example, a <<Flow>> relationship might have _MeaningForwards set to 'Flows to'. Used in the Traceability window and elsewhere.

[Uffe]

This doesn't seem to work.

I've created a metaclass Realization, given it the _Meaning attributes and drawn metaconstraints to it from my stereotypes, specifying roles "source" and "target". This gives no result.

There's nothing wrong with my stereotype definitions; as I said, if I specify the constraint with a metarelationship connector, it works but it isn't reversible.

This is especially problematic because quite a few of my business analysts and requirement engineers prefer drawing their realizations from the requirement. With the quick linker artifact I could accomodate that.

How do I solve this now?

I should mention that I'm now back on 15.0.1512; I was still on 15.1.1527 in my first post.