Inconsistent Type property in Requirement

[beginner]

When you open the dbl-click-properties of a requirement you'll find a Type dropdown top right. Actually (in the database and in the properties-window) EA uses the Stereotype property in this place. It is, when you create a native Requirement, the Stereotype is empty. In the dbl-click-properties you see the default value "Functional". Now you can also type "Functional" in the Stereotype of the properties-window. The dbl-click-properties still show "Functional", but now from the actual stereotype. You will also notice the <<Functional>> stereotype appear in the project browser for the element.

The inconsistency (one more in the long list) comes to light when you synchronize stereotyped requirements. When you have a <<Functional>> Requirement in your MDG it will only synch those that have the explicit "Functional" set from the properties-window.

To clean this inconsistency the Requirements dbl-click-properties must show the Type dropdown as Stereotype (with ellipsis and everything like in all other elements) instead.

b.

[Paolo F Cantoni]

Agreed!

In case you haven't already...

Submit a Registered Bug Report or Bug Report and tell us the name,
leaving a note here to say you've done it.
We users can then vote for it using a Registered Bug Report or Bug Report with the same name[/color]

Paolo

[beginner]

Browsing through the long list of automated replies from Sparx I did find that I reported it...

Addendum: The properties-window offers a drop down for used and/or MDG-defined stereotypes. The last entry reads "browse for other stereotypes..." which is exactly what the ellipsis in the "normal" dbl-click-properties does. So the change should be fairly easy?

b.