The classical Requirements Traceability Matrix

Most literature about requirements-traceability focus on the Requirements Traceability Matrix 1. This table gives the relation between the (high level) requirements versus all test. As ‘needs’ can’t generate this table (yet), I have created one as example.

With this overview one get insight about which test are needed to verify one requirement. Sometimes it explicitly counts the number of available tests pro requirement too. Albeit that is a nice result, the ATM isn’t that useful in an agile environment. When a requirement is added, ore one changes, the RTM itself gives little help to update the table.

RTM for the Exact Calculator (CALC2)

Test\Req

Generic Add (CALC_ADD)

Generic Sub (CALC_SUB)

Generic Multiply (CALC_MULT)

Generic Divide (CALC_DIV)

Big fractional numbers (CALC2_1000ND)

Basic addition test (CALC_TEST_ADD_1)

X

X

Big addition test (CALC_TEST_ADD_2)

X

X

Subtract test (CALC_TEST_SUB_1)

X

X

Multiplication test (CALC_TEST_MULT_1)

X

X

DIV test (demo2 only) (CALC2_TEST_DIV_1)

X

X

Footnotes & Links

1

Often shorthanded to RTM, or simle “Traceability Matrix”, as wikipedia does.

Wikipedia on RTM:

https://en.wikipedia.org/wiki/Traceability_matrix

Comments

comments powered by Disqus