Book a Demo

Author Topic: Requirement Property Fields  (Read 3077 times)

namealreadytaken

  • EA User
  • **
  • Posts: 24
  • Karma: +0/-0
    • View Profile
Requirement Property Fields
« on: October 11, 2018, 09:23:27 am »
Greetings,

I am a novice when it comes to EA, however I have experience using siimilar tools.

When a user displays the Element Properties window, 2 fields display, among others, under the General heading: Type & Stereotype.

What is the intention these fields? Are they dependant or independant on/from each other?

Using EA 14, I can select an element type, however, the values in the Stereotype drop down list do not change. Options in the list are "browse other stereotypes" and functional.

Thank you for your response.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Requirement Property Fields
« Reply #1 on: October 11, 2018, 09:42:34 am »
Hm. You should know what stereotypes are. Look up the UML specs or take a basics training.

Now for the Type in the requirements: this is a special Sparx spice (hey! SSS). It's actually stored in the stereotype for the requirements but for some historical reasons Sparx shows it as Type. G. Sparks knows why.

q.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Requirement Property Fields
« Reply #2 on: October 11, 2018, 02:35:48 pm »
Hi,

By "similar tools" are you referring to requirements management tools, visual design tools or something else?

EA covers a huge scope and is used by a huge variety of different types of experience.

The Type field gives you a choice from the basic element types available in EA. Requirement is one of these types.

Stereotype is a bit more complex, it's an extension mechanism. What you see in here will depend on what technologies you have enabled and what type you have selected. Continuing with the requirement example, SysML provides a number of different types of requirements. (eg. Functional Requirement, Interface Requirement and Performance Requirement.) Each of those can have additional properties, which are commonly called tagged values.