[uml] BybundleAbstractBuilder: child hierarchy (and logical grouping wrapper Component example)

HOT TIP: this content is flagged as highly recommended !

Webel module:

Package/Namespace: 

UML element type:

OOE stereotypes:

In MagicDraw UML, a Component does not "steal ownership" of a graphically contained child element if the child's SYMBOL is moved/dragged from WITHIN A DIAGRAM into the Component's SYMBOL; it only steals ownerhips if the child model element is moved into (under) the Component WITHIN THE MODEL BROWSER.

In all cases, the resulting underlying model is completely compatible with UML2 ! This feature is exploited in Webel's UML modelling recipes for introducing traceable logical groupings of elements completely "parasitically" w.r.t. the Package/Model element ownership structure.

UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML modelling domain:

This "logical" analysis wrapper Component is for graphical organisation only. It does not (in this case) change the logical grouped elements' ownerships, but it does indicate a possible future packaging.

UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML modelling domain:

The "unwrapped" diagram for the logical grouping component, showing Component Realization relationships to the logically (and otherwise graphically/visually) grouped participants.

The @Component is still (in this case) in fact contained (owned by) the Package 'flagplus', because how it was moved (dragged) as a graphical symbol into another graphical Component symbol, in MagicDraw UML ! By contrast, in MagicDraw UML, if you drag a Packageable model element in the project browser instead of in a diagraminto a Component it will change ownership ! Both of these modes yield fully compliant UML diagrams.

Notes (policies)
Visit also