| Work Product (Artifact): Requirements Traceability Matrix (RTM) |
| |
 |
| A table that traces requirements to the tests that are needed to verify that the requirement is fulfilled. |
|
Purpose
| The main goal of creating a requirement traceability matrix is to uniquely identify each requirement and trace them through
the entire project life cycle. |
Relationships
| Roles | Responsible:
| Modified By:
|
| Output From |
|
Main Description
| A requirement traceability matrix captures the complete user and system requirements and their traceability in a single
document. A good traceability matrix provides backward and forward traceability, i.e. a requirement can be traced to a test
and a test to a requirement. |
Properties
| Optional |  |
| Planned | |
Illustrations
Tailoring
| Impact of not having |
Without a requirement traceability matrix, it is possible that the system/solution that is built may not have the
necessary functionality to meet the customers and users needs and expectations. Also, not all requirements may be
included in the test cases and therefore, major defects could be missed during testing. It will be difficult to track
missing functionalities.
A seemingly simple request might involve changes to several parts of the system/solution and if proper traceability
process is not followed, the evaluation of the work that may be needed to satisfy the request may not be correctly
evaluated.
The completed system may have “Extra” functionality that may not have been requested by the customer, resulting in
wastage of time and effort.
|
| Reasons for not needing | While working on a very simple project that does not have any dependencies and complexities, a requirement traceability
matrix may not be created. |
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014
|
|
