DO-254 Verification (avionics/do254/hardware-verification)
Use when the task is verification of DO-254 airborne electronic
hardware: method selection, independence, coverage, and completeness
for the hardware item.
Domain quick reference
- Verification is the DO-254 process that shows the hardware item
satisfies its requirements; the methods are test, analysis, and
review, selected per item and design assurance level.
- Complex AEH (programmable logic, processors, significant internal
state) is verified by test, analysis, and review; simple AEH uses
reduced verification (review-based).
- Independent verification is expected at the higher hardware design
assurance levels (A/B); independence is separate from the methods
themselves.
- Requirements-based testing measures coverage against the item's
requirements: use a 0.98 ratio at levels A/B and 0.95 at C/D.
- Hardware/software integration evidence ties the hardware item to
the airborne software it hosts.
Workflow
- Classify the item as simple or complex AEH and note its hardware
design assurance level (A-D).
- Determine the verification methods for the item (full set for
complex AEH, reduced for simple AEH).
- Check whether independent verification is expected at the level.
- Validate requirements-based test coverage against the level's
ratio (0.98 for A/B, 0.95 for C/D).
- Review the hardware/software integration evidence, then confirm
the verification effort is complete against the required method
set.
Pitfalls
- Applying the full test/analysis/review set to simple AEH (or
dropping test from complex AEH).
- Treating independence as optional at levels A/B.
- Passing coverage below the level's ratio (0.97 at A/B is not
sufficient).
- Declaring verification complete while a required method is
missing from the evidence.
Behavior contract (gate 3)
The method-selection, independence, coverage, and completeness logic
is exercised by the gate 3 contract test:
scripts/test_hardware_verification.py against scripts/hardware_verification_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_hardware_verification.py
Compliance
- Standards referenced, not reproduced: DO-254 text is proprietary
(RTCA/EUROCAE); summary-only per standards-map.yaml and brief 06.
- compliance: STANDARDS-REF, gated: false.
1---2name: hardware-verification3description: "Use when verifying DO-254 airborne electronic hardware: determine the verification methods that apply to a simple or complex AEH item, check whether independent verification is expected at the hardware design assurance level, validate requirements-based test coverage against the A/B and C/D ratios, review hardware/software integration evidence, and confirm the verification effort is complete against the required method set. Methods scale from reduced verification for simple AEH to test, analysis, and review for complex AEH. Trigger: do-254, verification, airborne electronic hardware, aehl, hardware design assurance, requirements-based test, hardware/software integration, review, analysis."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: do-2548 reference-only: true9gated: false10domain: avionics11pack: avionics12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/hardware-verification15 domain: avionics16 subdomain: do25417 tags: [do-254, verification, aehl, hardware-design-assurance, requirements-based-test, hwsw-integration]18 version: 0.1.019 author: Aero Agent Skills20---2122# DO-254 Verification (avionics/do254/hardware-verification)2324Use when the task is verification of DO-254 airborne electronic25hardware: method selection, independence, coverage, and completeness26for the hardware item.2728## Domain quick reference2930- Verification is the DO-254 process that shows the hardware item31 satisfies its requirements; the methods are test, analysis, and32 review, selected per item and design assurance level.33- Complex AEH (programmable logic, processors, significant internal34 state) is verified by test, analysis, and review; simple AEH uses35 reduced verification (review-based).36- Independent verification is expected at the higher hardware design37 assurance levels (A/B); independence is separate from the methods38 themselves.39- Requirements-based testing measures coverage against the item's40 requirements: use a 0.98 ratio at levels A/B and 0.95 at C/D.41- Hardware/software integration evidence ties the hardware item to42 the airborne software it hosts.4344## Workflow45461. Classify the item as simple or complex AEH and note its hardware47 design assurance level (A-D).482. Determine the verification methods for the item (full set for49 complex AEH, reduced for simple AEH).503. Check whether independent verification is expected at the level.514. Validate requirements-based test coverage against the level's52 ratio (0.98 for A/B, 0.95 for C/D).535. Review the hardware/software integration evidence, then confirm54 the verification effort is complete against the required method55 set.5657## Pitfalls5859- Applying the full test/analysis/review set to simple AEH (or60 dropping test from complex AEH).61- Treating independence as optional at levels A/B.62- Passing coverage below the level's ratio (0.97 at A/B is not63 sufficient).64- Declaring verification complete while a required method is65 missing from the evidence.6667## Behavior contract (gate 3)6869The method-selection, independence, coverage, and completeness logic70is exercised by the gate 3 contract test:71scripts/test_hardware_verification.py against scripts/hardware_verification_logic.py72(stdlib unittest, offline). Run:73python3 scripts/test_hardware_verification.py7475## Compliance7677- Standards referenced, not reproduced: DO-254 text is proprietary78 (RTCA/EUROCAE); summary-only per standards-map.yaml and brief 06.79- compliance: STANDARDS-REF, gated: false.