# Towards the Definition of Enterprise Architecture Debts

arXiv: https://arxiv.org/abs/1907.00677 · HTML: https://mlsanity.com/paper/1907.00677/

## Key facts

- Cited by 1 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 28 Jun 2019.

## Built on by (most cited first, 1 of 1)

- [Large Language Models for Analyzing Enterprise Architecture Debt in Unstructured Documentation](https://mlsanity.com/paper/2604.00046/) (2026)

## Abstract (arXiv)

In the software development industry, technical debt is regarded as a critical issue in term of the negative consequences such as increased software development cost, low product quality, decreased maintainability, and slowed progress to the long-term success of developing software. However, despite the vast research contributions in technical debt management for software engineering, the idea of technical debt fails to provide a holistic consideration to include both IT and business aspects. Further, implementing an enterprise architecture (EA) project might not always be a success due to uncertainty and unavailability of resources. Therefore, we relate the consequences of EA implementation failure with a new metaphor --Enterprise Architecture Debt (EA Debt). We anticipate that the accumulation of EA Debt will negatively influence EA quality, also expose the business into risk.