Skip to main content

​
Access the Component RTM Sheet

  1. Navigate to the Home Dashboard from the sidebar
  2. Scroll to the PowerSheets section
  3. Click on a component-specific RTM sheet (e.g., “Camera Module - Component RTM” or “Safety Co-Processor - Component RTM”)
  4. The PowerSheet opens in a two-column layout showing subsystem requirements (left) and design requirements (right)

​
Understand the Two-Tier Layout

The Component RTM Sheet displays requirements decomposition in a hierarchical view: diagram Left section (Teal): Subsystem requirements with upward links to parent system requirements
Right section (Blue): Design requirements that implement each subsystem requirement, with document location
  1. Expand/Collapse Column Groups: Click the column group header to toggle between full view (all columns) and summary view (key fields only)
    • Subsystem requirements collapse to show only the description
    • Design requirements collapse to show only the description field
  2. View Upward Traceability: The “System Requirements” column (green header) shows which system-level requirements each subsystem requirement refines
    • Multiple system requirements may appear for one subsystem requirement
    • Click the requirement ID to navigate to the parent requirement
  3. Check Design Requirement Details: The right section shows:
    • Design Requirement ID: Unique identifier (e.g., DRS-201)
    • Description: Detailed implementation specification
    • Type: Functional, interface, performance, safety, etc.
    • Document: Which Design Requirements Specification contains this requirement
Use the Type column to filter design requirements by category. For example, filter to “safety” type to audit safety-critical implementation requirements linked to safety-classified subsystem requirements.

​
Create New Design Requirements Inline

The Component RTM Sheet includes entity factory capability for efficient requirement authoring:
  1. Focus on a subsystem requirement row where you want to add a design requirement
  2. Click in the Design Requirement Description field in the right section
  3. Type the new requirement text and press Tab or Enter
  4. The system creates a new design requirement work item in the appropriate Design Requirements Specification document
  5. The new design requirement is automatically linked to the parent subsystem requirement via the designRequirements link role
Entity factory creates design requirements in the default DRS document configured for the component. If your project uses multiple DRS documents per component, verify the new requirement appears in the correct document using the Document column. If it’s in the wrong document, you’ll need to move it manually via Polarion work item actions.

​
Verify Traceability Completeness

Check that every subsystem requirement has at least one design requirement:
  1. Scan the right section for empty rows: Subsystem requirements with no design requirements will show blank cells in the design requirements section
  2. Check the upward traceability column: Verify each subsystem requirement links to at least one parent system requirement (green column should not be empty)
  3. Review requirement counts at the bottom status bar to confirm expected coverage
Expected coverage pattern:
  • 1 subsystem requirement → 1-5 design requirements (typical decomposition ratio)
  • If a subsystem requirement has 0 design requirements, it may be too low-level (should be a design requirement itself) or incomplete
Use the Component RTM Sheet in combination with the Whole RTM Sheet to see the complete V-model traceability chain from customer requirements down through system/subsystem/design requirements to verification test cases.

​
Use Document Context for Multi-Component Projects

In projects with multiple components, each component has its own RTM sheet:
  1. The sheet is scoped to the current document context: Only subsystem requirements from the open document appear
  2. Design requirements come from all linked DRS documents: The Document column shows which specification each design requirement comes from
  3. Document grouping organizes rows by source: If the sheet shows requirements from multiple subsystem specs, rows are grouped by parent document title with sort order applied
If you see unexpected subsystem requirements in the Component RTM Sheet, check the document query parameter. The PowerSheet may be configured to pull from multiple subsystem specification documents. Verify you’re viewing the correct component scope by checking the sheet title and document breadcrumb.

​
Verification Steps

You should now see:
  • A two-column layout with subsystem requirements (teal) on the left and design requirements (blue) on the right
  • Upward traceability links (green header) showing parent system requirements
  • Document location information for each design requirement
  • Ability to collapse/expand column groups for focused reading
  • Entity factory capability to create new design requirements inline

​
See Also