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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b2116ed565f01bb0 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-11-02 17:40:15 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!howland.reston.ans.net!math.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!ajpo.sei.cmu.edu!riehler From: riehler@ajpo.sei.cmu.edu (Richard Riehle) Subject: Re: Paige's How To Get An Automatic Ada Waiver memo Message-ID: <1994Nov2.204015.23113@sei.cmu.edu> Sender: netnews@sei.cmu.edu (Netnews) Organization: AdaWorks Software Engineering, Palo Alto, CA References: Date: Wed, 2 Nov 1994 20:40:15 EST Date: 1994-11-02T20:40:15-05:00 List-Id: In article eachus@spectre.mitre.org (Robert I. Eachus) writes: > > COTS software in the DoD is defined as existing software >supported by the vendor. If you are willing to support the software >you sell and warrant that it works now, the DoD could care less what >language it is written in. Ada is only required if the government has >to pay to develop the software or maintain it. Robert, I wish it were that simple. How do we categorize dBASE IV, Clipper, FoxPro, etc? My experience with several Navy sites is that they merrily develop large applications using these tools, and justify the avoidance of Ada with the rationale that these are COTS products. And some of these systems are large and complex. And they will/do require DoD funds for long-term maintenance. One Navy luminary even affirmed to me at the famous Dual-Use conference that these database products are indeed regarded as COTS. Richard Riehle AdaWorks Software Engineering Suite 27 2555 Park Boulevard Palo Alto, CA 94306 (415) 328-1815 FAX 328-1112 email address: adaworks@netcom.com