Home » Modeling » UML2 Tools » inner (nested) classes
| |
Re: inner (nested) classes [message #473499 is a reply to message #473345] |
Fri, 28 March 2008 15:12 |
james bruck Messages: 1724 Registered: July 2009 |
Senior Member |
|
|
Hi Tatiana, Marius,
If I'm not mistaken, the composite aggregation is different from a nested
classifier. A nested classifier does not necessarily have to be part of
the internal structure of its owning parent. Tatiana, in your example,
MenuBar would own a property "dst" of type Button, whereas if one just
showed that Button was a nested classifier then no such property would exist
(necessarily).
Please correct me if I'm wrong.
Cheers,
- James.
"Tatiana Fesenko" <tatiana.fesenko@borland.com> wrote in message
news:6785c52638e68ca47533a2633ab@news.eclipse.org...
Hello Marius,
The owned class is always shown as a label inside 'classes' compartment. But
you can use Composite Aggregation link. It handles required to you semantics
of whole/part relationship. The picture how your example with MenuBar/Button
will look like if using Composite Aggregation is in the file attached.
To create Composite Aggregation use Links/Association/Composite Aggregation
palette entry.
Best wishes,
Tatiana.
> Hi,
>
> When i nest a class inside another class (i.e. to get an inner class)
> it shows up as an entry in the "class" compartment in the associated
> diagram (see
> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_is.png>). Is
> there any way to have the uml2 visualisation as shown in
> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_should .png>?
>
> cheers,
> marius
|
|
|
Re: inner (nested) classes [message #473513 is a reply to message #473499] |
Thu, 03 April 2008 08:34 |
Tatiana Fesenko Messages: 530 Registered: July 2009 |
Senior Member |
|
|
Thank you, James, you are always correct =)
Yes, composite aggregation semantics is close to the semantics of owned property,
not to the semantics of nested classifier.
However, the only representation for the nested classifier I've found in
the UML specification is a label inside parent classifier. Please correct
me if I am wrong.
Marius,
your second picture ( http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_should .png)
looks very like as Composite or Shared Aggregation, which hangles a bit different
from nested classifier semantics.
For more information reference corresponding sections of UML specification.
Cheers,
Tatiana.
> Hi Tatiana, Marius,
>
> If I'm not mistaken, the composite aggregation is different from a
> nested classifier. A nested classifier does not necessarily have to
> be part of the internal structure of its owning parent. Tatiana, in
> your example, MenuBar would own a property "dst" of type Button,
> whereas if one just showed that Button was a nested classifier then no
> such property would exist (necessarily).
>
> Please correct me if I'm wrong.
>
> Cheers,
> - James.
> "Tatiana Fesenko" <tatiana.fesenko@borland.com> wrote in message
> news:6785c52638e68ca47533a2633ab@news.eclipse.org...
> Hello Marius,
> The owned class is always shown as a label inside 'classes'
> compartment. But you can use Composite Aggregation link. It handles
> required to you semantics of whole/part relationship. The picture how
> your example with MenuBar/Button will look like if using Composite
> Aggregation is in the file attached.
>
> To create Composite Aggregation use Links/Association/Composite
> Aggregation palette entry.
>
> Best wishes,
> Tatiana.
>> Hi,
>>
>> When i nest a class inside another class (i.e. to get an inner class)
>> it shows up as an entry in the "class" compartment in the associated
>> diagram (see
>> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_is.png>). Is
>> there any way to have the uml2 visualisation as shown in
>> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_should .png>?
>>
>> cheers,
>> marius
|
|
| |
Re: inner (nested) classes [message #618650 is a reply to message #473345] |
Fri, 28 March 2008 15:12 |
james bruck Messages: 1724 Registered: July 2009 |
Senior Member |
|
|
Hi Tatiana, Marius,
If I'm not mistaken, the composite aggregation is different from a nested
classifier. A nested classifier does not necessarily have to be part of
the internal structure of its owning parent. Tatiana, in your example,
MenuBar would own a property "dst" of type Button, whereas if one just
showed that Button was a nested classifier then no such property would exist
(necessarily).
Please correct me if I'm wrong.
Cheers,
- James.
"Tatiana Fesenko" <tatiana.fesenko@borland.com> wrote in message
news:6785c52638e68ca47533a2633ab@news.eclipse.org...
Hello Marius,
The owned class is always shown as a label inside 'classes' compartment. But
you can use Composite Aggregation link. It handles required to you semantics
of whole/part relationship. The picture how your example with MenuBar/Button
will look like if using Composite Aggregation is in the file attached.
To create Composite Aggregation use Links/Association/Composite Aggregation
palette entry.
Best wishes,
Tatiana.
> Hi,
>
> When i nest a class inside another class (i.e. to get an inner class)
> it shows up as an entry in the "class" compartment in the associated
> diagram (see
> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_is.png>). Is
> there any way to have the uml2 visualisation as shown in
> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_should .png>?
>
> cheers,
> marius
|
|
|
Re: inner (nested) classes [message #619653 is a reply to message #473499] |
Thu, 03 April 2008 08:34 |
Tatiana Fesenko Messages: 530 Registered: July 2009 |
Senior Member |
|
|
Thank you, James, you are always correct =)
Yes, composite aggregation semantics is close to the semantics of owned property,
not to the semantics of nested classifier.
However, the only representation for the nested classifier I've found in
the UML specification is a label inside parent classifier. Please correct
me if I am wrong.
Marius,
your second picture ( http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_should .png)
looks very like as Composite or Shared Aggregation, which hangles a bit different
from nested classifier semantics.
For more information reference corresponding sections of UML specification.
Cheers,
Tatiana.
> Hi Tatiana, Marius,
>
> If I'm not mistaken, the composite aggregation is different from a
> nested classifier. A nested classifier does not necessarily have to
> be part of the internal structure of its owning parent. Tatiana, in
> your example, MenuBar would own a property "dst" of type Button,
> whereas if one just showed that Button was a nested classifier then no
> such property would exist (necessarily).
>
> Please correct me if I'm wrong.
>
> Cheers,
> - James.
> "Tatiana Fesenko" <tatiana.fesenko@borland.com> wrote in message
> news:6785c52638e68ca47533a2633ab@news.eclipse.org...
> Hello Marius,
> The owned class is always shown as a label inside 'classes'
> compartment. But you can use Composite Aggregation link. It handles
> required to you semantics of whole/part relationship. The picture how
> your example with MenuBar/Button will look like if using Composite
> Aggregation is in the file attached.
>
> To create Composite Aggregation use Links/Association/Composite
> Aggregation palette entry.
>
> Best wishes,
> Tatiana.
>> Hi,
>>
>> When i nest a class inside another class (i.e. to get an inner class)
>> it shows up as an entry in the "class" compartment in the associated
>> diagram (see
>> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_is.png>). Is
>> there any way to have the uml2 visualisation as shown in
>> < http://stud3.tuwien.ac.at/~e9926236/e_uml2_innerclass_should .png>?
>>
>> cheers,
>> marius
|
|
|
Goto Forum:
Current Time: Mon Sep 23 10:56:10 GMT 2024
Powered by FUDForum. Page generated in 0.04361 seconds
|