Traceability Matrix and its Uses
Traceability matrix is used to track requirements to any measurable objects in the software development process. Normally, we use traceability matrix to link requirements to use cases to process flow and requirements to process flow and requirements to business objectives. Requirements can be linked to design, specs or test cases. This mapping technique is useful to make sure that there is a complete coverage of requirement until the testing. However the most useful one that few know of is the linking requirements to the test cases and process flow. When the process flow is complete than we can have a comparison between the requirements and process flow and then we can easily identify the missing requirements. Another profound way of linking the requirements to validate is the reverse linking where we map the requirements with the business objectives or project plan. This way we can measure the value of requirements against the business objective and identify the relevant requirements. For the requirements which hold no value against the business objectives can be eliminated. In other hand, if we are unable to find all the requirements for the business objective than that means we have identified the missing requirement. In this case, the requirements should be added to your requirement document.
What are the differences between BRTM and RTM?
Traceability Matrix is created in different phases of software development cycle. BRTM is created during the initialization or planning phase of project life cycle. BRTM, Business Requirement Traceability Matrix, as its name suggest, it is the first traceability document created by Business Analyst to compare the Requirements against the Solutions/HLD or it can be reverse comparison document to compare requirements against the business objectives. BRTM is considered high level traceability document because this documents provide higher level comparison as opposed to RTM. RTM, Requirement Traceability Matrix are normally created by System Analyst using the BRTM which was already created by Business Analyst. In most cases, BRTM or RTM are not considered the required project documents, however, any Business Analyst or System analyst can improve the quality by implementing it as the reference document to the project deliverable that they are obliged to create.
Fig- BRTM Vs RTM Flow_Phases
BRTM simply compares requirements against business objectives or High Level design. However, RTM is used to compare requirement against detail system level requirements, Design elements and Test Cases. RTM is detailed version of BRTM in simple terms.