Towards the Definition of Enterprise Architecture Debts

Hacks, Simon; Hofert, Hendrik; Salentin, Johannes; Yeong, Yoon Chow; Lichter, Horst

doi:10.1109/edocw.2019.00016

Cited by 16 publications

(10 citation statements)

References 42 publications

(57 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Previously, Hacks et al [15] proposed to combine the concept of Technical Debt [8] with the concept of EA to so called EA Debts. EA Debts do not solely cover technical aspects but provide a more holistic view on the entire organization including for example flaws related to organizational structures.…”

Section: Ea Smellsmentioning

confidence: 99%

Using Knowledge Graphs to Detect Enterprise Architecture Smells

Smajevic

Hacks

Bork

2021

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Hitherto, the concept of Enterprise Architecture (EA) Smells has been proposed to assess quality flaws in EAs and their models. Together with this new concept, a catalog of different EA Smells has been published and a first prototype was developed. However, this prototype is limited to ArchiMate and is not able to assess models adhering to other EA modeling languages. Moreover, the prototype is not integrateable with other EA tools. Therefore, we propose to enhance the extensible Graph-based Enterprise Architecture Analysis (eGEAA) platform that relies on Knowledge Graphs with EA Smell detection capabilities. To align these two approaches, we show in this paper, how ArchiMate models can be transformed into Knowledge Graphs and provide a set of queries on the Knowledge Graph representation that are able to detect EA Smells. This enables enterprise architects to assess EA Smells on all types of EA models as long as there is a Knowledge Graph representation of the model. Finally, we evaluate the Knowledge Graph based EA Smell detection by analyzing a set of 347 EA models.

show abstract

Section: Ea Smellsmentioning

confidence: 99%

Using Knowledge Graphs to Detect Enterprise Architecture Smells

Smajevic

Hacks

Bork

2021

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

show abstract

“…"Enterprise Architecture Debt is a metric that depicts the deviation of the currently present state of an enterprise from a hypothetical ideal state." [7] In that sense, also the organizational position and the principles governing its design and evolution must be considered. This includes the different layers, respectively domains, of Enterprise Architecture and its associated artifacts.…”

Section: Ea Debtmentioning

confidence: 99%

“…In order to support many different cases flexibly, the metaphor relies on the artifactbased viewpoint of an EA, because especially in dynamically evolving environments robustness is very important. In this way, further artifacts can be added or removed for the purpose of adaption to the specific requirements [7].…”

Section: Ea Debtmentioning

confidence: 99%

See 1 more Smart Citation

Towards a Catalog of Enterprise Architecture Smells

Salentin¹,

Hacks²

2020

WI2020 Community Tracks

Self Cite

View full text Add to dashboard Cite

Code Smells are well known in the domain of Technical Debt (TD). They hint at common bad habits that impair the quality of the software system. By detecting those smells it is possible to suggest a better solution or, at least, make the developers aware of possible drawbacks. However, in terms of Enterprise Architecture (EA), which is a more holistic view of an enterprise including TD, there does not exist such a concept of EA Smells. Such EA Smells can be a component of EA Debt, working like a metric to rate the quality of data and estimate parts of the EA Debt in an EA Repository. The main goal of this work is to start the development of a catalog to facilitate future design and development of EAs. This catalog should be expanded and serve as food for thought to create a corresponding tool for the detection of smells.

show abstract

“…Thus, while e.g. the "Process" scope reflects the software delivery pipeline, the "Socio-Technical" scope integrates people into the development Enterprise Architecture [20] process and how they affect the quality. By this means not only dependencies to the code quality are identified, but also new emergent types of TD, which cannot be derived from the software quality itself.…”

Section: Figure 2: Observable Scope Of Technical Debtmentioning

confidence: 99%

Towards collaborative technical debt management in systems of systems

Schütz

Gómez

2020

Proceedings of the 3rd International Conference on Technical Debt

View full text Add to dashboard Cite

Systems Engineering is a matter of the perspective and scope where several principles of the systems thinking approach coincide. Following the fundamental system principle of holism and interaction theory, in order to understand the whole the system should be considered as a whole. Due to the phenomena of emergence, not all properties of a system can be determined or explained by its components alone. The conceptual model of Technical Debt already recognize the context sensitivity of Technical Debt as an essential factor and identifies phenomena that fall outside the core definition of Technical Debt as a major part of future research. This short paper shows why managing the parts does not equal managing the whole by introducing Technical Debt as an emergent characteristic and why the traditional Technical Debt-Management methods can only be partially applied to Systems of Systems. CCS CONCEPTS • Software and its engineering → Ultra-large-scale systems; Distributed systems organizing principles; Software functional properties; • Computing methodologies → Systems theory.

show abstract

Towards the Definition of Enterprise Architecture Debts

Cited by 16 publications

References 42 publications

Using Knowledge Graphs to Detect Enterprise Architecture Smells

Using Knowledge Graphs to Detect Enterprise Architecture Smells

Towards a Catalog of Enterprise Architecture Smells

Towards collaborative technical debt management in systems of systems

Contact Info

Product

Resources

About