CLOUD | DATA CENTER AND SERVER
Traceability Matrix
Overview
The Traceability Matrix View displays a two-dimensional matrix showing the links between two sets of requirements or other types of items. For example, you could have high-level customer requirements displayed as rows and their related lower-level specifications as columns. Links can be created and deleted on the fly. The Traceability Matrix View helps users visualize complex relationships within a set of requirements and to quickly create links and repair incorrect links.
To navigate to the Traceability Matrix View, open a project and select Traceability > Traceability in the easeRequirements navigation bar.
It is important to understand that the effective use of the Traceability Matrix View depends on the practices of your organization and its development process. You need to take into account how different types of requirements or other types of issues are structured, as well as how they are linked together and used. An organization might have different practices for different situations, so different matrices can be defined and saved in the Traceability Matrix View.
The sheer number of requirements in a project may also be a challenge to understanding traceability, so identifying significant subsets of the requirements and saving them in different views also promotes an effective solution.
- 1 Overview
- 2 User Interface
- 3 Traceability Matrix View Operations
- 3.1 Create new matrix view
- 3.2 Modify matrix view
- 3.3 Data Center Display issue in R4J tree view
- 3.4 Cloud Display issue in Jira view
- 3.5 Link two issues in matrix
- 3.6 Data Center Link multiple issues in matrix
- 3.7 Display link type
- 3.8 Delete link
- 3.9 Refresh matrix
- 3.10 Data Center Reset configuration
- 3.11 Cloud Export matrix
- 3.12 Data Center Export matrix
- 3.13 Data Center Page through matrix
- 3.14 Delete matrix view
- 3.15 Copy matrix view
- 3.16 Cloud Change status of matrix view
- 3.17 Cloud Reorder saved matrix views
- 3.18 Copy URL of matrix view
- 4 Known issues
User Interface
Traceability Matrix View
The view displays a two-dimensional matrix to show the links between requirements. Arrows appear in the intersections of the rows and columns where the corresponding requirements are linked. For example, if Requirements form the rows of the matrix and Specifications form the columns, then the arrows show which Specifications are linked to which Requirements. Above the matrix are buttons for managing the view.
A link shown as R -> C, where R is a row issue and C is a column issue, indicates that R has what Jira calls an “outward” link description to B. A link shown as R <- C indicates that R has what Jira calls an “inward” link description to B. Hovering over an arrow reveals the link description.
DATACENTER A red triangle to the right of the arrow indicates a suspect link.
A successful linking practice strongly depends on having a careful and consistent link type configuration, with intuitively meaningful link descriptions. See How to Configure Jira Links to support Traceability.
Data Center Active View
A panel to the left of the Traceability Matrix View displays the active traceability matrix and provides operations to save or copy it.
Saved Views
A panel to the left of the Traceability Matrix View provides a list of saved views and context menu operations to manage them. The views are organized into two folders according to their status:
Personal Views: These views are only available to the user that created them. By default, a newly created view is personal.
Public Views: These views are available to everyone who has access to the Jira project.
Traceability Matrix View Operations
Purpose | Operation |
|---|---|
Create new matrix view |
To determine the link descriptions, you should view the row issues as the subject of the relationship and the column issues as the object. For example, let’s suppose 1) the rows in a matrix are Requirements (R) and the columns are Specifications (S) and 2) the link type is Specification with the outward description “specifies” and the inward description “is specified by”. Then you would select the inward link description “is specified by”, because “R is specified by S”.
New views must be explicitly saved. |
Modify matrix view |
Modified views must be explicitly saved. |
Data Center Display issue in R4J tree view |
|
Cloud Display issue in Jira view |
|
Link two issues in matrix |
Data Center The dialog is a general linking dialog and in principle allows you to link to any issue. You may ignore the additional options to link to the designated issue in the matrix. |
Data Center Link multiple issues in matrix |
|
Display link type |
|
Delete link |
|
Refresh matrix |
|
Data Center Reset configuration |
|
Cloud Export matrix |
|
Data Center Export matrix |
|
Data Center Page through matrix |
|
Delete matrix view |
|
Copy matrix view | Cloud
The view is saved as a private view by default. Data Center
|
Cloud Change status of matrix view |
|
Cloud Reorder saved matrix views |
|
Copy URL of matrix view | Cloud
Data Center
|
Known issues
Cloud There is a possibility of encountering a 429 Error in the traceability matrix view. Read more here: https://easesolutions.atlassian.net/wiki/spaces/R4JC/pages/2197127173.