Skip to main content

​
Prerequisites

  • A project created from the Medical Device Safety Solution template
  • Requirements documents (User Needs, System Requirements, Design Requirements) populated
  • Understanding of the RTM domain model

​
Available PowerSheet Configurations

The solution includes these powersheet views in .polarion/nextedy/sheet-configurations/:
ConfigurationSource EntityPurposeColor Scheme
Whole RTM ConfigUserNeedComplete traceability matrix with V&VGreen / Purple / Blue / Orange
Component RTMSystemRequirementPer-component view with document scopingPurple / Blue
Use Steps SpecificationUseStepUse steps to user needs mappingGreen
Process StepsProcessStepProcess steps to system elements mappingGreen
User Need Validation SheetUserNeedValidation test cases with evidenceGreen / Orange / Red
System Verification SheetSystemRequirementSystem-level verification with evidencePurple / Orange / Red
Design Verification SheetDesignRequirementDesign-level verification with evidenceBlue / Orange / Red

​
Whole RTM Configuration

The master RTM view displays the complete traceability hierarchy from user needs through design requirements, with verification and validation test columns at each level.

​
Column Groups

diagram

​
Expansion Hierarchy

The Whole RTM source query expands 5 levels deep: 
UserNeed
  -> chapter (groupBy)
  -> useSteps -> useStep
  -> systemRequirements -> systemRequirement
      -> designRequirements -> designRequirement
          -> testCases -> testCase (Design Verification)
      -> testCases -> testCase (System Verification)
  -> testCases -> testCase (User Need Validation)

​
Predefined Views

ViewWhat It ShowsWhen to Use
DefaultAll columnsFull traceability analysis
Without V&VRequirements only (hides all test case columns)Requirements review meetings
SummaryIDs and titles only (hides rationale, descriptions, V&V)Executive overview

​
Key Configuration Properties

PropertyValueEffect
groupBychapter.titleGroups rows by document chapter
sortByoutlineNumber ascDocument-order display
collapseToColumn dot-pathControls collapsed group appearance
multiItemtrue (on useSteps, testCases)Shows multiple items per cell

​
Component RTM Configuration

A document-scoped view that shows system requirements with upward traceability to user needs and downward to design requirements. Key difference from Whole RTM: Uses applyCurrentDocumentTo: SystemRequirement constraint, limiting results to requirements in the currently open document.
FeatureWhole RTMComponent RTM
Source entityUserNeedSystemRequirement
Document scopingAll documentsCurrent document only
Test case columnsYes (3 levels)No
Column groups3 (green/purple/blue)2 (purple/blue)
Predefined views2 (Without V&V, Summary)None

​
Verification and Validation Sheets

Three parallel sheets provide focused V&V views at each level of the RTM hierarchy:

​
Common Structure

All three V&V sheets follow the same pattern:
  1. Requirements columns (read-only) — ID, Title, Rationale
  2. Test case columns (editable) — linked via verification/validation test cases
  3. Evidence columns — external references linked to test cases

​
Entity Factory (In-Sheet Creation)

The System Verification Sheet and Design Verification Sheet include entityFactory configurations:
SheetentityFactory.modulePathEffect
System VerificationTesting/SystemVerificationSpecificationCreate test cases directly into system verification document
Design VerificationTesting/DesignVerificationSpecificationCreate test cases directly into design verification document
User Need Validation(not configured)Test cases must be created in source documents first
Verification sheets use documentFilters or VerificationTestCase parameters to restrict which test cases appear. This prevents cross-specification contamination — system verification tests do not appear in the design verification sheet.

​
Customizing Views

​
Adding a Custom View

To add a view to any powersheet configuration:
  1. Open the .yaml file in .polarion/nextedy/sheet-configurations/
  2. Add a new entry under the views: section
  3. Specify which columns to show or hide using @all with -column exclusions:
views:
  My Custom View:
    - columnId1
    - columnId2
    - columnId3

​
Modifying Column Properties

Common column customizations:
PropertyDescriptionExample
widthColumn width in pixelswidth: 250
visibleShow or hide columnvisible: false
isreadOnlyPrevent editingisreadOnly: true
multiItemShow multiple linked itemsmultiItem: true
multiLineAllow text wrappingmultiLine: true
formatterApply visual formattingformatter: boldTitle
groupByGroup rows by this columngroupBy: true

​
YAML Anchors for Style Reuse

PowerSheet supports YAML anchors for sharing styles across columns: 
columns:
  testCase1:
    header:
      style: &orange
        backgroundColor: orange
  testCase2:
    header:
      style: *orange  # Reuses the orange style

​
Formatters and Styles

The solution defines these reusable formatters:
FormatterExpressionEffect
boldTitletrue (unconditional)Bold text on all cells
readOnlytrue (unconditional)Grey read-only appearance
boldreadOnlytrue (unconditional)Bold + grey100 background + fontWeight 600

​
Next Steps

Configurations: .polarion/nextedy/sheet-configurations/Whole RTM Config.yaml, Component RTM.yaml, Use Steps Specification.yaml, Process Steps.yaml, User Need Validation Sheet.yaml, System Verification Sheet.yaml, Design Verification Sheet.yaml | Model: .polarion/nextedy/models/rtm.yaml