<!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>Towards Quality-Driven Software Migration</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jan Jelschen</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gaurav Pandey</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andreas Winter</string-name>
          <email>winterg@se.uni-oldenburg.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Carl von Ossietzky Universita ̈t</institution>
          ,
          <addr-line>Oldenburg</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>8</fpage>
      <lpage>9</lpage>
      <abstract>
        <p>Long-running software systems suffer from software erosion, due to their constant evolution to meet new or changing requirements, severely limiting their maintainability. Migrating software systems, i.e. transferring legacy systems into modern environments and technologies without changing functionality [FWE+12], is a key technique of software evolution, and serves to keep existing software systems operational. Structured migrations allow for transferring established software solutions to cutting edge technology, without having to consider the significantly higher risks of developing a new system from scratch. Reliable predictions regarding long-term trends of software systems' quality are a prerequisite to make sensible decisions between software migration or redevelopment strategies, which enable a system's continued development, evolution, and operation. Especially when planning to migrate software systems, and choosing appropriate tools, a prognosis of project-specific quality properties of the system after migration is required. To assess and compare software quality before and after language migrations, like from COBOL to Java, a major obstacle to overcome is the paradigm shift between procedural and object-oriented programming that occurs (or should occur) when translating between these languages. For example, any measures which try to capture object-oriented properties like encapsulation will only provide meaningful results on the target system, with nothing to compare to on the source system side, i.e. a direct comparison is impossible. Recognizing these challenges, two main research questions can be identified, which lead to two sets of central objectives regarding quality criteria and quality prediction, to address them: 1. How to measure and compare the quality of legacy and migrated software systems? 2. How to predict the quality of software migration results? Quality Criteria. A basic prerequisite for quality measurements is having a set of criteria appropriate for assessing and comparing the quality of software systems under migration, and knowing which criteria are relevant for a specific project. Whereas criteria for incremental quality monitoring in plain forward engineering projects, utilizing a fixed development environment, are known, comparable criteria applicable for legacy and migrated systems are unknown. Therefore, a catalog of quality criteria has to be assembled, elicited from literature review and expert interviews, and a process to define a migration project's goals, and select suitable, measurable criteria has to be created. Quality Prediction. To help a cooperation to decide whether to migrate, or choose a different strategy (e.g. re- or new-development), or to tailor a migration process to specific needs, information is needed on the resulting system's quality properties before carrying out the migration. A quality prediction model has to be derived by measuring software systems before and after migration, and looking for correlations. Such a model will serve Copyright c 2014 for the individual papers by the papers' authors. Copying permitted for private and academic purposes. This volume is published and copyrighted by its editors.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Source</title>
    </sec>
    <sec id="sec-2">
      <title>System</title>
    </sec>
    <sec id="sec-3">
      <title>Artifacts</title>
    </sec>
    <sec id="sec-4">
      <title>Metrics M1</title>
    </sec>
    <sec id="sec-5">
      <title>AnalysisTools M2 M3</title>
    </sec>
    <sec id="sec-6">
      <title>GeneratorTools M4</title>
    </sec>
    <sec id="sec-7">
      <title>Transformation</title>
    </sec>
    <sec id="sec-8">
      <title>Tools</title>
    </sec>
    <sec id="sec-9">
      <title>Quality Assurance</title>
    </sec>
    <sec id="sec-10">
      <title>Tools</title>
    </sec>
    <sec id="sec-11">
      <title>Quality Control Center</title>
    </sec>
    <sec id="sec-12">
      <title>Target</title>
    </sec>
    <sec id="sec-13">
      <title>System</title>
    </sec>
    <sec id="sec-14">
      <title>Artifacts</title>
    </sec>
    <sec id="sec-15">
      <title>Quality</title>
    </sec>
    <sec id="sec-16">
      <title>Reports</title>
      <p>to project quality properties after a migration, given the source system, and the migration
toolchain with its parameters. It can also be used to refine such parameters in an iterative
process, to meet certain quality requirements in the target system.
To realize the quality control center, the central questions subject to research are a) which
criteria are relevant for a given migration scenario, b) how to measure and interpret them
in a way that correlates with experts’ assessments, and c) how to sensibly compare them,
considering programming paradigm shifts.</p>
      <p>These issues will be addressed by the project Q-MIG: Building a Quality-Driven, Generic
Tool-Chain for Software Migration1, which commenced on January 1, 2014. Q-MIG is
a joint project of pro et con Innovative Informatikanwendungen GmbH (focusing on the
software migration toolchain [EU11]) and Carl von Ossietzky University (focusing on the
quality control center). For integration, a service-based approach will be used [JMOW13].
Q-MIG aims at enabling project managers and software developers to make early strategic
decisions regarding the realization of software migrations, and to already carry out targeted
quality assuring measures during the migration. At the workshop, we would like to discuss
how to predict comparable (internal) quality criteria for software migration projects.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [EU11]
          <string-name>
            <given-names>U.</given-names>
            <surname>Erdmenger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Uhlig</surname>
          </string-name>
          .
          <article-title>Ein Translator fu¨r die COBOL-Java-</article-title>
          <string-name>
            <surname>Migration.</surname>
          </string-name>
          Softwaretechnik-Trends,
          <volume>31</volume>
          (
          <issue>2</issue>
          ),
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [FWE+12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Fuhr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Winter</surname>
          </string-name>
          , U. Erdmenger,
          <string-name>
            <given-names>T.</given-names>
            <surname>Horn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Kaiser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Riediger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Teppe. ModelDriven Software Migration - Process Model</surname>
          </string-name>
          ,
          <article-title>Tool Support and Application</article-title>
          . In A. Ionita,
          <string-name>
            <given-names>M.</given-names>
            <surname>Litoiu</surname>
          </string-name>
          , G. Lewis, eds, Migrating Legacy Applications:
          <article-title>Challenges in Service Oriented Architure and Cloud Computing Environments</article-title>
          . IGI, Hershey,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [JMOW13]
          <string-name>
            <given-names>J.</given-names>
            <surname>Jelschen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Meier</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.-C. Ostendorp</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Winter</surname>
          </string-name>
          .
          <article-title>A Description Model for Software Evolution Services</article-title>
          . In CoNaIISI, Cordoba,
          <year>November 2013</year>
          .
          <article-title>RIISIC. 1Q-MIG is funded by the Central Innovation Program SME of the German Federal Ministry of Economics and Technology (Bundesministerium fu¨r Wirtschaft und Technologie - BMWi)</article-title>
          .
          <source>Funding code: KF3182501KM3.</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>