Towards the Definition of Enterprise Architecture Debts

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...

Full description

Saved in:
Bibliographic Details
Published inarXiv.org
Main Authors Hacks, Simon, Höfert, Hendrik, Salentin, Johannes, Yoon Chow Yeong, Lichter, Horst
Format Paper Journal Article
LanguageEnglish
Published Ithaca Cornell University Library, arXiv.org 28.06.2019
Subjects
Computer Science - Software Engineering
Debt management
Industrial development
Maintainability
Software development
Software engineering
Online AccessGet full text

Cover

More Information
Summary: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.
ISSN:2331-8422
DOI:10.48550/arxiv.1907.00677