Critical analysis of vendor lock-in and its impact on cloud computing migration: a business perspective

Vendor lock-in is a major barrier to the adoption of cloud computing, due to the lack of standardization. Current solutions and efforts tackling the vendor lock-in problem are predominantly technology-oriented. Limited studies exist to analyse and highlight the complexity of vendor lock-in problem in the cloud environment. Consequently, most customers are unaware of proprietary standards which inhibit interoperability and portability of applications when taking services from vendors. This paper provides a critical analysis of the vendor lock-in problem, from a business perspective. A survey based on qualitative and quantitative approaches conducted in this study has identified the main risk factors that give rise to lock-in situations. The analysis of our survey of 114 participants shows that, as computing resources migrate from on-premise to the cloud, the vendor lock-in problem is exacerbated. Furthermore, the findings exemplify the importance of interoperability, portability and standards in cloud computing. A number of strategies are proposed on how to avoid and mitigate lock-in risks when migrating to cloud computing. The strategies relate to contracts, selection of vendors that support standardised formats and protocols regarding standard data structures and APIs, developing awareness of commonalities and dependencies among cloud-based solutions. We strongly believe that the implementation of these strategies has a great potential to reduce the risks of vendor lock-in

Re-engineering strategies for legacy software systems

Re-engineering can be described as a process for updating an existing system in order to meet new requirements. Restructuring and refactoring are activities that can be performed as a part of the re-engineering process. Supporting new requirements like migrating to new frameworks, new environments and architectural styles is essential for preservation of quality attributes like maintainability and evolvability. Many larger legacy systems slowly deteriorate over time in quality and adding new functionality becomes increasingly difficult and costly as technical debt accumulates. To modernize a legacy system and improve the cost effectiveness of implementing new features a re-engineering process is often needed. The alternative is to develop a completely new system but this can often lead to loss of years of accumulated functionality and be too expensive. Re-engineering strategies can be specialized and solve specific needs like cloud migration or be more generic in nature supporting several kinds of needs. Different approaches are suitable for different kinds of source and target systems. The choice of a re-engineering strategy is also influenced by organisational and business factors. The re-engineering of a highly tailored legacy system in a small organisation is different from re-engineering a scalable system in a large organisation. Generic and flexible solutions are well suited for especially smaller organisations with complex systems. The re-engineering strategy Renaissance was applied in a case study at Roima Intelligence Oy in order to find out if such a strategy is realistically usable, useful and valuable for a smaller organization. The results show that a re-engineering strategy is possible to be used with low overhead in order to prioritize different parts of the system and determining a suitable modernization plan. Renaissance was also shown to add value especially in the form of deeper understanding of the system and a structured way to evaluate different options for modernization. This is achieved through assessing the system from different views taking into account especially business and technical aspects. A lesson learned about Renaissance is that determining an optimal scope for the system assessment is challenging. The results are applicable for other organisations dealing with complex legacy systems with constrained resources. Limitations of the study are that the number of different kinds of re-engineering strategies discussed is small and more suitable strategies than Renaissance could be discovered with a systematic mapping study. The amount of experts participating in the process itself as well as the evaluation was also low, introducing some uncertainty to the validity of the results. Further research is needed in order to determine how specialized and generic re-engineering strategies compare in terms of needed resources and added value

KEY FACTORS INCREASING THE TRUST AND INTENTION TO ADOPT STANDARD CLOUD-BASED APPLICATIONS

A generic standard cloud-based application such as Google Docs are generally among the first to be considered for adoption by end-users. Thus, it is worthy to examine what factors influence trust and the intention of continuing use for such a cloud-based application. Unlike traditional, on-premise applications, familiarity is not an issue for trusting generic, simple cloud-based applications. Moreover, perceived risk is low enough that it has negative, as opposed to the usual positive, impact on trust and the intention of continuing use. The results of this study also imply that the agile adoption of standard cloud-based applications needs to consider factors, including perceived privacy control, system quality, and user satisfaction because these factors can increase the trust of users. Theoretical and practical implications were drawn from the findings of this study

Service Oriented Architecture Adoption: A Systematic Review

Service Oriented Architecture (SOA) has appeared as an absorbing architectural approach that empowers the available systems to reveal their performance in the act of services without creating important changes to the systems. This approach, due to its flexibility of adoption, has been widely appreciated by the businesses. Though there are many studies that depict successful factors of SOA, a few minor cases of failure have also been reported in the literature. In spite of the availability of rich material on SOA, there is no systematic literature review on the influential aspect of SOA adoption factors. Thus, this paper presents a systematic literature review of existing studies (from 2009 to 2015) related to the SOA adoption and its success and failure. The central purpose of the study is to focus on the existing issues and share the findings with researchers. Moreover, the findings of this paper would help the IT experts in organizations focus on the most important factors highlighted in this study, so they could decide whether it is advisable to adopt SOA in their context or not