Statistical Comparison of Architecture Driven Modernization with other Cloud Migration Frameworks and Formation of Clusters

Corporations are migrating their legacy software systems towards the cloud environment for amelioration, to avail benefits of the cloud. Long term success of modernizing a legacy software depends on the characteristics of the chosen cloud migration approach. Organizations must think over how strategically imperative is the chosen cloud migration framework to their business? Thus, the Object Management Group (OMG) has defined standards for the modernization process based on Architecture Driven Modernization (ADM) framework. ADM serves as a vehicle for facilitating the arrangement of information technology with business stratagem and its architecture. Until now, it seems that there is no systematic mapping among ADM and other cloud migration frameworks, highlighting the demanding features. This research aims to give an in-depth study of similar cloud migration frameworks. Thus, the researchers introduced the clusters containing cloud migration frameworks having similar features to ADM. This systematic mapping can be seen as a valuable asset for those who are interested in choosing the best migration framework from the pool of cloud modernization frameworks, according to their legacy software requirements. The clustering technique is used to appraise and compare ADM with some of the other cloud migration frameworks for highlighting the similarities and key differences. The quality of clusters is evaluated by the Rand index and Silhouette measurements. The study distills the record and yields a sound and healthy catalog for essential events and concerns that are communal in cloud migration frameworks. This research offers the one-stop-shop convenience that the industry desperately desires.

Cloud Computing Adoption: An Effective Tailoring Approach

Many organisations are currently moving their legacy systems to the cloud as it offers on-demand, elastic, and pay-as-you-go service models. However, different cloud migration scenarios can involve different activities during the migration process using one of many existing migration methods to make legacy cloud-compliant. There is no universally superior or applicable method for all cloud migration scenarios. In situations like this, designing situation-specific methods that fit several existing migration scenarios would be beneficial to the industry. The literature review reveals that issues surrounding the method tailoring for the cloud migration have not been addressed yet. To effectively harness this shortcoming, the idea of situational method engineering approach is applied to develop a framework for designing and maintaining bespoke methods for moving legacies to the cloud. The paper demonstrates the applicability of the framework via presenting two scenarios of creating, configuring, and sharing situational methods

Cloud migration

Migrating on-premises applications to cloud environment has become a popular task for organizations. In this thesis, cloud migration is defined to be an action where one or more parts of an application are migrated to a cloud platform. Multiple motivations are mentioned for such migration like reducing costs, flexibility, and scalability of the application. This thesis also goes through different strategies for cloud migration. After that, a literature-based, generalized migration process for cloud migration was created. This created migration process was then validated against case process. Phases in the case process were investigated through interviews. Interviews were done in two parts. First, all interviewees were interviewed one at a time. From these interviews, a draft of the case process was done. This draft was then validated and supplemented with a group interview. After creating both processes, they were compared. It was found that the literature-based process had a lot of similarities with the case process. Also, it was found that the case process had a few tasks that were not mentioned in the literature-based process. These tasks were discussing future of the application, estimating workload and project end date, defining migration scope, and familiarizing customers with application. These can be said to be important tasks, and they should have been in the literature-based process too

REMICS- REuse and Migration of Legacy Applications to Interoperable Cloud Services

The main objective of the REMICS project is to develop a tool-supported model-driven methodology for migrating legacy applications to interoperable service cloud platforms. The migration process consists of understanding the legacy system in terms of its architecture and functions, designing a new SOA application that provides the same or better functionality, and verifying and implementing the new application in a cloud computing platform suitable for the purpose. The project started in September 2010 and the first phase of the project has focused on performing state of the art analysis, understanding the requirements of two pilot cases and experimenting with the technologies. REMICS also aims to develop and extend several standards related to knowledge discovery, service interoperability, service modeling in the cloud, and testing and runtime management of services. In this short paper we present the technological approach and the status of the project.REMICS- REuse and Migration of Legacy Applications to Interoperable Cloud Service

REMICS- REuse and migration of legacy applications to interoperable cloud services

The main objective of the REMICS project is to specify, develop and evaluate a tool-supported model-driven methodology for migrating legacy applications to interoperable service cloud platforms. The migration process consists of understanding the legacy system in terms of its architecture and functions, designing a new SOA application that provides the same or better functionality, and verifying and implementing the new application in the cloud. The demonstrations will cover the following REMICS research topics: model-based analysis and testing and model-driven interoperability with the tools by Fraunhofer FOKUS and SINTEF. Video is published at http://goo.gl/ExV38

