Testing_118 : Requirement Traceability Matrix

RTM : Requirement Traceability Matrix

Purpose :

• Managing the Requirements.
• Make sure that all the requirement are covered in test cases so that while testing no functionality can be missed.

Definition :

A requirements traceability matrix is a document that trace and maps requirements with the test cases.
                                A traceability matrix is a respect from the requirement DB or repository. Traceability matrix is used in entire software development life cycle phases.

Type of Traceability matrix :-

• Forward Traceability : Mapping of requirements to test cases.
• Backward Traceability : Mapping of test cases to requirements.

 
Disadvantages of not using Traceability matrix [Some possible impact] : 

• Poor or unknown test coverage, more defects found in production.
• It will lead to miss some bugs in earlier test cycles which may arise in later test cycles. Then a lot of discussions arguments with other teams and managers before release. 
• Difficult project planning and tracking, misunderstanding between different teams over project dependencies, delay etc.

Benefits of using Traceability matrix :

• Make obvious to the client that the software is being developed as per the requirements.
• To make sure that all requirements included in the test cases.
• Easy to identify the missing functionalities.
• If there is a change request for a requirements, then we can easily find out which test cases need to update.

RTM Template :

RTM for Facebook (Example) :

BREQ# : business requirement id.
SREQ# : software requirement id.
FREQ# : functional requirement id.