Requirements: Stereotype vs Project Type

[Uffe]

Hey all,


How nicely do in-project defined requirement types play with profile-defined stereotypes?

Let's say I want to define a requirement type 'MyReqType'. I want it to show up in the Type dropdown in the properties dialog (project type), and I also want it to have a mandatory tagged value (stereotype).

If I define the requirement type both ways, how will EA behave?

If I create a «MyReqType» element from the toolbox, will EA recognize it as being of the 'MyReqType' requirement type, or will it see it as something different because the fully-qualified stereotype name is MyProfile::MyReqType?

If I create a regular requirement from the Common toolbox and set its type to 'MyReqType' in the property dialog during creation, will the tagged value be created?


Cheers,


/Uffe

[Nabil]

Hello Uffe, how about  project template package. Create requirement from toolbox also will have a tagged value you wish to have.
BR
Nabil

[Uffe]

That's not what I was asking about. I want to know the specific differences in behaviour between stereotyped and project-typed requirements.

/U