Development assurance
DO-333 support for formal analysis credit with a defensible soundness case
For avionics suppliers, OEMs, Engineering teams, this review is used when Formal analysis proposed as verification credit. EE checks formal specification and its validation against requirements, analysis method soundness argument, assumptions and their independent verification against the approval basis, the configuration baseline, and the available lifecycle data. The output gives software leads and verification leads an evidence map, discrepancy register, request list, and closure plan for the records that need applicant, supplier, or authority disposition.
What gets reviewed
- Challenge formal specification and its validation against requirements against the claim it supports.
- Reconcile analysis method soundness argument against the claim it supports.
- Confirm assumptions and their independent verification against the claim it supports.
- Index mapping of formal credit to the specific DO-178C objectives being replaced against the claim it supports.
- Compare approval basis against the claim it supports.
- Trace configuration definition against the claim it supports.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Source control: formal specification and its validation against requirements fails review if the cited record cannot be tied to the current baseline.
- Closure owner: analysis method soundness argument fails review if the cited record cannot be tied to the current baseline.
- Configuration match: assumptions and their independent verification fails review if the cited record cannot be tied to the current baseline.
- The review notes that evidence link: mapping of formal credit to the specific DO-178C objectives being replaced fails review if the cited record cannot be tied to the current baseline.
- Limit carryover: approval basis fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
- Manual source: formal specification and its validation against requirements
- Configuration item: analysis method soundness argument
- Closure evidence: assumptions and their independent verification
- Baseline record: mapping of formal credit to the specific DO-178C objectives being replaced
- Test file: approval basis
- Analysis note: configuration definition
Common discrepancies
- Program risk: analyzer soundness asserted from vendor claims.
- Authority question: environmental assumptions of the proof never verified in the integrated system.
- Finding in records: formal credit claimed for objectives the analysis method cannot address.
- Installer issue: baseline does not match the delivered records.
How the work runs
Frame 333 Formal
Confirm the exact event, affected file set, buyer role, and decision standard before any formal specification and its validation against requirements is treated as sufficient.
Trace Support Evidence
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Analysis Credit
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Soundness Case
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
Who uses the output
- software leads use the map to brief the decision.
- verification leads use the register to assign closure.
- certification liaisons use the request list to collect source records.
How the work fits into the transaction or program
Can formal analysis replace specific testing objectives on this program, and does the evidence carry the soundness and assumption burden DO-333 attaches to that swap. The evidence set centers on the formal specification and its validation against requirements, the analysis method soundness argument, assumptions and their independent verification, and the mapping of formal credit to the specific DO-178C objectives being replaced. The likely weak points are analyzer soundness asserted from vendor claims, environmental assumptions of the proof never verified in the integrated system, and formal credit claimed for objectives the analysis method cannot address. The output gives the software lead a cleanup register for DO-333 support for formal analysis credit with a defensible soundness case before formal analysis proposed as verification credit.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not grant certification credit, approve data, or sign return-to-service records. The package documents what was checked and what remains open for the responsible certification parties.
Specific to this review
- can formal analysis replace specific testing objectives on this program, and does the evidence carry the soundness and assumption burden DO-333 attaches to that swap.
- Formal specification and its validation against requirements often controls whether later summaries can be trusted.
- Analyzer soundness asserted from vendor claims is treated as a record gap until an owner closes it.
- FAA and EASA evidence should stay distinguishable from commercial claims and installer notes.
- The scope uses the 333 Formal Methods Support question as the control point, so the review stays tied to Formal analysis proposed as verification credit and the buyer decision behind it.
- The evidence starts with Formal specification and its validation against requirements and follows Evidence Review Analysis Credit references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for software lead: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Defensible Soundness Case Development questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Evidence map for DO-333 Formal Methods; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
Frequently asked questions
What makes this standards review different from a general file audit?
The scope is tied to 333 formal methods support and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block formal analysis proposed as verification credit or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is formal specification and its validation against requirements, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives software lead a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.