Application Modernization

Application Modernization should be much more than replacing legacy application “silos” with new silos, or acquiring the latest vendor technology.  Modernization should mean delivering open solutions within a genuinely agile architecture designed for responsiveness to business needs - delivering a modular architecture implemented with a portfolio of services.  Increasingly, application modernization is being driven by business process modernization and the need to rationalize and align the supporting software portfolio.

Key Application Modernization questions include:

  • How do we leverage existing investments to maximum advantage?
  • What modernization techniques should we use to increase efficiency?
  • How can we use architecture and modeling to reduce time-to-market and make our portfolio easier to modernize?
  • How can we ensure incremental progress while managing overall risk?

Application Modernization as practiced by Everware-CBDI is an architected and engineered process that ultimately produces a smaller overall software footprint which is more responsive to the business.  Ongoing, our modernized solutions can then be continuously modernized in a high-value/low-risk manner rather than high-risk/high-cost “big bang” replacement. 

This type of portfolio modernization is best accompanied with an appropriate level of organizational transformation grounded on service management and governance.  Our standards-based CBDI Service Architecture and Engineering framework provides the adaptive best-practice to enable that transformation.   Unlike outsourcing firms and translation/conversation vendors, we integrate our customer’s team with this effort to ensure internal ownership and long-term integrity of the modernized solutions.

Our Modernization consulting offerings include:

Agile Modernization

Increasing modernization efficiencies with agile approaches

Application Modernization for the Service Oriented Cloud

Application Modernization for the Service Oriented Cloud

Application Modernization Planning

Creating and directing the Modernization Roadmap

CA Gen Modernization

Modernizing your CA Gen assets while maximizing ROI

Model-Driven Development

Increasing modernization efficiencies with model-driven approaches

Portfolio Transition Engineering

Constructing and deploying a modernized portfolio

Service Oriented Application Modernization

Increasing modernization efficiencies with SOA and agile approaches

Associated Reports

SOAM Case Study Healthcare Benefits Management Application

This SOAM Case Study highlights the combination of Agile SOA with Model Driven Development in a large-scale project to deliver a Healthcare Benefits Management Application

MDAgile Datasheet (pdf)

Everware-CBDI’s development approach, known as Service Oriented Application Modernization (SOAM), in conjunction with our integrated toolset, MDAgileTM, addresses the challenges of achieving speed and agility – at scale.  By integrating SOA, Agile Methods and Model Driven Development (MDD), we are able to achieve significant improvements in development cycle-time with a commensurate reduction in project risk.  The end result is that IT is able to field higher quality solutions more rapidly and to be more responsive to the business.

MDAgileTM provides the tooling that supports SOAM and consists of the Service Specification Portal, the Construction Engine and the Transformation Asset Library.  By building an integrated suite of models, all under configuration management, teams can apply agile methods to work on aspects of the overall system without concern that what they are producing will negatively impact other teams. 

Realizing Agile IT for IT Leaders

“Agile IT” represents the ultimate goal for IT transformation – enabling IT to respond rapidly to changing business needs. Most large IT organizations have determined that business as usual won’t produce the needed agility and are adopting modern approaches.  However, as we have learned, adopting new methods on a piecemeal basis won’t get you there either.  An integrated approach is needed. Agile IT combines best practices from agile methods, service oriented architecture and model-driven development under a management framework known as portfolio transition engineering.

Adopting Agile IT within the typical IT environment requires additional capabilities and adjustments to current IT management practices.  Agile methods provide rapid delivery of capability increments.  However, to scale agile methods, project teams must be able to work independently.  Service Oriented Architecture (SOA) provides the organizing paradigm that allows smaller teams to achieve parallel development on a massive scale. This creates pressure on release management and development coordination disciplines.  Model-based development facilitates precise communications and synchronizes products across teams. Portfolio transition engineering enables the organization to implement and assimilate the rapid changes within a coherent framework.

This paper explains what Agile IT is, why it is needed and provides insights into how to prepare your organization to become more responsive to business challenges today.

Application Migration Patterns for the Service Oriented Cloud (pdf)

As well as deploying new applications to the cloud, many organizations will also be considering the opportunities to migrate current applications to the cloud in search of reduced costs or SLA improvements.  In this research note we consider several migration alternatives, expressed as a set of patterns.

The patterns can also be seen as a sequence of activities, through which the current application is gradually modernized

The Agile Application Modernization Project (pdf)

In this report, we discuss an agile project structure and organization and provide a detailed breakdown of the Application Modernization process in terms of Project Phases and Work Packages.

This approach to application modernization will allow an escalation from a sponsored modernization effort to an enterprise SOA effort over time. It can be viewed as the pragmatic middle ground between a difficult to motivate enterprise level SOA and successive SOA projects that will inevitably lead to service anarchy.