Search This Blog

Monday, November 7, 2016

Requirement Traceability Matrix

It is basically a table which specifies all the requirements and that maps with the corresponding Test case
Suppose we have 'n' no. of requirements and bunch of test cases associated with these requirements.
Imagine a table with requirement and it's corresponding test case and that is Traceability Matrix


  • Before starting of the execution if we create this matrix, we will come to know  whether all the requirements have been covered by the test cases or not
  • It helps us to achieve 100% test coverage without missing any requirement.
  • Before assigning the module if we go through this matrix, we will come to know if we have lost some requirement and we can cover that up.
  • It is better to start Traceability Matrix in the initial phase rather than the later phase
  • This provides a mapping  b/w actual requirements and the test cases written
  • Easy to determine the impacted test cases for regression
  • Can be used as a tracker in case of requirement change

  • Forward  traceability - It maps requirements to test cases, it helps us see which requirements are covered in which test cases? Or whether a requirements is covered at all.
  • Backward traceability - It maps test cases to requirements it  helps us see which test cases are mapped against which requirements.
  • Bi directional traceability -  It ensures that we are building the product right. A bi-directional traceability matrix contains both forward and backward traceability.

No comments:

Post a Comment