From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00,LOTS_OF_MONEY, TO_NO_BRKTS_FROM_MSSP autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e6a2e4a4c0d7d8a6 X-Google-Attributes: gid103376,public X-Google-Thread: 101deb,3488d9e5d292649f X-Google-Attributes: gid101deb,public X-Google-ArrivalTime: 2003-02-21 14:37:20 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!pln-w!extra.newsguy.com!lotsanews.com!cyclone-sf.pbi.net!151.164.30.35!cyclone.swbell.net!bos-service1.ext.raytheon.com!dfw-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3E56AA1D.14E15BAC@raytheon.com> From: Jerry Petrey <"jdpetrey"@raytheon.com> X-Mailer: Mozilla 4.79 [en]C-CCK-MCD CSC;Raytheon (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.pl1,comp.lang.ada Subject: Re: Donald's F-22 Question References: <3E51908E.9CCA3412@adaworks.com> <8Gh4a.7455$_c6.743959@newsread2.prod.itd.earthlink.net> <3E51ABCE.5491B9A2@adaworks.com> <3E5273DE.2050206@cox.net> <3E531E6F.BDFB2599@adaworks.com> <3E546C45.4010406@cox.net> <3E54F926.441D5BB5@adaworks.com> <3E5690DE.D0B10D53@adaworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 21 Feb 2003 15:37:17 -0700 NNTP-Posting-Host: 147.24.93.55 X-Complaints-To: news@ext.ray.com X-Trace: dfw-service2.ext.raytheon.com 1045867038 147.24.93.55 (Fri, 21 Feb 2003 16:37:18 CST) NNTP-Posting-Date: Fri, 21 Feb 2003 16:37:18 CST Organization: Raytheon Company Xref: archiver1.google.com comp.lang.pl1:4415 comp.lang.ada:34402 Date: 2003-02-21T15:37:17-07:00 List-Id: Richard Riehle wrote: > Returning to Donald's original question, repeated at the end of this message. > > I have been interested in the thread that started this. Lots of good > comments have been posted. No one has directly address Donald's > question vis a vis the F-22. > > The F-22 software is clearly a problem. There are probably programmers > out there who read these forums and have direct involvment with > this project. It would be interesting to hear from one or more of > them. > > Richard Riehle > > ====================================================== > > > "Donald L. Dobbs" wrote: > > > > > Not to belabor a point, but one of the lead stories today on the > > > Aviation Week web site www.aviationnow.com describes how the F-22 > > > program is now some $800 million overrun because of delays caused by > > > unreliable software. They can get it to run for about 8 hrs in the lab > > > before it crashes, but in the actual test flights it fails within 3.5 > > > hours forcing the pilot to reboot the system while in mid-flight. If > > > they are using Ada as you contend, then this is a terrible indictment > > > and confirms what I had heard earlier about the language's shortcomings. I worked for Lockheed during part of the F22 development period although not directly on the F22 program but on another aircraft system (in Ada also). The problem is a common one on large programs - mostly one of management. Managers assume all engineers are alike. There were a few good Ada programmers and a lot of average or below average AdaTran and AdaC programmers ("I can write Fortran (or C) in any language" people). The overall code that resulted, while Ada, was certainly not good Ada. It was a mess to get working and resulted in huge cost overruns, but I would guess it would have been much worse if they had used some other language. Certainly using Ada does not solve all the problems but it does make the job a little easier of having a wide variety of skill levels involved on a large project. With some good management (rarer than hen's teeth) and letting the minority of top notch software engineers manage and enforce a good process, great results can be achieved even with a lot of lessor skilled people on the team. This may be true in other languages as well, but more so in Ada, and every advantage helps in a large project like this. Jerry -- --------------------------------------------------------------------------------- -- Jerry Petrey -- Senior Principal Systems Engineer - Navigation (GPS/INS), Guidance, & Control -- Raytheon Missile Systems - Member Team Ada & Team Forth -- NOTE: please remove in email address to reply ---------------------------------------------------------------------------------