UML Profile: Connector from Element to Connector

[Geert Bellekens]

I'm making a UML profile and I would like to define a new connectortype that can be used from an Element to another Element, but also between a Connector and an Element.

Sort of like the connector between an AssociationClass and the Association, or between a constraint and a connector.
Does anyone now how to do that?
The connector steretoype I defined only works between Elements.

Thanks

Geert

[Uffe]

From what I remember from my intrepid expedition into the darkest heart of association classes, the link you see between the class and the connector is not itself a connector at all. Rather, it is displayed as a consequence of some semi-magic column in t_object and/or t_xref. In other words, I don't think that particular EA feature is extensible.

OTOH, based on the warning message you get when deleting an association class ("Do you wish to delete the remaining relationship connector"), maybe possibly you might have some luck with the "relationship" abstract metatype?

HTH,


/Uffe

[Eve]

Uffe, an association class is stored as both a connector and an object.

Geert, I suspect the only way you can achieve what you want is to extend an association class. It's pretty unique within EA.

[Paolo F Cantoni]

Geert,

Given the current architecture of EA, you CAN'T define arcs between arcs or between vertices and arcs.  The linkages you see (such as between Notes and arcs and Association Classes and arcs) are rendered using technologies other than arcs .
They utilise PDATA fields to reference the target of the link and then render them on the diagram.

There are some games you can play (such as linking multiple arcs to an Association Class (not using the UI) and things of that ilk, but otherwise you're stuck.

When I've needed to create relationships between arcs, I've used a stereotyped intervening vertices (such as a constraint).

It would be REALLY neat if Sparx created a mechanism to allow an Association Class to be a special case of the N-Ary relation object and the Association between any two Classes in the N-Ary relation to be projections of that association.

BTW, what is the semantics of this relationship between both vertices and vertices and arcs?  I'm intrigued!

Paolo

[Geert Bellekens]

Uffe, an association class is stored as both a connector and an object.

Geert, I suspect the only way you can achieve what you want is to extend an association class. It's pretty unique within EA.

I tried to extend the association class connector, but that didn't work.
Too bad, I guess I'l have to live with the limitation.

Geert

[Geert Bellekens]

BTW, what is the semantics of this relationship between both vertices and vertices and arcs?  I'm intrigued!

I'm making a UML profile for BAM (Business Activity Monitoring) based on this paper from a German university.
In the example they show a measuring point attached to a BPMN flow, which makes sense in a way.
But I'm afraid I'll have to do without.

Geert

[Paolo F Cantoni]

BTW, what is the semantics of this relationship between both vertices and vertices and arcs?  I'm intrigued!

I'm making a UML profile for BAM (Business Activity Monitoring) based on this paper from a German university.
In the example they show a measuring point attached to a BPMN flow, which makes sense in a way.
But I'm afraid I'll have to do without.

Geert

If you're talking about that Duration Icon, I'd use a Note as the base vertex type, stereotyped and shape scripted to create the Clock.  That way you can use note-links to other vertices and attached notes to arcs.  the metatype would still be Duration.

HTH,
Paolo

[Geert Bellekens]

I've now used Action as the metatype for most of the stereotypes. But I can try to change that to Note.
Have you extending Notes before? I'm just a bit afraid that there are other unwanted consequences since notes are a bit special.

Geert

[Paolo F Cantoni]

I've now used Action as the metatype for most of the stereotypes. But I can try to change that to Note.
Have you extending Notes before? I'm just a bit afraid that there are other unwanted consequences since notes are a bit special.

Geert

I've really only done it it the Stereotypes dialogs in the repository itself.  I haven't extended NOTE in an MDG - yet (I will be shortly).  

In any event, I'd recommend starting with that (direct stereotyping) - so that everything renders (and behaves) correctly, then I'd create the MDG element.  I normally use that process when doing stuff in MDGs - since as we know we get silent failures.  You then have something to "compare and contrast".

But I'm sure I'm "Teaching Grandma" (to suck eggs).

Paolo

[Paolo F Cantoni]

I've now used Action as the metatype for most of the stereotypes. But I can try to change that to Note.
Have you extending Notes before? I'm just a bit afraid that there are other unwanted consequences since notes are a bit special.

Geert

I've really only done it it the Stereotypes dialogs in the repository itself.  I haven't extended NOTE in an MDG - yet (I will be shortly).  

In any event, I'd recommend starting with that (direct stereotyping) - so that everything renders (and behaves) correctly, then I'd create the MDG element.  I normally use that process when doing stuff in MDGs - since, as we know, we get silent failures.  :-?  You then have something to "compare and contrast".

But I'm sure I'm "Teaching Grandma" (to suck eggs).

Paolo

[qwerty]

Top notch. Now you plainly cite yourself :-?

There is a Modify button.

q.

[Geert Bellekens]

I've now used Action as the metatype for most of the stereotypes. But I can try to change that to Note.
Have you extending Notes before? I'm just a bit afraid that there are other unwanted consequences since notes are a bit special.

Geert

I've really only done it it the Stereotypes dialogs in the repository itself.  I haven't extended NOTE in an MDG - yet (I will be shortly).  

In any event, I'd recommend starting with that (direct stereotyping) - so that everything renders (and behaves) correctly, then I'd create the MDG element.  I normally use that process when doing stuff in MDGs - since as we know we get silent failures.  You then have something to "compare and contrast".

But I'm sure I'm "Teaching Grandma" (to suck eggs).

Paolo

Another useful strategy is to only do small increments and test frequently.  So when it breaks then you are sure its because of the last modification.

Geert