Skip to main content

​
Overview

The System Verification Sheet provides a comprehensive view of system requirements verification status across your Automatic Emergency Braking (AEB) system. Each row represents a System Requirement work item, expanded to show:
  • System Requirement (purple column group) — what must be verified
  • Verification Test Cases (orange column group) — how verification is performed
  • Verification Evidence (red column group) — proof of successful verification
This denormalized layout supports the ISO 26262 V-Model verification flow, where system-level requirements must have bidirectional traceability to test cases. diagram
Use this PowerSheet when you need to:
  • Establish traceability between System Requirements and Verification Test Cases
  • Track verification evidence for ISO 26262 audits
  • Plan testing activities at the system level
  • Monitor verification coverage for system-level requirements
  • Create new test cases directly from requirements without manual navigation

​
Configuration Properties

​
Source Query Configuration

PropertyTypeDefaultDescription
sourceEntityStringSystemRequirementRTM domain model entity type defining the root items displayed in left column group. Queries all SystemRequirement work items from current document context.
documentContextStringcurrentDocument scoping mode that limits query to work items in the currently viewed Polarion LiveDoc. Prevents cross-document requirement pollution.
documentFilterString—Optional constraint applied to verificationTestCases expansion to restrict test cases to a specific Testing space module. Example: moduleFolder='Testing/SystemVerificationSpecification'

​
Column Group: System Requirements (Purple)

Configuration for the left-side column group displaying requirement metadata.
PropertyTypeDefaultDescription
groupNameStringSystem RequirementsDisplay label shown in column group header
headerColorString#7B3FF2Purple hex color for section header and row background. Visual grouping color per Diataxis framework: purple = requirements (what must be met).
collapseToStringdescriptionPrimary field shown when column group is collapsed. Users can minimize requirements section to show only description while preserving row grouping.
visibleBooleantrueWhether column group is visible by default. Set to true for always-visible requirement metadata.

​
Requirement Metadata Columns

PropertyTypeDefaultDescription
objectIdString (read-only)—Requirement ID (e.g., SYSREQ-001). Maps to work item identifier in Polarion. Formatted with readOnlyFormatter for grey background. Prevents accidental edits during verification review.
titleString (read-only)—Requirement title text. Configured with boldReadOnlyFormatter for visual emphasis. Shows with grey background to indicate protected content. Serves as keyboard focus point when user enters requirement row.
descriptionString (read-only)—Full requirement description text. Read-only field preventing modification from verification sheet context (requirements are authored in Requirements space). Serves as collapseTo target for collapsed view.
classificationEnumeration (read-only)—Safety classification field. Examples: SC (Safety Critical) or CC (Critical Component) per ISO 26262. Read-only to prevent accidental classification changes during verification planning.

​
Column Group: Verification Test Cases (Orange)

First-level relationship expansion showing linked test cases.
PropertyTypeDefaultDescription
relationshipRoleStringverificationTestCasesRTM model link role traversed from SystemRequirement to reach VerificationTestCase entities. Defines how PowerSheet discovers linked test cases for each requirement.
groupNameStringVerification Test CasesDisplay label for test case column group header.
headerColorString#FF9800Orange hex color for section header and row background. Visual grouping per framework: orange = tests (how we verify).
collapseToStringtitlePrimary field shown when test case group is collapsed. Users can minimize test detail while preserving traceability view.
multiRowBooleantrueWhether multiple test cases per requirement display as separate sub-rows. Enables one-to-many requirement-to-test relationship visualization.

​
Verification Test Case Columns

PropertyTypeDefaultDescription
testCaseIdString (expandable)—Displays test case ID from expanded verificationTestCases relationship. Notation: testCases.testCase refers to objectId of VerificationTestCase work item reached through relationship expansion. Provides stable reference for test case traceability.
titleString (editable)—Test case title with hasFocus:true and multiLine:true configuration. Enables keyboard-driven test documentation without excessive clicking. MultiLine support allows detailed test descriptions within column without horizontal scrolling constraints.
statusEnumeration—Test case execution status. Typical values: Planned, In Progress, Passed, Failed. Serves as primary status indicator for verification planning and tracking workflows.

​
Column Group: Verification Evidence (Red)

Second-level relationship expansion showing external evidence artifacts linked to test cases.
PropertyTypeDefaultDescription
relationshipRoleStringexternalReferencesRTM model link role traversed from VerificationTestCase to reach evidence artifacts. Second-hop expansion enables complete audit trail: requirement → test → evidence.
groupNameStringVerification EvidenceDisplay label for evidence column group header.
headerColorString#D32F2FDark red hex color. Visual grouping per framework: red = evidence (proof of verification). Distinct color emphasizes evidence tier importance for compliance.
collapseToStringartifactPrimary field shown when evidence group is collapsed.
multiRowBooleantrueMultiple evidence artifacts per test case display as separate sub-rows. Supports multiple evidence files (test reports, logs, screenshots) per test case.

​
Evidence Columns

PropertyTypeDefaultDescription
artifactString—External reference artifact identifier or filename. Examples: test_report_v2.pdf, test_log_20250215.csv. Serves as evidence identifier for audit traceability.
evidenceTypeString—Enumeration indicating evidence category. Typical values: Test Report, Test Log, Screenshot, Measurement Data, Analysis Report. Helps categorize verification evidence for compliance audits.
referenceLinkURL (hyperlink)—Hyperlink to external evidence location (document repository, artifact store, issue tracker attachment). Enables one-click navigation to evidence source for verification review.

​
Entity Factory Configuration

