AVIONICS · DO-178C · ARP4754A · DO-330

Avionics Software Engineering and Verification Support for DO-178C Programmes.

We support requirements, lifecycle data, verification, structural coverage, tool qualification, and SOI preparation across DAL A–E programmes. Agnile helps teams bring engineering discipline to airborne software programmes where traceability, reviews, test evidence, and configuration control are central to delivery.

Schedule a 60-minute callContact Us
DO-178C-Aligned DeliveryDAL A–E Programme SupportCertified PractitionersISO 9001

Part of Aerospace & Avionics

See the full Agnile aerospace portfolio — DO-178C verification support, ARP4754A / ARP4761 inputs, SOI review evidence packages, and certification-support evidence.

Explore Aerospace & Avionics

CAPABILITY AREAS

How we work across the DO-178C lifecycle.

Requirements and Planning

Software plans, standards, requirements development, traceability, review support, and lifecycle evidence structure.

Software Development

Embedded airborne software development, bootloader and data loading support, RTOS-based implementation, interface handling, and configuration-controlled code delivery.

Verification

Requirements-based testing, low-level and high-level test development, structural coverage, robustness testing, and test evidence preparation.

Certification Support

SOI review preparation, DO-330 tool qualification support, ARP4754A/ARP4761 interface support, and certification-support evidence organization.

ENGAGEMENT MODELS

How we engage on DO-178C programmes.

A full DAL B lifecycle for an airborne software item, DO-330 tool qualification for an in-house toolchain, or independent SOI audit support before DER review. We scope the actual work on the call.

  • AV-01·12–18 weeks

    DO-178C DAL B Programme

    Complete DO-178C DAL B lifecycle for one airborne software item — Plans through Verification with full traceability. Drafts the 5 plans + 3 standards, runs requirements-based testing, closes MC/DC where the DAL demands it, and delivers the SOI evidence pack.

    ENGAGEMENT FLOW

    Plans + Standards
    3w
    HLR + LLR
    5w
    Code + Static
    4w
    Verification + SOI
    6w

    DELIVERABLES

    • 5 plans + 3 standards
    • Traceable HLR / LLR set
    • Source + static analysis
    • Verification + SOI review evidence package
  • AV-02·6–8 weeks per tool

    DO-330 Tool Qualification

    Tool qualification for in-house or vendor toolchains used in the DO-178C lifecycle — TQL-1 through TQL-5 depending on tool function. Plans, validation testing, and the Tool Qualification Plan / Tool Operational Requirements / Tool Verification Report set.

    ENGAGEMENT FLOW

    TQL Determination
    1w
    TOR + Validation
    4w
    TQA + TVR
    3w

    DELIVERABLES

    • TQP + TOR + TVR set
    • Tool Qualification Data
    • Validation evidence + TQA report
  • AV-03·2–4 weeks

    SOI Audit Support

    Pre-audit gap assessment, evidence packaging, and on-site or remote support during DER review. Useful when an in-house team has built artefacts but wants an independent review before submitting them to the certification authority.

    ENGAGEMENT FLOW

    Gap Review
    1w
    Evidence Packaging
    2w
    Audit Support
    1w

    DELIVERABLES

    • Gap report
    • SOI review evidence package
    • Findings remediation list

WHY AGNILE

What we do differently.

  • 01

    DO-178C-aligned lifecycle support delivered as one engagement — planning data, standards, traceable HLR / LLR, source under agreed coding rules, verification evidence, structural coverage support, and SOI review evidence packages organised for customer, DER, or authority review.

  • 02

    DER and SOI review support. We help teams prepare lifecycle data, traceability, verification evidence, and findings responses for SOI-stage reviews.

  • 03

    MC/DC and structural coverage support for high-assurance airborne software. Source-to-object traceability, robustness testing, and structural-coverage analysis bundled together — not three separate sub-projects.

  • 04

    DO-330 tool qualification inputs — TQL determined per tool function, TOR validated against actual tool behaviour, TVR organised for review.

  • 05

    Cross-domain capability. We work both ISO 26262 automotive safety and DO-178C avionics safety in the same firm — useful when avionics IP migrates to automotive applications or vice versa.

STANDARDS DEPTH

Standards we work to.

DO-178C anchored. ARP4754A and ARP4761 set the system context. DO-330 qualifies the tools. DO-331/332/333 extend the approach.

  • DO-178C

    Software Considerations in Airborne Systems

    Across all 12 sections. Plans, standards, traceable requirements, structural coverage to MC/DC at DAL A, and the Software Accomplishment Summary — with bidirectional traceability from system requirements through code in DOORS or Polarion.

  • ARP4754A

    Guidelines for Development of Civil Aircraft and Systems

    System-level development — PASA / PSSA / SSA artefacts, item development assurance levels (IDAL) cascaded to software DAL, and the system requirements that anchor the DO-178C lifecycle.

  • ARP4761

    Safety Assessment Process

    Functional Hazard Assessment, fault tree analysis, common-cause analysis, and the iterative PSSA / SSA loop with system engineers — anchoring the safety case that drives DAL allocation.

  • DO-330

    Software Tool Qualification Considerations

    Tools qualified to TQL-1 through TQL-5 — drafting Tool Qualification Plans, Tool Operational Requirements, validation tests, and Tool Qualification Data ready for DER review.

  • DO-331 / DO-332 / DO-333

    MBD, OOT, and Formal Methods supplements

    We extend DO-178C with model-based development (DO-331), object-oriented technology (DO-332), and formal methods (DO-333) where the engineering approach calls for them.

HOW WE ENGAGE — DO-178C LIFECYCLE

From PSAC to Software Accomplishment Summary.

Six stages, each with named DO-178C sections and an explicit deliverable. Scroll to walk through what we deliver at each stage.

  1. 01

    Plans (PSAC, SDP, SVP, SCMP, SQAP)

    DO-178C §11

    We draft the five required plans — Plan for Software Aspects of Certification, Software Development, Software Verification, Software Configuration Management, and Software Quality Assurance — tailored to the DAL of your system.

    → Plan suite + DAL rationale

  2. 02

    Standards (Requirements, Design, Code)

    DO-178C §11.7–11.9

    Project-specific Software Requirements Standards, Design Standards, Code Standards. Tailored for the DAL with stricter rigor at DAL A/B (formal review, MC/DC awareness baked in).

    → 3 standards documents

  3. 03

    High-Level + Low-Level Requirements

    DO-178C §5.1–5.2

    HLR derived from system requirements with DO-178C traceability. LLR derived from HLR. Bidirectional traceability maintained from system level all the way to source.

    → Traceable HLR + LLR set

  4. 04

    Source Code & Static Analysis

    DO-178C §5.3 / §6.3.4

    Source code conforming to project Code Standards. Static analysis (LDRA, Polyspace, Helix QAC) for compliance, complexity, and dataflow. Source-to-object traceability for DAL A/B.

    → Source + static analysis reports

  5. 05

    Verification & Coverage

    DO-178C §6

    Requirements-based testing at HLR and LLR levels. Structural coverage analysis — Statement (DAL C), Decision (DAL B), MC/DC (DAL A). Robustness testing per §6.4.2.2.

    → Test cases + coverage closure

  6. 06

    SOI Audits & Certification

    DO-178C §11

    Configuration management, problem reporting, quality assurance in steady state. SOI-1 (planning) through SOI-4 (final) audit support with the DER. Software Accomplishment Summary at submission.

    → SOI review evidence package + SAS

CASE STUDY

What this looks like in practice.

Anonymised by request. References available on qualified enquiry.

Anonymised engagement summary. Customer identity and programme details withheld under NDA. Metrics reflect internally documented delivery outcomes.

AVIONICS · CNS

DO-178C DAL B Communications and Navigation software, MC/DC closed.

CONTEXT

An Indian avionics programme was developing a new CNS (Communications and Navigation Surveillance) function classified DAL B by the system safety assessment. The team had DO-178B experience but needed DO-178C-compliant lifecycle artefacts for the first time, with a tight DER review window.

APPROACH

Agnile drafted the five plans (PSAC, SDP, SVP, SCMP, SQAP), the three standards documents, and led requirements-based testing through to MC/DC closure on 47 kSLOC. SOI-1 and SOI-2 audits supported with DER engagement. The team delivered final SOI-3 and SOI-4 with our written evidence pack as the spine.

WHAT WE DELIVERED

  • 5 plans + 3 standards (DO-178C §11)
  • Traceable HLR / LLR set in DOORS
  • Source + static analysis (LDRA)
  • MC/DC test cases and coverage closure
  • SOI-1 + SOI-2 audit support pack

WHAT THE CUSTOMER GOT

  • SOI-1 + SOI-2 cleared first time
  • Coverage closure achieved at 47 kSLOC
  • Internal team trained on DO-178C lifecycle

DAL B · 47 kSLOC · MC/DC 100% · SOI-1+2 cleared

FAQ

Talk to an avionics engineer.

A 60-minute call: scope a DAL B programme, qualify a tool, or pressure-test your SOI-2 evidence pack before DER review. We respond to qualified enquiries within one business day.