1 / 7

Traceability Matrix in Software Testing

In an agile development environment, programmers, testers and business analysts work as a single team. The business analysts prepare comprehensive business requirement documents (BRD) to define the project needs as well as customer needs and expectations clearly. While evaluating the applications, the QA professionals refer to the BRD to plan and manage software testing process efficiently.

mindfiresolutions
Download Presentation

Traceability Matrix in Software Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Traceability Matrix in Software Testing

  2.  In an agile development environment, programmers, testers and business analysts work as a single team. The business analysts prepare comprehensive business requirement documents (BRD) to define the project needs as well as customer needs and expectations clearly.  While evaluating the applications, the QA professionals refer to the BRD to plan and manage software testing process efficiently. But they perform a variety of tests to assess various aspects of the software application.  Hence, it becomes essential to trace the business requirements to various tests to ensure that no business requirements remain unfulfilled.

  3.  Requirements traceability matrix makes it easier for testers to trace business requirements to the tests performed by them.  The matrix even helps testing professional to enhance test coverage, identify the missing functionality, and track test execution status. Also, the testers can refer to the traceability matrix to identify the test cases to be updated to meet changes in business requirements.  However, traceability matrix like test delivers differs from one project to another. The manager has option to choose from various types of traceability matrix. Likewise, he can also prepare requirement traceability matrix with varied fields.

  4. Different Types of Traceability Matrix in Software Testing FORWARD TRACEABILITY MATRIX: This type of traceability matrix business requirements to test cases. The mapping helps testers to ensure that each business requirement is tested thoroughly. Also, the testers can use the matrix to check if the testing project is progressing in the predefined direction.

  5. BACKWARD/REVERSE TRACEABILITY MATRIX: Backward or reverse traceability matrix maps test cases to business requirements. Hence, it becomes easier for testers to ensure that they are not testing any functionality which is not included in the business requirements additionally. Also, they can streamline the entire testing process without putting extra effort. BIDIRECTIONAL TRACEABILITY MATRIX: This form of traceability matrix maps business requirements to test cases as well as maps test cases to business requirements. As it combines forward and backward traceability matrixes, it becomes easier for testers to ensure that the test cases cover all business requirements and each business requirement is tested thoroughly.

  6. Workflow In addition to defining the scope of the software testing project, traceability matrix also helps testers to map test cases to business requirements and business requirements to test cases. Hence, the manger must prepare traceability matrix before the project starts. He still has option to keep the traceability matrix forward, backward, or bidirectional. However, the smarter test managers opt for bidirectional traceability matrix to examine output of deliverables, while creating test cases to cover business requirements required by a particular feature or functionality of the software application.

  7. Content Designed By: Mindfire Solutions

More Related