can any one help me to understand the difference between composition and aggregation relationship , and if any one know any site that explain the UML class diagrams for all relationships ... that would be great. thanks a lot.
+1
A:
Composition and aggregation have to do with cascading delete behavior.
Do the child objects have a life of their own beyond the parent? If yes, you need aggregation.
If the parent is deleted, do the children need to be deleted as well? If yes, you need composition.
So let's say you have a model where there's a School class, a Building class, and a Student class. A School has a one-to-many relationship with Building and a one-to-many relationship with Student.
The School-to-Building relationship is an example of composition. If you close the School, you might decide to bulldoze the buildings.
The School-to-Student relationship is aggregation. If you close the school, you certainly won't decide to murder all the Students.
You can read what Uncle Bob Martin has to say about it here.
duffymo
2010-10-31 18:55:12
i didn't get it
Ruba
2010-10-31 18:59:44
Give up now, then.
duffymo
2010-10-31 19:07:43
don't answer me if you want to make fun of me
Ruba
2010-10-31 19:13:45
I'm not making fun of you - I gave you a plain English answer.
duffymo
2010-10-31 19:17:02
duffymo, you messed up both definitions, composition is the relation where the lifetime of the parts is controlled by the parent.
jdehaan
2010-10-31 19:24:45
Just reverse them.
duffymo
2010-10-31 19:59:41
A:
The difference lies in the lifetime of the parts of an object.
- If the parts can live independently from the parent, then you have an aggregation.
- If the parts's lifetime are controlled by the parent it is a composition.
The composition can be seen as a special case of an aggregation.
jdehaan
2010-10-31 19:23:32
A:
Both aggregation and composition represent "has a" relationships. The difference between the two is that composition refers to exclusive ownership. For instance, a transaction "has a" transaction ID number, and that transaction is the only transaction that has that transaction ID number, the ID number is exclusive to the transaction. A transaction also "has a" transaction date, but many transaction might also have that same transaction date. Since the transaction date can be shared among multiple transactions it is not exclusive.
When you are drawing these two relationship types on a UML class diagram a composition relationship would be represented with a filled in diamond where a aggregation relationship would be represented by a diamond which is not filled in.
The book Introduction to Java Programming covers this subject in great detail.
typoknig
2010-10-31 19:25:01