Requirements Traceability Matrix

Requirements Traceability Matrix
Planning, Tracking and Managing Requirements
Why RTM?
 

•The client who had ordered for the product specifies his requirements to the Software Team and the process of Software Development gets started.

•In addition to the requirements specified by the client, the software team may also propose various value added suggestions that could be added on to the software. But maintaining a track of all the requirements specified in the requirement document and checking whether all the requirements have been met by the end product is a  difficult  and long process.

•The solution for this problem is the Requirements Traceability Matrix.

 Steps involved in RTM

•Requirements Traceability Matrix Document is the output of Requirements Management phase of SDLC.

•Requirements are nothing but the information what we gathered from BA , Designer , discussions and through Mails.

•We have to update these requirements in “Inventory Section” of RTM.

•Identify the Test scenarios associated with each requirement . 

•Develop the Test cases associated with each scenario. 

• Map Test case id with Test scenario in RTM.

     Inventory Section:

                Rid, R Description, R source these group of requirements together known as inventory section.

 

 Template

•The RTM Template shows the Mapping between the actual Requirement and User Requirement/System Requirement.

RID	DESCRIPTION	RSOURCE	TEST SCENARIO	TID	DEFECT ID
Inventory Section	Inventory Section	Inventory Section

 

 Advantages 

•We can identify the total number of test cases for requirement .

•To know the orphan requirements.

•To identify regression components.

•RTM is useful for status reporting.

• RTM document maps Test cases with associated requirements.

  

Importance of Traceability

•To determine whether the product meets its requirement .

•Helps to identify reusable test cases .

•Used to identify Orphan requirements.

•It helps to identify Regression testing components.