Versions Compared

Old Version 12

changes.mady.by.user Angelica Salazar

Saved on

compared with

New Version 13

changes.mady.by.user Angelica Salazar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Improved content
Section Column
width65%

Overview

The Traceability Matrix is an essential part of any Software development process, and hence irrespective of the size of the project, whenever there is a requirement to build a Software this concept comes into focus.

Requirements traceability matrix tracks every issue and links its relationships with other issues within a JIRA project.  You can easily identify the missing relationships and complexity of the artifacts.

Info
iconfalse
titleTraceability Matrix Knowledge
  • Read always from left to right (never follow the arrows)
  • The arrow identifies the direction: inward (arrow to left: Image Removed) or outward (arrow to top, Image Removed) relation
  • Red triangles on the right side of the arrows indicate suspect links
  • The mouse over hint gives you the description
Column
width30%
Panel
borderColor#dfe1e5
borderStylesolid

On this page:

Table of Contents
indent15px

Configure Rows and Columns

  • Open project in R4J
  • Select Traceability in navigation menu
  • Click on Configure View
    • Fill in required information:Row / Column Definition
  • Display Size: Max. number of issues to be included
    • Source: Select query type for issue search. Available options are:
  • Issue Types: Select all issues of specific type(s)
    • Filter: Select all issues of a specific Jira filter Only Managed Filters that appear

    Overview

    The Traceability Matrix 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 features displayed as rows and their related lower-level functional requirements as columns. Links can be created and deleted on the fly. The Traceability Matrix helps you to visualize complex relationships within a set of requirements and to quickly repair incorrect links.

    To navigate to the Traceability Matrix, open an R4J project and select the Traceability button at the top-right of the Tree View.

    Info

    It is important to understand that the effective use of the Traceability Matrix 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 coverage views can be defined and saved in the Coverage 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.

    Table of Contents

    Traceability Matrix Layout

    A panel on the left of the traceability view provides a list of saved views and buttons to manage the views. To open a view, select its name from the list of saved views. The rest of the traceability matrix displays the requirements included in the view.

    The requirements are arranged in a two-dimensional matrix. Arrows appear in the intersections of the rows and columns where the corresponding requirements are linked. For example, if customer features form the rows of the matrix and functional requirements form the columns, then the arrows show which functional requirements are linked to their customer features. The arrows show the direction of the link. A link shown as A → B indicates that A has what Jira calls an “outbound” link to B, while B has an “inbound” link to A. Red triangles to the right of the arrows indicate suspect links. Hovering over an arrow reveals the type of the link.

    Traceability Matrix Operations

    Purpose

    Operation

    Select items for new view

    If you do not select a saved view, you first select Configure View and then fill in the required information in the dialog to specify the requirements that appear in the rows and columns.

    By default the matrix size is limited to 20x20. A warning message is displayed if there are more items available. The size can be increased in the row and column definitions.

    The requirements are selected in one of three ways:

    • Specify the Issue Types to be used. For Source, select the option "Issues Types".

    • For Source, select the option "Filter" and provide the name of a saved Jira query.

    • For Source, select the option "JQL" and provide a query in the Jira Query Language.

    In the section Link Definition, specify the link types that are to be used. The Scope option determines if unlinked requirements are to be excluded from the matrix.

    Open issue in R4J tree view

    Select an issue key.

    • If the issue is contained in only one project tree, that project tree is opened in a new tab, with the selected issue displayed in the detail view.

    • If the issue is contained in multiple project trees, in the dialog select the project tree to be opened .

    • If the issue is not contained in any project tree, in the dialog confirm that you want to be redirected to the Jira issue view.

    Open issue in Jira

    Hover on an issue key and in the popup window select the issue key to open the Jira issue view page.

    Link an existing issue

    Hover on an empty cell and select the + icon to open the Link Existing Issues dialog, where you choose the link type and then proceed to create the new issue.

    Only Managed Filters in the following categories can be selected in the Filter picker: Filters shared with current requirements project, Filters

    in “My“

    in “My“, “Favorite“, and

    /or

    “Popular“.

  • JQL: Select all issues of a specific JQL query
  • Link Definition:
    • Link Types: Only display links of the selected type will be displayed
    • Scope: (Un-)check to only show issues that have a link between row and column
    • Note
    titleOn Display Size

    The traceability matrix has a default display size of 20 requirements for both row and column. If there are more items available than what is shown, a warning message will be displayed. 

    To see more data in the matrix, try modifying the display size value in the configuration dialog or set a more granular filter.

    Views

    The configuration of the traceability view can be stored in a view so that users do not have to define all of it every time they need to see it.

    To save a configuration as view, follow these steps:

  • Define configuration as described above
  • Click on Save view as in the left panel
    • Fill in

    Delete link

    Hover on an arrow and select it to open the Unlink Issue dialog, where you can unlink the issues.

    Display link type

    Hover on an arrow to display the link type.

    Refresh display

    Select Refresh to display the latest state of the requirements and their links.

    Clear configuration

    Select Clear to return to an empty view.

    Export

    Select the Export menu to save a view in an XML or Excel format.

    Saving Views

    The configuration of a matrix can be saved and reused.

    Purpose

    Operation

    Save new view

    Select the Save view as button in the left panel and fill in the required information:

    • Name:

     

    • Name of the view.

    • Visibility:

     Define

    • Specify if the view

    shall be

    • is private (available only

    for

    • to the currently logged in user) or public (

    for

    • available to all users with access to

    this requirements

    • the project)

    To load a previously stored configuration, follow these steps:

    1. Open project in R4J
    2. Select Traceability in navigation menu
    3. Select view in the left panel

    Export

    Once a view has been configured, it can be exported to either XML or Excel.

  • Open project in R4J
  • Select Traceability in navigation menu
  • Create or load view as described above
  • Click on Export
    • Select XML or Excel

    • .

    Save view

    Select the Save View button to save any changes made to an already saved view.

    Open saved view

    Select an existing view.

    Rename view

    Hover on the saved view's name, select "..." then select Rename and provide a new name.

    Delete view

    Hover on the saved view's name, select "..." then select Delete and confirm.

    Get URL

    Hover on the saved view's name, select "..." then select Get URL to get a shareable link to the view.