Skip to main content

Traceability Overview

diagram
These link roles implement the requirements decomposition and verification/validation chain:
Role IDForward LabelReverse LabelFromToCardinality
refinesRefinesis Refined bysysReq, desRequserNeed, sysReqmany-to-many
verifiesVerifiesis Verified bytestCasesysReq, desReqmany-to-many
validatesValidatesis Validated bytestCaseuserNeedmany-to-many
addressAddressis Addressed byuseStepuserNeedmany-to-many
The distinction between verifies and validates implements the ISO 14971 V&V separation: verification confirms a requirement is correctly implemented, while validation confirms a user need is met under real-world conditions.

These link roles create the risk assessment traceability graph connecting hazards, harms, risk records, failure modes, and risk controls:
Role IDForward LabelReverse LabelFromToCardinality
hasHazardhas Hazardis Hazard inriskRecordhazardmany-to-one
hasHarmhas Harmis Harm inriskRecordharmmany-to-one
hasCausehas Causeis Cause inriskRecord, failureModecausemany-to-many
assessesAssessesis Assessed byfailureModefunction, systemElement, processStepmany-to-many
assessesAssessesis Assessed byriskRecordfunction, systemElement, useStep, processStepmany-to-many
analyzedInis Analyzed inAnalyzesfailureModeriskRecordmany-to-many
mitigatesMitigatesis Mitigated bytask, riskControlfailureMode, riskRecordmany-to-many
The assesses link role has the most complex type constraint. It supports two distinct patterns:
  1. DFMEA pattern: failureMode assesses function, systemElement, or processStep
  2. HARA pattern: riskRecord assesses function, systemElement, useStep, or processStep

analyzedIn — DFMEA-to-HARA Bridge

The analyzedIn link role bridges DFMEA failure modes to HARA risk records, enabling cross-referencing between the two risk analysis methodologies. In risksheet configurations, this appears as the FMEA Reference / HARA Reference columns.
These link roles manage the product structure and requirement-to-control traceability:
Role IDForward LabelReverse LabelFromToConstraint
parenthas parentis parent ofAny typeSame typesameType='true'
allocatedTois Allocated tohas Allocatedfunction, failureMode, riskRecord, processStepsystemElementTyped
implementsImplementsis Implemented bytasksysReq, desReq, riskControlRule 1
implementsImplementsis Implemented bysysReq, desReqriskControlRule 2
The parent link enforces sameType='true', meaning only items of the same type can be hierarchically nested. A sysReq can be a child of another sysReq, but not of a userNeed. Cross-type hierarchy is handled by the refines link role instead.

implements — Two-Rule Structure

The implements link has two rules:
  1. Tasks implement requirements or controls: task —> sysReq / desReq / riskControl
  2. Requirements implement controls: sysReq / desReq —> riskControl
This creates bidirectional requirement-to-control traceability, visible in the HARA risksheet’s Requirements and Verification Evidence columns.
These link roles support defect tracking, change control, and follow-up actions:
Role IDForward LabelReverse LabelFromTo
detectedByis Detected byDetectsdefecttestCase
tracksTracksis Tracked bychangeRequestsysReq, desReq, riskRecord, failureMode, task, defect
followsUpFollows upis Followed up bytaskdefect, task, changeRequest

These link roles have no type constraints and apply to any work item type:
Role IDForward LabelReverse LabelConstraints
branched_fromis Branched fromhas BranchNone
derived_fromis Derived fromhas DerivedNone

The following table summarizes how link roles appear in risksheet column configurations:
RisksheetColumn TypeLink RoleTarget Type
HARAitemLink (L1)assessesuseStep
HARAitemLink (L2)hasHazardhazard
HARAitemLink (L4)hasHarmharm
HARAmultiItemLink (FMEA Ref)analyzedIn (backLink)failureMode
HARAtaskLinkmitigatesriskControl
DFMEAitemLink (L1)assessesfunction
DFMEAmultiItemLink (HARA Ref)analyzedInriskRecord
DFMEAtaskLinkmitigatestask
Risk Control PlanmultiItemLinkmitigatesriskRecord