8/6/2019 What is a Trace Ability Matrix

1/2

What is a Traceability Matrix / Requirements Traceability Matrix?

The concept of Traceability Matrix is to be able to trace from top level requirements to implementation, and

from top level requirements to test.

A traceability matrix is a table that traces a requirement to the tests that are needed to verify that the

requirement is fulfilled. A good traceability matrix will provide backward and forward traceability, i.e. a

requirement can be traced to a test and a test to a requirements. The matrix links higher level

requirements, design specifications, test requirements, and code files. It acts as a map, providing the links

necessary for determining where information is located. This is also known as Requirements Traceability

Matrix or RTM.

This is mostly used for QA so that they can ensure that the customer gets what they requested. The

Traceability matrix also helps the developer find out why some code was implemented the way it was, by

being able to go from code to Requirements. If a test fails, it is possible to use the traceability matrix to see

what requirements and code the test case relates to.

The goal of a matrix of this type is -

1. To make sure that the approved requirements are addressed/covered in all phases of development: From

SRS to Development to Testing to Delivery.

2. That each document should be traceable: Written test cases should be traceable to its requirement

specification. If there is new version then updated testcases should be traceable with that

How to Create a Requirements Traceability Matrix

Things Youll Need:

Project deliverables

Business requirements catalog

Use cases

Step1:

Create a template. There are many on the web from which to choose. The project manager, sponsor and

decision makers will thank you when they are receiving information in a consistent and logical format.

Step2:

Transfer data from your Business Requirements Catalog. You will need, at bare minimum, the exact

requirement identified from the Business Requirements Catalog that you need to have already created.

Step3:

Identify the requirement with a unique ID. The business requirements document should have already

assigned an identifier that you will use in this matrix. If not, you will create one now and insert it next to

the applicable requirement.

Step4:

8/6/2019 What is a Trace Ability Matrix

2/2

Copy the Use Case ID into the traceability matrix. You may or may not have used use cases to develop

your requirements. If you did, you will have an identifier on your use case. You must transfer the ID to this

matrix in order to see out of what data or scenario this requirement was born.

Step5:

Insert the System Requirements Specification (SRS) ID into the traceability matrix. You might not be theactual author of the SRS, but there must be a line on the matrix to trace the business requirement to the

corresponding system requirement needed.

Step6:

Insert the testing data into the traceability matrix. There are many different testing methods and

procedures that can be used in any project. The traceability matrix must account for the types of tests

used in this project. This should clearly indicate the specific test type, the date tested and the outcome of

pass/fail.

Step7:

Review your data. Your matrix should now clearly show the specific deliverable requirements fromconception clearly through testing. This will ensure that nothing gets moved into production haphazardly

and when asked, the Project Manager now has this information at the ready.