Overview
The Whole RTM (Requirements Traceability Matrix) PowerSheet provides a comprehensive five-tier view spanning customer requirements through system, subsystem, and design requirements down to verification test cases. This sheet enables safety engineers, requirements managers, and auditors to validate bidirectional traceability across the entire V-model hierarchy required by ISO 26262 Part 8 Clause 6.
Open the Whole RTM Sheet
- Navigate to Solution Template space from the sidebar
- Click Whole RTM Sheet in the document list
- Wait for PowerSheet to load the multi-tier traceability view (typically 5-15 seconds for projects with 100+ requirements)
The sheet loads with all requirements expanded by default, showing the complete traceability chain.
Understanding the Five-Tier Layout
The Whole RTM organizes requirements into five color-coded column groups representing the V-model decomposition:
Each tier represents one relationship expansion in the RTM domain model:
- Customer Requirements (green): Top-level user needs and specifications
- System Requirements (purple): System-level functional requirements (expanded via
refines link)
- Subsystem Requirements (teal): Component-scoped requirements (expanded via
refines link)
- Design Requirements (blue): Implementation-level specifications (expanded via
refines link)
- Verification Tests (orange): Test cases that verify design requirements (expanded via
verifies link)
Navigate the Traceability Hierarchy
Collapse/Expand Column Groups
Click the column group header to collapse entire tiers:
- Click Customer Requirements header → collapses to show only customer requirement titles
- Click System Requirements header → collapses to show only system requirement descriptions
- Repeat for any tier to maximize screen space while maintaining context
Collapsed groups display their collapseTo field (typically title or description) to preserve traceability context.
Group by Document
Use the hidden grouping column to organize requirements by source document:
- Right-click any column header → Group by → Document
- Requirements automatically organize into collapsible document sections
- Click document name to expand/collapse all requirements from that specification
This pattern is essential for multi-document projects where System Requirements Specification is split across subsystems or features.
Focus on Specific Requirements
Use the PowerSheet filter bar to isolate requirements:
- Filter by Classification →
SC or CC to show only safety-critical or conformance-critical requirements
- Filter by Status →
approved to show only baselined requirements
- Filter by ASIL (if visible) →
ASIL C or ASIL D to show high-integrity requirements
Use Tab to move between cells horizontally (across tiers) and ↓/↑ arrows to move vertically between requirements. This enables rapid visual scanning of traceability chains without mouse clicks.
Verify Traceability Completeness
Identify Missing Links
Empty cells in the RTM indicate traceability gaps:
- Empty system requirements cell → customer requirement not yet refined to system level
- Empty design requirements cell → subsystem requirement missing detailed design decomposition
- Empty verification tests cell → design requirement without verification evidence
Do NOT create placeholder work items just to fill empty RTM cells. Instead, create substantive requirements/tests with proper technical content, or acknowledge the gap as intentional scope limitation in gap analysis reports.
Check Cardinality
Valid traceability chains may have multiple items per tier:
- One customer requirement → three system requirements (decomposition)
- One system requirement → two design requirements (alternate implementations)
- One design requirement → four verification test cases (multiple test scenarios)
Each relationship creates a new sub-row in the PowerSheet, expanding the grid vertically.
Cross-Reference Coverage Metrics
Compare RTM visual inspection with automated coverage reports:
- Open Home Dashboard from sidebar
- Scroll to Traceability Coverage section
- Compare coverage percentages with RTM empty cells:
- “System Reqs → Design Reqs: 78%” should match ~22% empty design requirement cells
- “Design Reqs → Test Cases: 100%” should show zero empty test case cells
Discrepancies indicate either RTM query parameter issues or stale cache (refresh PowerSheet with Ctrl+F5).
Create Missing Work Items Inline
The Whole RTM supports inline entity creation to close traceability gaps without leaving the sheet:
Create System Requirements from Customer Requirements
- Locate customer requirement with empty system requirements cell
- Click the empty cell in the System Requirements column
- PowerSheet displays entity factory picker → select System Requirement
- Enter title and press
Enter → new system requirement created in the configured SRS document
- Link automatically created with
refines relationship
Create Verification Test Cases from Design Requirements
- Locate design requirement with empty verification test cell
- Click the empty cell in the Verification Tests column
- Select Verification Test Case from picker
- Enter test case title → new test case created in Testing/DesignVerificationSpecification
- Link automatically created with
verifies relationship
Inline creation places work items in pre-configured target documents defined in the PowerSheet YAML entityFactory section. If new work items appear in the wrong document, contact your configuration manager to update the entity factory target document paths.
Export for Audits
Generate static RTM snapshots for ISO 26262 compliance audits:
- Open Whole RTM Sheet
- Apply filters to show only approved requirements (Status =
approved)
- Click Export button (top-right toolbar) → Excel
- PowerSheet exports all visible rows with formatting preserved
- Save as
RTM_Baseline_<date>.xlsx for audit package
Alternatively, use Print to PDF for read-only audit evidence with watermarked headers showing export timestamp.
Comparison with Component RTM Sheet
| Feature | Whole RTM | Component RTM |
|---|
| Scope | All requirements across project | Single component/subsystem |
| Tiers | 5 (Customer → System → Subsystem → Design → Tests) | 3 (System → Subsystem → Design) |
| Use Case | Project-wide traceability validation, audit preparation | Focused subsystem design review |
| Performance | Slower load for large projects (>500 requirements) | Fast load (scoped to component) |
| Document Filter | None (shows all documents) | Filtered by component document parameter |
Use Whole RTM for comprehensive traceability validation; use Component RTM for day-to-day subsystem engineering work.
Verification Steps
After configuring filters and grouping, verify the RTM is displaying correctly:
- All five tiers visible with color-coded headers (green/purple/teal/blue/orange)
- No error messages in PowerSheet status bar (bottom-left)
- Requirement counts match dashboard statistics (±5% for multi-document rounding)
- Empty cells highlight gaps that align with coverage percentage metrics from Home Dashboard
- Inline creation works when clicking empty cells (entity factory picker appears)
See Also