Configuration Overview
| Configuration | Root Entity | Purpose | Key Feature |
|---|
| Whole RTM Config | UserNeed | Full requirements traceability matrix | 5-level deep expansion with V&V |
| Component RTM | SystemRequirement | Per-component requirements view | Current-document constraint |
| Design Verification Sheet | DesignRequirement | Design-level V&V traceability | entityFactory for in-sheet test creation |
| System Verification Sheet | SystemRequirement | System-level V&V traceability | Parallel to Design Verification |
| User Need Validation Sheet | UserNeed | Validation traceability | Uses validates link role |
| Use Steps Specification | UseStep | Use step to user need mapping | IEC 62366 usability traceability |
| Process Steps | ProcessStep | Process step to component mapping | PFMEA support |
Color Scheme
All powersheet configurations use a consistent color-coded header scheme:
| Entity Domain | Header Style | Color |
|---|
| User Needs | darkgreen / green | Green |
| System Requirements | darkpurple / purple | Purple |
| Design Requirements | darkblue / blue | Blue |
| Test Cases | darkorange / orange | Orange |
| Evidence / References | darkred / red | Red |
Whole RTM Config
File: Whole RTM Config.yaml
The master traceability matrix showing the complete V-model from User Needs through Design Requirements, with V&V test columns at each level.
Source Query
from: UserNeed
expand:
- chapter
- useSteps -> useStep
- systemRequirements -> systemRequirement
-> designRequirements -> designRequirement
-> testCases -> testCase
-> testCases -> testCase
- testCases -> testCase
Column Groups
| Group | Entities | Collapse Target |
|---|
| User Needs | Chapter, Use Steps, User Need ID/Title/Description | description |
| System Requirements | Sys Req ID/Title/Description/Document, Verification Tests | systemRequirements.systemRequirement.description |
| Design Requirements | Des Req ID/Title/Description/Document, Verification Tests | designRequirements.designRequirement.description |
Predefined Views
| View | Hidden Columns | Purpose |
|---|
| Without V&V | All test case columns | Requirements-only view |
| Summary | Rationale, outline numbers, use steps, tests, descriptions, documents | Compact overview |
Key Features
- Chapter-based
groupBy with outlineNumber sorting
- Multi-item expansion for use steps and test cases
- Hidden columns for subsystem, document type, and object ID (revealed for cross-subsystem analysis)
- Searchable document selection with
list.search on title and moduleName
Component RTM
File: Component RTM.yaml
A document-scoped view showing system requirements with bidirectional traceability to user needs (up) and design requirements (down).
Source Query
from: SystemRequirement
constraints:
applyCurrentDocumentTo: SystemRequirement
expand:
- userNeeds -> userNeed
- designRequirements -> designRequirement
applyCurrentDocumentTo constraint limits results to system requirements in the currently open Polarion document, making this sheet context-aware for per-component views.
Key Differences from Whole RTM
- No test case columns (focused on requirements chain only)
- No predefined views (single default presentation)
- No
sortBy defined (uses default query order)
Design Verification Sheet
File: Design Verification Sheet.yaml
Maps design requirements to their verification test cases and external evidence references.
Source Query
from: DesignRequirement
parameters:
documentFilters:
VerificationTestCase: Testing/DesignVerificationSpecification
expand:
- verificationTestCases -> verificationTestCase
-> externalReferences -> externalReference
Key Features
- entityFactory with
modulePath: Testing/DesignVerificationSpecification enables in-sheet creation of test cases
- documentFilters prevents cross-specification contamination
- Read-only design requirement columns with
boldreadOnly custom style (grey background, bold font)
- Document-based
groupBy and sorting
- Description column labeled as “Rationale”
System Verification Sheet
File: System Verification Sheet.yaml
Parallels the Design Verification Sheet at the system requirement level.
Source Query
from: SystemRequirement
parameters:
VerificationTestCase: Testing/SystemVerificationSpecification
expand:
- verificationTestCases -> verificationTestCase
-> externalReferences -> externalReference
Key Features
- Structurally identical to Design Verification but rooted at
SystemRequirement
multiLine: true on test case title (unique to this sheet)- entityFactory targets
Testing/SystemVerificationSpecification
- Together with Design Verification, provides complete V&V coverage across both requirement levels
User Need Validation Sheet
File: User Need Validation Sheet.yaml
Maps user needs to their validation test cases and evidence, completing V&V coverage at the top of the requirements hierarchy.
Source Query
from: UserNeed
orderBy: title asc
expand:
- chapter
- validationTestCases -> validationTestCase
-> externalReferences -> externalReference
Key Features
- Uses
validationTestCases (not verificationTestCases) — implements ISO 14971 distinction between validation (user needs) and verification (requirements)
- Chapter-based
groupBy for document structure preservation
- No
entityFactory — validation test cases must be created in source documents first
- No document filtering — all user needs across all documents are included
Use Steps Specification
File: Use Steps Specification.yaml
Maps use steps to the user needs they address, supporting IEC 62366 usability engineering traceability.
Source Query
from: UseStep
orderBy: title asc
expand:
- userNeeds -> userNeed
Key Features
- Both column groups use green styling (uniform color signals same domain)
- Editable columns (no
isreadOnly flags) — use steps and user needs can be edited in-sheet
- Visualizes the
address link role from the RTM model
Process Steps
File: Process Steps.yaml
Maps process steps to their associated system elements for PFMEA analysis support.
Source Query
from: ProcessStep
orderBy: title asc
expand:
- systemElements -> systemElement
Key Features
- System Elements displayed as
multiItem in a single cell (compact list view)
- Supports the
ProcessStep-to-SystemElement associates relationship from the RTM model
- Derived from Use Steps Specification template (internal IDs reference
useSteps/userNeeds)
The collapseTo for the System Elements group references userNeeds.userNeed.title, which is inherited from the Use Steps template and does not match any column in this sheet.
| Formatter | Expression | Effect |
|---|
boldTitle | true (unconditional) | Bold styling on key columns |
readOnly | true (unconditional) | Read-only styling on reference columns |
boldreadOnly | grey100 background + fontWeight 600 | Combined bold + read-only (verification sheets) |
