Purpose and Scope
The Design Verification Sheet supports design engineers and V&V engineers in:
- Tracking verification coverage — ensuring every design requirement has linked verification test cases
- Managing verification evidence — organizing test results and audit trail artifacts per test case
- Progressive disclosure workflow — expanding from requirements to tests to evidence on demand
- Cross-document verification — linking design requirements from Design space to test cases in Testing space
- Audit compliance — maintaining complete traceability for ISO 26262 functional safety reviews
Use this sheet when:
- Planning design-level verification activities (Part 4 §5.6 requirements)
- Reviewing verification test coverage before formal reviews
- Documenting verification evidence for design specifications
- Creating verification test cases directly from design requirements
- Tracking verification status across component and subsystem design documents
Sheet Architecture
Visual Organization
Column Groups
| Column Group | Color | Purpose | Collapsible |
|---|
| Design Requirements | Blue (#0277bd / #01579b) | Primary entity display (ID, title, type, rationale) | Yes → collapses to title |
| Verification Tests | Orange (#f57c00 / #e65100) | Linked test case metadata (ID, name, status) | Yes → collapses to title |
| Verification Evidence | Red (#d32f2f / #b71c1c) | External reference artifacts attached to test cases | Yes → collapses to description |
Configuration Properties
Source Query Configuration
| Property | Type | Value | Description |
|---|
entityType | string | DesignRequirement | Entity type queried from RTM model; queries all design requirements in current document |
currentDocumentContext | boolean | true | Constrains query to design requirements only from the currently viewed Polarion LiveDoc; prevents cross-document pollution |
documentFilters | array | ["Testing/DesignVerificationSpecification"] | Filters verification test case queries to only show test cases from this document path; ensures tests are organized in correct specification module |
Column Group: Design Requirements
| Property | Type | Value | Description |
|---|
header | string | Design Requirements | Column group label displayed in PowerSheet header |
color | object | { background: "#0277bd", darkBackground: "#01579b", text: "#fff" } | Blue semantic color for design phase per V-model convention |
collapseTo | string | title | When group is collapsed by user, only the title field remains visible; preserves context while saving screen space |
visible | boolean | true | Column group always visible by default |
columns | array | See Design Requirement Columns | Defines all fields displayed in this group |
Design Requirement Columns
| Column Name | Field | Type | Read-Only | Formatter | Keyboard Focus | Notes |
|---|
objectId | objectId | string | ✓ | readOnlyFormatter | No | Design requirement stable identifier (e.g., DR-001); prevents accidental edits |
title | title | string | ✓ | boldReadOnlyFormatter | Yes | Requirement title with bold styling; keyboard focus lands here when user enters requirements section |
type | type | enum | ✓ | readOnlyFormatter | No | Work item type (always DesignRequirement); read-only for data integrity |
description | description | text | ✓ | readOnlyFormatter | No | Detailed requirement text; read-only because requirements are authored in Design space, not in verification sheet |
rationale | rationale | text | ✓ | readOnlyFormatter | No | Why this requirement exists; provides context for verification planning |
Column Group: Verification Tests
| Property | Type | Value | Description |
|---|
header | string | Verification Tests | Expandable column group for linked verification test cases |
color | object | { background: "#f57c00", darkBackground: "#e65100", text: "#fff" } | Orange semantic color for verification activities per V-model test phase |
relationshipName | string | verificationTestCases | RTM model relationship traversed to reach linked test cases; allows multiple test cases per requirement |
relationshipTarget | string | verificationTestCase | Target entity type (VerificationTestCase work item) |
collapseTo | string | title | When collapsed, only test case title visible; enables summary view showing which tests cover each requirement |
multiItem | boolean | true | Allows many-to-many traceability: one design requirement can link to multiple test cases, each shown in separate sub-row |
entityFactory | object | See Entity Factory Configuration | Enables inline test case creation directly from sheet; creates new test cases in Testing/DesignVerificationSpecification module |
Verification Test Columns
| Column Name | Field | Type | Editable | Formatter | Notes |
|---|
objectId | objectId | string | No | readOnlyFormatter | Test case stable identifier (e.g., VT-023); read-only for traceability integrity |
title | title | string | Yes | boldFormatter | Test case name with bold styling; allows inline editing; hasFocus: true prioritizes keyboard input here |
status | status | enum | Yes | statusRenderer | Test case status (Planned, In Progress, Completed); editable for lifecycle management |
description | description | text | Yes | Default | Test execution description; multiLine: true allows detailed test procedure without column width constraints |
executionResult | executionResult | enum | Yes | passFailRenderer | Pass/Fail/Not Run status; color-coded (green/red) for quick scan |
Column Group: Verification Evidence
| Property | Type | Value | Description |
|---|
header | string | Verification Evidence | Third-level expansion showing external references attached to test cases |
color | object | { background: "#d32f2f", darkBackground: "#b71c1c", text: "#fff" } | Red semantic color distinguishing evidence artifacts from test data |
relationshipName | string | externalReferences | RTM model relationship from test case to evidence artifacts; enables audit trail |
relationshipTarget | string | externalReference | Target entity type (external reference work item or attachment) |
collapseTo | string | description | When collapsed, only evidence description visible; minimizes evidence clutter |
visible | boolean | true | Evidence columns visible by default; can be hidden via PowerSheet UI to focus on test planning |
Evidence Columns
| Column Name | Field | Type | Editable | Formatter | Notes |
|---|
artifactId | artifactId | string | No | readOnlyFormatter | Evidence artifact identifier or attachment name; read-only for audit compliance |
description | description | text | No | readOnlyFormatter | Evidence description (e.g., “Test execution log”, “Performance measurement report”); serves as collapse target |
type | type | enum | No | typeRenderer | Evidence type (Test Log, Screenshot, Report, Data File, etc.); visual indicator for artifact category |
uploadDate | uploadDate | date | No | readOnlyFormatter | Date artifact was attached; supports audit timestamp requirements |
Entity Factory Configuration
Test Case Creation
| Property | Type | Value | Description |
|---|
enabled | boolean | true | Enables inline test case creation; when disabled, users must navigate to Testing space to create test cases manually |
targetType | string | VerificationTestCase | Creates work item of type VerificationTestCase |
targetModule | string | Testing/DesignVerificationSpecification | Path to Polarion document where new test cases are created; ensures consistent organizational structure |
autoLinkRole | string | verifies | Automatically creates ‘verifies’ link from new test case back to design requirement |
defaultFieldValues | object | { status: "Planned", phase: "Design" } | Pre-fills new test case fields; speeds up test case creation |
Workflow
- User enters Design Verification Sheet with design requirements visible
- User expands Verification Tests column group
- User clicks “Create Test Case” button in orange column header
- Sheet creates new VerificationTestCase work item in Testing/DesignVerificationSpecification module
- Sheet automatically links new test case to design requirement via ‘verifies’ link role
- New test case appears in orange column group as a new sub-row ready for editing
Document Grouping and Filtering
| Property | Type | Value | Description |
|---|
groupBy | string | verificationTestCases.verificationTestCase.owningDocument | Groups rows by owning document of linked test case; when viewing multiple test documents, tests are organized by source specification |
groupByLabel | string | Document | Label shown in group header (e.g., “Document: DesignVerificationSpecification v3”) |
hiddenColumns | array | ["verificationTestCases.verificationTestCase.owningDocument"] | Hides the document column itself but retains groupBy behavior; prevents redundant column while preserving organizational structure |
sortOrder | string | ascending | Sorts groups and rows in ascending order by document name and requirement ID |
Progressive Disclosure Strategy
Expanded View (Full Detail)
Design Requirements | Req ID | Req Title | Req Description | Rationale
Verification Tests | Test ID | Test Title | Test Description | Status | Result
Verification Evidence | Evidence ID | Evidence Type | Description | Upload Date
Collapsed Requirements View
Design Requirements | Req Title
Verification Tests | Test ID | Test Title | Test Description | Status | Result
Verification Evidence | Evidence Type | Description
Summary View (Hidden via Named View)
Design Requirements | Req ID | Req Title
Verification Tests | Test ID | Test Title | Status
Verification Evidence | (hidden)
Read-Only Styling
| Formatter | Applied To | Visual Style | Purpose |
|---|
readOnlyFormatter | Design Requirement fields (objectId, type, description, rationale) | Grey background, non-editable text | Prevents accidental edits to traceability context; indicates that requirements are authored elsewhere |
readOnlyFormatter | Evidence fields (artifactId, uploadDate, type) | Grey background, non-editable text | Enforces immutability of audit evidence; maintains compliance with ISO 26262 evidence retention |
Visual Emphasis
| Formatter | Applied To | Visual Style | Purpose |
|---|
boldFormatter | Design Requirement title, Test Case title | Bold font weight (600) | Improves scannability; users can quickly identify key entities in large sheets |
boldReadOnlyFormatter | Design Requirement title | Bold + grey background | Combines emphasis with read-only indication; primary navigation field for keyboard users |
Status and Result Rendering
| Renderer | Field | Values | Color Coding | Purpose |
|---|
statusRenderer | verificationTestCases.status | Planned, In Progress, Completed, On Hold | Yellow / Blue / Green / Orange | Visual workflow indicator; helps identify blockers and progress |
passFailRenderer | verificationTestCases.executionResult | Pass, Fail, Not Run | Green / Red / Grey | Instant visual verification status; supports quick coverage assessment |
Keyboard Navigation
| Action | Key | Behavior |
|---|
| Enter design requirement section | ↓ from column header | Focus moves to first design requirement title field (hasFocus: true) |
| Edit design requirement title | F2 or Double-click | Title field enters edit mode; typically read-only so no effect |
| Move to verification test section | Tab | Focus moves to first linked test case ID |
| Edit test case title | Tab / F2 | Test case title field (hasFocus: true in orange group) becomes active; users can type test name |
| Add multiline test description | Shift+Enter | In description field with multiLine: true, creates line break without exiting field |
| Create new test case | Alt+Insert | Triggers entity factory; creates new test case in Testing/DesignVerificationSpecification |
| Collapse column group | Ctrl+- (minus) | Hides columns except collapseTo field (title for tests, description for evidence) |
| Expand column group | Ctrl++ (plus) | Shows all columns in group |
Common Workflows
Planning Design Verification
- Open Design Verification Sheet for target design requirement document (e.g., “Camera Module Design Requirements”)
- Review Design Requirements column group; verify all requirements visible
- Expand Verification Tests column group
- For each requirement without linked test cases:
- Click “Create Test Case” in orange header
- Enter test case title and description
- Sheet automatically links to requirement via ‘verifies’ role
- Save PowerSheet; new test cases appear in Testing/DesignVerificationSpecification
Tracking Test Execution
- Open Design Verification Sheet
- Expand Verification Tests and Verification Evidence column groups
- For each test case:
- Update Status field (Planned → In Progress → Completed)
- Record Result (Pass/Fail/Not Run)
- Attach evidence artifacts (test logs, screenshots, reports)
- Review Verification Evidence column to confirm all tests have supporting artifacts
- Generate verification traceability report for design review
Reviewing Verification Coverage
- Open Design Verification Sheet
- Switch to Summary View (if named view exists)
- Scan Design Requirement ID and Verification Tests count columns
- Identify requirements with zero linked test cases
- Use PowerSheet gap query to drill into uncovered requirements
- Create missing test cases via entity factory or Testing space
RTM Model Integration
The Design Verification Sheet depends on these RTM model entities and relationships:
| Entity Type | Role | Purpose |
|---|
DesignRequirement | Source | Primary query entity; defines all rows shown in blue column group |
VerificationTestCase | Target | Linked test cases displayed in orange column group; traversed via verificationTestCases relationship |
ExternalReference | Evidence | Audit trail artifacts displayed in red column group; linked from test cases via externalReferences relationship |
| Link Role | Direction | Cardinality | Purpose |
|---|
verifies | VerificationTestCase → DesignRequirement | Many-to-Many | Defines traceability from design requirements to verification test cases; supports ISO 26262 Part 4 verification coverage |
externalReferences | VerificationTestCase → ExternalReference | One-to-Many | Attaches evidence artifacts (test logs, reports, sign-off) to test cases; maintains audit trail |
Relationship to Other PowerSheets
| Related Sheet | Relationship | Use Case |
|---|
| System Verification Sheet | Parallel workflow | System-level verification; feeds up to design verification |
| Subsystem Verification Sheet | Parent level | Subsystem requirements decompose to design requirements; subsystem verification covers design tests |
| Component Characteristics Sheet | Data source | Design characteristics link to failure modes; verification of characteristics supports design FMEA coverage |
| Whole RTM Sheet | Traceability context | Shows full V-model decomposition; Design Verification Sheet is focused view of design → test layer |
Compliance References
| Standard | Applicable Clause | Evidence | Notes |
|---|
| ISO 26262-4 | §5.6 (Design verification) | Design Verification Sheet linking design requirements to verification test cases | Supports demonstration that design correctness verified per methodology |
| ISO 26262-8 | §6 (Bidirectional traceability) | verifies link role from test cases back to requirements | Enables traceability reporting for safety case review |
| ISO 26262-1 | §7.4.2 (Work products) | Verification test case records with status, result, and evidence | Design verification plan and report work products |
| IATF 16949 | §5.1.2 (Design review) | Design Verification Sheet evidence audit trail for PPAP level 3 | Supports Design Failure Mode Prevention Activity (DFMEA) reviews |
Design Requirement fields (ID, title, description) are read-only in this sheet because requirements are authored in Design space. Edit requirements directly in their source document or via Design Requirements PowerSheet. This sheet is for verification planning and tracking only.
When multiple design verification specifications exist (e.g., one per component), the sheet groups rows by owning document. Users can expand individual document groups to focus on verification for a single component without navigating between documents.
