Book a Demo

Author Topic: Adding fields for requirements  (Read 2935 times)

mikem

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Adding fields for requirements
« on: April 17, 2007, 12:53:14 pm »
I am creating requirements in EA and I would like to add two additional fields (Source of Requirement and Date Approved).  I would like them to be visible on the Properties view of the requirement so I can see all the key elements (i.e. status, priority, version, etc.) at one time.

Can this be done?  If so, would anyone mind sharing how to do this?  Thanks!

thomaskilian

  • Guest
Re: Adding fields for requirements
« Reply #1 on: April 17, 2007, 10:54:08 pm »
The only way would be to add Tags. You can have the Tags pane docked near the Properties. So you can see all of the at the same time.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Adding fields for requirements
« Reply #2 on: April 18, 2007, 12:57:39 pm »
Also have a look at the types of tags you can configure.  http://sparxsystems.com.au/EAUserGuide/index.html?predefinedtaggedvaluetypes.htm  You can also configure profiles to automatically include these tags. http://www.sparxsystems.com.au/EAUserGuide/index.html?definestereotypetags.htm

bioform

  • EA User
  • **
  • Posts: 230
  • Karma: +0/-0
  • Forty-Two?
    • View Profile
Re: Adding fields for requirements
« Reply #3 on: April 27, 2007, 05:23:49 pm »
Exactly... the profile/stereotype approach works well for me...

I include several tags such as Severity (if not available to user), Frequency, Priority, Risk (to the project plan), etc.

Also, since I do a fair amount of automation/add-in prototyping external to EA (using Access), I have created several tag values that I use to "derive" information from the model, then update these tag values, that I can then use to modify specific elements..

Example: Derive target precision level for a UC (how fully dressed SHOULD it be... based on other tagged values as described above...), then derive the current precision level (against my business rules), then color code the use case elements to indicate how close they are to meeting the target... e.g., White (PL0), Pink (PL1), Yellow (PL2), Aqua (PL3), and Green (PL4) or when the Current PL = Target PL...

Time is what keeps everything from happening at once, Space is what keeps it all from happening to you. <unknown>