By Topic

A case study on isolation of safety-critical software

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

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

Published in:

Computer Assurance, 1991. COMPASS '91, Systems Integrity, Software Safety and Process Security. Proceedings of the Sixth Annual Conference on

Date of Conference:

24-27 Jun 1991