Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Best Practices > Best Practices for requir...

Best Practices for requirement changes ? RSS Feed

Friday, November 28, 2014

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,
1 Replies
Sarah T.Sarah T.
re: Xavier Vidal on Friday, November 28, 2014
Monday, December 1, 2014
Hi Xavier

The recommended best practice would be:

  1. Copy the requirement and point the copy at the new release, making changes as necessary.
  2. Keep the old requirement pointing at the old release, mark as obsolete
  3. 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.
  • Started: 11/28/2014
  • Last Reply: 12/1/2014
  • Replies: 1
  • Views: 8870
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2017 | Licensed to Inflectra Corporation.