Interested to Buy Any Domain ? << Click Here >> for more details...
what is traceability matrix?
- 6 Answers
- 11959 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / suresh
It is a document where requriment specfication is mapped to
functional specification.functional specification is mapped
to source coding.source coding is mapped to test case
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / viji&meena
Traceability matrix is nothing but mapping FS to Test
cases.This ensures that u have written enough test cases
covering all the functionalities.
| Is This Answer Correct ? | 3 Yes | 1 No |
Answer / satyanarayana.a
Traceability matrix is a table which is used to map the
baselined documents like testplan,teststrategy,testcases
and defect profile documents.
| Is This Answer Correct ? | 2 Yes | 2 No |
Answer / rajeshwar rao
It is a doucment showing the releation ship between the
docments or test cases
by looking at the these traceability matrix we can check
all testcase or covered or not
by looking at these tracebality matrix we can all the
testcases are written as per the srs brs documents.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / rm
A traceability matrix is a document, usually in the form of
a table, that correlates any two baselined documents that
require a many to many relationship to determine the
completeness of the relationship. It is often used with
high-level requirements (these often consist of marketing
requirements) and detailed requirements of the software
product to the matching parts of high-level design,
detailed design, test plan, and test cases.
Common usage is to take the identifier for each of the
items of one document and place them in the left column.
The identifiers for the other document are placed across
the top row. When an item in the left column is related to
an item across the top, a mark is placed in the
intersecting cell. The number of relationships are added up
for each row and each column. This value indicates the
mapping of the two items. Zero values indicate that no
relationship exists. It must be determined if one must be
made. Large values imply that the relationship is too
complex and should be simplified.
To ease the creation of traceability matrices, it is
advisable to add the relationships to the source documents
for both backward traceability and forward traceability. In
other words, when an item is changed in one baselined
document, it's easy to see what needs to be changed in the
other.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / venkat nagender
Traceability matrix is a table which correlates the complete
SRS to testcases written for testing. This table is useful
in identifying whether all the testcases are covering the
requirements of the SRS, inturn the requirements of product
| Is This Answer Correct ? | 0 Yes | 1 No |
Hello Friends Can anybody give me some idea about telephonic interview on Testing.As a exp. what could be the questions , that u guys have faced or you know ? Plz help me out
what is configuration management...please explain... thanx
Suppose u found a bug which a developer could not reproduce and it is reproducing on your pc whenever tried , then in this siyuation what will be the status of the bug, and what u r going to do for that bug.
4 Answers Flextronics, Syntel,
Do you think tools are required for managing change. Explain and please list some tools/practices which can help you managing change.
what is differance between web applicatins and web based applications?
What is workadround
What is quality center? What are the modules of quality center?
Difference between postponed and deferred bug
Which testing is this- verifying the funtionality of each programme 1. white box testing 2. black box testing 3. glass box testing 4. grey box testing
What is verification and Validation?
1.what is verifacation,validation,how its achieved? 2.What is test techniques& strategy? 3.what is error,fault,failure? 4.what is Reviews,Walkthrough,Inspection & Audit? 5.What is Change management,Configuration management,Version control,Test harness? 6.Importance of Severity,Priority,explain Bug life cycle? 7.Difference between use case & test case with example? 8.When should stop testing? 9.Write a test case for online banking application in the topics user login,security,transaction to other accout,data protection. 10.If the software is tested but all the bugs was not fixed,will you release this software?If yes/No then why?
How do you know your code has met specifications when there are no specifications?
Automation Testing 
