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 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!usc!apple!netcomsv!jls From: jls@netcom.COM (Jim Showalter) Newsgroups: comp.lang.ada Subject: Re: Reserve Demobilization System Built Around Reused Ada Code Message-ID: <1991Jun1.042319.29304@netcom.COM> Date: 1 Jun 91 04:23:19 GMT References: <0D010010.gk4ndi@brain.UUCP> Organization: Netcom - Online Communication Services UNIX System {408 241-9760 guest} List-Id: >I don't disagree one bit. What I hate to see is another contractor horn-blowing >what was ultimately a rehashing of existing code. It was certainly NOT a >properly engineered system that drew on an established repository of reusable >code. It is misleading to the customer and the industry at large to portray >such development efforts as true reuse. I am NOT demeaning the achievement. >Let's just call a spade a spade. Maybe "rapid tailoring" or "rapid reengineering" >is a more suitable term for this type of approach. Chuck, why do I get the idea that we basically agree on a fundamental set of core principles, but keep getting wound around the axle because of semantics? You say tomayto, I say tomahto... (I'm not flaming--it is just an observation I've made.) Perhaps in this case the disagreement is simply due to my belief that the use of code more than once constitutes reuse BY DEFINITION, in contrast with some other notion you (I THINK) refer to as "true reuse". I guess the problem I have is I don't know what true reuse is, or how it differs from reusing (as opposed to rewriting from scratch) 800KSLOC of code on the project described at the beginning of this thread. I'm reminded, in fact, of a paper a friend of mine gave on reuse (he got his PhD in the subject) in which his opening words were "I'm not sure what reuse means". He went on to explain that it was a lot like the paradox of AI: every time someone achieves something in the AI domain, people respond by saying "Oh, well, THAT'S not AI, that's just ". And yet, progress keeps getting MADE in the AI field. Is reuse going to be a victim of the same phenomenon? My personal view of reuse is that it happens all the time, it happens in great amounts, and we all think there is a terrible problem with achieving reuse because we refuse to recognize it when it is staring us in the face because we were expecting something else, something more remarkable and harder to grasp. -- **************** JIM SHOWALTER, jls@netcom.com, (408) 243-0630 **************** *Proven solutions to software problems. Consulting and training on all aspects* *of software development. Management/process/methodology. Architecture/design/* *reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++. *