Can any one tell me what is test requirement traceability matrix all about ? in software testing with some supporting documents.
From India, Bangalore
Acknowledge(0)
Amend(0)
From India, Bangalore
Acknowledge(0)Amend(0)
Hi,
Test Requirement Traceability Matrix plays a very vital role. All the requirements can be traced using this document. In this document, we can find the requirements from the design and their respective test cases covering them. It is a good practice to have a traceability matrix for testing.
Thanks,
Ramsunnalu
From India, Bangalore
Acknowledge(0)Amend(0)
6Test Requirement Traceability Matrix plays a very vital role. All the requirements can be traced using this document. In this document, we can find the requirements from the design and their respective test cases covering them. It is a good practice to have a traceability matrix for testing.
Thanks,
Ramsunnalu
From India, Bangalore
Acknowledge(0)Amend(0)
Hi All,
Here is the layout and descriptions of the details needed to fill in the sheet:
1. Requirement:
Brief Description of the Requirement
2. Design Document
From which design doc did you get this? (e.g., Business Design doc, Technical Design Doc, Change Request, etc.)
3. Code
In which part of the code is it covered? (Developers have to fill this)
4. Unit Test Cases
Test case number/name covering this requirement (Developers have to fill this)
5. System Test Cases
Test case number/name covering this requirement (System Testers have to fill this)
The same can be found in the attached Xls.
Thanks
From India, Bangalore
Acknowledge(0)Amend(0)
Here is the layout and descriptions of the details needed to fill in the sheet:
1. Requirement:
Brief Description of the Requirement
2. Design Document
From which design doc did you get this? (e.g., Business Design doc, Technical Design Doc, Change Request, etc.)
3. Code
In which part of the code is it covered? (Developers have to fill this)
4. Unit Test Cases
Test case number/name covering this requirement (Developers have to fill this)
5. System Test Cases
Test case number/name covering this requirement (System Testers have to fill this)
The same can be found in the attached Xls.
Thanks
From India, Bangalore
Acknowledge(0)Amend(0)
Requirements Traceability Matrix
Description of Matrix Fields
Develop a matrix to trace the requirements back to the project objectives identified in the Project Plan and forward through the remainder of the project life cycle stages. Place a copy of the matrix in the Project File. Expand the matrix in each stage to show traceability of work products to the requirements and vice versa.
The requirements traceability matrix should contain the following fields:
- A unique identification number containing the general category of the requirement (e.g., SYSADM) and a number assigned in ascending order (e.g., 1.0; 1.1; 1.2).
- The requirement statement.
- Requirement source (Conference; Configuration Control Board; Task Assignment, etc.).
- Software Requirements Specification/Functional Requirements Document paragraph number containing the requirement.
- Design Specification paragraph number containing the requirement.
- Program Module containing the requirement.
- Test Specification containing the requirement test.
- Test Case number(s) where requirement is to be tested (optional).
- Verification of successful testing of requirements.
- Modification field. If a requirement was changed, eliminated, or replaced, indicate disposition and authority for modification.
Regards,
Dr. Prageetha
From India, Warangal
Acknowledge(0)Amend(0)
Description of Matrix Fields
Develop a matrix to trace the requirements back to the project objectives identified in the Project Plan and forward through the remainder of the project life cycle stages. Place a copy of the matrix in the Project File. Expand the matrix in each stage to show traceability of work products to the requirements and vice versa.
The requirements traceability matrix should contain the following fields:
- A unique identification number containing the general category of the requirement (e.g., SYSADM) and a number assigned in ascending order (e.g., 1.0; 1.1; 1.2).
- The requirement statement.
- Requirement source (Conference; Configuration Control Board; Task Assignment, etc.).
- Software Requirements Specification/Functional Requirements Document paragraph number containing the requirement.
- Design Specification paragraph number containing the requirement.
- Program Module containing the requirement.
- Test Specification containing the requirement test.
- Test Case number(s) where requirement is to be tested (optional).
- Verification of successful testing of requirements.
- Modification field. If a requirement was changed, eliminated, or replaced, indicate disposition and authority for modification.
Regards,
Dr. Prageetha
From India, Warangal
Acknowledge(0)Amend(0)Gathering data for an AI comment.... Sending emails to relevant members...
Join Our Community and get connected with the right people who can help. Our AI-powered platform provides real-time fact-checking, peer-reviewed insights, and a vast historical knowledge base to support your search.
Competency Matrix -Procedures and Requirements-NR B.doc
Software-Testin g-Ppt.pps
Fire Pump Testing – Weekly Operational Test.pdf