View Poll Results: Is test requirement traceability matrix very required in software testing?
Yes Very Much 5 45.45%
Yes but not very much needed 4 36.36%
No Need for that. 0 0%
Might be for Process purpose only. 2 18.18%
Voters: 11. You may not vote on this poll

selvamohan
Can any one tell me what is test requirement traceability matrix all about ? in software testing with some supporting documents.
From India, Bangalore
ramsunnalu
6

Hi
Test Requirement tracibility matrix play very vital role.
All the requirements can be traced out using this.
In this doc we can find the reqiurements from the design and respective testcases covering that.
This is a good practice to have tracibility matrix for testing.
Thanks
Ramsunnalu

From India, Bangalore
ramsunnalu
6

Hi All,
Here is the layout and descriptions of the details need to fill in the sheet
1.Requirement:
Brief Description fo the Reqiorement
2.Design Document
from which design doc u goe this ( Ex: Business Designdoc, Technical design Doc, Change Request, etc)
3.Code
in which part of code it is covered( Developer have to fil this)
4.Unit Test Cases
Test case number/name covered this requirement( Devloper have to fil this)
5. System Test Cases
Test case number/name covered this requirement( System Tester have to fil this)
The same can be fouind in attached Xls.
thanks

From India, Bangalore
Attached Files (Download Requires Membership)
File Type: xls tracibility_matrix_607.xls (13.5 KB, 474 views)

prageetha
9

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 requirement was changed, eliminated, or replaced, indicate disposition and authority for modification.

Regards,

Dr. Prageetha

From India, Warangal
prageetha
9

DEAR FRIEND, ALSO FIND THE FOLLOWING ATTACHMENT WHICH GIVES U THE FUNDAMENTALS ABOUT TRT MATRIX. REGARDS, DR. PRAGEETHA
From India, Warangal
Community Support and Knowledge-base on business, career and organisational prospects and issues - Register and Log In to CiteHR and post your query, download formats and be part of a fostered community of professionals.





Contact Us Privacy Policy Disclaimer Terms Of Service

All rights reserved @ 2024 CiteHR ®

All Copyright And Trademarks in Posts Held By Respective Owners.