RE: A Re-Write

1. Identify the business rules and write modules to enforce them.
Document the heck out of them.
2. Create all new data bases and enforce rules at the data level.  I.e..
Referential integrity
3. Create standard screen layouts and code screen handling, weather HTML
or 5250, create a standard layout and screen control.
4. Fill in the blanks.  In other words, make the screens work, using the
business rule objects created in step one.  (This is where you will be
thankful you documented the heck out of them.)
5. Start on your standard reports and graphs outputting it all to PDF so
it never get put on paper.  He. He. He.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

707.586.0551, ext. 1102
707.585.5700 FAX

Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com

Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information.  If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any
attachments thereto, is strictly prohibited.  If you have received this
e-mail in error, please immediately notify me by e-mail (by replying to
this message) or telephone (noted above) and permanently delete the
original and any copy of any e-mail and any printout thereof.  Thank you
for your cooperation with respect to this matter.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
steema@xxxxxxxxxxxxx
Sent: Tuesday, December 06, 2005 1:42 PM
To: Midrange Systems Technical Discussion
Subject: A Re-Write

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.