Of course, when dealing with modern underlying architecture, this approach works just fine. However, that’s rarely the case. Legacy applications in need of modernization are typically built on at least 10 – 15 year old (or older) architecture.
The problem this creates: Much has changed in that time. Programming methods have changed. Databases have changed. Application structures have changed. That’s just the beginning.
With all of these changes, you can’t simply build a new interface on top of old architecture and expect it to fit your needs. These changes require a fundamental shift in application architecture and development as a whole.
I could go on, but we’ve outlined everything in a free white paper entitled: Crash Course in Modernization. It explains the changes you must address, and even outlines 5 different modernization methods.