Diagrams invisible in matrix View

[utilisateurEA]

Hello,

I'd like to make links between some elements and diagrams. I tried to do this by using  the Matrix View but my diagrams are invisible.
Is there a solution to see them or another way to make links between elements and diagrams ?

Thank you

[Geert Bellekens]

Hi,

Diagrams actually don't exist in the UML metamodel, so it is not possible to add relations between elements and diagrams.

Maybe if you explain to us what you are trying to express we could suggest an alternate solution.

Geert

[utilisateurEA]

I would like to describe for exemple that a requirement is linked to a certain diagram.

[Geert Bellekens]

Why? What is the diagram representing, and why should the requirement be linked to that diagram?

Geert

[utilisateurEA]

Actually I could make a link between a diagram and a requirement. (by creating a new diagram and with a drag and drop (I make a link) I can see my diagram and link my reuirement to this.

BUT I would like to be able to see this in the matrix view (because in the future I could have a lot of links) but I can't display diagrams in the matrix view.

[ChrisBD]

Linking a requirement to a diagram is meaningless.

A diagram can exist without any elements on it. Being blank it doesn't describe anything and so can not meet a requirement.

You really need to link the requirement to an element on the diagram, whether a Use Case, Package, Class etc.

[utilisateurEA]

If the entire diagram is designed to follow a requirement, I won't link all the elements of the diagram, it's easier to read a link with the diagram, isn't it ?

[Paul Lotz]

Then link to the package (or element) that owns the diagram.  As stated above, it isn't meaningful to link to a diagram.  The diagram is just a view into the model.  The only semantic meaning is in the model.

[Paolo F Cantoni]

If the entire diagram is designed to follow a requirement, I won't link all the elements of the diagram, it's easier to read a link with the diagram, isn't it ?

It might be easier utilisateurEA, but unfortunately it's wrong...  As Paul says, the only semantics is in the model.  The reason those items are in the diagram is that THEY have the link to the requirement.

However, what you might be indicating is that the tediousness of having to connect each element could be alleviated by some automation.  That is, you assemble the the items that realize the requirement onto a single diagram and then run a script that says "hook all these items up to the specified requirement".

Conversely, you can use automation to say - show me on on one diagram all those items that are related to this requirement.

Paolo