Redefining Legacy: A Technical Debt Perspective | SpringerLink
Skip to main content
Springer Nature Link
Log in

Redefining Legacy: A Technical Debt Perspective

  • Conference paper
  • First Online:
Product-Focused Software Process Improvement (PROFES 2020)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 12562))

Abstract

Organisations that manage legacy systems at scale, such as those found within large government agencies and commercial enterprises, face a set of unique challenges. They manage complex software landscapes that have evolved over decades. Current conceptual definitions of legacy systems give practitioners limited insights that can inform their daily work. In this research, we compare conceptual definitions of large-scale legacy and technical debt. We hypothesise that large-scale legacy reflects an accumulation of technical debt that has never been through a remediation phase. To pursue this hypothesis, we identified the following question: How do practitioners describe their experience of managing large-scale legacy landscapes? We conducted 16 semi-structured open-ended, recorded and transcribed interviews with industry practitioners from 4 government organisations and 9 large enterprises involved with the maintenance and migration of large-scale legacy systems. A snowball sampling technique was used to identify participants. We adopted an approach informed by grounded theory. There was consensus among the practitioners in our study that the landscape is fragmented and inflexible, consisting of many dispersed and fragile applications. Practitioners report challenges with shifting paradigms from batch processing to near real-time customer-focused information systems. Our findings show there is overlap between challenges experienced by participants and symptoms typified by technical debt. We identify a novel type of technical debt, “Ecosystem Debt” which arises from the scale, and age, of many large-scale legacy applications. By positioning Legacy within the context of Technical Debt, practitioners have a more concrete understanding of the state of the systems they maintain.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution

Subscribe and save

Springer+ Basic
¥17,985 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
JPY 3498
Price includes VAT (Japan)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
JPY 5719
Price includes VAT (Japan)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
JPY 7149
Price includes VAT (Japan)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

