Skip to main content
Industry context: Medical device manufacturers must demonstrate that user needs trace through system requirements to design requirements, with validation evidence (did we build the right thing?) and verification evidence (did we build it right?) at each level. Regulatory submissions to FDA and Notified Bodies require this traceability chain. diagram

​
Domain Model

Three core entity types forming the requirements V-model, plus use steps for operational context and test case links for V&V evidence. 
domainModelTypes:
  Document:
    properties:
      type:
  Chapter:
    polarionType: heading
  UserNeed:
    polarionType: userNeed
    properties:
      outlineNumber:
      description:
      severity:
      component:
      type:
  SystemRequirement:
    polarionType: systemRequirement
    properties:
      outlineNumber:
      description:
      classification:
  DesignRequirement:
    polarionType: designRequirement
    properties:
      outlineNumber:
      description:

relationships:
  - from: UserNeed
    to: SystemRequirement
    cardinality: one-to-many
  - from: SystemRequirement
    to: DesignRequirement
    cardinality: one-to-many
  - from: UserNeed
    to: UseStep
    cardinality: one-to-many

​
Sheet Configuration — Whole RTM

The whole-project RTM expands all three levels with V&V branches at each, using color-coded column groups for visual orientation. 
columnGroups:
  userNeeds:
    groupName: User Needs
    groupStyle: darkgreen
    headerStyle: green
    collapseTo: title
  systemRequirements:
    groupName: System Requirements
    groupStyle: darkpurple
    headerStyle: purple
    collapseTo: systemRequirements.systemRequirement.description
  designRequirements:
    groupName: Design Requirements
    groupStyle: darkblue
    headerStyle: blue
    collapseTo: >-
      systemRequirements.systemRequirement
      .designRequirements.designRequirement.description

sortBy:
  - columnId: outlineNumber
    direction: asc

columns:
  outlineNumber:
    title: "#"
    width: 80
    formatter: readOnly
    columnGroup: userNeeds
  title:
    title: Title
    hasFocus: true
    width: 170
    formatter: boldTitle
    columnGroup: userNeeds
  description:
    title: Rationale
    width: 230
    columnGroup: userNeeds
  useSteps.useStep:
    title: Use Step
    multiItem: true
    width: 230
    columnGroup: userNeeds
  validationTestCases.validationTestCase:
    title: Validation Plan
    multiItem: true
    columnGroup: userNeeds
    header: &orange
      style: orange
  systemRequirements.systemRequirement:
    title: ID
    width: 100
    columnGroup: systemRequirements
  systemRequirements.systemRequirement.description:
    title: Description
    formatter: boldTitle
    width: 200
    columnGroup: systemRequirements
  systemRequirements.systemRequirement.verificationTestCases.verificationTestCase:
    title: Verification Plan
    multiItem: true
    columnGroup: systemRequirements
    header: *orange
  systemRequirements.systemRequirement.designRequirements.designRequirement:
    title: ID
    width: 100
    columnGroup: designRequirements
  systemRequirements.systemRequirement.designRequirements.designRequirement.description:
    title: Description
    formatter: boldTitle
    width: 200
    columnGroup: designRequirements
  systemRequirements.systemRequirement.designRequirements.designRequirement.verificationTestCases.verificationTestCase:
    title: Verification Plan
    multiItem: true
    columnGroup: designRequirements
    header: *orange

​
Source Configuration

The expand paths define how the RTM query traverses the entity hierarchy, pulling linked items from across multiple documents. V&V branches are nested at each level. 
sources:
  - id: "Powersheet RTM Template"
    title: User Need
    model: rtm
    query:
      from: UserNeed
    expand:
      - name: chapter
      - name: useSteps
        expand:
          - name: useStep
      - name: systemRequirements
        expand:
          - name: systemRequirement
            title: System Req.
            expand:
              - name: designRequirements
                expand:
                  - name: designRequirement
                    title: Design Req.
                    expand:
                      - name: verificationTestCases
                        expand:
                          - name: verificationTestCase
              - name: verificationTestCases
                expand:
                  - name: verificationTestCase
      - name: validationTestCases
        expand:
          - name: validationTestCase

​
Component-Scoped RTM

The same configuration pattern supports component-level views. Using applyCurrentDocumentTo, a single YAML config serves multiple SRS documents — each showing only the requirements belonging to that subsystem. 
# Component RTM -- reusable across subsystem SRS documents
sources:
  - id: "Powersheet RTM Template"
    title: System Req.
    model: rtm
    query:
      from: SystemRequirement
    constraints:
      applyCurrentDocumentTo: SystemRequirement
    expand:
      - name: userNeeds
        expand:
          - name: userNeed
            title: User Need
      - name: designRequirements
        expand:
          - name: designRequirement
            title: Design Req.

columns:
  objectId:
    title: ID
    formatter: readOnly
    width: 100
    columnGroup: systemRequirements
  description:
    title: Description
    width: 250
    hasFocus: true
    columnGroup: systemRequirements
  userNeeds.userNeed:
    title: User Needs
    multiItem: true
    width: 250
    columnGroup: systemRequirements
    header: &green
      style: green
  designRequirements.designRequirement:
    title: ID
    width: 100
    columnGroup: designRequirements
  designRequirements.designRequirement.description:
    title: Description
    width: 250
    columnGroup: designRequirements

​
Key Patterns

  • 3-level V-model hierarchy with V&V test case branches at each level — validation at user needs, verification at system and design requirements.
  • YAML anchors (&orange / *orange) for reusing header styles across V&V columns at multiple levels without repetition.
  • applyCurrentDocumentTo — a single YAML configuration serves multiple component SRS documents, each automatically scoped to its own requirements.
  • Cross-document tracing — the expand paths pull System Requirements from SRS documents and Design Requirements from DRS documents via the RTM model relationships.
  • Collapsible column groups — each group collapses to its key column for stakeholder-appropriate detail levels.
  • multiItem: true for V&V plan columns — renders multiple linked test cases as expandable lists within a single cell.

​
See Also