What is Traceability Matrix

What is Traceability Matrix

Why use traceability matrices?

The traceability matrices are the answer to the following questions when testing any software project:

• How is it feasible to ensure, for each phase of the SDLC, that I have correctly accounted for all the customer’s needs?
• How can I certify that the final software product meets the customer’s needs? It lets us make sure requirements are captured in test cases.

Disadvantages of not using traceability matrices include the following:

• More defects in production poor or unknown test coverage.
• Discovering bugs later in the development cycle resulting in more expensive fixes.
• Difficulties planning and tracking projects.
• Misunderstandings between different teams over project dependencies, delays, etc…

Benefits of using traceability matrices include the following:

• Making it obvious to the client that the software is being developed as required.
• Ensuring that all requirements are included in the test cases.
• Ensuring that developers are not creating features that no one has requested.
• Making it easy to identify missing functionalities.
• Making it easy to find out which test cases need updating if there are change requests.

Requirements Traceability Matrix:

In simple words, a requirements traceability matrix is a document that traces and maps user requirements, usually requirement IDs from a requirement specification document, with the test case IDs. The purpose of this document is to make sure that all the requirements are covered in test cases so that nothing is missed.

The traceability matrix document is prepared to show clients that the coverage is complete. It usually includes the following columns: requirement, baseline document reference number, test case/condition and defect/bug ID. Using this document the person can track the Requirement based on the Defect id.

Adding a few more columns to the traceability matrix gives you a good test case coverage checklist.