DO-178C Objective A7-9 references the activities identified in §6.4.4.2 item b. The text of 6.4.4.2 item b from both DO-178B and DO-178C are shown below.

It should be noted that the purpose of the prescribed “additional verification” from both texts is to establish the “correctness of such generated code sequences”. This is to say that the introduced code is not required to be structurally covered necessarily, but rather the code is required to be verified to be correct with respect to the design in which it is introduced. For an array index boundary check, for example, it would be better if the introduced object code could not be executed because the design itself precludes violating the array’s bounds.

Instead, the guidance expects that two items will be fulfilled:

1. The fact that the object code is introduced is identified, and

2. The form and function of the code is verified (which may be done by review, analysis, or test).

Form and function, for the example of an array bound check, consists of ensuring that the limits put in the introduced object code correspond to the correct limits to the array, and checking that the correct index variable is compared to those limits.

Identifying the introduced object code is a bit more complex.

DO-178C section 6.4.4.2.b updates