Interested to Buy Any Domain ? << Click Here >> for more details...
HI,
TRM(Test Responsibility Matrix) and RTM(requirement
Tracebility matrix) both are same??
- 4 Answers
- 13223 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / vanitha
no,trm and rtm both are different
RTM: means mapping between requirements and testcases(to
check whether all testcases are covered or not)
TRM: meanswhich type oftesting technique has to be chosen
to corresponding usecase
| Is This Answer Correct ? | 8 Yes | 1 No |
Answer / ratheesh palakulath
I Slightly difer with the answers #1 & #3 about RTM
RTM is not only a report consisting of Reqs(Bysiness/Func)
and Testcases.
RTM is a document which starts with Business requiremen IDs
Mapped to Func. Req Ids -> Design Units -> Code -> Test
Cases.
From Testing Department we deliver the RTM with Testcase
IDS mapped to Func Req IDs. Like this each department
produces their RTM and send it to the concerned.Then They
club all units and produces the RTM for the project.
This File which tracks Business Reqs till Code throurgh
Func Reqs, design and Testing is called RTM
Note: Well I haven't seen a TRM till now. Thanks Upendar
and Vanitha for the answers.
| Is This Answer Correct ? | 3 Yes | 1 No |
Answer / upendar
RTM means mapping between testcases and customer requriments
TRM means mapping between development stages and testing
components
| Is This Answer Correct ? | 1 Yes | 2 No |
what type of documents needed in every phase of sdlc for SQA?
write test case for ecomerce shopping
Need information on Documentum4.3, any websites. What is this Documentum,how to access,features and benefits. ASAP Thx.
How do you document well a website (i.e an ONG website) pls help me with a sample. Need your help UR
what are the key components of test plan document?
differentiate test scenario & test case?
17 Answers Talent Sprint, Triniti Advanced Software,
what is your company testcase format?
18 Answers Infosys, MasterMind, Sinsoft,
After asking the defect life cycle, if you think it is not a valid defect, what you will do, whether you will store in any document for future reviews,if yes, what is that document, where you will save that document? or just reject it and close it?
differentiate defect age & build version control?
How do we do testing if requirements are not documented properly?
Can't we write test plan without any document with us or we definitely require the document for that
What is Defect/Bug/Error Life Cycle?
Automation Testing 
