What is an RTM?

This presentation is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License

By Maira Bay de Souza

Definition

A requirements traceability matrix (RTM) is a table (usually a spreadsheet) where you can link the test cases to the requirements and vice-versa.

In one column you place the requirement name and in the other, the name of the test case that tests the requirement.

When should we use it?

An RTM is essential in large or complex projects, with many requirements.

But a tester in a small project might also find useful to create one just to help them organize themselves.

I have done that in many of my own projects.

More detailed RTMs

In medium to large projects, I have worked with RTMs that also linked the requirements to the high level design items, to the detailed level design items, to the high level test cases, to the detail level test cases.

More detailed RTMs (contd.)

The amount of information in an RTM will depend on the time we have to fill the matrix (ie Schedule constraints), the level of detail that the Project Manager and/or Test Manager wants, who is using the matrix (just test team or test and development), what other tools the team is already using, etc.

Tools

Several tools can replace an RTM.

I have worked in a very large project where we used an MS Access database to trace the requirements.

In the past few years, Test Director (from HP) has implemented many features that help trace the requirements to the test cases.

Tools (contd.)

I have also used a combination of tools for that same purpose (example: Rational ClearQuest + Lotus Notes).

What tool will be used, in most cases depends on the company policy.

Examples

See the Wikipedia article for an example of a very simple RTM.

And this website for a more complex RTM.

Questions and comments

If you have any questions about RTM - or any other testing topic for that matter - feel free to ask me!

I also appreciate any feedback you have about this presentation.