  Software system certification presents itself with many challenges, including
the necessity to certify the system at the level of functional requirements,
code and binary levels, the need to chase down run-time errors, and the need
for proving timing properties of the eventual, compiled system. This paper
illustrates possible approaches for certifying code that arises from control
systems requirements as far as stability properties are concerned. The relative
simplicity of the certification process should encourage the development of
systematic procedures for certifying control system codes for more complex
environments.
