Book a Demo

Author Topic: Working with Profiles  (Read 3006 times)

thomaskilian

  • Guest
Working with Profiles
« on: January 25, 2005, 09:43:37 am »
Hi there,
anybody with experience in defining a Profile? Just tried what the documentation was telling and managed to create a profile. I set up an EA repository to define the profile and exported it. I defined two stereotypes extending two metaclasses (issue and requirement). The stereotypes have one tag each (just testing...). When I use this profile I find that the two metaclasses appear with the name of the stereotype instead of their own. Also the stereotype is placed in the Type property (funny: it's not possible to type these values in the type since the drop down is mandatory - so once you click it, this value disappears). If further I draw a generalization between the stereotypes and re-import the profile, I find the specialised stereotype in the profile, being able to drag it onto arbitrary elements.

My question: is this behaviour intended?

(I'm gonna try the constraints feature and the synchronisation which is an enigma to me now...)

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Working with Profiles
« Reply #1 on: January 26, 2005, 02:43:02 pm »
Hi Thomas,

Quote
When I use this profile I find that the two metaclasses appear with the name of the stereotype instead of their own.
When you define a stereotype you are defining a new metaclass based on whichever metaclass you are extending, so yes the names of the stereotypes will appear in the Resource View when you import the profile.

Quote
Also the stereotype is placed in the Type property
In the Requirements Properties dialog, it appears that the stereotype field is named "Type". This seems strange but is probably intentional, for reasons lost in history.

Quote
If further I draw a generalization between the stereotypes and re-import the profile, I find the specialised stereotype in the profile, being able to drag it onto arbitrary elements.
This behaviour is fixed for build 745, due out soon. Child stereotypes will inherit tags and constraints from their parents and extend whichever metaclasses their parent extends. Further, you will be able to make the parent abstract and it will be excluded from the profile.

HTH,

Neil
The Sparx Team
[email protected]

thomaskilian

  • Guest
Re: Working with Profiles
« Reply #2 on: January 27, 2005, 02:38:07 am »
Hi Neil,
thanks for the feedback. It's propably that you have to get used to working with profiles. However, they are very useful :)
« Last Edit: January 27, 2005, 02:38:26 am by thomaskilian »

thomaskilian

  • Guest
Re: Working with Profiles
« Reply #3 on: February 11, 2005, 06:08:11 am »
Steep hill to profiles :P
Now I want to have Tags that are not free text or drop downs but DateTime, Author, etc whichever is possible with standard tags. According to the documentation you can't do that. Is there any workaround/time when it will be possible?

Just a second later: Defining the according tags beforehand will give the result I expected. However it would be nice to instantly define/use tags of e.g. DateTime being defined in profiles without going over Config/UML/Tags.
« Last Edit: February 11, 2005, 06:14:05 am by thomaskilian »