|
|
|
|
Re: composite aggregation [message #628231 is a reply to message #628230] |
Thu, 11 February 2010 11:56 |
Carsten Reckord Messages: 139 Registered: July 2009 |
Senior Member |
|
|
Hi Hector, Hi Vlad,
Vlad: I think what Hector is confused about is the term 'aggregate end' being used with regard to the Property (in your example class9) vs.
the (perhaps more intuitive) notion of the "aggregate class" (Class10).
Hector: I think this is a bit of a wording problem in the Superstructure. I agree that the notion of class B being the "aggregate end" is
more intuitive when looking at the diagram, but the Superstructure is explainging this in terms of the Properties making up the association
ends. So, in your example the 'target' property is specified as aggregation, making it the aggregating end of the association and 'source'
the aggregate end. Therefore, in terms of the involved properties, the diamond really is shown at the aggregate end (since 'source' is shown
next to class 'A', where the diamond is).
HTH,
Carsten
On 11.02.2010 12:29, Vlad Varnica wrote:
> Hi Hector,
>
> I have created a small video on the association :d
> This video explains how should be saved a standard association, an aggregation & composition in the UML Editor, the property view and in the model (e.g. the xmi metamodel).
> It also explain that the full association information is contained in the association end attribut and not in the association itself.
>
> See the 2minutes video at:
> Flash demo: http://www.download-omondo.com/AggregationAndComposition.swf
> exe file for windows: http://www.download-omondo.com/AggregationAndComposition.exe
> hqx file for Mac: http://www.download-omondo.com/AggregationAndComposition.hqx
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03565 seconds