Searches titles, sections and text. ↑ ↓ to move, Enter to open, Esc to close. Opens with / or Ctrl+K.

    Contact

    Avionics

    Evidence from a modified executable needs a representativeness argument. Passive trace observation reduces that particular difference.

    Avionics software goes through a costly certification before it flies. That certification is attached to a specific artifact. Verification evidence collected from a modified executable may require an argument that it represents the executable used in the certified system. Passive processor-trace observation avoids application-side coverage counters and can therefore reduce this particular difference.

    The constraint

    Instrumented builds are used in airborne-software verification, but any difference from the executable used in the airborne system must be understood and addressed within the project’s verification and configuration-control strategy. Added logging, runtimes or coverage counters can affect the executable and its timing. Passive trace observation is one route that avoids inserting those mechanisms into the application; it is not the only possible verification route.

    What that enables

    • Structural-coverage evidence, including MC/DC where applicable to the project’s Level A objectives, collected from the identified executable under test. Passive results and CEDARtools.Anchor-supplemented results are distinguished; an Anchor* executable is not described as unmodified.
    • Object-code accountability: object code that cannot be traced to source structure is flagged, not omitted. The exact obligation and accepted method come from the applicable DO-178C/ED-12C objective and project guidance.
    • Multi-core timing observations as an input to the interference analysis for which EASA AMC 20-193 provides an acceptable means of compliance. How that works with AbsInt
    • Long-duration observation in a controlled integration, rig or operationally representative environment, subject to trace availability, authorization, data handling and validity monitoring. Use in an aircraft or certified operational environment requires a separate installation and safety assessment.

    Accemic products provide measurement and analysis evidence; they do not certify an airborne system or determine compliance on their own. The intended use, tool-assurance strategy and acceptance of the evidence remain project-specific.

    CEDARtools® builds on our granted patent families for the decoding side; see patents.