From: Robert on
On Tue, 06 May 2008 12:38:35 -0600, Howard Brazee <howard(a)brazee.net> wrote:

>On Tue, 06 May 2008 12:06:02 -0500, Robert <no(a)e.mail> wrote:
>
>>Including other changes is the reason 'rehosting' projects fail. The rehosting and
>>business changes should be separate projects. For one reason, it simplifies regression
>>testing the rehosting project.
>
>Except that the whole reason for the conversion is to have the
>platform that the tools or system that the business purchased from a
>vendor.
>
>The users care diddly about the platform - they are buying the
>business change.

IT should pay for the platform change, because it could save 80% of platform expense and
40% of total IT budget. Those figures are from SABRE.

Use part of the savings to pay for the business change, the rest falls to the bottom line.
From: Robert on
On Tue, 06 May 2008 08:01:33 -0600, Howard Brazee <howard(a)brazee.net> wrote:

>On Mon, 05 May 2008 22:22:00 -0500, Robert <no(a)e.mail> wrote:
>
>>Changing the platform, say from mainframe to Unix server, does not require a rewrite, it
>>requires a recompilation.
>
>I've read about this theory - especially with regards to CoBOL. But
>I've done lots of real-world conversions, and they have all required
>rewrites.
>
>I guess this is because switching to new platforms has always been
>accompanied by bigger business changes than just finding a new
>computer.

Including other changes is the reason 'rehosting' projects fail. The rehosting and
business changes should be separate projects. For one reason, it simplifies regression
testing the rehosting project.
From: Anonymous on
In article <pk3124lqq3m7rqgkaqqlnbh0hm24bcvkb2(a)4ax.com>,
Robert <no(a)e.mail> wrote:
>On Tue, 06 May 2008 08:01:33 -0600, Howard Brazee <howard(a)brazee.net> wrote:

[snip]

>>I guess this is because switching to new platforms has always been
>>accompanied by bigger business changes than just finding a new
>>computer.
>
>Including other changes is the reason 'rehosting' projects fail. The
>rehosting and
>business changes should be separate projects.

Pish, tosh and piffle, Mr Wagner... aren't you aware that Everyone Knows
the best time to make major software upgrades is when you are also making
major hardware upgrades?

DD

From: Howard Brazee on
On Tue, 06 May 2008 12:06:02 -0500, Robert <no(a)e.mail> wrote:

>Including other changes is the reason 'rehosting' projects fail. The rehosting and
>business changes should be separate projects. For one reason, it simplifies regression
>testing the rehosting project.

Except that the whole reason for the conversion is to have the
platform that the tools or system that the business purchased from a
vendor.

The users care diddly about the platform - they are buying the
business change.
From: Howard Brazee on
On Sat, 3 May 2008 11:48:33 +1200, "Pete Dashwood"
<dashwood(a)removethis.enternet.co.nz> wrote:

>There seems to be some very pertinent comment here:
>http://www.devx.com/Java/Article/20791

I don't recall reading a text article followed by "Download the Codec
for this article". I didn't download anything despite my curiosity.