By Topic

A method to increase the design assurance level of software by means of FMEA

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
$31 $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)
Arkusinski, A. ; Honeywell Int., Albuquerque, NM, USA

Software that is used in airborne systems, especially those systems that require certification by the Federal Aviation Administration (FAA), is developed in accordance with DO-178B. The development and verification objectives imposed by DO-178B depend on the criticality level of the software. The cost of development, and especially of verification, is significantly higher each step the criticality is increased. Developers want to produce software to the lowest criticality level possible, consistent with a safety analysis, to keep development costs down. It may be desirable to increase the design assurance level of software without incurring the full cost of verification at the next higher criticality level. This paper presents a method of locating undetected software defects, that could cause a hazardous condition, in software that has been verified to DO-178B level D criticality. Locating and removing such defects has the effect of increasing the design assurance level of the software, at about 10% of the cost of a full verification to level C.

Published in:

Digital Avionics Systems Conference, 2005. DASC 2005. The 24th  (Volume:2 )

Date of Conference:

30 Oct.-3 Nov. 2005