Professional Documents
Culture Documents
DOI: 10.1007/s11633-014-0776-7
Abstract: Legacy system migration to the cloud brings both great challenges and benets, so there exist various academic research
and industrial applications on legacy system migration to the cloud. By analyzing the research achievements and application status,
we divide the existing migration methods into three strategies according to the cloud service models integrally. Dierent processes
need to be considered for dierent migration strategies, and dierent tasks will be involved accordingly. The similarities and dierences
between the migration strategies are discussed, and the challenges and future work about legacy system migration to the cloud are
proposed. The aim of this paper is to provide an overall presentation for legacy system migration to the cloud and identify important
challenges and future research directions.
Keywords: Migration, legacy system, cloud, infrastructure as a service (IaaS), platform as a service (PaaS), software as a service
(SaaS).
is Format images. The format of the respective component legacy systems will be completely replaced by commercial
transformed into another format in the second type, for ex- software delivered as a cloud service. Based on the second
ample, transforming a virtual machine image or enabling sub-strategy, some functionality of legacy systems will be
the execution of scripting languages on PaaS. Holistic mi- replaced by cloud service. To the third sub-strategy, legacy
gration aims to realize migration to complete application systems will be reengineered to cloud service. In reality, en-
built out of multiple components by migrating each com- terprises often migrate their legacy systems to cloud plat-
ponent separately. According to the holistic migration, the form by adopting the rst strategy. To this strategy, the
authors proposed the cloud motion framework that could migration is relatively easy to implement and has good cost-
leverage existing application models and provide support benet. But the migration could not take full advantage of
to migrate composite applications to cloud[17] . Reference cloud platform. To the second strategy, legacy systems need
[18] identied four migration types that could cloud-enable to be adapted according to the target platform, which can
applications by adaptation. The rst type replaces compo- bring disadvantages include missing capabilities, transitive
nents with cloud oerings, which is the least invasive type risk, and framework lock-in. To the SaaS related strategy, if
of migration. The second describes the case that migrates legacy system is replaced by commercial software delivered
some of the application functionality to the cloud. The as a service, the migration eort will be reduced greatly and
third is the classic migration case where the whole software reengineering is unnecessary. When replacing some business
stack of the application is migrated to the cloud. The last logic with existing cloud service, the adaption to the legacy
is complete migration of the application, which requires the system is necessary. But to reengineer legacy system to
migration of data and business logic for the cloud. While cloud service, the related work will be very challenging, and
Gartner[26] suggests information technology (IT) organiza- may require reverse engineering, structure redesign, service
tions consider the following ve options when they seek to generation, and so on. After comparing and analyzing, we
move legacy systems to the cloud: rehost on infrastruc- map the migration methods mentioned above to these ve
ture as a service, refactor for platform as a service, revise specic strategies. The mapping result is showed in Table
for IaaS or PaaS, rebuild on PaaS and replace with soft- 1.
ware as service. However, Cisco considers three application The proposed strategies realize classication to cloud mi-
migration options including SaaS, PaaS and IaaS in white gration in essence, which can cover all migration cases.
paper for migration of enterprise application to the cloud. Through mapping existing migration methods to the pro-
They think the migration to SaaS is no longer an applica- posed strategies, the migration methods can be better un-
tion migration but more of a replacement of the existing derstood and compared explicitly.
application with a SaaS. Migration to PaaS is an option
for migrating business applications that are based on stan- 3 Migration to IaaS and PaaS
dard application server software such as JavaEE or .net
platforms. Migration to IaaS involves deploying the appli- 3.1 Migration to IaaS
cation on the cloud service provider s servers. In addition,
the criteria that are used for considering every application Infrastructure as a service is a form of hosting, which in-
migration are discussed[27] . Similarly, Solentive software cludes network access, routing services, and storage. IaaS
proposed three main approaches for migrating legacy sys- provider generally provides hardware and administrative
tem to the cloud in a white paper, namely Iaas, PaaS and services used to store applications and a platform for run-
SaaS. The white paper looks at these approaches in detail ning applications. A virtual machine is built for an applica-
and analyzes the benets and disadvantages of each[28] . tion, which is loaded with all the software that will eventu-
Through comparing and analyzing, we can categorize ally run in the cloud. Then the virtual machine is uploaded
the migration into three strategies integrally: migration to to IaaS vendor s hosting environment and deployed to run.
IaaS, migration to PaaS and migration to SaaS. The rst IaaS is the best choice for moving applications to the cloud
strategy implements migration only by porting legacy sys- when there is no time to reengineer the applications for a
tem to the cloud by using IaaS. The legacy system will be cloud[29] .
migrated to the cloud by system refactoring according to With respect to migration method, cloud comput-
the platform of PaaS in the second strategy. As to the mi- ing service providers, such as Amazon and Cisco, pro-
gration to SaaS, it can be divided into three sub-strategies vide the details for migrating legacy systems to their
concretely, namely replacing by SaaS, revising based on platforms[27, 30] . Zhang[31] conducted migration studies
SaaS and reengineering to SaaS. To the rst sub-strategy, by migrating Hadoop and RUBiS to EC2 cloud platform.
Migrate to IaaS Migrate to PaaS Replace by SaaS Revise based on SaaS Reengineer to SaaS
Reference [17] type I, type III type II, type III type III
Reference [18] type III type I,type II type I, type IV type IV
Reference [26] rehost, revise refactor, revise, rebuild replace
Reference [27] to IaaS to PaaS to SaaS
Reference [28] to IaaS to PaaS to SaaS
J. F. Zhao and J. T. Zhou / Strategies and Methods for Cloud Migration 145
Through experiments, the installation mistakes and cong- 1) Dynamic resource requirement.
uration errors were identied as the two major sources of 2) Restriction to data storage location.
errors in migration. Then a migration management frame- 3) Requirement of special hardware devices.
work was proposed for providing the installation automa- 4) Amount of data stream.
tion and conguration validation, which uses templates to
simplify the largescale enterprise system installation process 3.2 Migration to PaaS
and uses policy to validate the conguration and monitor
the conguration changes[31] . Platform as a service is an application development and
Besides technology domain need to be taken into account, deployment platform delivered as a service to developers
there are a number of factors to weigh before migrating over the web, which provide the hardware plus a certain
legacy system to IaaS such as meaningful prerequisites, - amount of application software such as databases, middle-
nancial and legal considerations, culture shift, and so on. ware, and development tools. Migration based on PaaS is
If these conditions cannot be satised, migration of legacy not mandatory for resource management, but it is required
system to IaaS will be harder[32] . By presenting the re- to make the legacy system compatible to the requirement
sult of a case study that investigated the migration of an of PaaS provider.
IT system from a company s in-house data center to EC2, Microsoft, Cisco, and Solentive provide guide for migra-
reference [16] discussed the implications of migrating legacy tion to PaaS from technology domain[27, 37, 38] , but these
systems to the cloud from the perspective of an enterprise or guidelines are restricted to the PaaS they provide and not
organization. In addition to the benets of using the cloud, applicable to other general cases. For the general cases,
the signicant risks, such as deterioration of customer care reference [36] specied further checking steps for applica-
and service quality, increased dependence on external third tion migration to PaaS, including programming language,
party, lack of supporting resources, and so on, will come up. database, restrictions and limitations of the selected PaaS
Enterprise decision-makers should consider the overall orga- besides checking specic requirements related to hardware,
nizational implications of the changes brought by migrating software and input data as discussed in migration to IaaS.
legacy system to the cloud, so they can avoid implementing Furthermore, the general solutions to solve incompatibil-
local optimizations at the cost of organization-wide perfor- ity issues of database migration were discussed. Tran et
mance. al.[39] dened the scope of migration software system for
Many general instructions have been proposed to pro- the cloud. They identied all activities in migration that
vide guidance for application migration to IaaS. For ex- start from getting familiar with the application, the target
ample, Kothari and Arumugam[33] introduced guidelines to cloud platform, and the third party tool, then to build the
assess the feasibility of migrating applications to the cloud environment and get ready for migration, as well as to mod-
and suggested a general migration strategy for applications. ify and test to ensure that the application properly runs in
Sattaluri[34] discussed dierent aspects that need to be con- the cloud. Finally based on the experience of migrating
sidered during the application migration to IaaS. While PetShop. Net to Windows Azure and migrating Java Pet
Yunus[35] presented costs and risks of application migration Store to Amazon EC2, they compared the dierence be-
to IaaS, Mossburg listed four important points that lead to tween migrating legacy system to PaaS and to IaaS.
a successful cloud migration. These works provide general In brief, PaaS supplies a complete cloud IT stack for soft-
instructions for migration to IaaS. Reference [36] gave fur- ware development and delivery, which makes it possible to
ther details about what to do and how to do for application build true cloud applications and release them in a scal-
migration to IaaS. The existing research mentioned above able and elastic environment. Moreover, it also produces
can be divided into two aspects on the whole, namely mi- numerous restrictions at every technology layer of the ap-
gration method and migration decision. We present Table plication stack:
2 to show the focus of the existing research. 1) Programming language.
2) Database.
Table 2 Focus of the existing research in migration to IaaS 3) Middleware.
4) Third party library.
Migration method Migration decision 5) Restriction of the selected PaaS.
Reference [27] +
Reference [30] +
Reference [31] +
4 Migration related SaaS and compar-
Reference [32] + ison among strategies
Reference [16] +
Reference [33] + + SaaS is a software delivery model in which software and
Reference [34] +
associated data are centrally hosted on the cloud. SaaS is
Reference [35] +
typically accessed by users using a thin client via a web
browser, which has many advantages over the traditional
Reference [36] +
software delivery model. The recurring revenue stream,
In short, users have full privileges on the allocated virtual simpler maintenance and application update, and the lower
machine (VM) in migration to IaaS. They could do anything cost of delivery and distribution are especially attractive for
to the VM, but there is something need to be considered both application provider and end users. These advantages
before conducting migration: are driving a growing number of organizations of all sizes
to adopt SaaS solutions in order to achieve their business
146 International Journal of Automation and Computing 11(2), April 2014
we present Table 3 that maps them to the abstraction tiers structure, the redesign of the system structure and deploy-
described in SOA-MF. ment of the redesigned system. A framework MOMISC
Table 3 Mapping existing migration approaches to abstraction
was presented, which oers a set of solutions and tools to
tier
support migrating existing systems to the cloud. Based on
the framework, a hotel booking application was migrated
Code Basic design Composite design Concept to EC2 for verifying the feasibility of the framework.
Reference [41] + Through investigation of existing research, reuse and mi-
Reference [43] + + gration of legacy applications to interoperable cloud services
Reference [44] + (REMICS), a research project supported by the European
Reference [46] + Commission that started in 2010 for a period of three years,
Reference [48] + + has identied further work that needs to be done in the
Reference [49] + + project. Specically, knowledge discovery involves business
Reference [50] + + + and rule recovery that are necessary for identifying services
Reference [51] + + +
and designing new business processes except reverse engi-
neering of legacy code. Comprehensive methodology is em-
ployed to address dedicated design patterns and transfor-
4.2 Migration related SaaS
mations, especially for migration to the cloud. Migration
In order to provide some guidance on modifying architec- tools and methods need integration with model-based de-
ture of a service-based system for cloud computing, Babar velopment methods. PIM for SOA and cloud computing
and Chauhan[20] revealed some insights when they under- can adapt many dierent platforms in the cloud and di-
took a research and development project aimed at mod- verging technologies. These problems have been partially
ernizing an open source software framework, Hackystat, for addressed by developing methods, languages, transforma-
leveraging the exibility and scalability of the cloud com- tions and tools. The REMICS methodology will integrate
puting paradigm. In the process of migration, the key re- all these in an agile, model-driven, and service-oriented
quirements that can be migrated to the cloud are identied methodology for modernizing legacy systems in the end.
rstly. Having identied the key requirements, the next The migration starts with the recover activity which ex-
task is to analyze those requirements in the context of the tracts the architecture of the legacy application. The re-
existing architecture in order to gain a good understanding cover activity is implemented by knowledge discovery and
of the kinds of architectural change needed to be made. Fi- reverse engineering. The source architecture helps to ana-
nally, the architecture will be modied in accordance with lyze the legacy system, identify the best ways for migration,
the identied architecture change. Because this work fo- and benet from model-driven engineering technologies for
cused on the migration of the service-based system to cloud generation of the new system. The migrate activity reforms
computing platform, it did not involve reverse engineering. the source architecture into target architecture for service
Zhang et al.[19] proposed a generic methodology to guide cloud platform. In migration activities, SOA and cloud
how to migrate legacy system to cloud platform. The computing patterns are applied, legacy components may
generic methodology includes the following steps: represen- be replaced or wrapped, architecture may be redesigned by
tation of the legacy application, redesign the architecture service composition. After obtaining target architecture,
model with identied services, model driven architecture the service cloud implementation is achieved by MDA. In
(MDA) transformation, web service generation, invocation short, REMICS proposes a leap progress in legacy systems
of legacy functionalities, selection of a suitable cloud com- migration to service clouds, which signicantly improves
puting platform, and provision of cloud web service to the the baseline ADM concept[44, 5456] . This project involves
end users. This seven-step methodology guides developers the most advanced research in migrating legacy system to
to migrate legacy systems step by step and improves the service cloud now.
productivity and eectiveness of migration. In summary, migration to SaaS requires to consider the
In addition to the migration methodology, some re- specic migration strategy according to legacy system and
search on the implementation of migration to SaaS was existing SaaS. If existing SaaS has the same business func-
carried out. Current approaches are often limited to spe- tionality of legacy system, users can replace legacy system
cic cloud environments or do not provide automated sup- by SaaS. When some business functionality has been real-
port for the alignment with a cloud environment. Frey and ized by existing SaaS, legacy system can be modernized by
Hasselbring[53] proposed a model-based approach Cloud- revising legacy system based on existing SaaS. Users can
MIG for migrating legacy software system to scalable and take full advantage of the virtue of the cloud by reengi-
resource-ecient cloud-based application. CloudMig con- neering legacy system to SaaS, but the challenge cannot be
centrates on the SaaS provider perspective and facilitates ignored.
the migration of enterprise software system towards generic
IaaS and PaaS-based cloud environment. CloudMIG can 4.3 Comparison between the migration
generate considerable parts of a resource-ecient target ar- strategies
chitecture utilizing a rule-based heuristics, so it helps SaaS
providers to semi-automatically migrate existing software The most ideal strategy for a special migration to the
to the cloud computing platform. Li[21] looked into the mi- cloud relies on the individual needs of each organization and
gration towards the cloud in his dissertation for master s the condition of the legacy system, so organizations need
degree. The research focuses on the derivation of legacy to choose the most rational strategy before the migration.
148 International Journal of Automation and Computing 11(2), April 2014
With the PaaS strategy, organizations need to determine applications by compiling UML2 models. Blu Age engineer-
the extent of modications required for the application to ing automates 100% of the developments and reduces costs
be compatible with the cloud platform. If extensive modi- signicantly[24] .
cations are needed for PaaS, the IaaS strategy may be a Modelio is an open source modeling environment which
better choice. As an eective software-delivery mechanism, supports SoaML, the SOA architecture modeling standard,
SaaS could be an ideal choice for independent software ven- with specic editors dedicated to SOA architecture mod-
dors, but the challenge for reengineering to SaaS is obvious. eling and architecture implementation model generation.
Through integral analysis, we present Table 4 to compare Modelio s core architecture is based on a meta-meta in-
the characteristics of these ve migration strategies. frastructure. The core architecture supports extensibility
mechanisms, notably for UML prole denition, and pro-
5 Related development tools vides the concept of modules, which package extensions and
can be dynamically applied to or withdrawn from an exist-
MoDisco is a generic and extensible open source reverse ing model[25] .
engineering solution, which intensively uses MDE princi- Modisco and Blu Age are both ADM compliant case tools
ples and techniques to improve existing approaches for re- which can extract architecture model from legacy system.
verse engineering. In comparison to many development The extracted model will be the start point of the following
tools that focus on UML generation from a specic tech- forward engineering. Modelio imports the recovered system
nology and vice versa, MoDisco provides generic support model and generates SOA models through componentiza-
for dierent target meta models and extensibility to other tion and refactoring. SOFTTEAM developed a series of
technologies[22] . MoDisco supports four use-cases of ex- migration tools based Modelio environment. Now the link
isting software modernization. The rst use-case is qual- between Blu Age and Modelio is fully functional.
ity assurance which aims at verifying whether an existing
system meets the required qualities. The second is docu- 6 Challenges and future work
mentation which focuses on the extraction of information
from an existing system to help understand one aspect of Based on the above comparison and analysis, we identi-
the system. The third is improvement which concentrates ed the following challenges that could be research topics
on transformation of an existing system to integrate bet- in the future.
ter coding norms or design patterns. The last is migration 1) Holistic methodology
which implements transformation to the component, the Up to now, the existing research mostly focused on the
framework, the language, or the architecture of legacy sys- consideration of a special migration approach. A holistic
tem. In each case, modernizing an existing software system methodology of migrating legacy systems to the cloud is
includes three phases. Firstly the information should be needed. Firstly, the migration of legacy systems to the
extracted out of the artifacts of the system. Then the ex- cloud should be divided into reasonable types, the Cloud
tracted information will be understood in order to take good providers and legacy systems should be classied, too.
modernization decisions. Finally the information is trans- Then, according to a specic kind of legacy system, the
formed to new artifacts which may be metrics, document, selection of Cloud providers, the migration type to be ap-
code and so on[23] . plied, and the required adaption for the migration should be
Blu Age is another agile solution for application mod- made. At the same time, the advantages and risks accom-
ernization which focuses on extracting legacy architecture panying the migration should be advertised. Based on the
into a PIM presentation and regenerates it to a modern- information, organizations can make decision to migration
ized system using MDA approach. Blu Age application strategy. Finally, the methodology should propose adaption
is based on three complementary products. Blu Age re- processes in accordance with the given migration. With the
verse modeling extracts the business code of legacy appli- guidance of this holistic methodology, organization can ef-
cation and transforms it into UML2 model independent of ciently migrate legacy systems to the cloud, rather than
any technology. Blu Age database modernization migrates hesitate about what to do and how to do when facing a
database technologies by modernizing data and strengthen- migration task.
ing their integrity. Blu Age forward engineering generates 2) Scalability in IaaS
Table 4 Comparison between the migration strategies
Migrate to IaaS Migrate to PaaS Replace by SaaS Revise based on SaaS Reengineer to SaaS
Migration workload Little Moderate Little Moderate Much
For the migration to IaaS, if the amount of resources of legacy systems to SaaS.
required by the application is stable, it is unnecessary to 6) Other research topics
adapt the application for migration. However, for some ap- Besides migrating legacy system from traditional envi-
plications, resource requirements might vary signicantly ronments to cloud platforms, application migration between
from time to time, organization must implement a new cloud platforms may be necessary in the future. So how to
resource management component so that resources could migrate applications from one cloud platform to another
be acquired and released automatically on demands. This will be a research topic. In addition, testing strategies need
component can eciently optimize resource consumption in to be studied to verify whether the generated system af-
the cloud. The discussion on how to realize resource man- ter migration has the same functionality and better perfor-
agement is absent at present, so related solutions should be mance as before.
identied to solve this problem. 7) Our ongoing work
3) Usage of essential cloud characteristics Now we are focusing on migrating a workow manage-
For the migration to PaaS, in addition to the adaption to ment system to cloud platform Aneka. Through migration,
programming languages, databases and third-party compo- the existing workow management system running in the
nents, organization needs to consider redesigning some busi- in-house data center will be provided as SaaS to end users.
ness processes in order to exploit essential cloud character- The target workow system will concentrate on scientic
istics. For example, PaaS provides MapReduce program- computing on large data, which can take full advantage of
ming model which is a simple data-parallel programming the virtue of the cloud. In the migration process, the essen-
model designed for scalability and fault-tolerance. MapRe- tial cloud characteristics will be considered adequately. For
duce can automatically parallelize and execute the program example, Mapreduce programming model can be adopted
on a large cluster of commodity machines. When the legacy to implement parallel processing of big data and to analyze
system involves processing of large data sets, the related the execution log of workow system. In order to achieve
business process needs to be redesigned for migration in the aforementioned objectives, we will employ reengineer-
accordance with MapReduce programming model. Never- ing to SaaS to carry out the system migration, and further
theless, existing work have not paid enough attention to explore the reengineering to SaaS and try to propose some
take full advantage of the essential cloud characteristics. innovative methods. The key work and challenges involved
4) Architecture refactoring are as follows:
To reengineer legacy system to SaaS, the architecture i) Software structure recovery
of existing legacy applications need to be refactored using The workow management system is implemented using
design patterns for SOA and cloud computing. SOA and an object-oriented language. We will discover the static
cloud computing technologies complement each other. SOA model of this system using Modisco. After obtaining the
enables software architecture better scalability and reuse of static model, the classes will be grouped into layers through
application components. While the Cloud computing ad- a link analysis algorithm, which usually include user inter-
dresses the deployment architecture that easily scale. SOA face layer, business logic layer, and data access layer. Be-
has been paid much attention for several years, and cur- cause the business process of a system is realized in logic
rently it is in an established state. On the contrary, there layer, the business logic layer needs to be further analyzed
is little research in cloud design pattern due to the novelty for service identication in migrating legacy system to SaaS.
of the domain. To further analyzing the logic layer, special clustering al-
5) Integrated development environment gorithm will be adopted for extracting function modules
For the migration to SaaS, it refers to an integral reengi- in legacy systems. By adopting the orthogonal structure
neering. Good tools are prerequisite to successful execution analysis method, the obtained function modules through
of a job. An integrated development environment can pro- software structure recovery will be more accurate service
mote migration eciency, which should incorporate model candidates.
recovery tool, migration process tool, component recovery ii) Service identication
tool, pattern composition tool and service generation tool. For the target service, we will conduct analysis from two
Model recovery tool is used to extract model from the legacy aspects, namely, target system requirement and legacy sys-
system. Migration process tool oers support for the ap- tem implementation. Based on requirement analysis of the
proach of migrating legacy systems to SOA application de- target workow system, some business functions will be
ployed on cloud computing platforms. The component re- identied which are appropriate for providing as services.
covery tool is responsible for component identication, dis- The function modules in the legacy system implementa-
covery of services, interfaces and dependencies. The pattern tion have been discovered in the rst step. Based on these
composition tool adopts SOA and cloud computing design works, we will match the business functions with the func-
patterns to source architecture, which implements the it- tion modules. The candidate services in legacy system and
erative refactoring of legacy architecture to the targeted new services will be found. As a result, the function mod-
service cloud architecture. Service generation tool auto- ules in legacy system can be eciently reused.
mates the target code framework or target code generation iii) Model refactoring
according to MDA. A series of tools are planned to be devel- After service identication, we need to refactor the exist-
oped in REMICS, and some have been released. Since the ing software architecture to integrate them. Moreover, for
links between these development tools are mostly manual, some special candidate services such as those related to pro-
the integration between them is necessary. Otherwise more cessing the big data, we need to recover the dynamic model
outstanding tools are benecial to facilitate the migration of their implementation in the legacy system. Through an-
150 International Journal of Automation and Computing 11(2), April 2014
Software migration is the process of moving legacy sys- [10] Denition Migration, [Online], Available: http://searchcio.
tems from one operation environment to another, that is, techtarget.com, July 17, 2013.
in most cases, thought to be better. Migrating legacy sys-
tem to cloud computing can eectively protect software [11] A. Khajeh-Hosseini, I. Sommerville, J. Bogaerts, P. Tere-
assets and take advantage of cloud computing. Many re- gowda. Decision support tools for cloud migration in the
search projects have been carried out, and some innovative enterprise. In Proceedings of the 2011 IEEE International
Conference on Cloud Computing (CLOUD), IEEE, Wash-
methods and tools have been proposed so far. By inves- ington, DC, USA, pp. 541548, 2011.
tigating the existing literature, we classify the migration
into ve strategies, then review and compare the related [12] A. Khajeh-Hosseini, D. Greenwood, J. W. Smith, L. Som-
researches on every migration strategy. In addition, re- merville. The cloud adoption toolkit: Supporting cloud
lated development tools are surveyed. Based on the existing adoption decisions in the enterprise. Software: Practice and
research achievements and application status, some future Experience, vol. 42, no. 4, pp. 447465, 2012.
work are identied including holistic methodology, redesign
and adaption to application for special migration, architec- [13] C. Ward, N. Aravamudan, K. Bhattacharya, K. Cheng.
ture refactoring, integrated development environment, and Workload migration into clouds challenges, experiences, op-
portunities. In Proceedings of the 2010 IEEE International
so on. Besides, we notice the most advanced research in Conference on Cloud Computing (CLOUD), IEEE, Miami,
migration of legacy software to cloud computing has been FL, USA, pp. 164171, 2010.
performed in REMICS, so some further work in this re-
search eld should be carried out based on the achievement [14] Cloud Adoption Assessment, [Online], Available:
obtained in this project. http://www.eduserv.org.uk, July 20, 2013.
J. F. Zhao and J. T. Zhou / Strategies and Methods for Cloud Migration 151
[15] M. Menzel, R. Ranjan. CloudGenius: decision support for [30] Migrating your Existing Applications to the AWS Cloud,
web server cloud migration. In Proceedings of the 21st In- Amazon White paper, 2010.
ternational Conference on World Wide Web, ACM, New
York, NY, USA, pp. 979988, 2012.
[31] G. Zhang. Data and Application Migration in Cloud based
Data Centers: Architectures and Techniques, Ph. D. disser-
[16] A. Khajeh-Hosseini, D. Greenwood, I. Sommerville. Cloud tation, Georgia Institute of Technology, USA, 2011.
migration: A case study of migrating an enterprise IT sys-
tem to IaaS. In Proceedings of the 2010 IEEE International [32] Infrastructure as a Service, [Online], Available: http://
Conference on Cloud Computing (CLOUD), IEEE, Miami, www.educause.edu, July 20, 2013.
FL, USA, pp. 450457, 2010.
[28] Migrating to the Cloud 3 Main Approaches, Solentive [44] State of the art on modernization methodolo-
White paper, 2011. gies, methods and tools, [Online], Available:
http://www.remics.eu/publicdeliverables, July 20, 2013.
[29] S. Bhardwaj, L. Jain, S. Jain. Cloud computing: A study
of infrastructure as a service (IAAS). International Journal [45] G. Canfora, M. D. Penta, L. Cerulo. Achievements and chal-
of Engineering and Information Technology, vol. 2, no. 1, lenges in software reverse engineering. Communications of
pp. 6063, 2010. the ACM, vol. 54, no. 4, pp. 142151, 2011.
152 International Journal of Automation and Computing 11(2), April 2014
[46] G. Lewis, E. J. Morris, D. B. Smith, S. Simanta. Smart: [53] S. Frey, W. Hasselbring. Model-based migration of legacy
Analyzing the Reuse Potential of Legacy Components in A software systems to scalable and resource-ecient cloud-
Service-oriented Architecture Environment, Technical Re- based applications: The cloudMIG approach. In Proceed-
port, SEI, volume CMU/SEI-2008-TN-008, 2008. ings of the 1st International Conference on Cloud Comput-
ing, GRIDs, and Virtualization, pp. 155158, 2010.
[49] J. Oldevik, G. K. Olsen, U. Br onner, N. R. Bodsberg. Jun-Feng Zhao received his B. Sc. de-
Model-driven migration of scientic legacy systems to gree in computer science from Inner Mon-
service-oriented architectures. In Proceedings of the 1st In- golia Normal University, China, and his
ternational Workshop on Model-driven Software Migration, M. Sc. degree in software engineering from
pp. 47, 2011. National University of Defense Technology,
China in 2006. He is currently a lecturer
and a Ph. D. candidate at College of Com-
[50] S. Chung, J. B. C. An, S. Davalos. Service-oriented soft- puter Science, Inner Mongolia University.
ware reengineering: SoSR. In Proceedings of the 40th An- His research interests include software
nual Hawaii International Conference on System Sciences, reengineering, formal modeling and cloud
IEEE, Waikoloa, HI, USA, pp. 172c, 2007. computing.
E-mail: cszjf@imu.edu.cn
[51] A. Winter, J. Ziemann. Model-based migration to service-
oriented architectures. In Proceedings of the 11th Euro- Jian-Tao Zhou received her Ph. D. de-
pean Conference on Software Maintenance and Reengineer- gree from Tsinghua University in 2005. She
ing (CSMR 2007), Vrije Universiteit Amsterdam, pp.107 is a professor and Ph. D. supervisor in Col-
110, 2007. lege of Computer Science, Inner Mongolia
University.
Her research interests include network
[52] M. Razavian, P. Lago. Understanding SOA migration us- computing and formal methods.
ing a conceptual framework. Journal of Systems Integration, E-mail: cszjtao@imu.edu.cn (Correspon-
vol. 1, no. 3, pp. 3334, 2010. ding author)