| 1. |
- Besker, Terese, 1970, et al.
(författare)
-
A systematic literature review and a unified model of ATD
- 2016
-
Ingår i: Proceedings of the EUROMICRO Conference. - 1089-6503. - 9781509028191 ; , s. 189-197
-
Konferensbidrag (refereegranskat)abstract
- Fast software deliveries are hindered by high maintenance efforts due to internal quality issues and Technical Debt (TD) and specifically, Architectural Technical Debt (ATD) has received increased attention in the last few years. ATD has a significant influence and impact on system success and, left unchecked, it can cause expensive repercussions; it is, therefore, of maintenance and evolutionary importance to understand the basic underlying factors of ATD. Thus, with this as background, there is a need for a descriptive model to illustrate and explain the different ATD issues. The aim of this study is to synthesize and compile research efforts with the goal of creating new knowledge with a specific interest in the ATD field. The contribution of this paper is the presentation of a novel descriptive model, providing a comprehensive interpretation of the ATD phenomenon. This model categorizes the main characteristics of ATD and reveals their corresponding relations. The model is based on a systematic literature review (SLR) of currently recognized knowledge concerning ATD.
|
|
| 2. |
- Martini, Antonio, 1982, et al.
(författare)
-
The Introduction of Technical Debt Tracking in Large Companies - A Survey and Multiple Case-Study
- 2016
-
Ingår i: 2016 23rd Asia-Pacific Software Engineering Conference (APSEC).
-
Konferensbidrag (refereegranskat)abstract
- Large software companies need to support continuous and fast delivery of customer value both in the short and long term. However, this can be hindered if both the evolution and maintenance of existing systems are hampered by what has been recently called Technical Debt. Although a lot of theoretical work on Technical Debt has been recently produced, its practical management lacks empirical studies. In this paper we investigate the state of practice in several companies in order to understand how they start tracking Technical Debt. We combined different methodologies: we conducted a survey, involving 226 respondents from 15 organizations and a more in-depth multiple case-study in three organizations, where Technical Debt was tracked: we involved 13 interviews and 79 Technical Debt issues analysis. We found that the development time dedicated to manage Technical Debt is substantial (around 25%) but not systematic: only a few participants currently track Technical Debt. By studying the early approaches in the companies participating in the case-study, we understood how companies start tracking Technical Debt and what are the initial benefits and challenges. Finally, we propose a Strategic Adoption Model based to define and adopt a dedicated process for tracking Technical Debt.
|
|
| 3. |
- Martini, Antonio, 1982, et al.
(författare)
-
The introduction of technical debt tracking in large companies. A Survey and Multiple Case-Study
- 2016
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. ; 0, s. 161-168
-
Konferensbidrag (refereegranskat)abstract
- Large software companies need to support continuous and fast delivery of customer value both in the short and long term. However, this can be hindered if both evolution and maintenance of existing systems are hampered by Technical Debt. Although a lot of theoretical work on Technical Debt has been recently produced, its practical management lacks empirical studies. In this paper we investigate the state of practice in several companies in order to understand how they start tracking Technical Debt. We combined different methodologies: we conducted a survey, involving 226 respondents from 15 organizations and a more in-depth multiple case-study in three organizations, where Technical Debt was tracked: we involved 13 interviews and 79 Technical Debt issues analysis. We found that the development time dedicated to manage Technical Debt is substantial (around 25% of the overall development) but not systematic: only a few participants methodically track Technical Debt. By studying the approaches in the companies participating in the case-study, we understood how companies start tracking Technical Debt and what are the initial benefits and challenges. Finally, we propose a Strategic Adoption Model based to define and adopt a dedicated process for tracking Technical Debt.
|
|
