Skip to main content

​
Dashboard Purpose

The Design Engineer Dashboard aggregates design-focused metrics and work items relevant to design assurance activities under ARP 4754A and DO-254. It prioritizes:
  • Design requirement status and classification
  • Characteristic coverage across system elements
  • DFMEA assignment tracking
  • Change request and design verification status
  • User-filtered task queues (items assigned to current user)
The dashboard serves as the primary navigation hub for design engineers, with direct links to design-related PowerSheets and design space documents.

​
Key Metrics Panel

MetricPurposeData Source
Design Requirements (by Status)Tracks design req workflow state (draft/inReview/approved/published)Design requirement work items
Design Requirements (by Subtype)Classifies design reqs by engineering discipline: Electrical, Mechanical, Software, Labeling, UseabilitydesignRequirement.subType enum
Characteristic Coverage% of design requirements with linked characteristicsBackward-link coverage: desReq → characteristic
DFMEA Assignment% of design requirements linked to Design FMEA work itemsBackward-link coverage: desReq → failureMode (in DFMEA context)
Verification StatusTest cases linked per design requirement; pass/fail/not-run distributionTest execution status from testCase work items
Functions AllocatedNumber of functions allocated to system elements in the design spaceallocatedTo link: function → systemElement
Exact metric formulas and thresholds should be confirmed in the live dashboard — this page documents the conceptual structure based on available design requirement types and risksheet features.

​
Design Requirement Status

The Design Engineer Dashboard shows design requirement workflow status organized by document and system element hierarchy:
StatusDefinitionInterpretation
DraftDocument in initial creation; requirements under developmentOngoing work; may change structure
In ReviewDocument submitted for review; requirements undergoing peer/stakeholder reviewApproaching approval; changes expected from review feedback
ApprovedDocument formally approved; requirements baselinedFrozen for implementation; changes via change control
PublishedDocument released for implementationOfficial specification; traceable to design implementation
Status distribution bars show the proportion of design requirements in each state, helping identify specification bottlenecks.

​
Design Requirement Classification

Design requirements are classified by engineering subtype to organize work by discipline:
SubtypePurposeTypical Allocations
ElectricalElectrical system and hardware design requirementsSensor interfaces, power systems, bus interfaces
MechanicalMechanical system design requirementsStructural, thermal, mechanical interfaces
SoftwareSoftware design requirements and implementation specificationsFlight software, firmware, embedded algorithms
LabelingLabeling and documentation requirementsUser interface labels, procedural documentation
UseabilityUsability and human factors requirementsOperator interface, workload, training implications
Classification helps cross-functional teams focus on their respective engineering domains while maintaining traceability to system requirements.

​
Characteristic Coverage Analysis

Characteristics represent design properties, constraints, and implementation details that realize functions and satisfy design requirements. The dashboard tracks:
Coverage AspectMetricInterpretation
Overall Coverage %Design requirements with ≥1 linked characteristic / total design requirementsLower % may indicate incomplete design specification
By System ElementCharacteristics per component / design reqs per componentImbalance may indicate over/under-specification
Verification MappingCharacteristics with linked test cases / total characteristicsSupports design verification traceability
In the Aero1 reference project, 63 characteristics are defined across 8 components, supporting detailed design verification and DO-254 compliance objectives.

​
DFMEA Assignment and Risk Control Tracking

The Design Engineer Dashboard highlights design failure modes (DFMEA entries) linked to design requirements and risk controls:
ElementPurposeStatus Indicators
Design FMEA DocumentsRisk analysis at design level (component DFMEA) per system elementDocument approval status, work item count
Assigned Failure ModesDesign requirements with linked failure modesCoverage % (requirements → failure mode link)
Risk Control StatusRisk controls addressing design failure modesImplementation status: not-started, in-progress, complete
Post-Mitigation RPNResidual risk severity (Severity × Occurrence × Detection) after controls appliedColor coding: Red (>30, High), Yellow (11–30, Medium), Green (≤10, Low)
The dashboard flags design requirements without DFMEA coverage, supporting DO-254 design assurance planning. Design verification status is tracked through test case associations:
Link TypePurposeInterpretation
desReq → testCaseDesign requirement verificationTest case count per requirement
Test Execution StatusTest case state (pass/fail/not-run)Overall verification completeness
Verification MethodTest, Analysis, Inspection, Demonstration, ReviewPreferred method per test case
Test LevelUnit, Integration, System, Acceptance, QualificationDesign verification hierarchy
The dashboard aggregates pass/fail/not-run counts across design-linked test cases, indicating design verification progress.

