1
Uml Process / Re: Nesting / Deviding of UML Profiles possi
« on: November 06, 2007, 05:24:09 am »
Hi!
I have a similar problem as Stephanie had in June:
I want to define an abstract base-profile for architectural-styles and concrete profiles for concrete styles which have a "profile-application" relationship to the abstract base-profile, so that for each abstract stereotype at least one concrete stereotype needs to be created in the concrete style-profile and all constraints for the abstract stereotypes also apply to the concrete stereotypes:
<<profile>> AbstractStyle
<<metaclass>> Component
<<stereotype>> myAbstractComponent (extends Component)
<<profile>> ClientServerStyle
<<stereotype>> Client (derived from myAbstractComponent)
<<stereotype>> Server (derived from myAbstractComponent)
<<profile>> PipeAndFiltersStyle
<<stereotype>> Filter(derived from myAbstractComponent)
Now these profiles are not nested in one profile, but related by "profile-application":
<<profile>> ClientServerStyle
-<<apply>>->
<<profile>> AbstractStyle
<<profile>> PipeAndFiltersStyle
-<<apply>>->
<<profile>> AbstractStyle
I would have expected that after realising the "profile-application" relation between the concrete and the abstract profile and deriving the concrete stereotypes from the abstract stereotypes, I could create a concrete profile which include the concrete stereotypes with their constraints and the constraints of the abstract stereotypes, but the profiles are empty...
So my question is:
Has there been any process since June which helped to find a solution for the above described problem?
Best regards
Angela
I have a similar problem as Stephanie had in June:
I want to define an abstract base-profile for architectural-styles and concrete profiles for concrete styles which have a "profile-application" relationship to the abstract base-profile, so that for each abstract stereotype at least one concrete stereotype needs to be created in the concrete style-profile and all constraints for the abstract stereotypes also apply to the concrete stereotypes:
<<profile>> AbstractStyle
<<metaclass>> Component
<<stereotype>> myAbstractComponent (extends Component)
<<profile>> ClientServerStyle
<<stereotype>> Client (derived from myAbstractComponent)
<<stereotype>> Server (derived from myAbstractComponent)
<<profile>> PipeAndFiltersStyle
<<stereotype>> Filter(derived from myAbstractComponent)
Now these profiles are not nested in one profile, but related by "profile-application":
<<profile>> ClientServerStyle
-<<apply>>->
<<profile>> AbstractStyle
<<profile>> PipeAndFiltersStyle
-<<apply>>->
<<profile>> AbstractStyle
I would have expected that after realising the "profile-application" relation between the concrete and the abstract profile and deriving the concrete stereotypes from the abstract stereotypes, I could create a concrete profile which include the concrete stereotypes with their constraints and the constraints of the abstract stereotypes, but the profiles are empty...
So my question is:
Has there been any process since June which helped to find a solution for the above described problem?
Best regards
Angela