What is Requirement Traceability? Explain its importance.Requirement Traceability is mapping of requirements to test cases. There are two main traceability: Forward and Backward. It is important to know whether all the requirements mentioned in the Requirement Document have a corresponding test case or not. At the same time, it is important to know which requirement a particular test case has been written for. These are important if there are any changes in the requirement, we should know which test cases need to be re-written or modified.
Requirement Traceability is the final section of the test plan for measuring to cover all the requirement of the projects. It enables the users for finding the origin of every requirement and track all the changes which made the requirement.
Its purpose:
1. To ensure that a particular test case is based on one more requirements mentioned in the Requirement Doc.
2. To determine which test cases are written for which requirements
3. Also to check if test cases are written for every requirement.
4. If there arises any dispute over a bug in which developer says “it is not a bug as per the design”, in that case the test case can be traced back to the requirement.
5. It helps in finding out how many test cases are affected whenever there is any change in the application
Requirement Traceability verifies that each functional requirement used in the development matches to those that were written in the test cases based on other artifacts. It ensures that the team has covered all the requirements in testing and no functionality is missed out or left untouched. It determines the product stability.
|