Identifying and Prioritizing Architectural Debt Through Architectural Smells: A Case Study in a Large Software Company
- 15 September 2018
- book chapter
- Published by Springer Nature
- p. 320-335
Abstract
No abstract availableKeywords
This publication has 18 references indexed in Scilit:
- A semi-automated framework for the identification and estimation of Architectural Technical Debt: A comparative case-study on the modularization of a software componentInformation and Software Technology, 2018
- The Pricey Bill of Technical Debt: When and by Whom will it be Paid?2017
- Arcan: A Tool for Architectural Smells Detection2017
- A Case Study in Locating the Architectural Roots of Technical Debt2015
- On the Shape of Circular Dependencies in Java Programs2014
- Do developers care about code smells? An exploratory survey2013
- Assessing the capability of code smells to explain maintenance problems: an empirical study combining quantitative and qualitative dataEmpirical Software Engineering, 2013
- Supporting the identification of architecturally-relevant code anomalies2012
- Guidelines for conducting and reporting case study research in software engineeringEmpirical Software Engineering, 2008
- Object-Oriented Metrics in Practice2006