Skip to content

Arc Skills / Standards and development assurance

Check hardware assurance evidence against DO-254 objectives

This task checks whether supplied airborne electronic hardware evidence supports the project’s applicable objective matrix for a named item and hardware DAL. Arc Skills produces a configuration-aware evidence map and gaps for the authorized hardware assurance review.

Use this skill

Use Arc Skills to review hardware assurance evidence for this exact airborne electronic hardware item. Compare each supplied objective row with lifecycle evidence and the released device configuration.

Inputs:
- Controlled DO-254 basis, approved hardware DAL and objective matrix.
- Item, board and programmed-device identities.
- Plans, trace, verification records, anomalies and release records.

Return an objective-evidence matrix with source row, applicable item, artifact revision, test result, configuration match and open question. Leave unsupplied objective IDs unverified; do not infer compliance from an environmental pass.

Set up the toolkit · Read the skill instructions

What you provide and what you get

Inputs and outputs
What you haveHow it is usedWhat you get
Approved basis and DALSelects the project’s actual objective setApplicability boundary
Design and verification artifactsLinks requirement, implementation and resultObjective evidence map
Board/device/bitstream release recordsTests whether evidence covers the released itemConfiguration gap

A temperature pass cannot identify the released FPGA bitstream

Illustrative engineering example.

In this synthetic review, board B-3 carries FPGA F. Report TEMP-7 says B-3 passed the approved temperature procedure, but its log records only device type. Release package REL-4 names bitstream hash H-42; no test record names that hash.

FPGA evidence review excerpt
Claim or rowEvidence suppliedWhat it establishesOpen finding
Environmental performance of B-3TEMP-7: temperature pass on board B-3Board-level result in recorded test conditionsTested bitstream identity absent; compare log/programming record with H-42
Requirements to logic traceTRACE-2 links three sampled requirements to RTL revision R-5A trace exists for sampled design dataNeed project matrix to judge objective scope and completeness
Released configurationREL-4 records B-3 and H-42Identifies intended released configurationNo evidence yet ties TEMP-7 programmed image to H-42

TEMP-7 is useful evidence for environmental behavior on the tested board. It cannot prove that the released programmed logic was in the tested unit. Matching only the FPGA part number misses the configuration variable that can change behavior.

The review can say which documents exist and where the identity chain breaks. It cannot assign a numbered DO-254 objective or conclude hardware DAL satisfaction without the project-controlled objective matrix, approved classification and item-specific lifecycle records. A matching programming log or justified change-impact analysis could resolve the configuration question.

Check the item and evidence chain

  1. Record the airborne electronic hardware item boundary, approved DAL and controlled objective matrix.
  2. Trace each applicable row through design data, verification, review and anomalies.
  3. Match board revision, device, programmed image and operating conditions across evidence and release.
  4. Keep environmental qualification results distinct from development-assurance closure.

Questions about this task

Why is a passing temperature test insufficient?

It supports the tested environmental condition. A separate identity and lifecycle chain must show which programmed hardware was tested and whether it matches the released design.

Can a COTS label remove the review?

The project’s approved hardware classification and use determine scope. A purchased device that is configured or programmed for the item still needs a documented applicability decision.

Sources and further reading

  • FAA AC 20-152A: Official guidance on airborne electronic hardware development assurance.

FAA AC 20-152A addresses airborne electronic hardware; the controlled DO-254/ED-80 basis supplies detailed objectives and classification decisions.