Requirement Traceability Maprix – Scope Management Tool
Introduction: The Requirement Traceability Matrix is a tool that ensures that the project’s scope and requirements are consistent with the baseline. It “traces” the deliverables, establishing a thread for every requirement from the project’s inception until its completion. Requirement traceability matrix is actually a table that captures all the requirements for the development of the system. It is useful in both traditional (waterfall), and modern (agile), development methodologies. In traditional approach, it helps to trace requirements from testing to ensure that they are met. It is used in SCRUM methodology to link user stories between the product backlog (sprint backlog) and the product backlog (product backlog). RTM – Workflow: The Matrix forms the basis for the project’s scope, deliverables, and is created at the beginning. The RTM Matrix is bi-directional. It tracks the requirements “forward” through the output of deliverables, and “backward” through the business requirements for specific characteristics of the product. The RTM can also be used to identify scope changes as they occur. Requirement traceability Matrix-Parameters: The RTM is available in many formats, layouts, and structures. RTMs are created and used by projects according to their organizational standards and requirements. However, a good RTM usually contains one or more of these elements. Requirement ID (or Requirement Num) – This number is used to list each project requirement in numerical order.
Requirement Type – Grouping the requirements according to function.
Description of the Requirement – Name and brief description
Trace to Design Specification: Specify the identification number for the requirement as it appears in the SRS.
Refer to Unit Test Cases Identification Number
Refer to Integration Test Cases Reference/Identification number
System Test Cases Reference/Identification number
Reference to User Acceptance Test Cases / Identification number
Trace to Test Script – Test scripts should always be prepared for the actual testing.
Conclusion: Requirement tracking is a technique that ensures project deliver what stakeholders expect. It is a great technique that can improve the quality and reliability of the final product and reduce costs and rework. The RTM allows you to trace requirements throughout the entire project’s lifecycle, from design to coding to testing to user acceptance. Requirement traceability is an ongoing, continuous, iterative process. It should be shared with key stakeholders to ensure they are updated and aware of any assumptions or constraints contained in the Requirement traceability matrix. The Project manager can avoid potential scope management issues later in the project by making judicious use RTM. It is important to remember that tracing down to the lowest degree of detail may not be the best option for large projects with many requirements. References: – Requirements traceability and the effect on the System Development Lifecycle, (SDLC), Glenn A. Stout.
Requirement Traceability Matrix through Documentation For Scrum Methodology. By Gunavathi Duraisamy and Rodziah Atan. Journal of Theoretical and Applied Information Technology.
Tom Carlos – Requirements Traceability Maprix