Quality is delighting customers
TM is a measurement document which is used to to confirm that we have written test cases to exercise all of the test conditions ( Requirements ) or not... TM is the only document through which we can cross confirm it that We are going to cover all of the testable requirements with our Test Scenarios and Test cases...
It is a Document is tabular form which is maintained throughout the life cycle of the Project...
TM can be broadly categorised as :-
to have better understanding go through this uploaded Document too ............
Thanks for ur reply Samrat jha..
Plz explain this also ,If suppose my testing schedule is less in that time how TM ll use to us?
And also if suppose v receive lots of functional changes then what v ll do in this case?
In less time you can keep your Requirement at high level and Test cases at high level.......
Functional changes :--- Actually TM helps us in managing test Activities properly... If You see that in Requirement Column a new requirement has been added .. it means Now the Design will be changed to meet the new Requirement ---> then further Code will be changed to deal with new design ---> thereafter testers will require to make changes in Test scenario and further test cases will be derived from test scenario..............
Hope it will help you..
1. Forward Traceability – Mapping of Requirements to Test cases.
a. Tracing the requirement sources to their resulting product requirements to ensure the completeness of the product requirement specification.
b. Tracing each unique product requirement forward into the design that implement that requirement, the code that implement that design and the test that validate the requirement and so on.
The objective is to ensure that each requirement is implemented in the product and that each requirement is thoroughly tested.
2. Backward Traceability – Mapping of Test Cases to Requirements.
a. Tracing each unique work product (e.g. design element, object/class, code unit, test) back to its associated requirement. Backward Traceability can verify that the requirements have been kept current with the design, code and test.
b. Tracing each requirement back to its sources.
3. Bi-Directional Traceability – A Good Traceability matrix is the References from test cases to basis documentation and vice versa.