Aggregation (object-oriented programming) - Revision history

M4gnum0n: R section

2011-03-23T00:49:44Z

R section

← Previous revision		Revision as of 00:49, 23 March 2011
Line 1:		Line 1:
	#REDIRECT [[object composition#Aggregation]]		#REDIRECT [[object composition#Aggregation]] {{R section}}

201.213.37.39: Redirect to anchor

2007-08-07T01:03:47Z

Redirect to anchor

← Previous revision		Revision as of 01:03, 7 August 2007
Line 1:		Line 1:
	#REDIRECT [[object composition]]		#REDIRECT [[object composition#Aggregation]]

TakuyaMurata: #REDIRECT object composition

2005-06-18T22:05:07Z

#REDIRECT object composition

← Previous revision		Revision as of 22:05, 18 June 2005
Line 1:		Line 1:
	#REDIRECT [[composition ~~(computer science)~~]]		#REDIRECT [[object composition]]

TakuyaMurata: merging into composition (computer science)

2005-06-18T22:02:20Z

merging into composition (computer science)

← Previous revision		Revision as of 22:02, 18 June 2005
Line 1:		Line 1:
	~~{{merge\|~~composition (computer science)\|]]		#REDIRECT [[composition (computer science)]]

	{{cleanup-verify}}

	'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.

	Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. If the university closes, the departments will no longer exist, but the professors in those departments will. Therefore, a University can be seen as a composition of departments, whereas departments have an aggregation of professors.

	Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:

	<pre>
	class Professor;

	class Department
	{
	...
	private:
	Professor faculty[20];
	...
	};
	</pre>

	In aggregation, the object may only contain a reference or pointer to the object:

	<pre>
	class Professor;

	class Committee
	{
	...
	private:
	Professor* members[5];
	...
	};
	</pre>

	{{Compu-stub}}
	[[Category:Object-oriented programming]]

Gadfium: Reverted edits by Principalityofgalore to last version by TakuyaMurata

2005-05-28T09:23:02Z

Reverted edits by Principalityofgalore to last version by TakuyaMurata

← Previous revision		Revision as of 09:23, 28 May 2005
Line 1:		Line 1:
			{{merge\|composition (computer science)\|]]
	PRINCIPALITY OF GALORE!!!

			{{cleanup-verify}}

			'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.

			Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. If the university closes, the departments will no longer exist, but the professors in those departments will. Therefore, a University can be seen as a composition of departments, whereas departments have an aggregation of professors.

			Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:

			<pre>
			class Professor;

			class Department
			{
			...
			private:
			Professor faculty[20];
			...
			};
			</pre>

			In aggregation, the object may only contain a reference or pointer to the object:

			<pre>
			class Professor;

			class Committee
			{
			...
			private:
			Professor* members[5];
			...
			};
			</pre>

			{{Compu-stub}}
			[[Category:Object-oriented programming]]

Principalityofgalore at 08:18, 28 May 2005

2005-05-28T08:18:40Z

← Previous revision		Revision as of 08:18, 28 May 2005
Line 1:		Line 1:
			PRINCIPALITY OF GALORE!!!
	{{merge\|composition (computer science)\|]]

	{{cleanup-verify}}

	'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.

	Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. If the university closes, the departments will no longer exist, but the professors in those departments will. Therefore, a University can be seen as a composition of departments, whereas departments have an aggregation of professors.

	Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:

	<pre>
	class Professor;

	class Department
	{
	...
	private:
	Professor faculty[20];
	...
	};
	</pre>

	In aggregation, the object may only contain a reference or pointer to the object:

	<pre>
	class Professor;

	class Committee
	{
	...
	private:
	Professor* members[5];
	...
	};
	</pre>

	{{Compu-stub}}
	[[Category:Object-oriented programming]]

TakuyaMurata: {{merge|composition (computer science)|]]

2005-05-21T03:39:12Z

{{merge|composition (computer science)|]]

← Previous revision		Revision as of 03:39, 21 May 2005
Line 1:		Line 1:
			{{merge\|composition (computer science)\|]]

	{{cleanup-verify}}		{{cleanup-verify}}

