Skip to main content
The Design Engineer Dashboard is a role-specific dashboard in TestAuto2 — Automotive Safety Solution that serves design engineers performing ISO 26262 system-level and component-level design work.
This dashboard centralizes design requirements management, functional decomposition, characteristics allocation, and design-level failure mode analysis (DFMEA). It provides design engineers with real-time visibility into traceability coverage, design gaps, and verification status across all design artifacts.

Dashboard Overview

The Design Engineer Dashboard implements the design phase of the ISO 26262 V-model, combining:
  • Requirements refinement — System requirements decomposed into design requirements per system element
  • Functional allocation — Functions allocated to system elements (subsystems and components)
  • Characteristics management — Design characteristics (tolerances, performance parameters) linked to functions
  • Design failure analysis — Component-level DFMEA identifying design failure modes and safety controls
  • Verification traceability — Design requirements linked to design-level verification test cases

Dashboard Components

ComponentTypePurposeData Source
Design Space BannerHeaderBranded space identity with purple color scheme (#4527a0 system, #5e35b1 subsystem, #7e57c2 component)nxSpaceBanner macro
Design Artifact StatisticsKPI CardReal-time count of design requirements, functions, characteristics, and documents in Design spaceLucene query: type:(desReq function characteristic) filtered by moduleFolder=‘Design’
Design Document Inventory TreeNavigation TreeHierarchical document list organized by system element structure showing System Element / Document relationshipsnxDocInventoryTree macro with expandable tree view
System Requirements Refinement CoverageCoverage BarPercentage of design requirements properly linked upstream to system requirements via ‘refines’ relationshipnxCoverageBar: (desReq with outgoing ‘refines’ link) / total desReq
Design Requirements to Test Cases VerificationCoverage BarPercentage of design requirements verified by test cases via back-linked ‘verifies’ relationshipnxCoverageBar: (desReq with incoming ‘verifies’ backlink) / total desReq
SC/CC Characteristics to Failure ModesCoverage BarAdvanced traceability metric tracking safety-critical/cybersecurity-critical characteristics through DFMEA failure modesMulti-hop algorithm: SC/CC desReq → backlinks characteristics → backlinks failure modes
Design DFMEA Quick LinksNavigationDirect access to component-level DFMEA Risksheet documents and related DFMEA reports for each system elementLinks to …/Risks/[Component] DFMEA/ documents
System Structure NavigatorReport LinkAccess to system hierarchy visualization and design element decomposition structureLink to System Structure Navigator wiki page
Data Model DiagramReport LinkVisual representation of RTM domain model showing work item types and relationshipsLink to Data Model Diagram wiki page
Design Verification Sheet LinkPowerSheet LinkInteractive PowerSheet showing design requirements with linked test cases via ‘verifies’ roleLink to Design Verification Sheet PowerSheet configuration

Coverage Metrics

System Requirements Refinement Coverage

Query Logic:
Design Reqs with 'refines' link to System Reqs / Total Design Reqs
Gap Query: type:desReq AND NOT linkedWorkItems:refines=TA*
This metric ensures design requirements properly flow down from system-level requirements. A high coverage percentage (target 100%) indicates complete decomposition with full upstream traceability.

Design Verification Coverage

Query Logic:
Design Reqs with back-linked Test Cases via 'verifies' / Total Design Reqs
Gap Query: type:desReq AND NOT backlinkedWorkItems:verifies=TA*
This metric shows the percentage of design requirements that have associated verification test cases. ISO 26262 Part 4 requires 100% of design requirements to be verified (review, analysis, simulation, or testing).

SC/CC Characteristics to Failure Modes Multi-Hop Coverage

Algorithm:
  1. Query all design requirements with classification = ‘sc’ (safety-critical) or ‘cc’ (cybersecurity-critical)
  2. For each SC/CC requirement, find back-linked characteristics via ‘refines’ relationship
  3. For each characteristic, check if it has back-linked failure modes via ‘assesses’ relationship
  4. Coverage = (characteristics with assessed failure modes) / (total characteristics)
Gap Analysis Query:
type:desReq AND classification.KEY:(sc cc) AND 
NOT linkedWorkItems:refines=TA*
This identifies SC/CC design requirements without linked characteristics, indicating incomplete design decomposition for safety-critical features.
The nxLinkCoverage macro only supports single-hop traceability checks. Multi-hop coverage (requirement → characteristic → failure mode) requires custom Velocity scripts using nested #foreach loops to iterate through link relationships.

Configuration Properties

Velocity Macro Initialization

PropertyTypeDefaultDescription
nextedy_solutions.vmImportRequiredImports Nextedy Solutions macro library providing styled components (nxSpaceBanner, nxStatsBar, nxLinkCoverage, nxCoverageBar, nxDocInventoryTree)
#nxInit()InitializationRequiredInitializes Nextedy macro runtime environment and session context
#nxCommonStyles()CSS SetupRequiredInjects common CSS classes for Nextedy dashboard styling including purple color scheme and layout components

Dashboard Statistics Configuration

PropertyTypeDefaultDescription
Design Requirements Count QueryLucenetype:desReqLucene query to count design requirement work items in Design space
Functions Count QueryLucenetype:functionLucene query to count function work items allocated to system elements
Characteristics Count QueryLucenetype:characteristicLucene query to count characteristic (tolerance, performance parameter) work items
Design Documents CountFiltermoduleFolder='Design'Document inventory filtered to Design space folder showing all LiveDoc modules

Coverage Metrics Configuration

PropertyTypeDefaultDescription
Refinement Link RoleStringrefinesLink role used to connect design requirements to upstream system requirements (backward traceability)
Verification Link RoleStringverifiesLink role used to connect design requirements to test cases (verification relationship)
Characteristics Link RoleStringrefinesLink role connecting design requirements to characteristics via downward refinement
Failure Mode Link RoleStringassessesLink role connecting characteristics to failure modes in DFMEA analysis
Coverage ThresholdPercentage100%Target coverage for all metric bars (visual indicator: green ≥ threshold, yellow 75-99%, red < 75%)
Gap Query Drill-DownBooleantrueEnables clickable gap queries on coverage bars to drill down to uncovered items

Document Inventory Tree Configuration

PropertyTypeDefaultDescription
Space FilterStringDesignFilters document tree to Design space modules only
Column HeaderStringSystem Element / DocumentDisplay label showing hierarchical structure of design artifacts
Expandable TreeBooleantrueEnables expand/collapse functionality for nested system elements and their documents
Initial Expand LevelInteger1First level of system elements expanded on page load; deeper levels expand on click

Design Workflow Visualization

diagram
Source TypeLink RoleTarget TypeCardinalityPurpose
Design RequirementrefinesSystem Requirement1:NDesign requirement decomposes system requirement
Design RequirementverifiesDesign Verification Test Case1:NTest case verifies design requirement per ISO 26262 Part 4-6
Design RequirementrefinesCharacteristic1:NCharacteristic operationalizes design requirement tolerance/performance
CharacteristicassessesFailure Mode1:NCharacteristic degradation potential linked to DFMEA failure mode
System ElementcontainsDesign Requirement1:NDesign requirements scoped to system element (subsystem/component)
FunctionallocatedToSystem ElementN:1Function assigned to system element for implementation
CharacteristiccharacteristicFunctionN:1Characteristic measures performance or constraint on function

Dashboard Integration Points

Risksheet Documents (Component DFMEA)

The dashboard links to 8 component-level DFMEA Risksheet documents:
  • Camera Module - Component DFMEA (24 failure modes)
  • Radar Module - Component DFMEA (18 failure modes)
  • System-on-Chip (SoC) - Component DFMEA (22 failure modes)
  • Safety Co-Processor - Component DFMEA (7 failure modes)
  • Memory (Flash/RAM) - Component DFMEA (not yet documented)
  • CAN Transceivers - Component DFMEA (19 failure modes)
  • Sensor Housing Assembly - Component DFMEA (19 failure modes)
Each Risksheet displays failure modes with Severity/Occurrence/Detection ratings, post-mitigation Action Priority, and linked risk controls.

PowerSheet Configurations

PowerSheetPurposeLink
Design Verification SheetShows design requirements with verification test cases via ‘verifies’ backlinkssheet-configurations/Design Verification Sheet.yaml
Design Characteristics SheetExpands each design requirement with associated characteristics (target values, tolerances)sheet-configurations/Design Characteristics Sheet.yaml
System Structure NavigatorHierarchical view of system elements, functions, and allocated characteristicsreports/System Structure Navigator wiki page

Version and Compatibility

PropertyValue
Nextedy Solutions Minimum Version3.0+
Polarion Minimum Version2301.0+
ISO 26262 Compliance ScopePart 4 (System Design), Part 5 (Hardware Design)
Supported DFMEA LevelsSystem (SFMEA), Subsystem, Component (DFMEA)
Standard Link Rolesrefines, verifies, assesses, mitigates
  1. Ensure all design requirements have upstream system requirement links via ‘refines’ (100% coverage target)
  2. Create design verification test cases for all design requirements — ISO 26262 mandates 100% verification
  3. Link characteristics to design requirements to establish traceability through design decomposition
  4. Review SC/CC characteristics coverage to failure modes — safety-critical characteristics require DFMEA analysis
  5. Use the Design Verification Sheet PowerSheet to validate all design-level verification evidence