Development assurance
DO-332 support for object-oriented vulnerabilities answered, not ignored
software lead, software architect, certification liaisons use this page when OO language or technique on a certified program. EE reviews vulnerability analysis set including local type consistency and run-time dispatch substantiation, heap memory management verification, exception handling coverage with the baseline data and cited standards or rules. The buyer receives a mapped record set, unsupported-claim log, missing-data request list, and action plan that separates complete evidence from items needing specialist judgment.
What gets reviewed
- Compare vulnerability analysis set including local type consistency and run-time dispatch substantiation against the claim it supports.
- Trace heap memory management verification against the claim it supports.
- Challenge exception handling coverage against the claim it supports.
- Reconcile traceability through class hierarchies against the claim it supports.
- Confirm approval basis against the claim it supports.
- Index 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
- The review notes that evidence link: vulnerability analysis set including local type consistency and run-time dispatch substantiation fails review if the cited record cannot be tied to the current baseline.
- Limit carryover: heap memory management verification fails review if the cited record cannot be tied to the current baseline.
- Source control: exception handling coverage fails review if the cited record cannot be tied to the current baseline.
- Closure owner: traceability through class hierarchies fails review if the cited record cannot be tied to the current baseline.
- Configuration match: approval basis fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
- Test file: vulnerability analysis set including local type consistency and run-time dispatch substantiation
- Analysis note: heap memory management verification
- Manual source: exception handling coverage
- Configuration item: traceability through class hierarchies
- Closure evidence: approval basis
- Baseline record: configuration definition
Common discrepancies
- Installer issue: C++ or Ada programs certified as if procedural with no vulnerability analysis.
- Buyer concern: type substitutability asserted without local type consistency verification.
- Program risk: heap use hidden behind libraries the analysis never covered.
- Authority question: baseline does not match the delivered records.
How the work runs
Frame 332 Object
Confirm the exact event, affected file set, buyer role, and decision standard before any vulnerability analysis set including local type consistency and run-time dispatch substantiation is treated as sufficient.
Trace Technology Support
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 Review Vulnerabilities
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Not Ignored
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.
- software architects 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
Does a program using OO or related techniques (inheritance, polymorphism, active memory) satisfy the DO-332 vulnerability analyses on top of the base DO-178C objectives. The evidence set centers on the vulnerability analysis set including local type consistency and active dispatch substantiation, active memory management verification, exception handling coverage, and traceability through class hierarchies. The likely weak points are c++ or Ada programs certified as if procedural with no vulnerability analysis, type substitutability asserted without local type consistency verification, and heap use hidden behind libraries the analysis never covered. The output gives the software lead a cleanup register for DO-332 support for object-oriented vulnerabilities answered, not ignored before OO language or technique on a certified program.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not replace the applicant, STC holder, authorized representative, or regulator. Approval, acceptance, and airworthiness decisions remain with the people and authorities assigned to those functions.
Specific to this review
- does a program using OO or related techniques (inheritance, polymorphism, heap memory) satisfy the DO-332 vulnerability analyses on top of the base DO-178C objectives.
- Vulnerability analysis set including local type consistency and run-time dispatch substantiation often controls whether later summaries can be trusted.
- C++ or Ada programs certified as if procedural with no vulnerability analysis 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 332 Object Oriented Technology question as the control point, so the review stays tied to OO language or technique on a certified program and the buyer decision behind it.
- The evidence starts with Vulnerability analysis set including local type consistency and run-time dispatch substantiation and follows Support Evidence Review Vulnerabilities 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 Answered Not Ignored 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-332 Object Oriented Technology; 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 332 object oriented technology and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block oo language or technique on a certified program or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is vulnerability analysis set including local type consistency and run-time dispatch substantiation, 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.