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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,103b407e8b68350b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-03 12:02:20 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: snarflemike@yahoo.com (Mike Silva) Newsgroups: comp.lang.ada Subject: Re: Anybody in US using ADA ? Date: 3 Jan 2003 12:02:20 -0800 Organization: http://groups.google.com/ Message-ID: <20619edc.0301031202.1d0d8c1a@posting.google.com> References: <20619edc.0301021029.33f6cc69@posting.google.com> <20619edc.0301022244.2c16c563@posting.google.com> NNTP-Posting-Host: 206.245.217.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1041624140 3331 127.0.0.1 (3 Jan 2003 20:02:20 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 3 Jan 2003 20:02:20 GMT Xref: archiver1.google.com comp.lang.ada:32503 Date: 2003-01-03T20:02:20+00:00 List-Id: But isn't it the case that the amount of software in the "DoD arena", as well as in general in the areas where Ada would excel, is increasing much faster than such per-sloc reductions, so that total software budgets (and overruns) are becoming larger, and significantly so? Does anybody know of DoD numbers that show the total amount they spend, directly and indirectly, on software development per year? Mike "John R. Strohm" wrote in message news:... > Uh, excuse me? > > Cost per SLOC, in constant dollars, has declined SIGNIFICANTLY over the last > 20 years. This was one of the big findings in the SEI CMM stuff, that it > really is significantly cheaper to do things right the first time. > > At one point, I was informally putting together a business case for Ada and > Rational R1000s at GD/FW, based on (a) Rational's productivity numbers and > "force multiplier" effects, (b) the known size of F-16C/D operational flight > software, (c) the expected size of the next airplane's software, (d) the > size of the parking lots at GD/FW (which were ALREADY overflowing). > > "Mike Silva" wrote in message > news:20619edc.0301022244.2c16c563@posting.google.com... > > David Emery wrote in message > news:... > > > Mike Silva wrote: > > > > "Marin David Condic" wrote in message > news:... > > > > > > > >>Its a shame to see that many in the DoD arena are abandoning Ada > because > > > >>"Everybody else is using C++". > > > > > > > > > > > > Seems like we should be seeing some results of the "DoD arena" rush to > > > > C++ by now. As the data comes in, we should either see that indeed > > > > C++ introduced problems and added costs that Ada would have avoided > > > > (my expectation), or that it didn't (in which case, time to re-examine > > > > assumptions). So, where are the C++ disaster coverups, and/or the > > > > shining successes? > > > > > > In 1990 MITRE did an internal study based on then available data > > > saying that the cost to maintain Ada was -LINEAR- on SLOC, not > > > exponental as Barry Boehm says. If you think about this, it's a > > > radical conclusion. And it wasn't done by the Ada people at MITRE, but > > > by our cost center's statisticians and cost analysts > > > > > > Back when Emmett Paige was ASD-C3I, he held a series of Ada Dual-Use > > > summits. At each, my position was: DoD has the data available to show > > > if Ada has the value we claim. Let's collect the data and let the facts > > > speak for themselves. > > > > > > Two results from this experience: > > > 1. DoD didn't want to gather and then hear facts > > > 2. Language decisions are generally not made on the > > > basis of -any facts- but rather management perception of > > > "acceptability", "training costs", etc. > > > > > > dave > > > (been there, done that, forgot my T-shirt) > > > > The only reason things *may* be different this time is that the > > amount, and cost of writing, software is so much greater today than > > 10-20 years ago that the risk of failure (or gross overrun) may be too > > great to ignore or sweep under the carpet anymore, or, inverting, the > > potential savings from using the right tools may be too great to > > ignore.... > > > > Mike