A case study on isolation of safety-critical software

In the case study presented, a series of problems affecting safety that were identified in a large, real-time control system that contained both safety-critical and non-safety-critical functions were examined. The study identified those errors whose safety impact was caused, at least in part, by problems in parts of the software that had been determined not to be safety-critical. Methods to isolate safety-critical software are explored, along with some of the problems with those methods.<
>