mano_cz wrote:My intention is that CLASS B can contain {CLASS A, CLASS B, CLASS C} and will reimplement some methods from CLASS A. I have this relationship implemented in C#, but i want to know if its ok from UML point of view. Thanks for any answers.
Remember that UML is a modelling language so you have some freedom on representing your models. What you have presented is valid. However, I'm not sure if it is representing your idea of "CLASS B can contain {CLASS A, CLASS B, CLASS C}".
I interpret your class diagram in the following way:
CLASS A objects are an aggregation of CLASS B objects.CLASS B objects inherit CLASS A.CLASS C objects inherit CLASS A.
. Is this class diagram ok? Is possible that one class inherit from another and aggregate from this class too? My intention is that CLASS B can contain {CLASS A, CLASS B, CLASS C} and will reimplement some methods from CLASS A. I have this relationship implemented in C#, but i want to know if its ok from UML point of view. Thanks for any answers.
![[Avatar]](/images/avatar/22b1cd168ec628442b3d4dc00fca434b.png)
![[WWW]](/templates/default/images/icon_www.gif){kind=icon}