Overview
TestAuto2 — Automotive Safety Solution provides automated traceability coverage analysis through space dashboards and the Safety Readiness Scorecard. This guide shows you how to check coverage percentages, identify gaps, and interpret the metrics for compliance audits.
Check Coverage on Space Dashboards
Requirements Space Coverage
- Navigate to Documentation → Requirements from the sidebar
- Scroll to the Traceability Coverage section
- Review three key coverage metrics:
| Metric | What It Checks | Target |
|---|
| Customer → System Requirements | % of customerRequirement items with backlinked sysReq via ‘refines’ | ≥80% |
| System → Design Requirements | % of sysReq items with backlinked desReq via ‘refines’ | ≥70% |
| System → Test Cases | % of sysReq items with backlinked testCase via ‘verifies’ | ≥90% |
- ✅ Green percentage (coverage)
- Red count (gap items)
- Clickable gap link to see uncovered items
Click the red gap count to open a Polarion query showing exactly which work items lack required links. You can triage these items directly from the query results.
Design Space Coverage
- Navigate to Documentation → Design
- Check the Traceability Coverage section for:
- Design → System Requirements: Forward traceability (desReq links to sysReq via ‘refines’)
- Design → Test Cases: Verification coverage (desReq backlinked from testCase via ‘verifies’)
- SC/CC Design → Failure Modes: Safety-critical chain through characteristics
The SC/CC coverage metric requires a three-level chain: Design Requirement → (refines) → Characteristic → (assesses) → Failure Mode. A break at any level shows as uncovered. Use the gap query to find which characteristics lack FMEA analysis.
Risks Space Coverage
- Navigate to Documentation → Risks
- Review:
- Failure Modes → Risk Controls: % of failureMode items with linked riskControl via ‘mitigates’
- Hazards → Safety Goals: % of hazard items with linked safetyGoal via ‘derives’
Testing Space Coverage
- Navigate to Documentation → Testing or V&V
- Check:
- Validation Test Cases → Customer Requirements: Back-traceability via ‘validates’
- Verification Test Cases → System Requirements: Back-traceability via ‘verifies’
- Verification Test Cases → Design Requirements: Back-traceability via ‘verifies’
Check Overall Coverage with Safety Readiness Scorecard
Access the Scorecard
- From Home Dashboard, click Safety Readiness Scorecard in the Reports section
- Or navigate directly via sidebar: Documentation → Safety Readiness
Interpret the Compliance Matrix
The scorecard displays a table with per-standard metrics:
| Standard | Req % | Trace % | Verif % | FMEA % | Overall |
|---|
| ISO 26262 Pt 3 | 0% | 100% | 48% | N/A | 49% |
| ISO 26262 Pt 4 | 87.1% | 100% | 83.9% | 100% | 92% |
| ISO 26262 Pt 5 | 91.7% | 100% | 100% | 100% | 97% |
| AIAG-VDA FMEA | N/A | N/A | N/A | 94.2% | 94% |
| IATF 16949 | 73% | 60% | N/A | N/A | 60% |
Column Definitions
- Req %: Requirements with at least one outgoing link (any role) / total requirements of relevant type
- Trace %: Work items with any incoming OR outgoing traceability link / total items
- Verif %: Requirements with back-linked test cases via ‘verifies’ or ‘validates’ / total requirements
- FMEA %: Failure modes with post-mitigation Action Priority assigned / total failure modes
- Overall: Arithmetic mean of applicable metrics (N/A excluded)
- Green (≥80%): Compliant
- Orange (60-79%): Attention needed
- Red (<60%): Non-compliant
Use Whole RTM PowerSheet for Visual Coverage
Access the RTM Sheet
- From Home Dashboard, click Whole RTM Sheet in the PowerSheets section
- Or navigate: Documentation → PowerSheets → Whole RTM
Interpret the Four-Tier View
The RTM sheet displays a cascading matrix:
Empty cells indicate missing links:
- Blank System Req column → Customer requirement not refined
- Blank Subsystem Req column → System requirement not decomposed
- Blank Design Req column → Subsystem requirement not refined to design
- Blank Verification columns → Requirements not verified by test cases
A break in the decomposition chain (e.g., Customer → System → missing Subsystem → Design) prevents complete V-model traceability. ISO 26262 Part 8 requires continuous bidirectional traceability across all levels.
Check Coverage Programmatically
Using Lucene Queries
Copy the gap queries from dashboard source:
System requirements without verification:
type:sysReq AND NOT backlinkedWorkItems:verifies=TA*
type:desReq AND classification.KEY:(sc cc)
Using Velocity Macros
Access the macro source in .polarion/pages/nextedy_solutions.vm:
#nxLinkCoverage("sysReq" "testCase" "verifies" "back")
## Returns: $nxLcCovered, $nxLcTotal, $nxLcGaps
Coverage: ${nxLcCovered}/${nxLcTotal} (${nxLcGaps} gaps)
Verification Steps
You should now see:
- Space dashboards with green/orange/red coverage bars for each traceability chain
- Gap counts you can click to investigate specific uncovered work items
- Safety Readiness Scorecard showing per-standard compliance percentages with traffic light color coding
- Whole RTM PowerSheet with visual cascade showing decomposition and verification coverage
For ISO 26262 certification audits, export the Safety Readiness Scorecard to PDF and attach gap query results as evidence of traceability analysis. Auditors expect ≥90% coverage for safety-critical requirements at ASIL C/D.
See Also
