The document outlines the ARTIST project which aims to facilitate the migration of legacy software systems to cloud computing. The project will develop tools to assess legacy software maturity and the feasibility of migration. It will provide a methodology and model-based approach to guide the migration process, considering both technical and business aspects. The expected results include tools to analyze legacy software and evaluate migration costs/benefits, as well as a validation framework or migrated applications. The project involves four use cases and is currently developing initial software prototypes and the first version of its methodology.

1. ARTIST: Advance software-based
seRvice provisioning and migraTIon
of legacy SofTware
Clara Pezuela (ATOS)
Project Coordinator
An end-to-end and assisted solution
for migrating legacy systems to the
cloud

2. Presentation Outline
 Mission and motivation
 Project at a glance
 Expected impact
 Approach
 Methodology
 Expected results
 Use Cases
 Current Status
 Consortium
 Contact Info

3. Mission
ARTIST aims at facilitating the
transformation and modernization of
legacy software assets and businesses
to the cloud.

4. Motivation
 Cloud computing facilitates new ways to deliver better
quality software
 Companies need to move legacy software into the
cloud of services, obtaining benefits like
– Rapid elasticity
– High availability
– Up-front costs
 Software modernization of legacy software is still a major
challenge1
– More ambitious when cloud environments (paradigm shift)
are addressed
– Implies fundamental changes to how software is
modernized, delivered and sold
 Consequently, the software modernization process
needs to consider technical and business aspects
1Canfora et al.: Achievements and challenges in software reverse engineering, CACM, 54, 4, 2011

5. ARTIST at a glance
 Vision (what)
– ARTIST helps organizations in the process to modernise and
transform legacy software to run in the Cloud/SaaS, and
be offered through a new business model
 Goal (how)
– Adapting legacy software to run on the cloud,
– Considering both technical modernization, business model
aspects and the impact in the organizational processes
 Offering (by)
– Evaluating if their applications are able (and if its worth it)
to run them on the cloud
– Performing the end-to-end migration process of the
applications: methods and tools to assess, plan, design,
implement and validate the migration process

6. Impact
 Up to 90% of software cost relates to its maintenance following
implementation…
 …yet once implemented it is never again cutting edge
ARTIST impact goal:
 To slash by 40% the migration cost relative to manual migration
 Permitting more frequent migration to more suitable platforms
 Mainly addressed to ISPs, software owners and cloud providers
“Balancing software continuity with optimal
performance and cost”

7. Approach
Tools to support the decision of
migrating or not and to which
cloud provider
• Maturity Assessment of the
application to be migrated. Current
vs. ideal maturity
• Technical Feasibility: High Level
Reverse Engineering + other metrics
such as code reusability potential
• Business Feasibility: Impact in the
business processes, Risks, ROI +
other metrics
PRE-MIGRATION MIGRATION POST-MIGRATION
Methods, models and tools to
support the migration to cloud
• Create a “to do” list for migration steps
(methodology)
• Analyse and model the legacy
software (model discovery and
understanding)
• Modelling target environment (cloud
modeling)
• Benchmark cloud providers to select
best ones for legacy app
(benchmarking)
• Transform the legacy models to
modernized models (forward
engineering)
• Including the business model
aspects within the architecture
• Ensuring the migrated code
fulfils the cloud requirements
• Redefinition of business processes
• Definition of the business model
Tools to support the
migrated software
• V&V (behavioural and end
users) methods and tools
• Certification model for SaaS
application providers
• Repository of artefacts, tools,
etc. for easing the evolution

8. Methodology

9. Expected results
 A set of tools to analyse and classify legacy SW and business and
to evaluate feasibility, cost, implications and benefits of migration
 Methodology (tool-supported) to guide companies in the entire
migration process (technical, business, process)
 Model-based approach for source/target applications and
infrastructures/platforms (CloudML@ARTIST)
 Reusable set of artefacts (models and transformations) provided
through an enhanced repository
 A validation framework for migrated applications
 A certification model for warranty the compliance of migrated
application with cloud
 Four validation scenarios (Java and .NET) to demonstrate the
feasibility of ARTIST results

10. Use cases
 Tsunamis early detection system
 ARTIST will allow the migration of the operators desktop
(SWT/Jface) to a webtop (GWT/GXT)
 User interface and data schema will be migrated
 eGov application for the integration of processes and
data from different public administrations
 ARTIST will allow the easy deployment of a PaaS in a
cloud
 Media application for News Agencies
 ARTIST will allow to create a “light” NewsAsset version
 with the basic functionalities
 hosted in a cloud environment
 configured to address the needs of existing
customers
 Social networking solutions for the enterprise
 ARTIST will allow to extend a legacy app to integrate it
with SaaS apps
 No migration of legacy code, but generation of
facades to connect legacy code with services in the
cloud (Ubison)

11. Current status (M12)
 First software prototypes of:
– Feasibility Tools (maturity assessment, technical feasibility
assessment and business feasibility assessment)
– Extensions of MoDisco for Model understanding and model
discovery with the inclusion of new views and a taxonomy
– Transformations and optimization patterns to deploy applications
on a cloud provider
– Non functional properties verification tool
 First version of CloudML@ARTIST
 In the process of benchmarking cloud providers (IaaS / PaaS)
to gather metrics so that they can be compared against each
other
 First version of the methodology including technical-related
tasks, business-related tasks and process-related tasks
 First version of the certification model
 Full definition and architecture of the 4 use cases

12. The consortium

13. Contact information
 Project coordinator contact:
Clara.pezuela@atos.net
 Project web site: www.artist-project.eu
 Newsletter subscription
 Linkedin: ARTIST project
 Twitter: @ARTISTeu

14. THANKS FOR YOUR ATTENTION