Definition of Requirements traceability according to BABOK v3:
Requirements traceability: The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known.
What is Traceability Matrix?
It is a document to track the requirements and check if the present project requirements are met. In other words, RTM simply means that the requirements are mapped to the respective test cases so that all test cases are covered to test the defined functionality.
The focus of the QA testing team is to have maximum test coverage, so that we need to test everything there is to be tested.
What goes in the RTM?
Test cases, Business requirements document (BRD), Functional requirements document (FRD) some would also call this FRD as Technical design document (TDD). If your project is running on Agile model with no BRD but just “Features” with linked user stories, then take user story number in the matrix template.
RTM template model:
Projects identify and use many forms of templates.
Few use them for a simple track of test cases.
While few uses them to have an overview of requirements (user stories with acceptance criteria).
QA and PM team uses template to have a full coverage of the test cases along with the defects, UAT and user stories (acceptance criteria’s).
An ideal template which is highly used in most projects has the listed fields:
· Project Name
· Template version
· Business Requirement Document Use case number
· Business Requirements Use case
· Functional or Non functional requirements user story number
· User story acceptance criterion number
· Test case ID
· Test case description
· Test case steps
· Test data
· Defect and so on…
It is no rocket science or a special technique to ponder upon. It’s a simple tracking template with parameters that captures every acceptance criterion and its test case with the expected result. So, at the end of the Sprint, RTM has all functionality captured through test cases.