Architectural Debt Management in Value-Oriented Architecting

Architectural technical debt (ATD) may be incurred when making architecture decisions. In most cases, ATD is not effectively managed in the architecting process: It is not made explicit, and architecture decision making does not consider the ATD incurred by the different design options. This chapter proposes a conceptual model of ATD and an architectural technical debt management process applying this ATD conceptual model in order to facilitate decision making in a value-oriented perspective of architecting. We also demonstrate how ATD management can be employed in architectural synthesis and evaluation in a case study. The contribution of this work provides a controllable and predictable balance between the value and cost of architecture design in the long term.

[1]  Robert L. Nord,et al.  Managing technical debt in software-reliant systems , 2010, FoSER '10.

[2]  Robert L. Nord,et al.  A general model of software architecture design derived from five industrial approaches , 2007, J. Syst. Softw..

[3]  Carolyn B. Seaman,et al.  Measuring and Monitoring Technical Debt , 2011, Adv. Comput..

[4]  Robert L. Nord,et al.  Managing technical debt in software development: report on the 2nd international workshop on managing technical debt, held at ICSE 2011 , 2011, SOEN.

[5]  Jan Bosch,et al.  Software Architecture as a Set of Architectural Design Decisions , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[6]  Frank Buschmann,et al.  To Pay or Not to Pay Technical Debt , 2011, IEEE Software.

[7]  Paris Avgeriou,et al.  Forces on Architecture Decisions - A Viewpoint , 2012, 2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture.

[8]  Robert L. Nord,et al.  Technical Debt: From Metaphor to Theory and Practice , 2012, IEEE Software.

[9]  Forrest Shull,et al.  Prioritizing design debt investment opportunities , 2011, MTD '11.

[10]  Paris Avgeriou,et al.  A documentation framework for architecture decisions , 2012, J. Syst. Softw..

[11]  Ward Cunningham,et al.  The WyCash portfolio management system , 1992, OOPSLA '92.

[12]  Mark Klein,et al.  Quantifying the costs and benefits of architectural decisions , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[13]  Robert L. Nord,et al.  In Search of a Metric for Managing Architectural Technical Debt , 2012, 2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture.