Requirement Trace-ability matrix is
matrix to map between requirements and test cases or test scenarios.
Normally testing team should involve rite from the requirement phase for
any project if requirements are clear to develop application or
product. If testing team gets involved right from the requirement phase
then requirement traceability is one of the important documents that can
detail what kind of test coverage the test cases or scenarios have.
Requirements Traceability Matrix (RTM) is updated by Development and Testing teams and used by stake holders of the project to check if all the requirements are addressed, implemented and Tested. Traceability Matrix allows forward or backward tracking of Business requirement, Functional Requirement, Design Code and Testing.
Traceability Matrix is a living document that would be updated whenever there are approved additions or changes to Business / Functional Requirements, Design, Unit / Integration / Functional Test Cases and Defects.
Traceability Matrix can be created and maintained in a Spread sheet or Rich text document IBM ClearQuest Test Manager (CQTM) or HP Quality Center (QC).
Traceability Matrix Template differs from organization and project, typically it will track the following.
Follow @TestingQ
Requirements Traceability Matrix (RTM) is updated by Development and Testing teams and used by stake holders of the project to check if all the requirements are addressed, implemented and Tested. Traceability Matrix allows forward or backward tracking of Business requirement, Functional Requirement, Design Code and Testing.
Traceability Matrix is a living document that would be updated whenever there are approved additions or changes to Business / Functional Requirements, Design, Unit / Integration / Functional Test Cases and Defects.
Traceability Matrix can be created and maintained in a Spread sheet or Rich text document IBM ClearQuest Test Manager (CQTM) or HP Quality Center (QC).
Traceability Matrix Template differs from organization and project, typically it will track the following.
- Priority (High, Medium, Low)
- Requirement Type (Enhancement, Change Request, Upgrade,Downgrade)
- Business Requirement Description
- Functional Requirement No.
- Functional Requirement Description.
- Feature or Module Name
- Source Code Reference (Path and Name)
- Unit Test Case Path and Name
- Integration/System Test Case Path and Name
- Open Defects
- Closed Defects