References

  1. Alves, N.S., Mendes, T.S., de Mendonça, M.G., Spínola, R.O., Shull, F., Seaman, C.: Identification and management of technical debt: a systematic mapping study. Inf. Softw. Technol. 70, 100–121 (2016)

    Article  Google Scholar 

  2. Arvanitou, E.M., Ampatzoglou, A., Bibi, S., Chatzigeorgiou, A., Stamelos, I.: Monitoring technical debt in an industrial setting. In: Proceedings of the Evaluation and Assessment on Software Engineering, EASE 2019, pp. 123–132. Association for Computing Machinery, New York (2019)

    Google Scholar 

  3. Bass, J., Monaghan, B.: Legacy systems interview guide, July 2020. https://doi.org/10.17866/rd.salford.12662537.v1

  4. Bennett, K.: Legacy systems: coping with success. IEEE Softw. 12(1), 19–23 (1995)

    Article  Google Scholar 

  5. Bisbal, J., Lawless, D., Wu, B., Grimson, J.: Legacy information systems: issues and directions. IEEE Softw. 16(5), 103–111 (1999)

    Article  Google Scholar 

  6. Brown, N., et al.: Managing technical debt in software-reliant systems, pp. 47–52 (01 2010)

    Google Scholar 

  7. Cunningham, W.: The WyCash portfolio management system. SIGPLAN OOPS Mess. 4(2), 29–30 (1992)

    Google Scholar 

  8. Dedeke, A.: Improving legacy-system sustainability: a systematic approach. IT Prof. 14(1), 38–43 (2012)

    Article  Google Scholar 

  9. Eisenberg, R.J.: A threshold based approach to technical debt. SIGSOFT Softw. Eng. Notes 37(2), 1–6 (2012)

    Google Scholar 

  10. Fowler, M.: bliki: Technicaldebtquadrant (2020). https://martinfowler.com/bliki/TechnicalDebtQuadrant.html

  11. García-Holgado, A., García-Peñalvo, F.J.: Mapping the systematic literature studies about software ecosystems. In: Proceedings of the Sixth International Conference on Technological Ecosystems for Enhancing Multiculturality, TEEM 2018, pp. 910–918. Association for Computing Machinery, New York (2018)

    Google Scholar 

  12. Gholami, M.F., Daneshgar, F., Beydoun, G., Rabhi, F.: Challenges in migrating legacy software systems to the cloud - an empirical study. Inf. Syst. 67, 100–113 (2017)

    Article  Google Scholar 

  13. Glaser, B.G.: The discovery of grounded theory: strategies for qualitative research (2003)

    Google Scholar 

  14. Gupta, R.K., Manikreddy, P., Naik, S., Arya, K.: Pragmatic approach for managing technical debt in legacy software project. In: Proceedings of the 9th India Software Engineering Conference. ISEC 2016, pp. 170–176. Association for Computing Machinery, New York, NY, USA (2016)

    Google Scholar 

  15. Holvitie, J., Licorish, S.A., Martini, A., Leppänen, V.: Co-existence of the’technical debt’and’software legacy’concepts. In: QuASoQ/TDA@ APSEC. pp. 80–83 (2016)

    Google Scholar 

  16. Khadka, R., Batlajery, B., Saeidi, A., Jansen, S., Hage, J.: How do professionals perceive legacy systems and software modernization?, no. 1, pp. 36–47. IEEE Computer Society (2014)

    Google Scholar 

  17. Khadka, R., Saeidi, A., Idu, A., Hage, J., Jansen, S.: Legacy to SOA evolution: a systematic literature review. In: Migrating Legacy Applications: Challenges in Service Oriented Architecture and Cloud Computing Environments, pp. 40–70 (2012)

    Google Scholar 

  18. Kontsevoi, B., Soroka, E., Terekhov, S.: Tetra, as a set of techniques and tools for calculating technical debt principal and interest. In: Proceedings of the Second International Conference on Technical Debt, TechDebt 2019, pp. 64–65. IEEE Press (2019)

    Google Scholar 

  19. Kruchten, Philippe, A.: Managing technical debt: reducing friction in software development. In: SEI Series in Software Engineering (2019)

    Google Scholar 

  20. Manikas, K., Hansen, K.M.: Software ecosystems-a systematic literature review. J. Syst. Softw. 86(5), 1294–1306 (2013)

    Article  Google Scholar 

  21. McGregor, J.D., Monteith, J.Y., Zhang, J.: Technical debt aggregation in ecosystems. In: Proceedings of the Third International Workshop on Managing Technical Debt, MTD 2012, pp. 27–30. IEEE Press (2012)

    Google Scholar 

  22. Razavian, M., Lago, P.: A systematic literature review on SOA migration. J. Softw. Evol. Process 27(5), 337–372 (2015)

    Article  Google Scholar 

  23. Rios, N., de Mendonça Neto, M.G., Spínola, R.O.: A tertiary study on technical debt: types, management strategies, research trends, and base information for practitioners. Inf. Softw. Technol. 102, 117–145 (2018)

    Article  Google Scholar 

  24. Wolff, E., Johann, S.: Technical debt. IEEE Software 32(4), 94–c3 (2015)

    Article  Google Scholar 

  25. Zaytsev, V.: Open challenges in incremental coverage of legacy software languages. In: Proceedings of the 3rd ACM SIGPLAN International Workshop on Programming Experience, pp. 1–6. PX/17.2. Association for Computing Machinery, New York (2017)

    Google Scholar 

  26. Zazworka, N., Shaw, M., Shull, F., Seaman, C.: Investigating the impact of design debt on software quality, pp. 17–23 (2011)

    Google Scholar 

Download references

Acknowledgements

We would like to acknowledge and thank the participants who took part in this study. Many of which are in senior positions, as such we appreciate them taking the time to participate in this study.

Author information

Authors and Affiliations

  1. University of Salford, 43 Crescent, Salford, M5 4WT, UK

    Ben D. Monaghan & Julian M. Bass

Authors
  1. Ben D. Monaghan
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Julian M. Bass
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Ben D. Monaghan .

Editor information

Editors and Affiliations

  1. Politecnico di Torino, Turin, Torino, Italy

    Maurizio Morisio

  2. Polytechnic University of Turin, Turin, Torino, Italy

    Marco Torchiano

  3. Fraunhofer Institute for Experimental Software Engineering, Kaiserslautern, Rheinland-Pfalz, Germany

    Andreas Jedlitschka

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Monaghan, B.D., Bass, J.M. (2020). Redefining Legacy: A Technical Debt Perspective. In: Morisio, M., Torchiano, M., Jedlitschka, A. (eds) Product-Focused Software Process Improvement. PROFES 2020. Lecture Notes in Computer Science(), vol 12562. Springer, Cham. https://doi.org/10.1007/978-3-030-64148-1_16

Download citation

  • DOI: https://doi.org/10.1007/978-3-030-64148-1_16

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-030-64147-4

  • Online ISBN: 978-3-030-64148-1

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation