Business analysis - Activity
Requirements traceability
Tracking each product requirement back to its source and the person that originated it
What's it for?
Keeps each requirement connected to where it came from and how it was delivered and tested.
For example…
Requirements traceability shows that a regulatory requirement led to a particular screen change and was verified by three specific test cases.
When a requirement changes, traceability lets the team see which design decisions, stories and tests may also need updating.