Towards the Definition of Enterprise Architecture Debts

June 28, 2019 Β· Declared Dead Β· πŸ› 2019 IEEE 23rd International Enterprise Distributed Object Computing Workshop (EDOCW)

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Simon Hacks, Hendrik HΓΆfert, Johannes Salentin, Yoon Chow Yeong, Horst Lichter arXiv ID 1907.00677 Category cs.SE: Software Engineering Citations 17 Venue 2019 IEEE 23rd International Enterprise Distributed Object Computing Workshop (EDOCW) Last Checked 4 months ago
Abstract
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.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted