<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>REMICS Project: Reuse and Migration of Legacy Applications to Interoperable Cloud Services</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andrey Sadovykh SOFTEAM</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>France</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Alexis Henry BLU AGE Software - Netfective Technology</institution>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Franck Barbier University of Pau - Netfective Technology</institution>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Parastoo Mohagheghi</institution>
          ,
          <addr-line>Arne J. Berre SINTEF</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-The main objective of the REMICS project is to specify, develop and evaluate a tool-supported modeldriven 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 show the support for two tasks in this migration: recovery process with the BLU AGE tool and the use of SoaML and forward engineering with Modelio tool.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>I. REMICS APPROACH AND DEMONSTRATIONS
The REMICS1 project will provide tools for
modeldriven migration of legacy systems to loosely coupled
systems following a bottom up approach; from
recovery of legacy system architecture (using OMG’s
ADMArchitecture Driven Modernization) to deployment in a
cloud infrastructure which allows further evolution of the
system in a forward engineering process. The migration
process consists of understanding the legacy system in
terms of its architecture, business processes and functions,
designing a new Service-Oriented Architecture (SOA)
application, and verifying and implementing the new
application in the cloud. These methods will be complimented
with generic “Design by Service Composition” methods
providing developers with tools simplifying development
by reusing the services and components available in the
cloud.</p>
      <p>In order to instrument the migration process, the
REMICS project will integrate a large set of
metamodels and will propose several dedicated extensions. For
the architecture recovery the REMICS will extend the
KDM metamodel. On Platform Independent Model (PIM)
level, the components and services are defined using
SoaML (SOA Modeling Language2) which is developed
in the SHAPE project3. The REMICS project will
extend this language to address the specific architectural
patterns and model driven methods for architecture
migration, and to cover specificities of service clouds
development paradigm. In particular, the PIM4Cloud
Computing, model-driven Service Interoperability and
Models@Runtime extensions are intended to support the
REMICS methodology for service cloud architecture
modeling.</p>
      <p>Furthermore, REMICS will investigate existing test
notations such as the UML2 test profile (UTP) for their
application to the SOA and Cloud Computing domain and
refine and extend them.</p>
      <p>The project will focus on open source metamodels and
models with an emphasis on Open Models for standards
and will be actively involved in the standardization process
of the related standards for cloud computing, business
models, SOA, service interoperability, knowledge
discovery, validation and managing services.</p>
      <p>REMICS targets the following main impact objectives:
REMICS will preserve and capitalize on the business
value engraved in legacy systems to gain flexibility
brought by Service Clouds, lower the cost of service
provision and shorten the time-to-market.</p>
      <p>REMICS research will provide innovations in
advanced model driven methodologies, methods and
tools in Software as a Service engineering.</p>
      <p>REMICS will provide standards-based foundation
service engineering and will provide a suite of open
ready-to-use metamodels that lowers barriers for
service providers.</p>
      <p>REMICS started in September 2010 and will run for
three years while it builds on the results of several
ongoing or finished EU projects such as SHAPE and
MODELPLEX4 (both finished recently) with focus on
modeldriven development of applications, MOMOCS with
focus on model-driven modernization, and SOA4ALL and
RESERVOIR with focus on service-oriented development.
The relevant results of previous projects will therefore
be discussed and extensions planned in REMICS will be
presented. The presentation will also discuss collaboration
areas which should be of interest to other projects and
conference participants.</p>
      <p>The demonstrations will show the support for two tasks
in this migration: recovery process using BLU AGE5 tool
and the use of SoaML and forward engineering with
Modelio6 tool. Both tool providers are participating in the
REMICS project.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>