Re: A Re-Write

[Booth Martin <booth@xxxxxxxxxxxx>]

Having done this twice, I would suggest a winnowing process.  Identify a 
few criteria, and define them with this Rule of Thumb:  "Give us Bang 
for the Buck!"  Talking it over ahead of time is well worth it, 
especially to keep expectations in line.  You are most likely talking a 
two year process, maybe more.

Not much sense in converting a process that is used once a year, for 
year-end processing, for example, but then again, there might be a lot 
of value in updating a piece that has a long tradition of being 
troublesome to use or train in your shop.

The next suggestion is to pick a couple of small pieces to do first. 
Get them under your belt, see the typical problems, and gain a sense for 
how the process itself will work best with you and your users.

Establish standards now.  Simple ones, but get them in place first.

Thats just my 2 cents.

steema@xxxxxxxxxxxxx wrote:
> Hi -
> What are some steps and methodologies you would take if given an objective
> to re-write an old RPG 3 system? Management wants to go to ILE.
> Some of my ideas:
>
> 1. Identify all parts used on the old system. Warehouse Distribution w/
> Imports type of company.
> 2. Take all input screen online programs and see what parts can be written
> into a service program, procedures, modules, etc...
> 3. Do same for batch processes and report writing.
>
> Not sure how I would organize this effort.
>
> Steve