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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d3d1abbae7094b87,start X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,d3d1abbae7094b87,start X-Google-Attributes: gidf43e6,public From: smccoy@hisd.harris.com (Scott McCoy) Subject: Three releases and rewrite? Date: 1996/08/14 Message-ID: <4utj8s$14q@su102w.ess.harris.com>#1/1 X-Deja-AN: 174230399 sender: smccoy@dr3w (Cheshire Cat) content-type: text/plain; charset=us-ascii organization: Harris Corp. Information Systems Division mime-version: 1.0 reply-to: smccoy@hisd.harris.com newsgroups: comp.software-eng,comp.lang.ada Date: 1996-08-14T00:00:00+00:00 List-Id: General question: In the recent past, as my group has gotten more and more away from pure DoD development and more into non-government work, I've noticed something: It seems like a rule of thumb for commercial software applications is that after three major releases (i.e., 1.0, 2.0, 3.0), you rewrite the application from scratch. Now, I understand that technology constantly changes (new languages, utilities, architectures, etc.), so a rewrite after three releases would be sensible in order to keep competitive. Is this a reasonable rule of thumb? (I thought this relevant to the Ada folks, since we often get requirements that systems must be operational for 20 years, so we don't get the opportunity to do a re-write every few years.) -- Scott McCoy Opinions expressed are my own. ON HUMILITY To err is human, to moo bovine.