How to create requirement traceability matrix with TFS

The requirement traceability matrix is one of the common methodological processes in testing. Still, so many projects do not know or use it in project testing.

In my opinion, the traceability matrix is one of the best ways to measure the coverage of the requirement.

What meaning of the requirements traceability matrix?

The requirement traceability matrix is used to record the relations of the requirements to the design, development, testing.

How to manage the traceability matrix with TFS?

Changes to the requirements are also recorded and tracked in the TM.

The TM is maintained throughout the lifecycle of the software release and is reviewed and approved by the QA Manager, SW Director, and Product Manager (of course, it could change depends on project policy).

For QA the requirement traceability matrix is very important because the process is done to make sure that all the requirements have been covered in QA test cases.

Here is an example of a success TFS traceability matrix using.

  1. If you are using the User Story methodology please open a new  US in TFS.        

Go to all links tab->Link to ->Opened a window “Add Link to User Story”

Choose “Link type”->Child

In Link, Details choose the field “Work item IDs” and put a number of the relevant test case. Press “ok”

In the same way, you can relate test case to the relevant US, just choose link type “parent”

 2. The second step is to link the bug to the test case :

Open a new bug-> Go to all links tab->Link to ->Opened a window “Add Link to New Bug”

Choose “Link type”->Parent

In Link, Details choose the field “Work item IDs” and put a number of a relevant test case or User Story. Press “ok”

In the same way, you can relate the test case to the relevant bug just choose link type “child”.

Is this post helpful for you? Share your thoughts in comments on how it helped you. 

Join to Productive Hut Family and be part of a testing community!