Multiple instances of diagram elements

[ian]

For more complex UML diagrams, it is often useful to be able to include more than one instance of the same diagram element (eg. class, interface etc) for clarity.

This must be coupled with the ability to hide associations shown in the diagram for specific diagram elements of course => otherwise the potential confusion of associations would make this feature redundant.

A particular example where this is useful is in class diagrams including interfaces - where an interface may be implemented by several classes; and being restricted to using a single instance of the interface on the diagram can make it very unreadable.  Ironically this issue parallels (in design terms) one of the differences between using interfaces and multiple inheritance.

(From memory rose & together take this approach.)

In any case, congratulations, its a great product!  

[Jonesy]

I've actually requested this feature to be added multiple times, but have heard no news.

It's really frustrating that such a (on the surface) simple feature, isn't available - and I scratch my head sometimes as to why many others don't seem to worried about it's absence.

It would be great to see this added, and would same me some major headaches in terms of workarounds I have had to apply to my models, to keep my diagrams at least somewhat intuitive.

The ability to represent the same element, multiple times on the same diagram, simply means that my models which underpin them, can be both smaller in size, and less complex.

[Glassboy]

For more complex UML diagrams, it is often useful to be able to include more than one instance of the same diagram element (eg. class, interface etc) for clarity.

As in the "virtualise connector end" feature?

[skiwi]

In build 1224 (http://www.sparxsystems.com/products/ea/history.html)


Draw diagram elements multiple times by selecting on a connector to virtualize either end

• Allows a diagram to use a simpler layout when one element is referenced many times

• Virtual elements are drawn using the same style as the original, including when legend coloring is applied

[skiwi]

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

[qwerty]

When I see such a diagram, how can I determine that a virtualized instance is not a "real" one?

q.

[Geert Bellekens]

When I see such a diagram, how can I determine that a virtualized instance is not a "real" one?

q.

You'll know when you select it. EA selects both representations at once. Feels a bit weird. Too bad they decided to make this quirky workaround instead of simply allowing to add elements to a diagram twice.
We all know it is technically possible. If you do so with scripting EA doesn't stop you and it doesn't have any problem handling multiple instances on a diagram.

Geert

[qwerty]

A diagram is (I guess) intended for a paper printout. That's why different elements got different shapes. So to clarify: how on a printed diagram can I distinguish between real and virtualized instance?

q.

[Glassboy]

A diagram is (I guess) intended for a paper printout. That's why different elements got different shapes. So to clarify: how on a printed diagram can I distinguish between real and virtualized instance?

For one thing, it doesn't honour use Alias.  So if you are using friendly names for all of your classes, it is quite obvious it's virtualised.  It also can't be put into info view, so on diagrams using info view it stands out.

I would like to be able to colour them differently tho'.