transparent gif

 

Ej inloggad.

Göteborgs universitets publikationer

Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study

Författare och institution:
Antonio Martini (Institutionen för data- och informationsteknik, Software Engineering (Chalmers), Chalmers); Jan Bosch (Institutionen för data- och informationsteknik, Software Engineering (Chalmers), Chalmers); Michel Chaudron (Institutionen för data- och informationsteknik (GU))
Publicerad i:
Information and Software Technology, 67 s. 237-253
ISSN:
0950-5849
Publikationstyp:
Artikel, refereegranskad vetenskaplig
Publiceringsår:
2015
Språk:
engelska
Fulltextlänk:
Sammanfattning (abstract):
Context A known problem in large software companies is to balance the prioritization of short-term with long-term feature delivery speed. Specifically, Architecture Technical Debt is regarded as sub-optimal architectural solutions taken to deliver fast that might hinder future feature development, which, in turn, would hinder agility. Objective This paper aims at improving software management by shedding light on the current factors responsible for the accumulation of Architectural Technical Debt and to understand how it evolves over time. Method We conducted an exploratory multiple-case embedded case study in 7 sites at 5 large companies. We evaluated the results with additional cross-company interviews and an in-depth, company-specific case study in which we initially evaluate factors and models. Results We compiled a taxonomy of the factors and their influence in the accumulation of Architectural Technical Debt, and we provide two qualitative models of how the debt is accumulated and refactored over time in the studied companies. We also list a set of exploratory propositions on possible refactoring strategies that can be useful as insights for practitioners and as hypotheses for further research. Conclusion Several factors cause constant and unavoidable accumulation of Architecture Technical Debt, which leads to development crises. Refactorings are often overlooked in prioritization and they are often triggered by development crises, in a reactive fashion. Some of the factors are manageable, while others are external to the companies. ATD needs to be made visible, in order to postpone the crises according to the strategic goals of the companies. There is a need for practices and automated tools to proactively manage ATD.
Ämne (baseras på Högskoleverkets indelning av forskningsämnen):
NATURVETENSKAP ->
Data- och informationsvetenskap ->
Programvaruteknik
Nyckelord:
Agile software development, Architectural Technical Debt, Qualitative model
Postens nummer:
223988
Posten skapad:
2015-10-12 07:52
Posten ändrad:
2016-09-14 16:08

Visa i Endnote-format

Göteborgs universitet • Tel. 031-786 0000
© Göteborgs universitet 2007