Problem using custom tag of type association

[dstueven]

Hi all,
I have a quite complex model with different levels, one being a business capability layer and one being a logical product layer. On the business capability layer I have connected different capabilities using associations to represented an integration that needs to be built between them.
I have also connected business capabilities to logical products to tell which capability get's implemented by which product.
Finally I have also connected logical products to each other using associations with a self created stereotype to represent integrations that need to be built between products.
Now I would like to connect integration links on the capability level with integration links on the product level to show which integration on capability level gets realized by which integration on product level.
I intended to do this sing a self created tag of the RefGUIDList type. Unfortunately when I assign this tag and use it, I can't select any of my existing associations, as they do not get listed in the upcoming project browser.
I used the following definition in the detail window of the Tagged value type:

Type=RefGUIDList;
Values=Association;

Maybe the reason is because also the normal project browser never shows the association existing in the model? Is there any way to get a selection window that will list existing associations?

Thanks for any help!

[Geert Bellekens]

Is there any way to get a selection window that will list existing associations?

No, unless you set the tagged value to AddinBroadcast, and you handle the association selection in your addin.

Geert

[Paolo F Cantoni]

The problem may also be related to the fact that there are TWO "Association" types in EA.  The relationship (arc) and the n-ary Association element (vertex).

I think if you added one of these "Association" vertices to the project, it would turn up on your list.

Also, note that when you use a RefGUID, EA tries to locate the element and return its name.  Since your association relationship is unlikely to have a name, it most likely will return "blank".

Geert's solution is the only viable one if you intend to go via the RefGUID route.  However, why not just link one relationship to the other?  We do that increasingly.

Paolo

[dstueven]

Hi Paolo,
you wrote "However, why not just link one relationship to the other?  We do that increasingly.".
That sounds good, but how do I do that? My associations do not show any link option - or at least I didn't find anything like that...
Would be great if you could point me where to find it.

Thanks!

Dirk

[Paolo F Cantoni]

Hi Paolo,
you wrote "However, why not just link one relationship to the other?  We do that increasingly.".
That sounds good, but how do I do that? My associations do not show any link option - or at least I didn't find anything like that...
Would be great if you could point me where to find it.

Thanks!

Dirk

Hi Dirk,

It's not clear if you are asking about manual or automated creation of the relationship.  But since in order to get the automation right, you'll need a worked manual example, I'll show you how to do it manually, and then you can investigate what the result is in the DB.

So, to create a relationship between a relationship and another relationship, you need to:
1) Select the origin relationship
2) In the "centre" of the rendered line, you should find a QuickLinker widget
3) Grab the widget and drag it to the other relationship (or even a shape) when you release, you'll get the QuickLinker options to select which relationship you want to create.

That's it!

You'll find that the new relationship is drawn from the "centre" to the "centre" of the other line.  "Centre" is emphasised because depending upon the line style and the underlying shape script, the "centre" may not be where you are expecting it.

Where one relationship joins the other relationship, EA creates a misnamed "Proxy Connector".  It is misnamed because it is actually a shape (and therefore in t_object) that is a Connector Proxy.  If you are connecting two relationships with another, you get two connector proxies - one at each end.  These can now be selected and moved (to some extent) along the relationship they are attached to.

HTH,
Paolo