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
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!ucbvax!MITRE-BEDFORD.ARPA!munck
From: munck@MITRE-BEDFORD.ARPA.UUCP
Newsgroups: comp.lang.ada
Subject: Re:  Software Reuse
Message-ID: <24332.551033743@mbunix>
Date: Thu, 18-Jun-87 12:55:43 EDT
Article-I.D.: mbunix.24332.551033743
Posted: Thu Jun 18 12:55:43 1987
Date-Received: Sat, 20-Jun-87 06:49:32 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
List-Id: <comp.lang.ada>


I don't know if I've ever seem a more straightforward explanation of the
DoD's Software Crises than this:

> As a "Government" manager of major software developments, ... There
> is no way, short of pushing my nose in it, that I will believe a
> paper analysis showing me how much _I_ will save tomorrow if only I
> give you more today.

Remember that the _I_ (underlining mine) is really "the poor slob who'll
be maintaining this system years after I get a job in Industry." 
Remember too, that EVERYBODY'S project is too important (major) to take
the risk of being the first to use any new technique.

Of course, with FORTRAN, JOVIAL, CMS-2, and/or the Chinese Army approach
to programming, there's no risk.  We KNOW that it will be late, over
budget, and buggy.  No surprises, no risks.

                      -- Bob Munck, MITRE