Book a Demo
« previous next »
Pages: [1]

Author Topic: Managing Requirement Versions  (Read 4618 times)

Tonyo

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Managing Requirement Versions
« on: November 27, 2006, 09:24:25 am »
Greetings!

We are trying to find a way to not only maintain a version number for each requirement, but to also maintain the original versions and the date(s) they were changed.

Has anyone found a way to do this in EA?

Thanks
Logged

thomaskilian

  • Guest
Re: Managing Requirement Versions
« Reply #1 on: December 01, 2006, 04:44:58 am »
I simply use a Tag for that.
Logged

thomaskilian

  • Guest
Re: Managing Requirement Versions
« Reply #2 on: December 18, 2006, 02:34:28 pm »
Quote
Using tags for requirements versions
on: Today at 16:44:18
A while ago, a coworker of mine mentioned on the sparx forum that we were looking for a way to store the text for old versions of a requirement.  You had responded "I simply use a Tag for that.".  We've looked into this, but would you mind elaborating just a bit more how you do this?  For starters, we found (I think) that the tag is limited in how many characters are allowed -- some of our requirements statements simply wouldn't all paste into the tag field.   Also, do you know if there any way to export or print the old versions along with the new using tags?  Thanks!!!

Hi,
you don't mind responding on the forum?

The way I do it is quite "simplistic". You can add tags to almost (:() any element including requirements. Use the Tagged Values window to create a new Tag called e.g. History using the "New Tag" icon. This lets you enter an initial value for the tag. I normally put a string here in the form "YYMMDD (username) text" to get it started. If the value is going to to be ammended at another time, I open the Tag in the Tagged Values window using the Edit Notes button. Then I add more lines like the one above. The notes window can take quite a lot text. I have no idea how much, but until now I did not find any limitation for me.
If you're going to use this heavily it's probably a good idea to write an add-in supporting this editing.
Logged

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Managing Requirement Versions
« Reply #3 on: December 18, 2006, 02:51:22 pm »
You can get around the size limitation of tags by defining them as memo fields. Click here for help on how to do that.
Logged
The Sparx Team
[email protected]

bioform

  • EA User
  • **
  • Posts: 230
  • Karma: +0/-0
  • Forty-Two?
    • View Profile
Re: Managing Requirement Versions
« Reply #4 on: December 27, 2006, 04:14:21 pm »
I am using the "Change" object to document changes to the model (requirements, use cases, etc.) as part of our CCB (Change Control Board) process.

If anyone is interested in discussing this in detail, create a thread, notify me and I will discuss my approach and experiences...

Hope everyone has a good end to the current, and a good start to their NEW year!
Logged
Time is what keeps everything from happening at once, Space is what keeps it all from happening to you. <unknown>

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Managing Requirement Versions
« Reply #5 on: December 27, 2006, 04:20:04 pm »
Quote
I am using the "Change" object to document changes to the model (requirements, use cases, etc.) as part of our CCB (Change Control Board) process.

If anyone is interested in discussing this in detail, create a thread, notify me and I will discuss my approach and experiences...

Hope everyone has a good end to the current, and a good start to their NEW year!
Consider putting it on the EA User Wiki...

We're too busy detecting XMI RTE bugs at present, but maybe that could be the EA Users' New Year Resolution - put interesting stuff on the EA User Wiki!

Paolo
Logged
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Tonyo

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Managing Requirement Versions
« Reply #6 on: January 03, 2007, 10:32:07 am »
Bioform -

I would be very interested how you are using the Change object to manage versions of requirements. Would you mind just responding to this message thread instead of starting a new thread?

Logged

bioform

  • EA User
  • **
  • Posts: 230
  • Karma: +0/-0
  • Forty-Two?
    • View Profile
Re: Managing Requirement Versions
« Reply #7 on: January 03, 2007, 11:34:59 am »
Sure!

I'm kinda in crunch mode right now, trying to implement some requirement stereotypes (separate thread under my handle) and push forward on automating requirement documentation using MS Word & EA (prototyping what an EA add-in would do - using MS Access)...

but it should not be more than a week before I can post...
(david.r.rains at Earthlink) :)
Logged
Time is what keeps everything from happening at once, Space is what keeps it all from happening to you. <unknown>

Rob_M

  • EA User
  • **
  • Posts: 58
  • Karma: +0/-0
    • View Profile
Re: Managing Requirement Versions
« Reply #8 on: January 08, 2007, 12:08:59 pm »
Logged
Pages: [1]
« previous next »