217.206.30.28 at 06:49, 16 May 2005

2005-05-16T06:49:55Z

← Previous revision		Revision as of 06:49, 16 May 2005
Line 3:		Line 3:
	'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.		'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.

	Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. If the university closes the departments will no longer exist, but the professors in those departments will. Therefore, a University can be seen as a composition of departments, whereas departments have an aggregation of professors.		Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. If the university closes, the departments will no longer exist, but the professors in those departments will. Therefore, a University can be seen as a composition of departments, whereas departments have an aggregation of professors.

	Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:		Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:

217.206.30.28 at 06:49, 16 May 2005

2005-05-16T06:49:37Z

← Previous revision		Revision as of 06:49, 16 May 2005
Line 3:		Line 3:
	'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.		'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.

	Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. ~~These relationships can be modelled as composition since if~~ the university ~~disbands~~ the departments ~~certainly~~ will, ~~and~~ if a ~~department disbands,~~ the professors in ~~that~~ ~~department~~ will ~~no longer have jobs at the university (and no longer exist in this scope)~~. ~~On the other hand~~, ~~suppose several professors are on~~ a ~~committee.~~ ~~This~~ ~~relationship~~ ~~is best modelled~~ as ~~an aggregation—but not~~ a composition~~—since~~ ~~the~~ ~~disbanding~~ of ~~the~~ ~~committee~~ ~~would~~ ~~not~~ ~~mean the~~ professors ~~lost their jobs~~.		Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. If the university closes the departments will no longer exist, but the professors in those departments will. Therefore, a University can be seen as a composition of departments, whereas departments have an aggregation of professors.

	Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:		Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:

66.51.82.153: The terms composition and aggregation should be switched. Composition causes the contained objects to be destroyed if the container is destroyed. In aggregation, the objects may not be destroyed.

2005-04-06T13:16:48Z

The terms composition and aggregation should be switched. Composition causes the contained objects to be destroyed if the container is destroyed. In aggregation, the objects may not be destroyed.

← Previous revision		Revision as of 13:16, 6 April 2005
Line 3:		Line 3:
	'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.		'''Aggregation''' is a form of [[Composition (computer science)\|composition]] where one looks at the system as a whole rather than as parts. It is also based on [[has-a]] [[relationship]] and is implemented by creating [[Object (computer science)\|objects]] of other [[Class (computer science)\|classes]] inside the class. An example will be a [[Automobile\|car]] class which is an aggregation of different classes like [[wheel]], [[engine]], [[Car body\|body]] etc.

	~~Aggregation~~ differs from ~~composition~~ in that ~~aggregation~~ indicates ownership; ~~that~~ is, in ~~aggregation~~, when the containing object is destroyed, so are the contained objects. In ~~composition~~, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. These relationships can be modelled as ~~aggregation~~ since if the university disbands the departments certainly will, and if a department disbands, the professors in that department will no longer have jobs at the university (and no longer exist in this scope). On the other hand, suppose several professors are on a committee. This relationship is best modelled as a ~~composition~~—but not an ~~aggregation~~—since the disbanding of the committee would not mean the professors lost their jobs.		Composition differs from aggregation in that composition indicates ownership. That is, in composition, when the containing object is destroyed, so are the contained objects. In aggregation, this is not necessarily true. For example, a [[university]] consists of various departments (e.g., [[chemistry]]), and each department contains a number of professors. These relationships can be modelled as composition since if the university disbands the departments certainly will, and if a department disbands, the professors in that department will no longer have jobs at the university (and no longer exist in this scope). On the other hand, suppose several professors are on a committee. This relationship is best modelled as an aggregation—but not a composition—since the disbanding of the committee would not mean the professors lost their jobs.

	~~Aggregation~~ is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:		Composition is usually implemented such that an object contains another object. For example, in [[C plus plus\|C++]]:

	<pre>		<pre>
Line 19:		Line 19:
	</pre>		</pre>

	In ~~composition~~, the object may only contain a reference or pointer to the object:		In aggregation, the object may only contain a reference or pointer to the object:

	<pre>		<pre>