Technical debt, which refers to immature software artifacts that fail to meet the required level of quality, has recently been attracted increasing attention from both academic and industry in software engineering field. To date, little work has been done on technical debt at architecture level, i.e., architectural debt. In the short term, architectural debt may be incurred to fulfill specific business advantages; and, in the long term, architectural debt can to a great extent reduce the maintainability and evolvability of a software system. Our group focuses on architectural debt management which main goal is to achieve the balance between value and cost of architectural debt. Until now, we have proposed a conceptual model of architectural debt and an architectural technical debt management process applying this ATD conceptual model in order to facilitate the decision-making in a value-oriented perspective of architecting. Our current work is focusing on identifying, measuring, and documenting architectural debt.
- STAND (Semantic-enabled collaboration Towards Analysis, Negotiation and Documentation on distributed requirements engineering)
Tools and Demos
For tools and demos regarding this research area, please visit our Resources page.
(For more publications go to the publications page for Technical Debt.)
|Xiao He, Paris Avgeriou, Peng Liang, and Zengyang Li. Technical Debt in MDE: A Case Study on GMF/EMF-Based Projects. In Proceedings of the 19th International Conference on Model Driven Engineering Languages and Systems (MoDELS). ACM, pages 162–172, 2016.|| doi|