Cloud provider independence using DevOps methodologies with Infrastructure-as-Code

On choosing cloud computing infrastructure for IT needs there is a risk of becoming dependent and locked-in on a specific cloud provider from which it becomes difficult to switch should an entity decide to move all of the infrastructure resources into a different provider. There’s widespread information available on how to migrate existing infrastructure to the cloud notwithstanding common cloud solutions and providers don't have any clear path or framework for supporting their tenants to migrate off the cloud into another provider or cloud infrastructure with similar service levels should they decide to do so. Under these circumstances it becomes difficult to switch from cloud provider not just because of the technical complexity of recreating the entire infrastructure from scratch and moving related data but also because of the cost it may involve. One possible solution is to evaluate the use of Infrastructure-as-Code languages for defining infrastructure (“Infrastructure-as-Code”) combined with DevOps methodologies and technologies to create a mechanism that helps streamline the migration process between different cloud infrastructure especially if taken into account from the beginning of a project. A well-structured DevOps methodology combined with Infrastructure-as-Code may allow a more integrated control on cloud resources as those can be defined and controlled with specific languages and be submitted to automation processes. Such definitions must take into account what is currently available to support those operations under the chosen cloud infrastructure APIs, always seeking to guarantee the tenant an higher degree of control over its infrastructure and higher level of preparation of the necessary steps for the recreation or migration of such infrastructure should the need arise, somehow integrating cloud resources as part of a development model. The objective of this dissertation is to create a conceptual reference framework that can identify different forms for migration of IT infrastructure while always contemplating a higher provider independence by resorting to such mechanisms, as well as identify possible constraints or obstacles under this approach. Such a framework can be referenced from the beginning of a development project if foreseeable changes in infrastructure or provider are a possibility in the future, taking into account what the API’s provide in order to make such transitions easier.Ao optar-se por infraestruturas de computação em nuvem para soluções de TI existe um risco associado de se ficar dependente de um fornecedor de serviço específico, do qual se torna difícil mudar caso se decida posteriormente movimentar toda essa infraestrutura para um outro fornecedor. Encontra-se disponível extensa documentação sobre como migrar infraestrutura já  existente para modelos de computação em nuvem, de qualquer modo as soluções e os fornecedores de serviço não dispõem de formas ou metodologias claras que suportem os seus clientes em migrações para fora da nuvem, seja para outro fornecedor ou infraestrutura com semelhantes tipos de serviço, caso assim o desejem. Nestas circunstâncias torna-se difícil mudar de fornecedor de serviço não apenas pela complexidade técnica associada à criação de toda a infraestrutura de raiz e movimentação de todos os dados associados a esta mas também devido aos custos que envolve uma operação deste tipo. Uma possível solução é avaliar a utilização de linguagens para definição de infraestrutura como código (“Infrastructure-as-Code”) em conjunção com metodologias e tecnologias “DevOps” de forma a criar um mecanismo que permita flexibilizar um processo de migração entre diferentes infraestruturas de computação em nuvem, especialmente se for contemplado desde o início de um projecto. Uma metodologia “DevOps” devidamente estruturada quando combinada com definição de infraestrutura como código pode permitir um controlo mais integrado de recursos na nuvem uma vez que estes podem ser definidos e controlados através de linguagens específicas e submetidos a processos de automação. Tais definições terão de ter em consideração o que existe disponível para suportar as necessárias operações através das “API’s” das infraestruturas de computação em nuvem, procurando sempre garantir ao utilizador um elevado grau de controlo sobre a sua infraestrutura e um maior nível de preparação dos passos necessários para recriação ou migração da infraestrutura caso essa necessidade surja, integrando de certa forma os recursos de computação em nuvem como parte do modelo de desenvolvimento. Esta dissertação tem como objetivo a criação de um modelo de referência conceptual que identifique formas de migração de infraestruturas de computação procurando ao mesmo tempo uma maior independência do fornecedor de serviço com recurso a tais mecanismos, assim como identificar possíveis constrangimentos ou impedimentos nesta aproximação. Tal modelo poderá ser referenciado desde o início de um projecto de desenvolvimento caso seja necessário contemplar uma possível necessidade futura de alterações ao nível da infraestrutura ou de fornecedor, com base no que as “API’s” disponibilizam, de modo a facilitar essa operação.info:eu-repo/semantics/publishedVersio

REMICS- REuse and Migration of Legacy Applications to Interoperable Cloud Services - REMICS Consortium

International audienc