Design Forum - Composition and aggregation implementation stratagy

Articles |
News |
Weblogs |
Books |
Forums

Artima Forums | Articles | Weblogs | Java Answers | News

Sponsored Link •

Design Forum
Composition and aggregation implementation stratagy

4 replies on 1 page. Most recent reply: Jun 1, 2006 7:52 PM by Erik Engbrecht

Welcome Guest
Sign In

Back to Topic List

Reply to this Topic

Search Forum

Threaded View


Previous Topic		Next Topic

Flat View: This topic has 4 replies on 1 page

Pradeepkumar Patil

Posts: 1
Nickname: sunrise
Registered: Mar, 2006

Composition and aggregation implementation stratagy

Posted: Mar 22, 2006 4:53 AM

If composition is the tight relation between whole and part and aggregation is loose relationship betwen them then what strategy should one apply in designing UMl for effective and efficient implementation?. how can we distinguish them programatically.

Vijay Nathani

Posts: 29
Nickname: vijaynath
Registered: Jan, 2006

Re: Composition and aggregation implementation stratagy

Posted: May 3, 2006 1:30 AM

Programmatically there is no difference between composition, aggregation and association in languages like Java, where the garbage collection is automatic.

Vijay Nathani,
www.geocities.com/vijay_nathani

Shashank D. Jha

Posts: 68
Nickname: shashankd
Registered: May, 2004

Re: Composition and aggregation implementation stratagy

Posted: May 24, 2006 12:29 AM

> If composition is the tight relation between whole and
> part and aggregation is loose relationship betwen them
> then what strategy should one apply in designing UMl for
> effective and efficient implementation?.

If you are using UML for OOA/D, use the relation that exists in the interacting classes/objects. Always remember OOA/D is for modeling real world entities.

>how can we distinguish them programatically.
So for sure there is difference in code as well. In case of composition, the creation and destruction is responsibility of "whole". And the reference of "part" is not passed to interating entities. Example, "floor" (part) of a room (whole) is never shared with another room.

But a wall of a room is shared. So difference in code right?

---------------
Shashank D. Jha
iCMG
e-mail shashank@icmgworld.com

Shashank D. Jha

Posts: 68
Nickname: shashankd
Registered: May, 2004

Re: Composition and aggregation implementation stratagy

Posted: May 24, 2006 12:54 AM

Erik Engbrecht

Posts: 210
Nickname: eengbrec
Registered: Apr, 2006

Re: Composition and aggregation implementation stratagy

Posted: Jun 1, 2006 7:52 PM

> Programmatically there is no difference between
> composition, aggregation and association in languages like
> Java, where the garbage collection is automatic.
>
> Vijay Nathani,
> www.geocities.com/vijay_nathani

Not exactly. That's true for immutable objects (like String), but composition is similar to ownership, so it can be very important that other objects aren't modifying an object that is owned by another.

Association, aggregation, and composition may all be directly coded using fields (1..1 and 0..1) or collections (m..n), but the way they should be treated elsewhere in code very differently.

Flat View: This topic has 4 replies on 1 page

Previous Topic

Next Topic


	Web Artima.com