Traceability

 

Overview

A best practice in product development is the adoption of a requirements-driven approach: all features of the product, as well as aspects of its development, should be directly or indirectly related to requirements. This concept is known as traceability. A related concept is coverage: high-level requirements should be covered by lower-level requirements and these in turn covered by other types of items such as test cases. For example, customer features can be broken down into functional requirements, which in turn can be related to test cases (represented as issues in Jira). We expect all customer features to be traceable to functional requirements and these in turn to be traceable to test cases. In this way we establish traceability and we ensure adequate coverage in our product development.

R4J Linking Features

R4J Feature

Purpose

R4J Feature

Purpose

Coverage View

To see how multiple requirements are linked to each and to determine the overall coverage. See Coverage View.

Traceability Matrix

To view and manage the links between different requirements. See Traceability Matrix.