Cost‐driven software migration: An experience report

Abstract

Software migration projects are often bound either by time or cost or by both. If the project is bound by both time and cost, the user must sacrifice something else, usually the quality. The migration strategy depends on how the project is bound. Most migration projects are bound by time. The new system must be in operation by a given date, no matter what it costs. The project described here—a state employee payroll system—is bound by cost. It must remain within the budget, no matter how long it takes. The original costs were estimated based on the code size and the productivity measured in previous migration projects using three different approaches: conversion, redevelopment, and reimplementation. The conversion approach would have been the cheapest, but it had already been tried and failed. The redevelopment approach was considered to be out of the question due to the high costs. Thus, reimplementation remained as the only alternative. The costs of this approach were estimated using three different estimation methods and approved by the state government. The project has been in progress for 4 years, and until now, the estimated costs and actual costs are in the same order of magnitude: the costs have remained within budget. In fact, the costs are less than what was estimated with some methods. As this particular project is not bound by time, it is a good example of continuous migration.

Migrating GUI behavior: from GWT to Angular

“…Table III summarizes the results for the naturalness of code. SonarQube categories the errors by severities 11 . Blockers have an important impact on the system and are likely to happen; majors have a limited impact and are likely to happen; minors have a limited impact and are unlikely to happen.…”

“…Sneed and Verhoef [11] described three ways to migrate an application: conversion, reimplementation, and wrapping.…”

From GWT to Angular: An Experiment Report on Migrating a Legacy Web Application

“…Many migration approaches were proposed for the modernization of applications [2], [3], [4], [5]. They can be divided into three categories [6]: from scratch, wrapping, and semi-automated migration.…”

A Hybrid Artificial Bee Colony and Artificial Fish Swarm Algorithms for Software Cost Estimation

“…Correct forecasts may significantly improve a company's success in terms of SCE and resource allocation. Conversely, inaccurate estimates can lead to significant financial losses and project failure [3]. Therefore, it is crucial to find novel models with improved estimate skills.…”