Traceability Matrix:
Traceability matrix used to Map requirements to test cases.
Basically Traceability matrix ia two types:
 1. Vertical Traceability matrix.
 	2. Horizontal Traceability matrix.
Vertical Traceability matrix is high level document which 
map the requirements to all phases of the Software 
development cycle.
I.e. Unit testing, Component Integration testing, System 
Integration testing, Smoke/Sanity testing, System Testing, 
Acceptance testing...etc.
I am unable to show the template in this editor.
I am uploading a Template u can download from the 
Following link:
http://www.4shared.com/dir/7839233/bee1752d/Share_Doc.html
 2. Horizontal Traceability matrix.
It is related to testing related.
Traceability matrix used to:
1. Coverage analysis,
When a requirement changed it will used to identify the 
Test cases prepared on that requirement.
Once the test case identified it will be very easy to 
update the test case according to new requirement.
As a basic Rule of thumb: 
Each requirement should have at least one test case. By 
seeing the traceability matrix one can easily analyze the 
no. of test cases prepared for each requirement.
If there is no test case ID's found  against one 
requirement  that means ,test case is missing for that 
requirement.
Without Traceability matrix it is very difficult to 
estimate the test coverage and Change Management.

Byee Friends:

Rajendra Prasad

rajendra_penumalli@yahoo.com

Hi Rajendra
I hope this link can give you some ideas.
http://www.jiludwig.com/Traceability_Matrix_Structure.html

Requirements traceabiltiy is the capacity to relate your 
requirements to one another and to aspects of other project 
artifacts. Its primary goal is to ensure that all of the 
requirements have been met and validated.

Vertical traceabiltiy traces from requirements to 
design,the source code that implements the design and the 
tests that validate the requirements.
Horizontal traceability identifies relationships among 
similar items,such as between requirements.