connecting different projects

[sergeysps]

Hi there,

here the situation.
I'm supposed to have to different projects:
A) That is a FrameWork which provides a set of Components. Those can be used by other Applications.
B) Is an application which uses the Framwork and has also some components on its own as well.

So I would like to have some sort of Component Diagram in B which references the framework A in it. It would be also nice if I could click on this reference and so that framework A opens in a new window or somthing.
I know there is possibility of imporint/exporitng packages but if for example the framework is used in a large amount of other applications and then it changes => a lot of updating work

So to summarize: I m searching for the possibilty of referencing other projects within a diagram, so i dont have "copy&paste" the parts I need.

//Sergey

[qwerty]

Maybe my story might help.

q.

[sergeysps]

Hej,

thanks for your answer but as far as I can see your problem was that different people were working on the same project at the same time.
I would just like to be able to make a link between components from project A to project B (C,D,E), so that if the component in project A changes, i dont have to update B,C,D,E manually.

//Sergey

[bernardm]

Maybe a basic question here but what about putting all your projects in the same repo?

[sergeysps]

I dont use any repos or anything. The both projects are on my hard drive. I just dont find any possibility if i am for example within one project in the component diagram how i could reference a component from another project. The project browser always shows only the current project.
The only possibilty i could think of is to put all the systems in the same project and separate them by creating different models within the project.

//S

[bernardm]

That's exactly what I meant. What we do is the following : we put all projects in the same repository (the same eap or db) when there is a strong coupling between them. On the other hand, we put a new project in a separate repository when it is not or loose coupled from the others.

[sergeysps]

Ah ok,

how do i put two different projects into one .eap file? Normally, when i create a new project, an eap file is created. But I cant create a second project, with the same name, because then EA complaining that this file already exists. The only thing where i succeeded is to have several models within one project.
Sorry for the not so smart question, but im new to EA, so Im still struggeling a bit with adminstrations of my models/projects and didnt really start modelling yet

//S

[bernardm]

I think this is a matter of perception. You can have one single .eap file whose root packages are considered as "projects". Here is an excerpt the typical .eap package structure we promote in our company:
=> my business domain.eap
        + project 1 package
              + domain model package
              + use case model package
              + ...
        + project 2 package
              + ...
        + project 3 package
              + ...

[sergeysps]

Hej,

I cant add a package to the root node for some reason. The only things I can add are views and other models.
Another question: can I export parts of my project somehow to a new .eap or do i ve to work around by creating a new project and importing the xml file in it?

//S

[bernardm]

Oups, sorry by root package I meant root node (root model).

[Geert Bellekens]

Another question: can I export parts of my project somehow to a new .eap or do i ve to work around by creating a new project and importing the xml file in it?

//S

Only by XMI export/import.

Another option to share a package between models is to use version control.
We have a shared model that connected to TFS, and which is loaded in our two "project" repositories.

Geert