|
| Redirect | ||||||
|---|---|---|---|---|---|---|
|
Introduction
The ability to trace linkages from requirements all the way to defects or vice versa is particularly useful in a software release cycle. In fact, it can have special meaning at various phases in that release cycle. For example, starting with requirements, knowing how many of them have tests written for them is useful in the early stages to ensure appropriate test coverage. Once the software has been built, keeping track of which test executions have passed for a particular requirement allows the team to make a quality statement about these requirements. And then keeping track of how many open defects exist for requirements help make a Go/No-Go decision regarding the readiness of the software to be shipped.
...
Here's an example of such a report:
Defects to Requirements
Select a Version and a particular Issue Type that can be the starting point of your traceability report. That is usually a “Bug”. The resulting list of issues can then be narrowed down to the ones you want a report on. Selecting the “Defect to Requirement” option and clicking on “Generate Traceability Report” will you give you a full traceability report from Defects --> Test Executions --> Tests --> Requirements.
...