Click here to Skip to main content
14,332,103 members

Understanding Association, Aggregation, and Composition

Rate this:
4.82 (125 votes)
Please Sign up or sign in to vote.
4.82 (125 votes)
15 Mar 2012CPOL
In this article we will try to understand 3 important concepts association, aggregation and composition.

Table of contents


In this article, we will try to understand three important concepts: association, aggregation, and composition.

We will also try to understand in what kind of scenarios we need them. These three concepts have really confused a lot of developers and in this article, my attempt would be to present the concepts in a simplified manner with some real world examples.

Extracting real world relationships from a requirement

The whole point of OOP is that your code replicates real world objects, thus making your code readable and maintainable. When we say real world, the real world has relationships. Let’s consider the simple requirement listed below:

  1. Manager is an employee of XYZ limited corporation.
  2. Manager uses a swipe card to enter XYZ premises.
  3. Manager has workers who work under him.
  4. Manager has the responsibility of ensuring that the project is successful.
  5. Manager's salary will be judged based on project success.

If you flesh out the above five point requirement, we can easily visualize four relationships:-

  • Inheritance
  • Aggregation
  • Association
  • Composition

Let’s understand them one by one.

Requirement 1: The IS A relationship

If you look at the first requirement (Manager is an employee of XYZ limited corporation), it’s a parent child relationship or inheritance relationship. The sentence above specifies that Manager is a type of employee, in other words we will have two classes: parent class Employee, and a child class Manager which will inherit from the Employee class.

Note: The scope of this article is only limited to aggregation, association, and composition. We will not discuss inheritance in this article as it is pretty straightforward and I am sure you can get 1000s of articles on the net which will help you in understanding it.

Requirement 2: The Using relationship: Association

Requirement 2 is an interesting requirement (Manager uses a swipe card to enter XYZ premises). In this requirement, the manager object and the swipe card object use each other but they have their own object life time. In other words, they can exist without each other. The most important point in this relationship is that there is no single owner.

Image 1

The above diagram shows how the SwipeCard class uses the Manager class and the Manager class uses the SwipeCard class. You can also see how we can create objects of the Manager class and SwipeCard class independently and they can have their own object life time.

This relationship is called the “Association” relationship.

Requirement 3: The Using relationship with Parent: Aggregation

The third requirement from our list (Manager has workers who work under him) denotes the same type of relationship like association but with a difference that one of them is an owner. So as per the requirement, the Manager object will own Worker objects.

The child Worker objects can not belong to any other object. For instance, a Worker object cannot belong to a SwipeCard object.

But… the Worker object can have its own life time which is completely disconnected from the Manager object. Looking from a different perspective, it means that if the Manager object is deleted, the Worker object does not die.

This relationship is termed as an “Aggregation” relationship.

Image 2

Requirements 4 and 5: The Death relationship: Composition

The last two requirements are actually logically one. If you read closely, the requirements are as follows:

  1. Manager has the responsibility of ensuring that the project is successful.
  2. Manager's salary will be judged based on project success.

Below is the conclusion from analyzing the above requirements:

  1. Manager and the project objects are dependent on each other.
  2. The lifetimes of both the objects are the same. In other words, the project will not be successful if the manager is not good, and the manager will not get good increments if the project has issues.

Below is how the class formation will look like. You can also see that when I go to create the project object, it needs the manager object.

Image 3

This relationship is termed as the composition relationship. In this relationship, both objects are heavily dependent on each other. In other words, if one goes for garbage collection the other also has to be garbage collected, or putting from a different perspective, the lifetime of the objects are the same. That’s why I have put in the heading “Death” relationship.

Putting things together

Below is a visual representation of how the relationships have emerged from the requirements.

Image 4

The source code

You can download the sample source code for this article.


To avoid confusion henceforth for these three terms, I have put forward a table below which will help us compare them from three angles: owner, lifetime, and child object.

