Home » Modeling » UML2 » Propagating stereotypes for all components
Propagating stereotypes for all components [message #476917] |
Fri, 08 February 2008 09:54  |
Eclipse User |
|
|
|
Originally posted by: antti.evesti.vtt.fi
Hello,
Is it possible to define and connect a UML profile to the component diagram,
i.e. component element, in a way that propagates all stereotypes from the
profile for all the components inside the diagram? Now, I have to connect a
stereotype separately for each component and this is laborious task if there
is dozens components.
I mentioned following statement from the UML superstructure
A profile should be able to specialize the semantics of standard UML
metamodel elements. For example, in a model with the profile "Java model,"
generalization of classes should be able to be restricted to single
inheritance without having to explicitly assign a stereotype
|
|
|
Re: Propagating stereotypes for all components [message #476918 is a reply to message #476917] |
Fri, 08 February 2008 14:34   |
james bruck Messages: 1724 Registered: July 2009 |
Senior Member |
|
|
Hi Antti,
When you create your uml::Extension, you can set the isRequired() to true.
Later, when the profile is applied, all required stereotypes will also be
applied.
In this way, you would not have to apply each Stereotype individually.
I'm not sure if this is exactly what you were looking for.
Cheers,
- James.
"Antti Evesti" <antti.evesti@vtt.fi> wrote in message
news:foh8su$frl$1@build.eclipse.org...
> Hello,
>
> Is it possible to define and connect a UML profile to the component
> diagram, i.e. component element, in a way that propagates all stereotypes
> from the profile for all the components inside the diagram? Now, I have to
> connect a stereotype separately for each component and this is laborious
> task if there is dozens components.
>
> I mentioned following statement from the UML superstructure
> A profile should be able to specialize the semantics of standard UML
> metamodel elements. For example, in a model with the profile "Java model,"
> generalization of classes should be able to be restricted to single
> inheritance without having to explicitly assign a stereotype
|
|
|
Re: Propagating stereotypes for all components [message #476924 is a reply to message #476918] |
Mon, 11 February 2008 08:31  |
Eclipse User |
|
|
|
Originally posted by: antti.evesti.vtt.fi
Thanks! That was exactly what I meant.
Antti
"James Bruck" <jbruck@ca.ibm.com> wrote in message
news:fohpak$qd0$2@build.eclipse.org...
> Hi Antti,
>
> When you create your uml::Extension, you can set the isRequired() to true.
> Later, when the profile is applied, all required stereotypes will also be
> applied.
>
> In this way, you would not have to apply each Stereotype individually.
>
> I'm not sure if this is exactly what you were looking for.
>
> Cheers,
> - James.
>
>
>
>
> "Antti Evesti" <antti.evesti@vtt.fi> wrote in message
> news:foh8su$frl$1@build.eclipse.org...
>> Hello,
>>
>> Is it possible to define and connect a UML profile to the component
>> diagram, i.e. component element, in a way that propagates all stereotypes
>> from the profile for all the components inside the diagram? Now, I have
>> to connect a stereotype separately for each component and this is
>> laborious task if there is dozens components.
>>
>> I mentioned following statement from the UML superstructure
>> A profile should be able to specialize the semantics of standard UML
>> metamodel elements. For example, in a model with the profile "Java
>> model," generalization of classes should be able to be restricted to
>> single inheritance without having to explicitly assign a stereotype
|
|
|
Re: Propagating stereotypes for all components [message #625996 is a reply to message #476917] |
Fri, 08 February 2008 14:34  |
james bruck Messages: 1724 Registered: July 2009 |
Senior Member |
|
|
Hi Antti,
When you create your uml::Extension, you can set the isRequired() to true.
Later, when the profile is applied, all required stereotypes will also be
applied.
In this way, you would not have to apply each Stereotype individually.
I'm not sure if this is exactly what you were looking for.
Cheers,
- James.
"Antti Evesti" <antti.evesti@vtt.fi> wrote in message
news:foh8su$frl$1@build.eclipse.org...
> Hello,
>
> Is it possible to define and connect a UML profile to the component
> diagram, i.e. component element, in a way that propagates all stereotypes
> from the profile for all the components inside the diagram? Now, I have to
> connect a stereotype separately for each component and this is laborious
> task if there is dozens components.
>
> I mentioned following statement from the UML superstructure
> A profile should be able to specialize the semantics of standard UML
> metamodel elements. For example, in a model with the profile "Java model,"
> generalization of classes should be able to be restricted to single
> inheritance without having to explicitly assign a stereotype
|
|
|
Re: Propagating stereotypes for all components [message #626023 is a reply to message #476918] |
Mon, 11 February 2008 08:31  |
Eclipse User |
|
|
|
Originally posted by: antti.evesti.vtt.fi
Thanks! That was exactly what I meant.
Antti
"James Bruck" <jbruck@ca.ibm.com> wrote in message
news:fohpak$qd0$2@build.eclipse.org...
> Hi Antti,
>
> When you create your uml::Extension, you can set the isRequired() to true.
> Later, when the profile is applied, all required stereotypes will also be
> applied.
>
> In this way, you would not have to apply each Stereotype individually.
>
> I'm not sure if this is exactly what you were looking for.
>
> Cheers,
> - James.
>
>
>
>
> "Antti Evesti" <antti.evesti@vtt.fi> wrote in message
> news:foh8su$frl$1@build.eclipse.org...
>> Hello,
>>
>> Is it possible to define and connect a UML profile to the component
>> diagram, i.e. component element, in a way that propagates all stereotypes
>> from the profile for all the components inside the diagram? Now, I have
>> to connect a stereotype separately for each component and this is
>> laborious task if there is dozens components.
>>
>> I mentioned following statement from the UML superstructure
>> A profile should be able to specialize the semantics of standard UML
>> metamodel elements. For example, in a model with the profile "Java
>> model," generalization of classes should be able to be restricted to
>> single inheritance without having to explicitly assign a stereotype
|
|
|
Goto Forum:
Current Time: Wed Nov 29 00:23:58 GMT 2023
Powered by FUDForum. Page generated in 0.02721 seconds
|