Diagrams and Tree View

[Hugo]

Hi

I am exploring EA but noticed that when I drag a diagram elemnt from one tree node to another, the diagrams themselves do not show the change.

I now have a set of diagrams in a project that are completely inconsistent with the tree view hierarchy.

Is this bug?

[«Midnight»]

Take a look at the diagram properties dialog (F5 if you have a diagram open). Try checking either Show Additional Parents or Highlight Foreign Objects. These may clear up some of the confusion.

Remember that moving an element to another package does not in itself remove or add it to any diagrams, but merely redefines where diagrams go to obtain the element.

[Hugo]

Thanks for helpful responses.

I am a little confused, because there are ultimately two hierarchical structures representing my overall model.

One is the tree (rendered as a TreeView) the other is the diagram(s) rendered visually.

It would (I suggest) be very useful to have another TreeView (optionally displayed) that shows the hierarchy of the diagrams and their contained elements.

One benefit (there are others) is that this WOULD allow the user to move diagram elements between diagrams by dragging them around a tree.

Currently (I may be wrong) there is no straightforward way to drag objects from one diagram to another because one cannot open multiple diagrams windows, using an alternative "diagram tree view" might prove useful.

Finally having this alternative TreeView might make it easier for users to understand that the diagram view and the other hierarchical view, are quite distinct.

Thanks anyway
Hugo

[Hugo]

Before I leave for the evening, here is another related issue that confuses me.

A use case diagram contained another element a Package called PrimaryUseCases. This appears a pink box as you know, in there is a list of contained use cases in this box.

The PrimaryUseCases element is also a child (in the tree view) of the UseCaseModel node node in the tree.

Now when I dragged my use case node (AddAuthorisedUser) within the tree view (as I described earlier) I dragged it to be a child of the PrimaryUseCases node.

The effect of this is that in the UseCaseModel (the main, outer diagram) the pink box called PrimaryUseCases now contains the additional use case (or rather its name) BUT if I double click that pink box I do NOT see this newly added use case diagram because (as you said) it has not been added to tha diagram simply because I moved it within the tree.

My confusion though, is that WHY does it appear in the pink box named PrimaryUseCases (seen in the main other UseCaseModel diagram) ?

Clearly dragging this use case HAS altered the diagrammatic view, because the package PrimaryUseCases clearly shows its name, yet dbl-clicking it show a use case diagram that has no trace of it.

Would you not agree that rendering a use case package in a diagram that contains a list of use cases BUT does not contain these diagrams when expanded, is inconsistent?

Thanks
Hugh