|
Eric,Retrofitting the future into the past is not as difficult as it seems. But it takes a little strategy, and the baggage we carry is not strategic at all.
A quick example. ILE was introduced 12 years ago. It allowed our developers to write modular code. For those people who have already implemented ILE correctly, they have already made a step in the right direction. For those people who have not, it would be best for them to start using ILE correctly first.
I look at commitment control like this. For new applications, it is a required component. Is there a business benefit to retro-fitting it? If so, then retro-fit it.
Trevor----- Original Message ----- From: "DeLong, Eric"
Subject: RE: Application design & architecture
Trevor, As Walden put it, we're looking to renovate our applications while we're living there. Many of the issues we deal with relate to poor design,fractured development, poor documentation, loss of technical expertise, andso forth. We're looking to proceed with ILE to support a retrofit of ourapplications. At the same time, we want to ensure that the framework we laydown now will support our goals for the future... Much of the problem comes from the "baggage" that as400 pros have carried with them over the years. The bit about commitment control is just one ofthe many elements being denied to the developer simply because 20 years agoit caused a problem.... Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-297-2863 or ext. 1863
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.