Here are some papers about software/µP in space for those who want more examples/details: * Space Software Validation using Abstract Interpretation (2009) htt

Here are some papers about software/µP in space for those who want more examples/details: * Space Software Validation using Abstract Interpretation (2009) http://www.di.ens.fr/~rival/dasia09.pdf http://www.di.ens.fr/~rival/dasia09.pdf From the conclusion: This study has shown that embedded space software are difficult to analyze due to non linearity (mainly in quaternion computations) and complex control command algorithms involved (e.g., Kalman filter). It should be noticed that the software architecture which suits static analysis by abstract interpretat ion best is also the more readable one and maintainable one. This technique can thus be a metrics of good architectures. In spite of these difficulties, abstract interpretation techniques can greatly improve the quality of space embedded software. * Qualification of the Atomated Transfer Vehicule (ATV) Flight Control ftp://ftp.elet.polimi.it/outgoing/Marco.Lovera/ESAGNC08/S01/01_Clerc.pdf A lot of information about the test process, the usage of Hadware-In-the-Loop and Monte Carlo testing. * Requirements review, Needs for launchers, space vehicles & orbital infrastructures (2006) http://microelectronics.esa.int/conferences/ngmp2006/D2-1200-ESA_RT.pdf http://microelectronics.esa.int/conferences/ngmp2006/D2-1200... High-level requirements for On-Board Computer (OBC).