Book a Demo

Author Topic: requirement stability  (Read 3477 times)

jodsm

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
requirement stability
« on: February 09, 2009, 09:24:50 pm »
In build 834 of Sparx 7.1 internal requirements can have a stability attribute set. Once these requirements are externalized this information seems to be lost. Also, via the external requirements one cannot change this attribute. Since we work mostly with external requirements, we would like to be able to capture this information as well. any workarounds ?

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: requirement stability
« Reply #1 on: February 09, 2009, 11:40:04 pm »
I suspect - without proof - that the Stability attribute is simply something that came along with being a (sort of) class feature. Once the requirement is 'promoted' to being a separate element this attribute is lost.

Perhaps a usable workaround would be to capture this as a tagged value. You could even create a special tagged value that would only accept values from a predefined list, which you would populate with the values that EA allows for the Stability attribute. See the EA help for to do this. [HINT: Look up Structured Tagged Values.]

HTH, David
No, you can't have it!