From: Jeff Seigle <jseigle@csci.csc.com>
Subject: Re: DOD-STD-1679A(Navy)
Date: 10 Mar 1995 14:52:47 GMT
Date: 1995-03-10T14:52:47+00:00 [thread overview]
Message-ID: <3jpp3v$nr1@explorer.csc.com> (raw)
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).
next reply other threads:[~1995-03-10 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-10 14:52 Jeff Seigle [this message]
1995-03-10 15:37 ` DOD-STD-1679A(Navy) Garlington KE
1995-03-11 4:22 ` DOD-STD-1679A(Navy) verne
-- strict thread matches above, loose matches on Subject: below --
1995-03-07 3:02 DOD-STD-1679A(Navy) Mark Cronan
1995-03-07 4:50 ` DOD-STD-1679A(Navy) verne
1995-03-08 12:44 ` DOD-STD-1679A(Navy) Doc Elliott
1995-03-09 17:05 ` DOD-STD-1679A(Navy) Garlington KE
1995-03-18 1:30 ` DOD-STD-1679A(Navy) Scott . Smart CDR
[not found] ` <3jkddt$mk1@michp1.redstone.army. <50716@suned1.Nswses.Navy.MIL>
1995-03-21 18:12 ` DOD-STD-1679A(Navy) Doc Elliott
1995-03-23 12:23 ` DOD-STD-1679A(Navy) Mike Meier
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox