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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e009f0918a859dbe X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-10 07:21:46 PST Path: bga.com!news.sprintlink.net!uunet!in1.uu.net!explorer.csc.com!usenet From: Jeff Seigle Newsgroups: comp.lang.ada Subject: Re: DOD-STD-1679A(Navy) Date: 10 Mar 1995 14:52:47 GMT Organization: CSC Intelicom HQ, Bethesda MD Message-ID: <3jpp3v$nr1@explorer.csc.com> NNTP-Posting-Host: jseigle-pc.hq.csci.csc.com X-Newsreader: Date: 1995-03-10T14:52:47+00:00 List-Id: In article <3jncg0$7vu@butch.lmsc.lockheed.com> l107353@cliffy.lfwc.lockheed.com (Garlington KE) writes: >Doc Elliott (helliott@losat.redstone.army.mil) wrote: >: ?!?!?!?! The Navy actually will accept a CSCI that has KNOWN problems? >: And yet they still get more of the DoD budget than we do..... > >To be fair, I think all U.S. military services have a waiver and deviation >process that permits accepting CSCIs with known problems. Every commercial software product you buy has "known problems." Trouble is, you're not the one who knows about them. Wouldn't you rather have a list of the problems? It is not unheard of to deliver software with known problems to the DoD or anyone else, as long as you come clean about it (and fix it later).