The Requirements Mapping Matrix (RMM) is a requirements traceability matrix that aids in the mapping of models information to business rules. Common mappings to include in a RMM are Process Flows to Requirements to Business Objectives. Features, code and test cases can also be included in an RMM. Ultimately, the goal of the RMM is to add traceability between requirements models and requirements, themselves.

The purpose of this tool is to help ensure that all of the necessary requirements are being considered and created. It is similar to a traceability matrix, however, it has additional columns allowing more for more than two objects’ relationships to be mapped.

When using this model it is vitally important to keep it up to date.

For more information on requirements mapping, visit In Praise of Requirements Mapping.

Learn more about requirements models in our book Visual Models for Software Requirements (Microsoft Press, 2012) Joy Beatty and Anthony Chen. (See Chapter 7 for Requirements Mapping Matrix)