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:
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:
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
“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.
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
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.
Cloud Computing is intrinsically service-based. But this is not just in the highly generalized sense of the term ‘service’, but also in the more specific Service Oriented Architecture (SOA) use of the term, where capabilities are provided via published service interfaces. In this research note we consider why SOA should not be forgotten just because more fashionable terms have risen to the top of the toybox.