A requirements traceability matrix is a document that traces and maps user requirements like requirement ids from requirement specification document with the test case ids. Bug Trace uses a patch and the original files (the files from which the patch was generated) to recover traceability links between a bug and the methods modified (added, changed, or removed) to fix the bug. Traceability of bug is defined by the requirements, requirement scenarios, test plans and high level designs etc. Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and test cases. Everything is needed to be considered with its test cases and failed test cases. The traceability of bug can be followed in so many ways.
- Mapping the functional requirement scenarios (FS doc) test cases (id) failed test cases (bugs).
- Mapping between business requirements (BR doc) test cases (id) failed test cases.
- Mapping between high level designs (Design doc) test cases (id) failed test cases.
- Mapping between requirements (RS doc) test case (id) failed test cases.
- Mapping between test plans (TP doc) test case (id) failed test cases.
Requirements traceability matrix gives a complete visual representation of the entity items that are linked to one another by means of the relationships. Using this matrix you can also create new, edit, delete relationships by double clicking on the cell that appears in the intersection of the two entity items. You can also clear impacts from the requirements traceability matrix itself. Requirements tracing is the process of documenting the links between the user requirements for the system you're building and the work products developed to implement and verify those requirements. A requirements traceability matrix may be used to check to see if the current project requirements are being met, and to help in the creation of a Request for Proposal, various deliverable documents, and project plan tasks. It purpose is to make sure that all the requirements are covered in test cases so that while testing no functionality can be missed. This document is prepared to make the clients satisfy that the coverage done is complete as end to end; this document consists of requirement doc, test cases and defects. Using this document the person can track the requirement based on the defect id. Traceability matrices are used to trace requirements to test cases in order to ensure that there are test cases for all the requirements. The traceability matrix links a business requirement to its corresponding functional requirement right up to the corresponding test cases. If a Test Case fails, traceability helps determine the corresponding functionality easily. It also helps ensure that all requirements are tested. A traceability matrix is created by associating requirements with the work products that satisfy them. Tests are associated with the requirements on which they are based and the product is tested to meet the requirement. In traceability, the relationship of driver to satisfier can be one-to-one, one-to-many, many-to-one, or many-to-many. Any relationship occurs in this case.