Due

to the intended use as an IFR PFD, we are certifying to DO-178B Level B.

As

a result, virtually all software has been developed from scratch

(including

BIOS, OS, video BIOS, in addition to upper level applications).  That's

just

the way it is.  DO-178B is a process document, and it has very strict
guidelines for documentation and verification.

So Rick, the bottom line is; the  Windows 95 OS cannot be certified by the

FAA.

Is that a true statement? If not why not?
If it is the lack of source code would it be easier to certify Linux?

It sounds like the strict guidelines for documentation and verification
mentioned above answers Paul's question.  FAA doesn't "just trust Bill" with
Windows/DOS operating system.  Probably because they use them in the office
:-)

Bill Schertz

Bill Freeman wrote:

ultra-high reliability software is a very difficult field.  The first Ariane
V blew
all to pieces due to a software glitch.  There are many more examples.  My
guess is that a full featured OS is way too heavy on non-mandatory features
to make it cost effective for an ultra-reliable system application.  Too bad,
as I agree with Paul that it is better to have your software vendor different
from your hardware vendor so you can switch if you like.

I agree that deregulation is the answer.  Then WE get to decide if it is good
enough to risk our lives on - not some GS14 in DC that doesn't know
EFIS from KTAS from CD-ROM from SDRAM,  . . . or really care
very much either.

Bill
Long EZ builder & pilot
mechanical engineer

The Aircraft Rotary Engine Newsletter.              Powered by Linux.

http://home.earthlink.net/~rotaryeng/            http://www.linux.org