An exploration of the many ways to approach the discipline of enterprise architecture

Abstract

Despite growing interest in enterprise architecture (EA) around the world in recent years, a lack of common understanding is frequently described by EA researchers/practitioners. We conducted a systematic mapping study and it revealed that the extent to which the authors/researchers are focused on EA, the sectors in which they are working, the academic disciplines in which they have studied, the countries where their affiliated organizations are located, the subject areas of the journals/publishers of their publications and the way they have approached EA and its practitioners are some major elements that might influence the existing uniformity in EA. In addition, this study demonstrates how important it is to pay attention to the definition of 'enterprise architecture' itself. The contribution of this study is the organization of the EA literature according to three major questions concerning 'who' have been published in the literature, 'where' they have been located and 'what' their publications are about. This helps to better identify sources of variety which could be on the basis of the lack of common understanding in EA and provides practitioners and stakeholders a better understanding of this challenge. This also provides relevant directions for future studies.

Metodología para la evaluación y comparación de marcos de trabajo de arquitectura empresarial

“…A lo largo del tiempo, ha aumentado la investigación sobre el despliegue de la arquitectura empresarial entre la academia y la industria (Anthony et al, 2021), produciéndose una multitud de interpretaciones del concepto de arquitectura empresarial (Nilsen, 2012;Singh, 2013;Dang y Pekkola 2017;Kotusev, 2017;Saint-Louis y Lapalme, 2018;Abdallah y Abran, 2019;Marini, 2019;Pähler et al, 2019;Rogier et al, 2020;Ajer, 2020;Hussein, 2022) y que ha producido una falta de consenso (Hussein, 2022). Hasta el momento no existe una definición única de arquitectura empresarial (Niemann, 2005;Ross et al, 2006;Winter y Fischer, 2007;Perroud y Inversini, 2013;Kotusev et al, 2015;Nygård y Olsen, 2016;Dang y Pekkola, 2017) y para TRIBUNA -168-Chavez Rodríguez M. M Metodología para la evaluación y comparación de marcos de trabajo de arquitectura empresarial muchos autores se trata de un concepto en evolución (Leal et al, 2021).…”

Towards software reuse through an enterprise architecture-based software capability profile

“…The design of an enterprise information system that underpins the operations of an enterprise is guided by the development of strategy, management of programs and enterprise architecture (EA) [13]. The latter supports practitioners to handle enterprise information system engineering and changes [14], and align business strategies with IT to catch unexploited opportunities that has placed enterprises in competitive disadvantage in emerging market due to inadequate alignment [15].…”

Towards Different Enterprise Architecture Project Types

“…EA is thus used for business transformation [44]; in fact, it is seen as a process that simplifies business transformation and integration [28]. EA is further viewed as a solution for enterprise integration into the changing environment in which it operates [13,50]. The EA project type, business transformation, is derived from enterprise adaptation and integration into the dynamic environment and the need for agility and innovation.…”

“…The cost-saving EA project type is also derived from a study where reduction in business and IT cost through elimination of duplicate information systems and business processes is mentioned as a reason why EA is performed in the public sector [42]. A systematic mapping study of literature on various ways and reasons why EA is conducted confirms that EA can be performed to eliminate duplication in functionality and to enhance reuse of functionality in order to reduce IT cost [50]. Thus, elimination of duplication of information systems is another EA project type that is derived.…”

“…Another implication is that architects who work together will differ on their roles and what they are responsible for. This may lead to conflict, which may complicate stakeholder engagement and EA project execution [50].…”