DO-254 Certification: Requirements, Compliance Process and Design Assurance for Airborne Hardware

The level assigned to a function influences the development and verification activities required for the associated hardware. Higher assurance levels generally involve more extensive evidence and verification objectives.

It is important to note that the applicable assurance level is established at the system level and allocated to hardware through the relevant safety and development processes. Not every electronic component automatically receives the same DAL.

The DO-254 Compliance Process

A structured development lifecycle is central to achieving DO-254 objectives. The specific activities depend on the hardware complexity, assurance level, and project approval requirements.

1. Planning and Certification Strategy

The first step is to establish a hardware development plan and define how compliance will be demonstrated. This includes identifying applicable standards, responsibilities, development tools, verification methods, and required documentation.

Planning early helps teams avoid gaps in evidence that could delay reviews or approval.

2. Hardware Requirements Definition

The engineering team translates allocated system requirements into clear, measurable hardware requirements. These requirements should be complete, consistent, verifiable, and traceable to their sources.

For example, a requirement for a navigation processing unit might specify how input data must be handled or how the hardware responds to an error condition.

3. Hardware Design and Implementation

During this stage, engineers develop the hardware architecture and implement the required functionality. Depending on the design, this may involve FPGA logic, ASIC development, circuit design, or other complex electronic hardware technologies.

Effective FPGA design services can support this stage by helping teams develop, review, and implement hardware logic while maintaining traceability to the applicable requirements.

4. Verification and Validation

Verification activities determine whether the hardware design satisfies its requirements and applicable objectives. Methods may include reviews, analyses, simulations, testing, and other appropriate verification techniques.

For FPGA-based designs, verification may involve simulation, testbench development, coverage analysis, and hardware-level testing where applicable.

Validation focuses on whether the resulting implementation fulfils its intended use and allocated system needs. The exact scope and terminology should follow the project's development and approval framework.

5. Configuration Management and Traceability

DO-254 development requires controlled hardware designs, requirements, verification results, and supporting records.

Configuration management helps ensure that the design being reviewed is the same version that was verified. Bidirectional traceability also helps demonstrate that requirements have been implemented and that the required verification activities have been completed.

6. Compliance Documentation and Reviews

The final stage involves compiling the evidence needed to demonstrate that the applicable objectives have been addressed. Documentation may include development plans, requirements records, design data, verification procedures, test results, review records, and compliance summaries.

Reviews with the relevant approval stakeholders help identify gaps and resolve issues before the hardware is accepted into the wider aircraft development process.

Common Challenges in DO-254 Implementation