Aerospace and Defence
Document

Object code verification and DO-178C objective A7-9

5 Sections

Level A software developers have been tasked with the verification of object code that is directly untraceable to source code since the introduction of RTCA/DO-178B in 1992. This type of object code consists of executable statements that “[introduce] branches or side effects that are not immediately apparent at the Source Code level”, including such things as compiler-generated array index boundary checks.  

Learn now DO-178C corrected what many saw as an oversight by including this so-called “hidden objective” in Table A-7 of Annex Amaking it more explicit in the Annex tables. And discover how DO-178C opened the door for using newer techniques for identifying and verifying object code not directly traceable to source code. 

REGISTER FOR FREE OR REQUEST LINK

Background

REGISTER FOR FREE OR REQUEST LINK

DO-178C section 6.4.4 updates

REGISTER FOR FREE OR REQUEST LINK

DO-178C section 6.4.4.2.b updates

REGISTER FOR FREE OR REQUEST LINK

Summary

No cookie

Pen
odio massa libero Aliquam Praesent accumsan et, ut vulputate, ut