From: smccoy@hisd.harris.com (Scott McCoy)
Subject: Three releases and rewrite?
Date: 1996/08/14
Date: 1996-08-14T00:00:00+00:00 [thread overview]
Message-ID: <4utj8s$14q@su102w.ess.harris.com> (raw)
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.
next reply other threads:[~1996-08-14 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-14 0:00 Scott McCoy [this message]
1996-08-15 0:00 ` Three releases and rewrite? Dr. Richard Botting
1996-08-17 0:00 ` Robert Dewar
1996-08-17 0:00 ` Scott McCoy
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox