What is Tracebility Matrix?

In Agile software development, a large functionality is divided into multiple sub-functionalities to reduce complexity and simplify implementation. Each sub-functionality is represented as a user story, while the complete functionality is represented as an epic.

Each user story is implemented and tested independently. Every story is mapped to its corresponding test cases to ensure that all requirements are adequately verified.

To confirm that every requirement has been tested and that no functionality has been missed, a Traceability Matrix is created. A Traceability Matrix establishes a relationship between user stories (or requirements) and their corresponding test cases, enabling complete test coverage and easy tracking of testing progress.

By referring to the Traceability Matrix, testers, developers, and other stakeholders can verify that every user story has been thoroughly tested and that no requirement has been omitted. It also helps identify missing test cases, supports impact analysis when requirements change, and provides evidence of complete requirement coverage.

Example

Consider a registration form that is being developed for new student admissions to a college. The overall functionality can be divided into the following user stories:

  1. Capture the personal details of the student.

  2. Capture the academic qualifications of the student.

  3. Generate the merit based on the student's academic qualifications.

Each of these user stories is implemented and tested independently. The corresponding test cases are then mapped to their respective user stories in a Traceability Matrix. This mapping ensures that every requirement is covered by one or more test cases and confirms that the entire registration functionality has been thoroughly tested before release.

Comments

Popular posts from this blog

How much SQL is needed for Test Engineer?

Software Testing Course

Major testing types