By Topic

An analysis of selected software safety standards

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

3 Author(s)
D. R. Wallace ; Nat. Inst. of Stand. & Technol., Gaithersburg, MD, USA ; D. R. Kuhn ; L. M. Ippolito

Standards, draft standards, and guidelines that provide requirements for the assurance of high integrity software are studied. The focus is on identifying the attributes necessary in such documents for providing reasonable assurance for high integrity software, and on identifying the relative strengths and weaknesses of the documents. The documents vary widely in their requirements and the precision with which the requirements are expressed. Security documents tend to have a narrow focus and to be more product oriented, while safety documents tend to be broad in scope and center primarily on the software development process. It is found that overall there is little relationship between the degree of risk and the rigor of applicable standards. Recommendations are provided for a base standard for the assurance of high integrity software.<>

Published in:

IEEE Aerospace and Electronic Systems Magazine  (Volume:7 ,  Issue: 8 )