A Storytest-Driven Approach to the Migration of Legacy Systems

  • Fabio Abbattista
  • Alessandro Bianchi
  • Filippo Lanubile
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 31)


In this paper, we propose an agile approach, for the migration of legacy software which combines a user story-based iterative process with automated acceptance testing. The proposed approach, named Storytest-Driven Migration (STDM), requires that acceptance tests are written both on the legacy and target versions of a software system. Because of their relevance, the quality of automated acceptance tests is assured through software inspections. As a proof of concept, we conducted a first migration project of a web application towards both a web application framework and a mobile platform.


migration storytest-driven development acceptance testing 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Andersson, J., Bache, G., Sutton, P.: XP with Acceptance-Test Driven Development: A rewrite project for a resource optimization system. In: Marchesi, M., Succi, G. (eds.) XP 2003. LNCS, vol. 2675, pp. 180–188. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  2. 2.
    Beck, K.: Test Driven Development: By Example. Addison-Wesley, New York (2002)Google Scholar
  3. 3.
    Bisbal, J., Lawless, D., Wu, B., Grimson, J.: Legacy information systems: issues and directions. IEEE Software 16(15), 103–111 (1999)CrossRefGoogle Scholar
  4. 4.
    Bohnet, R., Meszaros, G.: Test-Driven Porting. In: Agile Development Conference (ADC 2005), pp. 259–266. IEEE Computer Society, Los Alamitos (2005)CrossRefGoogle Scholar
  5. 5.
    Brodie, M.L., Stonebraker, M.: Migrating Legacy Systems. Morgan Kaufmann, San Francisco (1995)Google Scholar
  6. 6.
    Brugali, D., Torchiano, M.: Software Development, Case Studies in Java. Addison Wesley, New York (2005)Google Scholar
  7. 7.
    Hennessy, M., Power, J.F.: Ensuring behavioral equivalence in test-driven porting. In: Conference of the Center for Advanced Studies on Collaborative Research (CASCON 2006). ACM Press, New York (2006)Google Scholar
  8. 8.
    Lanubile, F., Mallardo, T.: Inspecting Automated Test Code: a Preliminary Study. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds.) XP 2007. LNCS, vol. 4536, pp. 115–122. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  9. 9.
    Melnik, G., Maurer, F.: Multiple Perspectives on Executable Acceptance Test-Driven Development. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds.) XP 2007. LNCS, vol. 4536, pp. 245–249. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  10. 10.
    Meszaros, G.: XUnit Test Patterns: Refactoring Test Code. Addison Wesley, New York (2007)Google Scholar
  11. 11.
    Mugridge, R., Cunningham, W.: Fit for Developing Software: Framework for Integrated Tests. Prentice Hall PTR, Englewood Cliffs (2005)Google Scholar
  12. 12.
    Reppert, T.: Don’t Just Break Software, Make Software: How Story-Test-Driven-Development is Changing the Way QA, Customers, and Developers Work. Better Software 6(6), 18–23 (2004)Google Scholar
  13. 13.
    Varma, P., Anand, A., Pazel, D.P., Tibbitts, B.R.: NextGen eXtreme porting: structured by automation. In: ACM Symposium on Applied Computing (SAC 2005), pp. 1511–1517. ACM Press, New York (2005)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Fabio Abbattista
    • 1
  • Alessandro Bianchi
    • 1
  • Filippo Lanubile
    • 1
  1. 1.Dipartimento di InformaticaUniversity of BariBariItaly

Personalised recommendations