Traceability matrix is used to map between requirements and 
test cases
it is used to check all requirements are covered or not?

USer Reqid/User req description/Functinal req spec/Desugn 
Spec

Plz mention the architecture of tracebility matrix




i am not getting,can you explain briefly

A document showing the relation between Test requirement 
and Test case.To check whether the testcases are mapped 
with the requirement

mapping between test cases and customer requirement is 
called traceability matrix

Traceability Matrix is a table that relates the customer 
requirements and it is used inorder to ensure that all the 
customer requirements have been satisfied by the test cases.

In a software development process, a Traceability Matrix is 
a table that correlates any two baselined documents that 
require a many to many relationship to the determine 
completeness of the relationship. It is often used with 
high-level requirements (sometimes known as Marketing 
Requirements) and detailed requirements of the software 
product to the matching parts of high-level design, 
detailed Design, test plan, and test cases

Traceablity matrix is document , which shows the 
relationship between Requirement doc , usecase doc , Test 
case doc and the defect doc. For one Requirement , there 
can be one or more use case ,and for one use case there can 
be one or more test case.Traceablity matrix shows the tree 
structute from requirement ==>use case==>test case.
Traceablity also used for defect doc i.e If we have a bug 
id of the bug than using this bug id and Traceablity matrix 
we can find out which user requirement is not satisfied.

Traceability Matrix - mapping between User Requirements and 
Test Cases

User Requirements - Taken from RS or FDS whichever is 
applicable in the organization
e.g. User should be able to add new record

Test Case - Contains scenario written so as to test the 
requirement, with an unique number for reference

Traceability Matrix contains the following columns: 
(example values are given in brackets)
Sl.No (1)
FDS/RS Name (FDS_New Module.doc_1.0)
FDS/RS Path (\\inserver\documents\)
Requirement (BR-1, SR-1, RS-1)
Coding Section (add_new - routine names used in code or 
name of the coding section given by developer)
Development Resource (Developer's Name)
Test Case (TC_001)
Testing Resource (Tester's name)
Testing Status (Pass/Fail)