Architecture Technical Debt: Understanding Causes and a Qualitative Model

Martini, Antonio; Bosch, Jan; Chaudron, Michel R. V.

doi:10.1109/seaa.2014.65

Cited by 73 publications

(68 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In the context of (software) architecture, this is known as architectural technical debt. In a multiple-case embedded system case study in 5 large software companies (Martini et al, 2014), different factors for architectural technical debt have been identified, like pressure to deliver, prioritization of features over products, non-complete refactoring, or technology evolution. An identified example of architectural technical debt was a situation where a company used three different communication networks in a system, decided to refactor the complete system towards using a unified communication networks to make evolution easier.…”

Section: Architectural Technical Debtmentioning

confidence: 99%

Evolution of software in automated production systems: Challenges and research directions

Vogel‐Heuser

Fay

Schaefer

et al. 2015

Journal of Systems and Software

253

View full text Add to dashboard Cite

a b s t r a c tCoping with evolution in automated production systems implies a cross-disciplinary challenge along the system's life-cycle for variant-rich systems of high complexity. The authors from computer science and automation provide an interdisciplinary survey on challenges and state of the art in evolution of automated production systems. Selected challenges are illustrated on the case of a simple pick and place unit. In the first part of the paper, we discuss the development process of automated production systems as well as the different type of evolutions during the system's life-cycle on the case of a pick and place unit. In the second part, we survey the challenges associated with evolution in the different development phases and a couple of cross-cutting areas and review existing approaches addressing the challenges. We close with summarizing future research directions to address the challenges of evolution in automated production systems.

show abstract

Section: Architectural Technical Debtmentioning

confidence: 99%

Evolution of software in automated production systems: Challenges and research directions

Vogel‐Heuser

Fay

Schaefer

et al. 2015

Journal of Systems and Software

253

View full text Add to dashboard Cite

show abstract

“…As part of the Software Architecture Change Characterization Scheme (SACCS), a general classification of causes of architecture changes presented in [16] and another work [17] by the same authors can be used as the basic categorization of the causes of architecture changes in the two OSS projects in this study, which is elaborated in Section III. The work in [18] analyzes group interviews in various workshops for different levels of participants, e.g., developers, testers, and architects in five companies. The results validated a taxonomy of the causes for architecture technical debt, a kind of architecture inconsistency, which can be incurred and repaid by architecture changes.…”

Section: A Cause Of Architecture Changementioning

confidence: 99%

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

Ding¹,

Liang²,

Tang³

et al. 2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

“…As part of the Software Architecture Change Characterization Scheme (SACCS), a general classification of causes of architecture changes presented in [17] and another work [18] by the same authors can be used as the basic categorization of the causes of architecture changes in the two OSS projects in this study, which is elaborated in Section 3. The work in [19] analyzes group interviews in various workshops for different levels of participants, e.g., developers, testers, and architects in five companies. The results validated a taxonomy of the causes for architecture technical debt, a kind of architecture inconsistency, which can be incurred and repaid by architecture changes.…”

Section: Cause Of Architecture Changementioning

confidence: 99%

Understanding the Causes of Architecture Changes Using OSS Mailing Lists

Ding

Liang

Tang

et al. 2015

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

The causes of architecture changes can tell about why architecture changes, and this knowledge can be captured to prevent architecture knowledge vaporization and architecture degeneration. But the causes are not always known, especially in open source software (OSS) development. This makes it very hard to understand the underlying reasons for the architecture changes and design appropriate modifications. Architecture information is communicated in development mailing lists of OSS projects. To explore the possibility of identifying and understanding the causes of architecture changes, we conducted an empirical study to analyze architecture information (i.e., architectural threads) communicated in the development mailing lists of two popular OSS projects: Hibernate and ArgoUML, verified architecture changes with source code, and identified the causes of architecture changes from the communicated architecture information. The main findings of this study are: (1) architecture information communicated in OSS mailing lists does lead to architecture changes in code; (2) the major cause for architecture changes in both Hibernate and ArgoUML is preventative changes, and the causes of architecture changes are further classified to functional requirement, external quality requirement, and internal quality requirement using the coding techniques of grounded theory; (3) more than 45% of architecture changes in both projects happened before the first stable version was released. * This paper is an enhanced version of our previous paper "Causes of Architecture Changes: An Empirical

show abstract

Architecture Technical Debt: Understanding Causes and a Qualitative Model

Cited by 73 publications

References 14 publications

Evolution of software in automated production systems: Challenges and research directions

Evolution of software in automated production systems: Challenges and research directions

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

Understanding the Causes of Architecture Changes Using OSS Mailing Lists

Contact Info

Product

Resources

About