Linking elements from one model to another?

[carlclarke]

Wouldn't it be great if I could define and maintain my 'corporate' components in one model and use them in other models via a link (like linking item from one folder to a diagram in another).

I could use this for:

* Reversing frameworks, components and libraries like the .NET framework or some COM component or the MFC class libraries.

* Linking to Actors (or even use cases & requirements) defined in a central model.

* Maintaining my corporate database in one model even though it is used in many.

The list goes on. Sure there are some user considerations such as how do you resolve the side effects of the changes? However it beats having a many megabyte Base model that is 'statically linked' to every new model.

Any takers?  

[Bruno.Cossi]

Hi Carl,

I am not sure whether I understand it properly, but it sounds like something you can do already. You can create multiple Project Roots (right click on the root in the Project Browser). You could then create a root for the shared area that would contain your framework and a new root for each model that would then be able to refer to the framework one.
Does this solve it?

Bruno

[carlclarke]

Dear Bruno

I think I can see how it would work the way that you suggest - although it is not really the solution that I had in mind because this will still leave me with everything in one model. So if you come up with some wizzy component and provide a model for it; the only way I can get it in my model is to export it from yours and import it into mine. Effectively, in your solution all of my projects become root nodes in one big model (project, .eap file etc). However your suggestion is - today - the closest that I can get to what I am looking for.

Another modelling tool, (not a great tool in too many ways, but good in a few others such as component management and an easy multiuser environment) called SELECT Component Architect, allows you to link classes from one model into another, giving you a read only link to the class. If you modify the class in the source model then the changes are reflected in the destination model.

Thanks for your solution Bruno. I would still love to see EA do it better if it is possible.