Deployment question

[thomaskilian]

According to 10.3.11 of Superstructures a <<deploy>> is an alternative representation of an element nested inside a node. When I drag a component over a node EA does not generate a <<deploy>> relation but moves the component inside the node in the browser. Shall I call this a bug?

[alexander]

I have found that the inclusion of an element inside another is not sufficient. I usually make the relationship and keep both for tracing purposses.
I think this is a general policy for EA since you might want to keep this elements in another package instead of inside the 'parent element'
I give a few examples of what I mean:
+ Use Cases and Requeriments (you must make the realise relationship manually even after inserting the requirement inside the usecase)
+ Packages and Clases (although you can use this in the code generation tool because you generate by package it is not reflected in any trazable way, you can not see what clases are affected when changing a package definition except by following the browser view)
+ The same with activities, process and every compossed element.

It would be nice to have an automatic relationship stereotiped 'contains' to represent this connection... mantaining 'invisible' relationships is difficult and tends to be forgotten.