MDG Quicklinker: problem with the direction when selecting Composes

[Guillaume]

Hello,

I have an MDG with stereotyped ArchiMate elements. I use the "stereotyped relationship" dependencies to define the Quicklinker rules.
It works well except for the following:
- I have a "SampleA" stereotype
- I want to create Composition links from a SampleA stereotyped element to another one -> this is defined via a  "stereotyped relationship" self-dependency with stereotype tagged value = "ArchiMate3::ArchiMate_Composition"
Testing the MDG, the "Composed of" quicklinker works as expected. However when I choose "Composes", it creates the composition with Direction = Source - Destination (expected result: Unspecified).

Is there a workaround? (I'm using the latest 14.1 build)

Thanks

[Paolo F Cantoni]

Hi Guillaume,

May I ask why you expected the direction property to have the result "Unspecified"?  To my understanding, Composition is always a directed relationship.  Notwithstanding you are defining a reflexive (but NOT symmetrical) relationship, one SampleA is the holonym (whole) and the other is the meronym (part).  IIRC the default direction is "Source -> Destination".

Paolo

[qwerty]

Navigability is something different (you'd need to foster UML 2.5 for details). It's an association and the diamond specifies where the aggregation goes (and only to one side).

q.

[Guillaume]

Hi,

My aim is to have consistent links i.e. without any arrow at the end of the composition link (on the part's side).

I tested it with standard Archimate 3 Application components and I got the same issue so it looks like a small bug with the Archimate 3 MDG.
See the following diagram:


I'll submit it to Sparx.

Thanks

[Guillaume]

This is still an active issue in the current build i.e. if you define a stereotyped connector with a direction = unspecified e.g. an association, composition...
Creating the association with the quicklinker with the forwards link (src -> target) it works.
If you select the opposite/backwards meaning (e.g. associated from, compose to whole), the arrow end is available and needs to be removed.
I also tried to set the navigability to unspecified ou not navigable in the stereotype definition both ways, but the result is the same.

[Geert Bellekens]

I can confirm that this is indeed a bug.

I noticed it as well (though I didn't actually report it yet)

Geert