Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Best Practices > Best Practices for requir...

Best Practices for requirement changes ?

Friday, November 28, 2014

Hi,

I'm starting with SpiraTeam and I would like to know what is the best practices for requirement changes (like modification or deletion) without losing tracability ?
I would like to :
- Modify a requirement at a given release (change its description, its release version and reset its test coverage status)
- Set a requirement as obsolete
- Keep tracability of my requirement and its tested status at a given release.

Best Regards,
Xavier.

1 Replies

Monday, December 1, 2014

~~inflectra.sarahx~~

re: xaviervidal Friday, November 28, 2014

Hi Xavier

The recommended best practice would be:

Copy the requirement and point the copy at the new release, making changes as necessary.
Keep the old requirement pointing at the old release, mark as obsolete
If you need the test case status / traceability separate for each of the two requirement versions, you will also need to clone the test case and have the new requirement point to the new test case and the old requirement point to the old test case.

Regards

Sarah

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

Statistics

Started: Friday, November 28, 2014
Last Reply: Monday, December 1, 2014
Replies: 1
Views: 15825

Best Practices for requirement changes ?

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

Edit Thread

Edit Message

Search Results