Name
Abstract | ||
|---|---|---|
In the software development industry, Technical Debt is regarded as a critical issue in terms 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, and expose the business to risk. |
Year | DOI | Venue |
|---|---|---|
2019 | 10.1109/EDOCW.2019.00016 | 2019 IEEE 23rd International Enterprise Distributed Object Computing Workshop (EDOCW) |
Keywords | Field | DocType |
Enterprise Architecture Management, Enterprise Architecture Debt (EA Debt), Term Definition | Enterprise architecture,Systems engineering,Engineering management,Computer science,Debt | Conference |
ISSN | ISBN | Citations |
2325-6583 | 978-1-7281-4599-0 | 0 |
PageRank | References | Authors |
0.34 | 25 | 5 |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Simon Hacks | 1 | 4 | 4.21 |
| Hendrik Höfert | 2 | 0 | 0.34 |
| Johannes Salentin | 3 | 0 | 0.34 |
| Yoon Chow Yeong | 4 | 0 | 0.34 |
| Horst Lichter | 5 | 252 | 51.53 |