Composite Use cases and relationships

[Tree]

Hi
When modeling our system we are comfortable with the concept of breaking down a a general Use Case representing a collection of more specific Use Cases using the structured composite diagram method in EA.  The concern I have is... as the model grows, and more individuals are in the model, things sometimes get moved around.  If one individual moves a "specific" use case out from under the general use case, the project browser "implied" relationship is no longer there.  Is it true that  no underlying model relationship is  (automatically) created by EA when a composite structure is create.  There is no Composite relationship displayed in the relationship window.  
How do you recommend solving this lost relationship issue?  

[qwerty]

The best is to use EA "security" with Require User Lock to Edit. This way you need to explicitly unlock packages and the risk of accidental moving is reduced.

q.

[Helmut Ortmann]

Hi,

in general: EA maintains composite relationships. I've also encountered sometimes problems with this relationships. These issues were related to Version Controlled Packages. In my experience manageable. What EA release you are using?

You can detect lost relationships by query. I admit it's not trivial.

Personally I would create a composite structure by nested packages (package in package). If you have troubles you can easily  rebuild the lost relationship. I like structuring something by packages. Everybody understands it and is able to see it at first glance.

If you do this the EA composite diagram is just a shortcut for the convenience of the user. Lost no real problem.

Helmut