Skip to main content

Dashboard Overview

The Design Space Dashboard displays design requirements, functions, characteristics, and their traceability to system requirements and test cases. It is organized using a purple color scheme (#4527a0/#0d47a1/#5e35b1/#7e57c2) with visual hierarchy indicators for system, subsystem, and component levels in the document tree.
The Design space consolidates all design-phase artifacts including design requirements, system functions, and design characteristics. It enables design engineers to track functional decomposition, allocate characteristics to failure modes, and verify design completeness against system requirements and test cases.

Dashboard Architecture Diagram

diagram

Dashboard Widgets

Space Banner

The Design Space Banner is a branded header widget displaying the space identity and description.
PropertyTypeDefaultDescription
Space Titlestring”Design”Primary heading for the Design space
Subtitlestring”Design Requirements, Functions, Characteristics — Decomposition and Verification”Descriptive subtitle explaining the space purpose
Primary Colorhex#4527a0Dark purple — primary brand color for Design space styling and icon backgrounds
Secondary Colorhex#5e35b1Medium purple — used for hover states and secondary UI elements
Icon Numberinteger3Material Design Icons reference for the space icon (typically a blueprint or component icon)
Collapse ControlbooleanfalseWhether the banner is initially collapsed

Artifact Statistics Bar

The Statistics Bar displays live work item counts for all design-phase artifact types using Lucene queries.
PropertyTypeQuery PatternDescription
Design Requirements Countmetrictype:desReqTotal count of Design Requirement work items in the project
Functions Countmetrictype:functionTotal count of Function work items (allocated to system elements)
Characteristics Countmetrictype:characteristicTotal count of Characteristic work items (tracked in Control Plan and Design FMEA)
Total DocumentsmetricmoduleFolder:'Design'Count of all LiveDoc modules (documents) in the Design space
Refresh Intervalduration30 secondsAuto-refresh period for live metric updates

Design Document Inventory Tree

The document inventory tree provides hierarchical navigation of all Design space documents, organized by system element structure.
PropertyTypeDefaultDescription
Space FilterstringDesignFilter documents to this Polarion moduleFolder (space) only
Hierarchy Column Headerstring”System Element / Document”Column label showing the hierarchical relationship
Expandable TreebooleantrueEnable tree expansion/collapse for system/subsystem/component levels
Icon StylingCSS class.icon-sys, .icon-sub, .icon-cmpPurple color scheme: system (#4527a0), subsystem (#5e35b1), component (#7e57c2)
Document Type ColumnstringDocument type icon + nameShows type (e.g., ‘DFMEA’, ‘Characteristics Sheet’)
Work Item CountintegerderivedTotal work items (artifacts) in each document

Traceability Coverage Metrics

The dashboard displays three critical coverage bars showing multi-level traceability through the V-model.

Design Requirements → System Requirements Coverage

PropertyTypeLink RoleDescription
Source Itemsquerytype:desReqAll Design Requirement work items
Target Link TypestringrefinesDesign requirements refine system requirements (same link role used for customer→system and system→design decomposition)
Link DirectionstringoutboundDirect links from design requirement to system requirement
Coverage Formulaexpressioncount(desReq with outbound refines link) / total(desReq)Percentage of design requirements with at least one upstream system requirement
Gap QueryLucenetype:desReq AND NOT linkedWorkItems:refines=TA*Find unlinked design requirements (missing upstream traceability)
Display FormatvisualProgress bar + percentage + counte.g., “12/15 (80%)“
Color CodeRGBGreen ≥80%, Yellow 50-80%, Red <50%Visual status indicator based on coverage threshold
Every Design Requirement must link to at least one System Requirement via the ‘refines’ relationship. This establishes the upstream traceability required by ISO 26262 Part 4 (System Design) and Part 5 (Hardware Design).

Design Requirements → Test Cases Verification Coverage

PropertyTypeLink RoleDescription
Source Itemsquerytype:desReqAll Design Requirement work items
Target Link TypestringverifiesTest cases verify design requirements
Link Directionstringbacklink (incoming)Backward links from test case to design requirement (nxLinkCoverage with backlink parameter)
Coverage Formulaexpressioncount(desReq with backlink from testCase via verifies) / total(desReq)Percentage of design requirements with at least one verification test case
Gap QueryLucenetype:desReq AND NOT backlinkedWorkItems:verifies=TA*Find unverified design requirements
Verification MethodsenumReview, Analysis, Simulation, TestingDesign requirements may be verified by any ISO 26262 method, with test cases (Testing method) showing here
Display FormatvisualProgress bar + percentage + counte.g., “15/15 (100%)“

SC/CC Design Requirements → Failure Modes Coverage (Multi-Hop Traceability)

PropertyTypeLink RoleDescription
Source Itemsquerytype:desReq AND classification.KEY:(sc cc)Design requirements classified as Safety-Critical or Cybersecurity-Critical
Hop 1: Design Req → Characteristicsrelationshiprefines (backlink)Characteristics refine design requirements, establishing the link between requirement properties and failure mode analysis
Hop 2: Characteristics → Failure Modesrelationshipassesses (backlink)Failure modes assess characteristics, showing what can fail and its impact
Coverage FormulaexpressionFor each SC/CC desReq: (1) find backlinked characteristics via ‘refines’, (2) check if those characteristics have backlinked failure modes via ‘assesses’, (3) count items with complete 2-hop pathPercentage of SC/CC design requirements with complete failure mode analysis coverage
Velocity ImplementationcodeManual nested #foreach loop (not using nxLinkCoverage macro, which only supports single-hop)Key configuration detail: nxLinkCoverage macro does not support multi-hop checks; dashboard uses custom Velocity script with nested item traversal
Gap QueryLucenetype:desReq AND classification.KEY:(sc cc)Manually inspect results to identify incomplete 2-hop paths (desReq → char → failureMode)
Display FormatvisualProgress bar + percentage + counte.g., “11/14 (78%)”
The SC/CC Design Requirements → Failure Modes coverage metric implements a custom Velocity script because the standard nxLinkCoverage macro only supports direct (single-hop) link counting. The script iterates through:
  1. Design requirements with classification.KEY:(sc cc)
  2. For each requirement, fetch backlinked characteristics (via refines)
  3. For each characteristic, check for backlinked failure modes (via assesses)
  4. Count SC/CC requirements with at least one complete path

Dashboard Properties Configuration

<nxSpaceBanner>
  <spaceId>Design</spaceId>
  <title>Design</title>
  <description>Design Requirements, Functions, Characteristics — Decomposition and Verification</description>
  <primaryColor>#4527a0</primaryColor>
  <secondaryColor>#5e35b1</secondaryColor>
  <iconNumber>3</iconNumber>
</nxSpaceBanner>

Statistics Bar Configuration

<nxStatsBar>
  <statItem>
    <label>Design Requirements</label>
    <query>type:desReq</query>
    <icon>📋</icon>
  </statItem>
  <statItem>
    <label>Functions</label>
    <query>type:function</query>
    <icon>⚙️</icon>
  </statItem>
  <statItem>
    <label>Characteristics</label>
    <query>type:characteristic</query>
    <icon>📊</icon>
  </statItem>
  <statItem>
    <label>Documents</label>
    <query>moduleFolder:'Design'</query>
    <icon>📁</icon>
  </statItem>
</nxStatsBar>

Document Inventory Configuration

<nxDocInventoryTree>
  <spaceFilter>Design</spaceFilter>
  <columnHeader>System Element / Document</columnHeader>
  <expandFirstLevel>true</expandFirstLevel>
  <iconStyle>
    <system>#4527a0</system>
    <subsystem>#5e35b1</subsystem>
    <component>#7e57c2</component>
  </iconStyle>
</nxDocInventoryTree>

Coverage Metrics Configuration

coverageMetrics:
  - id: desReq_sysReq
    name: "Design Req → System Req (refines)"
    sourceType: desReq
    linkRole: refines
    direction: outbound
    gapQuery: 'type:desReq AND NOT linkedWorkItems:refines=TA*'
    
  - id: desReq_testCase
    name: "Design Req → Test Cases (verified by)"
    sourceType: desReq
    linkRole: verifies
    direction: backlink
    gapQuery: 'type:desReq AND NOT backlinkedWorkItems:verifies=TA*'
    
  - id: sccc_failureMode
    name: "SC/CC Design Req → Failure Modes (via characteristics)"
    sourceFilter: 'type:desReq AND classification.KEY:(sc cc)'
    hop1: { role: refines, direction: backlink }
    hop2: { role: assesses, direction: backlink }
    customVelocity: true
The dashboard footer includes direct navigation links to related reports and analysis documents.
LinkTargetDescription
System Structure Navigatorreference/reports/system-structure-navigator.mdVisual system hierarchy diagram showing system → subsystem → component decomposition with function and characteristic allocations
Data Model Diagramreference/reports/data-model-diagram.mdEntity-relationship diagram showing work item types and link roles in the RTM domain model