The PowerSheet includes intelligent work item creation capability that streamlines test case creation workflow.
PropertyTypeDefaultDescription
entityFactoryConfiguration—Inline creation handler for new VerificationTestCase work items. When user creates test case link from requirement row, PowerSheet automatically creates new test case and links it to parent requirement.
targetModuleStringTesting/SystemVerificationSpecificationPolarion LiveDoc module where new test cases are created. This module path must match system specification convention. Example value shows System Verification test cases organized under Testing space. Must correspond to document structure in your project.
autoLinkBooleantrueAutomatically establish verificationTestCases link from requirement to newly created test case. Eliminates manual linking step; ensures consistent traceability setup.
workItemTypeStringVerificationTestCaseWork item type for created entities. Must be defined in project RTM domain model and correspond to active work item type in Polarion project.

​
Formatting and Display Configuration

​
Read-Only Field Formatting

Requirement fields use protective formatting to prevent accidental edits during verification review: 
Formatters:
  - readOnlyFormatter:
      Background: grey (#CCCCCC)
      TextStyle: regular
      EditProtection: enabled
      Purpose: Visual cue that field is view-only; prevents modifying requirement data from verification context

  - boldReadOnlyFormatter:
      Background: grey (#CCCCCC)
      TextStyle: bold
      EditProtection: enabled
      Purpose: Emphasizes key identifier fields (title, ID) while protecting from edits

​
Column Width Optimization

ColumnWidthRationale
Requirement ID120pxFixed width accommodates typical format (SYSREQ-001)
Requirement Title250pxOptimized for 1-2 line titles without truncation
Requirement Description400pxFull description text visible; users can expand for longer text
Test Case Title300pxMultiLine mode allows wrapped text; focus enabled for efficient documentation
Evidence Type150pxEnumeration values typically 20-30 characters

​
Document Grouping and Organization

PropertyTypeDefaultDescription
groupByFieldStringparentDocumentPowerSheet groups rows by source document. When working across multiple System Requirements Specifications (SRS), grouping provides organizational context boundaries.
groupVisibleBooleantrueDocument title group headers are visible, showing which specification contains each requirement. Helps users understand requirement origin when reviewing cross-document verification.
sortOrderStringascendingGroups sorted in ascending order by document name/ID. Provides consistent, predictable document ordering for verification review workflows.

​
Views Configuration

The PowerSheet includes multiple named views supporting different verification workflow phases:

​
Default View: Full Verification Traceability

Shows all column groups: System Requirements (purple), Verification Test Cases (orange), Verification Evidence (red). Use this view for comprehensive verification planning and evidence tracking.

​
Requirement Planning View

Hides evidence columns (red), showing only requirements and test cases. Use this view for initial test case planning without evidence artifact clutter.

​
Evidence Review View

Shows requirements and evidence only (no intermediate test case columns). Use this view for focused evidence audit where test case details are known.

​
Collapsed Summary View

Shows only requirement ID, title, test case count, and highest-priority evidence. Use for high-level verification status overview in reporting and management reviews. 
[SYSREQ-001 | Obstacle Detection at 40 km/h | 2 Tests | Evidence: 3]
[SYSREQ-002 | Timely Braking Response | 1 Test | Evidence: 2]

​
RTM Model Integration

System Verification Sheet depends on these RTM domain model entities and relationships:

​
Required Entity Types

EntityReferencePurpose
SystemRequirementwork item typeRoot entity; each row represents one system requirement from active document
VerificationTestCasework item typeLinked via verificationTestCases relationship; represents test case verifying requirement
ExternalReferencelink targetEvidence artifacts; linked from test cases via externalReferences relationship

​
Required Relationship Roles

RoleDirectionSourceTargetCardinality
verificationTestCasesoutboundSystemRequirementVerificationTestCase1..*
externalReferencesoutboundVerificationTestCaseExternalReference0..*

​
Document Filter Constraint

The documentFilter property restricts verification test case query: 
moduleFolder='Testing/SystemVerificationSpecification'
This constraint ensures that only test cases residing in the designated Testing space module are displayed, preventing cross-project test case pollution and maintaining document organization.

​
Workflow Integration

​
Creating New Verification Test Cases

  1. Open System Requirements document containing Polarion LiveDoc
  2. Click Add Test Case button in test case column group for desired requirement
  3. PowerSheet presents entity factory dialog with pre-populated:
    • Parent requirement link automatically set
    • Module destination: Testing/SystemVerificationSpecification
    • Work item type: VerificationTestCase
  4. Enter test case title, description, method, environment
  5. Click Create — PowerSheet creates test case and automatically establishes verificationTestCases link

​
Linking Existing Test Cases

  1. Click Link Test Case in test case column for requirement row
  2. Select existing VerificationTestCase from module browser
  3. PowerSheet establishes bidirectional link immediately
  4. Test case details populate in subsequent sub-rows

​
Adding Verification Evidence

  1. Navigate to test case row containing target test
  2. Click Add Evidence in evidence column group
  3. Provide evidence artifact reference (file path, URL, document ID)
  4. Enter evidence type enumeration (Test Report, Test Log, Screenshot, etc.)
  5. Click Link — PowerSheet creates externalReferences link

​
Verification Coverage Tracking

The System Verification Sheet contributes to ISO 26262 Part 4 verification coverage metrics:
MetricCalculationTarget
System Requirement Verification Coverage(SystemRequirements with ≥1 verificationTestCases backlink) / Total SystemRequirements100%
Test Case Evidence Coverage(VerificationTestCases with ≥1 externalReferences backlink) / Total VerificationTestCases90%+
Requirement-Evidence Chain Completeness(Requirements with complete chain: sysReq → test → evidence) / Total requirements80%+
  • Create verification test cases before executing verification activities
  • Link evidence artifacts immediately after test execution to maintain accurate status
  • Review uncovered requirements monthly during verification planning cycles
  • Use Collapsed Summary view for management reporting on coverage metrics
  • Coordinate with Testing space document owners to ensure test case organization

​
See Also