Q2-What is the purpose of the Requirement traceability matrix?

The main purpose of Requirement traceability matrix is to keep track of the requirement, its source, trace the shifts, and how the requirement will be delivered throughout the project life cycle.it is a document that details the technical requirements for a given test scenario and its current state. Basically a requirements traceability matrix is a document that demonstrates the relationship between requirements and other artifacts. It’s used to demonstrate that requirements have been contented and it typically documents requirements, tests, test results, and issues. It assist the testing team understand the level of testing that is done for a given product. The components of RTM are Requirement ID or Requirement Number ,Requirement Type, Requirement Description, Unit Test Cases Reference , Integration Test Cases Reference , System Test Cases Reference , User Acceptance Test Cases Reference , Trace to Test Script .
Requirement traceability matrix makes sure that your requirement fulfill your business goals. It helps in quality assurance, team understand what need to be tested. RTM can also be used for decision-making throughout product development life cycle and useful for managing projects. We can know exactly how far we have progressed. And we will be able to manage the scope of our requirements. By linking our requirements to tests, we will recognize how we can realistically meet those requirements and still ship on time.
Requirement traceability matrix can be used to avoid costly errors. With the help of RTM the team member can have proper and consistent documentation. Missing requirement can also be attended on time. A requirement traceability matrix can aid us in filtering defects linked to crucial requirements, along with defect severity, priority, and more. RTM will also consider the efforts of the testing teamwork towards reworking or reconsidering on the test cases. This entitle a manager or stakeholder to quickly determine the level of risk associated with a production run