Requirements Traceability Matrix
Ideally each software developed must satisfy the set of requirements completely. So, right from design, each requirement must be addressed in every single document in the software process. The documents include the HLD, LLD, source codes, unit test cases, integration test cases and the system test cases. Refer the following sample table which describes Requirements Traceability Matrix process. In this matrix, the rows will have the requirements. For every document {HLD, LLD etc}, there will be a separate column. So, in every cell, we need to state, what section in HLD addresses a particular requirement. Ideally, if every requirement is addressed in every single document, all the individual cells must have valid section ids or names filled in. Then we know that every requirement is addressed. In case of any missing of requirement, we need to go back to the document and correct it, so that it addressed the requirement.
For testing at each level, we may have to address the requirements. One integration and the system test case may address multiple requirements.
|
| DTP Scenario No | DTC Id | Code | LLD Section |
| Requirement 1 | +ve/-ve | 1,2,3,4 |
|
|
| Requirement 2 | +ve/-ve | 1,2,3,4 |
|
|
| Requirement 3 | +ve/-ve | 1,2,3,4 |
|
|
| Requirement 4 | +ve/-ve | 1,2,3,4 |
|
|
| … |
|
|
|
|
| … |
|
|
|
|
| … |
|
|
|
|
| … |
|
|
|
|
| … |
|
|
|
|
| … |
|
|
|
|
| … |
|
|
|
|
| Requirement N | +ve/-ve | 1,2,3,4 |
|
|
|
| TESTER | TESTER | DEVELOPER | TEST LEAD |
No comments:
Post a Comment