Skip to end of metadata
Go to start of metadata


Relationships between issues in JIRA are built via linking issues with each other. Direct links of an individual issue can be displayed when users view issue detail. Indirect links can not be viewed; and a report listing all links between issues does not exist as a default JIRA function.

Indirect links can occur between issues when issue A is linked to issue B; and issue B is linked to issue C. Then issue A is linked to issue C indirectly. Indirect links are useful when doing change impact analysis and finding shortest path between issues.

It is sometimes necessary to report the differences between two traceability matrices; i.e when requirements baselines are updated.

Qualty models such as CMMI and ISO 15504 also mention traceability matrices or records in process areas. In tables below, the references from these models to traceability are summarized.

Since JIRA has already "Link" function, we have developed a plugin. With this plugin users can create and save traceability matrices and generate reports.

User Manual is here:   Traceability Matrix and Link Graph

Plugin is here: Atlassian Marketplace

 

 

Capabilities

(tick) Change Impact Analysis

(tick) Indirect links

(tick) Bi-directional traceability between issue types

(tick) Create and save traceability matrices as baselines

(tick) Compare baselines

(tick)ISO 15504 ve CMMI compatability 

 

 

 

 

 

 

 

CMMI
Process Area
 
Explanation
Traceability Matrix -Ä°zlenebilrilik Matrisi

Requirements Management

Technical Solution

Configuration Management

 

SP 1.4 Maintain Bidirectional Traceability of Requirements (

Traceability is 
particularly needed when assessing the impact of requirements changes on 
project activities and work products.)

Generate a requirements traceability matrix.

SP 1.3 Manage Requirements Changes (

Evaluate the impact of requirement changes from the standpoint of 
relevant stakeholders. 
Requirements changes that affect the product architecture can affect many 
stakeholders.)

SP 2.2 Establish a Technical Data Package

CM-Introductory Part

An example of a baseline is an approved description of a product that includes internally consistent versions of requirements, requirement traceability matrices, design, disciplinespecific
items, and end-user documentation.

 

 

    

 

 

ISO 15504
Process
Explanation
Traceability Record

ENG.2

ENG.3

ENG.4

ENG.5

ENG.6

ENG.7

ENG.2.BP5:

ENG.3.BP6:

ENG.4.BP4:

ENG.4.BP6:

ENG.5.BP5:

ENG.6.BP3:

ENG.7.BP5:

  • No labels