VEROCEL

VerOLink - Verify Object Linking

Requirements-based testing provides one means to verify that software behaves or performs as expected. The use of structural coverage analysis, particularly when performed at the object code level (see VerOCode) provides evidence that unintended functions have been removed. What remains is the determination and objective evidence that each software function is invoked as expected, and that an error introduced by the linker does not go undetected as required by the DO-178B control coupling objective.

VerOLink is a verification tool that satisfies the control coupling objective under DO-178B. Control coupling provides a measure of the correctness of the integration of many independently compiled object files linked to form a single executable image.

VerOLink is used to provide this final check. Verification of the code integration repeats the processing performed by the linker and the associated tools independently, and cross-checks that the integration is consistent.

VerOLink verifies that the function calls within an executable image have been resolved correctly when the linker combined the object modules.

VerOLink checks that the address of a called function in the executable image corresponds to the start address of the function being invoked. This, in essence, verifies the links produced by the linker between function calls in separately compiled units.

VerOLink is available with qualification materials, making it applicable for use on all levels of systems, through Level A.

Click here for examples of VerOLink’s results.


			VerOLink - Verify Object Linking VerOLink - Verify Object Linking Requirements-based testing provides one means to verify that software behaves or performs as expected. The use of structural coverage analysis, particularly when performed at the object code level (see VerOCode) provides evidence that unintended functions have been removed. What remains is the determination and objective evidence that each software function is invoked as expected, and that an error introduced by the linker does not go undetected as required by the DO-178B control coupling objective. *VerOLink* is a verification tool that satisfies the control coupling objective under DO-178B. Control coupling provides a measure of the correctness of the integration of many independently compiled object files linked to form a single executable image. *VerOLink* is used to provide this final check. Verification of the code integration repeats the processing performed by the linker and the associated tools independently, and cross-checks that the integration is consistent. *VerOLink* verifies that the function calls within an executable image have been resolved correctly when the linker combined the object modules. *VerOLink* checks that the address of a called function in the executable image corresponds to the start address of the function being invoked. This, in essence, verifies the links produced by the linker between function calls in separately compiled units. *VerOLink* is available with qualification materials, making it applicable for use on all levels of systems, through Level A. Click here for examples of *VerOLink’s* results.