4.5 Article

Architectural design decisions that incur technical debt - An industrial case study

Journal

INFORMATION AND SOFTWARE TECHNOLOGY
Volume 139, Issue -, Pages -

Publisher

ELSEVIER
DOI: 10.1016/j.infsof.2021.106669

Keywords

Technical debt; Architectural design decisions; Architectural knowledge; Architectural technical debt

Funding

  1. ITEA3, Netherlands [17038 VIS-DOM]
  2. RV, Netherlands [17038 VIS-DOM]

Ask authors/readers for more resources

This study explores debt-incurring architectural design decisions in software development, including the main types, reasons for their occurrence, and how practitioners deal with them. The results provide a categorization of DADDs types, a process for deliberate DADDs, a conceptual model showing relationships between causes and triggers of inadvertent DADDs, and main factors influencing the way of dealing with DADDs.
Context: During software development, some architectural design decisions incur technical debt, either deliberately or inadvertently. These have serious impact on the quality of a software system, and can cost significant time and effort to be changed. While current research efforts have explored general concepts of architectural design decisions and technical debt separately, debt-incurring architectural design decisions have not been specifically explored in practice. Objective: In this case study, we explore debt-incurring architectural design decisions (DADDs) in practice. Specifically, we explore the main types of DADDs, why and how they are incurred in a software system, and how practitioners deal with these types of design decisions. Method: We performed interviews and a focus group with practitioners working in embedded and enterprise software companies, discussing their concrete experience with such architectural design decisions. Results: We provide the following contributions: 1) A categorization for the types of DADDs, which extend a current ontology on architectural design decisions. 2) A process on how deliberate DADDs are made in practice. 3) A conceptual model which shows the relationships between the causes and triggers of inadvertent DADDs. 4) The main factors that influence the way of dealing with DADDs. Conclusion: The results can support the development of new approaches and tools for Architecture Technical Debt management from the perspective of Design Decisions. Moreover, they support future research to capture architecture knowledge related to DADDs.

Authors

I am an author on this paper
Click your name to claim this paper and add it to your profile.

Reviews

Primary Rating

4.5
Not enough ratings

Secondary Ratings

Novelty
-
Significance
-
Scientific rigor
-
Rate this paper

Recommended

No Data Available
No Data Available