​
Functions and System Element Decomposition

The Design Engineer Dashboard includes function allocation and system decomposition context:
EntityCount in Aero1Organization
Functions18 totalOrganized by subsystem (Sensor/Processing/Actuator); each function has detailed characteristics
System Elements (Design Focus)8 componentsADCI, IRU, PCIM, MFP, NVM, BITE Monitor, PSU, Bus Interface
Characteristics (Design Detail)63 totalComponent-level design properties; allocated to functions
The dashboard provides quick navigation to component-specific PowerSheets (Functions and Characteristics sheets) for detailed design work.

​
User-Filtered Work Queues

The Design Engineer Dashboard supports role-based filtering to show:
  • Design requirements assigned to current user (via Polarion user assignment)
  • Change requests affecting assigned design documents
  • Review tasks pending current user approval
  • Design verification items (test cases) assigned to current user
User filtering and assignment fields depend on Polarion project configuration. Confirm that design requirement work items have an owner/assignee field configured.
The Design Engineer Dashboard includes a right sidebar with links to:

​
Design Documents

  • Design Requirement Specifications (all spaces, system-element-organized)
  • Function Specifications (per subsystem)
  • Characteristics Specifications (per component)

​
Design PowerSheets

  • Whole RTM Sheet — Full traceability from customer to test
  • ARP 4754A Sheet — Assurance level decomposition with DAL classification
  • Design Verification Sheet — Design requirement to test case verification mapping
  • Component RTM — Component-level design detail with functions and characteristics
  • Functions/Characteristics Sheets — Per-component detailed design work

​
Design Analysis Reports

  • System Decomposition Report (design req distribution per component)
  • FMEA Coverage Gaps (characteristics without failure mode analysis)
  • Classification Consistency Report (design req classification completeness)
  • System Structure Navigator (interactive design element tree)

​
Standards and Process

  • V-Model Process Guide (design phase overview)
  • Certification Readiness Scorecard (design readiness per standard)
  • DO-254 Compliance Matrix (hardware design assurance objectives)

​
Dashboard Layout

diagram For detailed design information, see:

​
Source References

This page documents the Design Engineer Dashboard role view based on:
  • Polarion page configuration for role dashboards (page.xml)
  • Design requirement work item type definition
  • DFMEA risksheet integration patterns
  • Aero1 Flight Control Computer project walkthrough (live project example)
Design Engineer Dashboard exact metric formulas, status values, and user filtering behavior are implemented in the live Polarion project configuration. Test the dashboard in your project instance to confirm metric calculations and available filters match this reference.
Code: .polarion/pages/spaces/_default/Program Manager Dashboard/page.xml, Safety Engineer Dashboard/page.xml, Design Engineer Dashboard/page.xml, VandV Engineer Dashboard/page.xml, Config Manager Dashboard/page.xml (0.74) · .polarion/pages/spaces/Requirements/Home/page.xml, Design/Home/page.xml, Risks/Home/page.xml, Testing/Home/page.xml, Risks/FMEA Reports/page.xml, Documentation/Home/page.xml, Documentation/Powersheet Help Redirect/page.xml, RiskTemplates/Home/page.xml (0.69) · .polarion/pages/spaces/_default/Home/page.xml (0.54) · datasets/sol-aero-ui-walkthrough/summary.md, navigation.md, dashboards/home-dashboard.md, dashboards/role-dashboards.md, dashboards/standards-compliance.md, risksheet-views/risksheet-views.md, work-item-types/data-model.md (0.54) · .polarion/pages/spaces/_default/Standards Compliance Overview/page.xml, Certification Readiness Scorecard/page.xml, Compliance Matrix/page.xml (0.45) · .polarion/tracker/fields/designRequirement-subType-enum.xml, environmentalCategory-enum.xml, fta-gateType-enum.xml, cca-analysisType-enum.xml, controlType-enum.xml, riskControlType-enum.xml, verificationMethod-enum.xml, testLevel-enum.xml (0.41) · .polarion/pages/spaces/_default/Requirements Traceability Summary/page.xml, Verification Validation Summary/page.xml, Risk Control Effectiveness Report/page.xml, System Decomposition Report/page.xml, FMEA Coverage Report/page.xml, Classification Consistency Report/page.xml, System FMEA Report/page.xml, System Structure Navigator/page.xml (0.40) · .polarion/pages/scripts/velocity/nextedy_solutions.vm (0.39) · .polarion/nextedy/sheet-configurations/DO-326A Security Requirements Traceability.yaml (0.38) · .polarion/nextedy/sheet-configurations/Whole RTM Config.yaml (0.38)