Enterprise Evolution | FREQUENTLY ASKED QUESTIONS II
Frequently Asked Questions II
Can organizations modernize applications in phases, or does it require an all-at-once replacement
of entire systems?
Modernization is by nature an incremental process. The assessment, for example, is phase one.
Depending on the type of project, subsequent phases may include user interface changes;
remediation work to rationalize and modularize data usage and program logic; data redesign;
platform or language migration; and the extraction and reuse of business logic under target
architectures. Because each step cited in this modernization roadmap brings systems increasingly in
line with business requirements, management can readily justify incremental deliverables in their
own right. So while it is common sense to phase in any project containing a natural progression of
incremental steps, it makes even more sense to deliver incremental value back to the business
community sooner versus later.
Are there tools to remediate our applications before we transform them into the target
There are tools and techniques to remediate applications prior to migrating them to target
architectures. For example, teams can rationalize redundant, hard to decipher data definitions;
cleanup poorly structured source code; isolate data access, user access and business logic;
modularize programs along functional lines; and consolidate functional redundancies. These are
manageable, low risk options that produce systems that are significantly more adaptable to target
architectures, including SOA, model driven architecture (MDA), J2EE or .NET, and to target
languages such as Java or C#.
What is the value of remediation from a cost/benefit or business value perspective?
Application remediation provides significant benefits based on the requirements driving the
initiative. Cost benefits should be business-driven to the degree possible. Typical examples include