From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=3.0 tests=BAYES_00,TO_NO_BRKTS_PCNT
	autolearn=no autolearn_force=no version=3.4.5-pre1
Date: 3 Jun 93 16:20:26 GMT
From: mdisea!mothost!schbbs!tigger!tannen@uunet.uu.net  (David Tannen x8273)
Subject: Re: Contractors submitting inaccurate Ada reuse surveys
Message-ID: <1993Jun3.162026.24147@schbbs.mot.com>
List-Id: <comp.lang.ada>

This is a great idea from the DoD, but the DoD contracts people have no way of 
knowing
if code is really being reused.  Is code reuse being done when you rewrite <50%
 of
a package body for each new application?  Should a contractor be rewarded for t
his
kind of reuse?  Or should the developer's adjust their design to utilize the 
components that are available?


At last year's TriAda there was a great reuse tutorial given by JP Rosen.  He a
lso
wrote an article in CACM last year concerning Ada components.  His basic premis
e is
that we need to work more like a EE does.  When a EE is designing a circuit, he
will design for components that already exist (adjusting his wonderful design t
o
use as much off the shelf material as possible).  Most programmers (myself incl
uded)
tend to write the software ourselves, because we don't trust other people's cod
e.


Greg what are you going to do if the contractor submits a list of "in-house" 
components that will be reused?

David Tannen
-------------------------------------------------------------------------------
-----
-- "Dependence on wizardry to mitigate the fundamental limitations of software
-- is called 'hacking'."  Grady Booch
-------------------------------------------------------------------------------
-----