Here’s the final “R” of the quartet I’ve been discussing: Refactoring and its proposition is so obvious that we usually forget about it. Note that I said obvious, not easy. Keep reading to figure out what I mean.
By Rafael Victória-Pereira
Finally, let’s discuss the final R of the Modernizing IBM i Applications from the Database up to the User Interface and Everything in Between IBM Redbook modernization goals: refactoring.
“Do No Harm”
Refactoring is a variation of reengineering: in this approach, the application’s code is improved in such a way that the functionality and interfaces with other applications are not affected. In other words (the words of Hippocrates), “do no harm” is also refactoring’s philosophy. To make sure that you really did no harm to the application or its operating context, extensive testing is required. Because tests, particularly of the magnitude required here, are very time-consuming, they should be as automated as possible. If your modernization process also included a UI modernization, there are many tools that can easily map and thoroughly test the interaction flow. There are also tools that can do the same for green-screen applications, although they are restricted to the boundaries set by the type of UI, which makes these tools less flexible.