Author Topic: Requirement Types and Stereotypes-which is which?  (Read 1156 times)

mehl

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Requirement Types and Stereotypes-which is which?
« on: October 21, 2003, 11:14:43 am »
Hello --

Stereotype seems to become Type after I create a Formal Requirement on
Views > Custom> Formal Requirements
using
Insert > New Element

I entered the following:
Type:  "Requirement" (chosen from listbox)
Name:  "test Requirement"
Stereotype:  "access"  (chosen from listbox)

When that entry was completed, I checked the properties and found
Short Description:  "test Requirement"
Type:  "access"
Stereotype:  not shown

Clicking the dropdown for Type shows values such as
Display
Functional
Performance
etc.

and not the same values in list from which I selected the Stereotype "access" when I entered the requirement.

Should I expect to see the properties described this way ("Stereotype" disappeared), or is there a bug?

Thanks for any information to help me understand this.

Larry Mehl
mehl@cyvest.com

Sean Kearon

  • EA User
  • **
  • Posts: 126
  • Karma: +0/-0
    • View Profile
Re: Requirement Types and Stereotypes-which is whi
« Reply #1 on: October 30, 2003, 01:53:40 am »
Hi Larry

It appears that stereotypes are not directly applicable to requirements.  EA allows you to define the type of the requirement and translates the stereotype entered in the 'new element' dialog into a requirement type.  

You can maintain the requirement types from Configuration | General Types | Requirements.  But note that these are not treated as UML stereotypes and do not appear in the stereotypes list.

As far as I know, requirement is not part of the UML, it is a feature provided by EA.  A very userful one too :)  

HTH

Sean

mehl

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Re: Requirement Types and Stereotypes-which is whi
« Reply #2 on: October 30, 2003, 09:42:03 am »
Sean --

Thanks for the explanation.

Larry