Book a Demo

Author Topic: Requirements - Saving the reason for changing one  (Read 7461 times)

tatiane

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Requirements - Saving the reason for changing one
« on: October 06, 2009, 02:03:59 am »
Good Morning,

My name is tatiane
I´m from brazil and I’ve been learning about how EA can help me in management requirements. I found all the things I believe its important except one.
When we have a requirement change how can I catch the reason for changing??
I’m looking for a  way no save this reason. I know about de audit feature, but I didn’t find the specific place to save the reason for changing a requeriment.

Can you help me??

Thanks a lot.

tatiane

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #1 on: October 06, 2009, 02:04:48 am »
People , sorry for my english ok ..  ;)

Graham_Moir

  • EA User
  • **
  • Posts: 749
  • Karma: +10/-15
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #2 on: October 06, 2009, 02:48:27 am »
Hello Tatiane.

Have you tried the "Maintenance" window (View menu/Maintenance or Alt+4?)

Once this is displayed you have 4 tabs for Defects/Changes/Issues/Tasks.

So I think in your case you would select the requirement to give it the focus and then enter a change record for it.

G.

PS A change history built up in this way can be reported by EA too.
« Last Edit: October 06, 2009, 02:49:16 am by Graham_Moir »

tatiane

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #3 on: October 06, 2009, 07:33:13 am »
i've just tried Graham_Moir..
i put a new kind of problem type called ChangeReq
but how can i create a change for my Requirement and associate to the new problem type ?

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #4 on: October 06, 2009, 07:44:20 am »
Quote
I've just tried Graham_Moir..
i put a new kind of problem type called ChangeReq
but how can i create a change for my Requirement and associate to the new problem type ?
Hi Tatiane,

Did you create the ChangeLog using the "Change" element on the (Common) toolbox?  If so, then you misunderstood what Graham was saying.

EA has external "Changes", "Issues" "Requirements" etc, which are independent of any one element (these are created from the toolboxes).  It also has internal equivalents - which are tied to the selected element.  It was this second type that Graham was referring to.  If you select your requirement and then type [Alt+4] the Maintenance window for THAT requirement will be visible.  You can enter the change into the Changes tab and it will be associated directly with that requirement (and no other).

HTH,
Paolo
« Last Edit: October 06, 2009, 07:46:31 am by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

tatiane

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #5 on: October 06, 2009, 11:08:36 pm »
Thank you guys...
Now i understand. It worked
thanks for the help!!!
Bye.. :D

Oliver F.

  • EA User
  • **
  • Posts: 573
  • Karma: +2/-1
  • Aren´t we all in the model business ?
    • View Profile
    • Karl Storz homepage
Re: Requirements - Saving the reason for changing
« Reply #6 on: October 07, 2009, 01:15:47 am »
Quote
Have you tried the "Maintenance" window (View menu/Maintenance or Alt+4?)

Once this is displayed you have 4 tabs for Defects/Changes/Issues/Tasks.

Uh oh, there are rather useful things in EA which slipped through my fingers and one of those is that maintenance window.
How could I ignore this as it delivers exactly what I have been looking for before? :D

Thanks Graham for remembering.

Oliver

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #7 on: October 07, 2009, 12:15:55 pm »
Quote
[size=18]...[/size]
Thanks Graham for remembering.
Seconded!  I, too, had forgotten...

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

johnvv

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #8 on: October 25, 2009, 06:58:14 am »
I have just noticed this thread.  The facility is something that I have needed as well, its good to see it was already there.  

However, regarding visibility, is there any way to indicate on a diagram, or to see in a dialog for an element that it does actually have some maintenance/changes recorded against it?  

Or is it only 'visible' if one keeps the maintenance window open for everything?

John

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Requirements - Saving the reason for changing
« Reply #9 on: October 25, 2009, 11:03:46 am »
Quote
[size=18]...[/size]
Or is it only 'visible' if one keeps the maintenance window open for everything?

John
Hi John,

I think it's the latter.  Unfortunately EA isn't very good at providing indicators for further detail.

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