scholarly journals Challenges in migrating legacy software systems to the cloud — an empirical study

2017 ◽  
Vol 67 ◽  
pp. 100-113 ◽  
Author(s):  
Mahdi Fahmideh Gholami ◽  
Farhad Daneshgar ◽  
Ghassan Beydoun ◽  
Fethi Rabhi
Author(s):  
Lerina Aversano ◽  
Raffaele Esposito ◽  
Teresa Mallardo ◽  
Maria Tortorella

In e-business, addressing the technical issues alone is not enough to drive the evolution of existing legacy applications, but it is necessary to consider problems concerning the strict relationship that exists between the evolution of the legacy system and the evolution of the e-business process. To fulfill this purpose, this chapter proposes a strategy for extracting the requirements for a legacy system evolution from the requirements of the e-business process evolution. The strategy includes a toolkit composed of a set of decision tables and a measurement framework, both referring to the organization, business processes, and legacy software systems. The decision tables allow the identification of the processes to be evolved, the actions to be performed on them and their activities, and the strategies to be adopted for evolving the information systems. The measurement framework aims at achieving a greater understanding of the processes and related problems, taking into account organizational and technological issues.


Author(s):  
Gill Mallalieu ◽  
Steve Clarke

The idea of the ‘wicked problem’ (Churchman, 1967), which advocates a pragmatic oscillation between problem and solution, rather than an attempt to reduce the problem to a series of steps to be followed sequentially, has been particularly helpful to us in conceptualising the relationships between people, organisations and information technology (IT). This conceptualisation was tested in the RAMESES project (Risk Assessment Model: Evaluation Strategy for Existing Systems), using grounded theory (Strauss and Corbin, 1997) as the basis for the methodology. The overall objective of RAMESES is ‘to provide a strategic model for the risk assessment of legacy software systems within SMEs (small-to-medium enterprises) considering business process change.’ Thus the relationship between the organisation, the way its staff carried out its processes, and their legacy IT systems was at the centre of our concerns. This chapter describes how the broad conceptualisation of the problem led to a detailed method to address it and the results available to date.


Author(s):  
K. Velmurugan ◽  
M.A. Maluk Mohamed

One of the vital reasons for reverse engineering legacy software systems is to make it inter-operable. Moreover, technological advancements and changes in usability also motivate reverse engineering to exploit new features and incorporate them in legacy software systems. In this context, Web services are emerging and evolving as solutions for software systems for business applications in terms of facilitating interactions between business to business and business to customers. Web services are gaining significance due to inherent features like interoperability, simple implementation, and exploiting the boom in Internet infrastructure. Thus, this work proposes a framework based strategy using .net for effortless migration from legacy software systems to Web services. Further, this work also proposes that software metrics observed during the process of reverse engineering facilitate design of Web services from legacy systems.


2021 ◽  
Vol 173 ◽  
pp. 110868
Author(s):  
Manel Abdellatif ◽  
Anas Shatnawi ◽  
Hafedh Mili ◽  
Naouel Moha ◽  
Ghizlane El Boussaidi ◽  
...  

Author(s):  
Lerina Aversano ◽  
Daniela Guardabascio ◽  
Maria Tortorella

Software architecture is an artifact that expresses how the initial concept of a software system has actually been implemented. However, changes to the requirement imply continuous modification of the software system and may affect its architecture. It is expected that when a software system reaches the mature state, the requirements for evolution decrease and its architecture becomes more stable. The paper analyzes how the architecture of a software system evolves during its life cycle, with the aim of obtaining quantitative information on its possible instability after it has been declared mature. The goal is to verify if the architectural instability decreases with the increase of the software system maturity and to identify the software components that are more unstable among multiple releases. The paper proposes metrics that measure the instability of the architecture of a software system and its components through different releases. Open source software projects classified as mature and active and related historical data are analyzed. The results of the empirical study point out that the instability of software projects continues to evolve even after they are declared mature. The proposed metrics give a useful support for investigating the instability of a software project, even if further factors can be analyzed. Furthermore, the study can be replicated on other software systems belonging to different domains and developed using different programming languages.


Sign in / Sign up

Export Citation Format

Share Document