You might be trying to put too much into a single matrix. I use the excel rule - if I can't fit it in two dimensions, break it into another table.
The A stuff is good, with the exception of test cases. Here's the reasoning why. You can have mutliple test cases testing a single requirement or a single requirement tested in multiple test cases. It is not always a one-to-one relationship. Therefore, I usually have a table with the requirements along one axis and the test cases along another, and a lot of x's for the intersections.
Same way with your items from column B.
Design spec and test spec is what your company defines them to be. For me, design spec is when they take a detailed requirement and lay out a document saying how it will be implemented in design. Test spec is how that requirement will be tested - I use them as precursors to the actual test cases. Sometimes they are called "test conditions" or "test points".
I want to share my Traceability Matrix.
In functional Spec,the requirements are given numbers(Requirement ID) beside them.For these IDs we have to prepare Test Cases with a Test Case Id assigned.I mean to say that we have to map the requirements with the Test Cases that are written.
The other supporting documents will be the others that are mentioned by Darrel.
Am working in company as a software tester..AM being asked to produce the list functional and non fuctional requirements of a software application or product..can anyone suggest me any links were i can trace any useful information regarding that.