Comments on: Aggregation + Composition = Headache http://mullr.wordpress.com/2007/11/01/aggregation-composition-headache/ fixing bugs, taking names Mon, 02 Mar 2009 16:53:20 +0000 http://wordpress.com/ hourly 1 By: mullr http://mullr.wordpress.com/2007/11/01/aggregation-composition-headache/#comment-76 mullr Fri, 13 Jun 2008 22:24:24 +0000 http://mullr.wordpress.com/2007/11/01/aggregation-composition-headache/#comment-76 You make a good point that I overlooked: that it can be worth deliberately building a team vocabulary. Also, your definition of the terms is succinct and good. I concede the point. :) You make a good point that I overlooked: that it can be worth deliberately building a team vocabulary. Also, your definition of the terms is succinct and good. I concede the point. :)

]]> By: leblanc meneses http://mullr.wordpress.com/2007/11/01/aggregation-composition-headache/#comment-73 leblanc meneses Fri, 13 Jun 2008 05:04:17 +0000 http://mullr.wordpress.com/2007/11/01/aggregation-composition-headache/#comment-73 i disagree in removing them from vocabulary. It like arguing why memorize the names of the common design patterns. Terms help explain a problem in one word or a short phrase. Have I memorized how to actually model with filled or open diamond ... no i still refer to the documentation. However, i do use the terms during speech. Now that i've spent the time to understand the terms i expect my coworkers to also. It actually helps during discussion. When i hear aggregation I think: 1) polymorphism - loosely coupled 2) the client is given the object which only knows of an interface When i hear composition I think: 1) tightly coupled 2) the client can't be created without creating its internal parts. now things i don't expect my all my coworkers know is: composition can become loosely coupled if you apply factory design pattern or dependency injection. i disagree in removing them from vocabulary. It like arguing why memorize the names of the common design patterns.

Terms help explain a problem in one word or a short phrase.

Have I memorized how to actually model with filled or open diamond … no i still refer to the documentation. However, i do use the terms during speech.

Now that i’ve spent the time to understand the terms i expect my coworkers to also. It actually helps during discussion.

When i hear aggregation I think:
1) polymorphism – loosely coupled
2) the client is given the object which only knows of an interface

When i hear composition I think:
1) tightly coupled
2) the client can’t be created without creating its internal parts.

now things i don’t expect my all my coworkers know is:
composition can become loosely coupled if you apply factory design pattern or dependency injection.

]]>