Different representations (notations) for one (1) Diagram Element

[Viking]

Well, there is a way with so-called virtualized connectors (search the help). That will create an element stub more than once in a diagram. Personally I would not use them since it introduces more issues than it might solve. But that's my POV.

q.

P.S. The help only links to this: http://sparxsystems.com/enterprise_architect_user_guide/12.1/automation_and_scripting/diagram2.html Look for virtualized below in that

Many thanks. To be honest, I do not understand anything 

[qwerty]

There is a way to do that manually, but the help does not find anything (Roy?). Somewhere this is described - most likely. Basically, you create connector which ends in a stub of an element which is already present in the diagram. So this can appear multiple times. I have tried that once but immediately forgot about it (since, as I already mentioned, I think it's simply rubbish). So try to find "virtual" in the docs or read the diagramming pages to find the relevant information (if you like; good luck).

q.

[PeterHeintz]

Maybe having different sharps of the same thing is what you are looking for, but keep in mind that this is only some kind of shape.

For instance you can regard yourself in a model as an Actor, a Class, an Object, a Component,… an maybe it is possible to make you look like an Actor, a Class, an Object, a Component depending of in what diagram you appear, but you have to decide in the model what you are only once (either Actor or Class, ...) if you want to be there only once.

[qwerty]

I think the way via stereotyped diagrams is pretty ok. Since you have stereotyped them they actually work like a photo filter and put things in different light or perspective. This way you can look onto an element from top, left or right. So far I had happily used just one picture of an element whilst putting it in different contexts and that was just right. But I can imagine that there's a use case for what Viking is asking for.

q.

[Glassboy]

There is no concept in UML to mix languages on element level, you only can extend something, quiet similar to that, there is no notation defined (AFAIK) to mix English, Chinese and Bhotia in one sentence.

It's called a Pidgin https://en.wikipedia.org/wiki/Pidgin.  Pidgins turn into Creoles, and Creoles form the basis of fully formed languages.

Or its called loan words.  Native English speakers use 10s to 100s of words a day that aren't English.

[Paolo F Cantoni]

Hi Viking,

You've hit the nail on the head...  There is one item and many viewpoints.  Some viewpoints require different representations of the same object for whatever reason - it's not directly a question of language, although it's a common use case.  It's basically a tooling issue not a language issue.

Sparx EA provides a solution (although somewhat embryonic at this time - V13 imminent). 

We have the same problem.  Unfortunately, you have to do a lot of work yourself.  We have elected to do this because of the overall benefits.

Firstly, you have to create shapescripts of your own for these elements (for example, take both the ArchiMate and BPMN scripts and combine into one). 

Then if you purely want to use the language of the viewpoint (diagram) only, then you make the shapescript respond appropriately (to diagram.mdgtype).

Else, you can now create diagram properties that allow the shapescript to respond differently, depending upon how you want it to.  See "Query Methods" help page and the BPMN Annotation shapescript for how to use user-selected properties.

We've taken the latter approach since we aren't directly language dependent - we've effectively built a common modelling environment appropriating ideas from various standards and combining them.

HTH,
Paolo

[RoyC]

If you are still looking for the "Virtualized Connectors", they are documented here:

http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/virtual_routing.html

The object is actually a virtualized connector end, which is what they are documented as.

[Paolo F Cantoni]

If you are still looking for the "Virtualized Connectors", they are documented here:

http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/virtual_routing.html

The object is actually a virtualized connector end, which is what they are documented as.

And to reinforce what Roy is saying they aren't simple diagram objects...

But I don't think that's what the OP was asking for.

Paolo

[qwerty]

@Roy: When searching "virtualized" in the help you are led to the automation site only. Can you correct that, please?

q.

[Viking]

Well, there is a way with so-called virtualized connectors (search the help). That will create an element stub more than once in a diagram. Personally I would not use them since it introduces more issues than it might solve. But that's my POV. q.
P.S. The help only links to this: http://sparxsystems.com/enterprise_architect_user_guide/12.1/automation_and_scripting/diagram2.html Look for virtualized below in that

Very helpful. Thank you very much.