Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: Imhotep on April 26, 2022, 12:33:09 am

Title: Automatically Added Relations in Diagrams
Post by: Imhotep on April 26, 2022, 12:33:09 am

Hi all,
We model together in a team repository (PostgreSQL). We noticed that the EA automatically adds relationships to diagrams where they were not originally visible. In principle, the behavior is correct, but of course you want to keep your view as it was originally intended. In the meantime, is there a way to turn off the automatic addition?
Regards,
Bernhard

Title: Re: Automatically Added Relations in Diagrams
Post by: Geert Bellekens on April 26, 2022, 12:42:21 am

There are a few thing you can do

- When adding a relation you can choose to hide it in other diagram
- After finishing a diagram you can "freeze" it to avoid other relations to appear on it.

But, both solutions are really a kind of stopgap. What you need to figure out is why this is a problem.
Why do you want to hide certain relations from your diagrams?

In most cases this is an indicator of an underlying error in modelling (e.g. Using Activities instead of Actions, or using Classifiers instead of Instances)
You should really investigate why this is a problem.

Geert

Title: Re: Automatically Added Relations in Diagrams
Post by: Imhotep on April 26, 2022, 02:48:02 am

Thanks, Geert! To answer your question: We are currently in requirements capture. If relationships from other requirements diagrams appear here, it will disturb rather than help. Later in the requirements analysis, of course, all relationships must be taken into account, but in our current phase we would like to freeze the diagram for the time being.

Regards,
Bernhard

Title: Re: Automatically Added Relations in Diagrams
Post by: Paolo F Cantoni on May 03, 2022, 01:16:45 pm

Quote from: Imhotep on April 26, 2022, 02:48:02 am

Thanks, Geert! To answer your question: We are currently in requirements capture. If relationships from other requirements diagrams appear here, it will disturb rather than help. Later in the requirements analysis, of course, all relationships must be taken into account, but in our current phase, we would like to freeze the diagram for the time being.

Regards,
Bernhard

Hi Bernhard,

Freezing diagrams can be tricky.  Sparx has created a "Freezing mechanism" but it is only for "visible connectors".  We found that for us, we needed to "freeze" more than just connectors.  However, the built-in functionality may be enough for your needs.

There are also related issues to model evolution and diagram "snapshotting".

HTH,
Paolo