How to prepare tracebility matrix?

Showing Answers 1 - 6 of 6 Answers

karthik

  • May 19th, 2006
 

Tracebility matrix is document used for tracking the requirement --->Test cases --> defect...This document is prepared to make the clients satisfy that the coverage done is complete as end to end,This document consists of Requirement/Base line doc Ref No., Test case/Condition , Defects/bug id.Using this document the person can track the Requirement from the defect id.......

  Was this answer useful?  Yes

rekha

  • May 24th, 2006
 

Tracebility matrix is the relstionship between requirement and testcase,using that we can make tracebilityn matrix

  Was this answer useful?  Yes

BISWAJIT PANI

  • Jun 14th, 2006
 

The main purpose of Tracebility Matrix is to creat a relationship between Requirements, Test case and  Defects  ( optional )

In Tracebility matrix Sheet we can use  high level requirements but better to use Low level Requirements

If we will use Low Level Requirements then it will better to test the requirement coverage properly

so it is called UNI DIRECTIONAL Tracebility Matrix

but in that sheet if we will use one new column as the end column named

"DEFECTS " then after testing by seeing the defects also we can know which requirement has not cover properly..

This is called BI DIRECTIONAL tracebilitry matrix

Regards

Biswajit pani (09986183456)

panibiswajit@yahoo.com

  Was this answer useful?  Yes

NicolaasJK

  • Nov 3rd, 2010
 

Depends on what you want to trace in the first place.

Generally the goal is to start with the source material ( examples Use Cases, websites, magazines, books, screenshots, Epic ). The team will generate requirements from the source material. Tasks will be created from the requirements. So this will look like this in a spreadsheet:

|| Source Name || Source Version || Source Location || Requirement || Requirement Version || Component Name || Task || Planned Implemented Milestone || Actual Implemented Milestone ||

One that is there and testing have to be covered as well then create the following:

|| Requirement ID || Requirement Version || Test Plan version || Test Design Name || Test Design version || Test Script Name || Test Script version || Test Case Name || Test Case version || Test Result || Tested Build ||

If it's unit test then:

|| Requirement ID || Requirement Version || Class ID || Unit Test Name || Result ||

As you can see, it is not advisable to us a spreadsheet but rather a tool. Seapine have great tools and you can generate reports in a few seconds before the test meeting or weekly report.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions