AeroCert
AeroCert automates aircraft software certification. Aerocert is tailored to the standard a programme works under, and covers software, hardware, ground systems and space across five standards today.
Standards AeroCert currently supports
DO-178C
DO 178C applied to electronic hardware, covering the custom chips and programmable circuits inside an aircraft.
DO-278
The standard for ground systems that support aircraft in flight, including air traffic control, navigation, and surveillance.
ECSS
The European standards governing how spacecraft software is specified, built, and verified, written for systems that cannot be repaired after launch.
DO-254
DO 178C applied to electronic hardware, covering the custom chips and programmable circuits inside an aircraft.
NPR-7150
NASA's software requirements, where every piece of software is classified by what failure would cost and that classification sets the evidence the programme must produce.
Certification is the most expensive and perpetually behind schedule part of aircraft or safety-critical software, and most of that weight sits in a few areas: high level requirements, low-level requirements, test cases and linking these together.
AeroCert constructs all of these.
What makes AeroCert different is how these artefacts are produced. The engine creates an understanding of the entire programme, rather than using a prompt engineering wrapper around the LLM. What this means is each artefact is precisely and repeatably created and linked to the other artefacts and the understanding of the full programme.
Neuro-symbolic reasoning and why this makes AeroCert fundamentally different from generative AI tools
.png)
Read now
What AeroCert constructs
These are the artefacts AeroCert creates and maintains across a programme. Each one is composed, reviewed, and linked into the traceability matrix as it is produced.
Scope estimator
The full scope of a programme, estimated before work begins.
Low-level test cases and procedures
Composed and reviewed, derived from the low-level requirements.
High-level test cases and procedures
Composed and reviewed, derived from the high-level requirements.
Low-level requirements
Composed and reviewed, each one tracing to specific lines of code within a function. Where the code does not yet exist, they trace to subsections of the activity diagrams.
High-level requirements
Composed and reviewed, derived from system requirements and the design documentation.
Linking between all the requirements and the test cases
Follow any requirement up to its source, down to code, across to tests.
Every artefact carries the reasoning that produced it, which is what an auditor asks to see.