OwnerNo ownerSingle ownerSingle owner
Life timeHave their own lifetimeHave their own lifetimeOwner's life time
Child objectChild objects all are independentChild objects belong to a single parentChild objects belong to a single parent

Video on Association, Aggregation, and Composition

I have also added a video in case you do not want to read this long article.

<object type="application/x-shockwave-flash" codebase=",0,0,0" width="640" height="360" data=""><param name="movie" value="" /><param name="quality" value="high" /><param name="wmode" value="transparent" />

Just a note: I have recorded around 500 videos, do have a look at my videos on .NET, OOP, SQL Server, WCF, Silver light , LINQ , VSTS, SharePoint, Design Patterns, UML and a lot more.

Thanks for reading my article.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Comments and Discussions

QuestionNice article Pin
Ganesan Senthilvel15-Mar-12 6:54
memberGanesan Senthilvel15-Mar-12 6:54 
QuestionOn Composition ... Pin
Doc Lobster15-Mar-12 6:44
memberDoc Lobster15-Mar-12 6:44 
AnswerRe: On Composition ... Pin
Shivprasad koirala15-Mar-12 21:00
memberShivprasad koirala15-Mar-12 21:00 
GeneralRe: On Composition ... Pin
Doc Lobster16-Mar-12 2:35
memberDoc Lobster16-Mar-12 2:35 
GeneralRe: On Composition ... Pin
Shivprasad koirala16-Mar-12 3:41
memberShivprasad koirala16-Mar-12 3:41 
QuestionInheritance is not PARENT CHILD relationship... Pin
Vinod Kumar Gupta29-Feb-12 2:21
memberVinod Kumar Gupta29-Feb-12 2:21 
AnswerRe: Inheritance is not PARENT CHILD relationship... Pin
Shivprasad koirala29-Feb-12 4:30
memberShivprasad koirala29-Feb-12 4:30 
GeneralMy vote of 5 Pin
Ragunathan Maniraj28-Feb-12 23:17
memberRagunathan Maniraj28-Feb-12 23:17 
great write-up shiv Wink | ;)
GeneralMy vote of 3 Pin
Lakamraju Raghuram27-Feb-12 2:54
memberLakamraju Raghuram27-Feb-12 2:54 
GeneralRe: My vote of 3 Pin
Shivprasad koirala29-Feb-12 4:29
memberShivprasad koirala29-Feb-12 4:29 
QuestionFew questions Pin
Lakamraju Raghuram26-Feb-12 17:51
memberLakamraju Raghuram26-Feb-12 17:51 
AnswerRe: Few questions Pin
Shivprasad koirala26-Feb-12 23:30
memberShivprasad koirala26-Feb-12 23:30 
GeneralRe: Few questions Pin
Lakamraju Raghuram26-Feb-12 23:53
memberLakamraju Raghuram26-Feb-12 23:53 
GeneralRe: Few questions Pin
Shivprasad koirala26-Feb-12 23:54
memberShivprasad koirala26-Feb-12 23:54 
GeneralMy vote of 5 Pin
Brij26-Feb-12 17:44
mentorBrij26-Feb-12 17:44 
GeneralMy vote of 5 Pin
Jaikrishan21-Feb-12 2:00
memberJaikrishan21-Feb-12 2:00 
GeneralMy vote of 4 Pin
kashif Atiq19-Feb-12 19:51
memberkashif Atiq19-Feb-12 19:51 
GeneralMy vote of 5 Pin
surajfrommumbai17-Feb-12 0:51
membersurajfrommumbai17-Feb-12 0:51 
GeneralMy vote of 5 Pin
saxenaabhi616-Feb-12 17:59
membersaxenaabhi616-Feb-12 17:59 
QuestionNice Post! Pin
Mahmud Hasan15-Feb-12 19:38
memberMahmud Hasan15-Feb-12 19:38 
GeneralMy vote of 5 Pin
maq_rohit15-Feb-12 2:37
professionalmaq_rohit15-Feb-12 2:37 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Posted 14 Feb 2012

Tagged as


182 bookmarked