Enterprise Architecture Management: Toward a Taxonomy of Applications

Rahimi, Fatemeh; Gøtze, John; Møller, Charles

doi:10.17705/1cais.04007

Cited by 26 publications

(30 citation statements)

References 54 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Several frameworks were proposed, refined and implemented in practice [3][4][5][6][7][8][9], and scholarly research investigated the nature and impact of EA [10][11][12][13][14][15][16]. Recent developments in the broad domain of EA include Enterprise Architecture Management (EAM) that elevates EA as a strategic business function rather than an IT function within organizations, and recent research indicate that EAM may indeed assist with organizational agility and transformation [17][18][19][20][21].…”

Section: Introductionmentioning

confidence: 99%

The Zachman Framework for Enterprise Architecture: An Explanatory IS Theory

Gerber

Roux

Kearney

et al. 2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Enterprise Architecture (EA) has had an interesting and often controversial history since its inception in the late 80's by pioneers such as John Zachman. Zachman proposed the Zachman Framework for Enterprise Architecture (ZFEA), a descriptive, holistic representation of an enterprise for the purposes of providing insights and understanding. Some scholars claim that EA is an imperative to ensure successful business structures or business-IT alignment, or more recently with Enterprise Architecture Management (EAM), to manage required organizational transformation. However, EA initiatives within companies are often costly and the expected return on investment is not realized. In fact, Gartner recently indicated in their 2018 Enterprise Architecture Hype Cycle that EA is slowly emerging from the trough of disillusionment after nearly a decade. In this paper we argue that the role and value of EA is often misunderstood, and that EA, specifically the ZFEA for the purpose of this paper, could be considered as a theory given the view of theory within Information Systems (IS). The purpose of IS theories is to analyse, predict, explain and/or prescribe and it could be argued that EA often conform to these purposes. Using the taxonomy of theories as well as the structural components of theory within IS as proposed by Gregor, we motivate that the ZFEA could be regarded as an explanatory theory. Positioning ZFEA as IS explanatory theory provides insight into the role and purpose of the ZFEA (and by extension EA), and could assist researchers and practitioners with mediating the challenges experienced when instituting EA and EAM initiatives within organizations.

show abstract

Section: Introductionmentioning

confidence: 99%

The Zachman Framework for Enterprise Architecture: An Explanatory IS Theory

Gerber

Roux

Kearney

et al. 2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Similarly, the EA community has already started to address this situation in scientific ways. 1,5,7,10,67,68 But to date, it is clear that the studies that have prioritized addressing the problematic related to the existence of various perspectives in EA do not seem to be commonly accepted yet. A meta-analysis of this problematic must continue to be conducted.…”

Section: Discussionmentioning

confidence: 99%

“…To achieve this objective, other references that analyzed or identified a list of the most common EA definitions were consulted in order to verify that these definitions were similar to those found in this study. For example, the definitions included in the study of Rahimi et al 10 were consulted. This study is one of the few that analyzed many EA definitions with the objective to explain "what EA means," even if this was not the objective of the whole study.…”

Section: Execution Of the Reviewmentioning

confidence: 99%

“…This study is one of the few that analyzed many EA definitions with the objective to explain "what EA means," even if this was not the objective of the whole study. The majority of the EA definitions found in the study of Rahimi et al 10 were already included in the definitions previously extracted in our database. However, eight new explicit definitions found within this study were added to our database.…”

Section: Execution Of the Reviewmentioning

confidence: 99%

See 1 more Smart Citation

Examination of explicit definitions of enterprise architecture

Saint-Louis

Morency

Lapalme

2019

International Journal of Engineering Business Management

View full text Add to dashboard Cite

Various understandings of enterprise architecture (EA) exist and there is no agreement on them. The various definitions of EA are not always complementary but sometimes in opposition. Within this study, we conduct a systematic literature review to analyze explicit definitions of EA. Based on concepts from the academic field of terminology, we have broken down these definitions into many parts in order to examine each part individually before making generalizations. The findings show how some of the EA definitions are implicit, incomplete, complex, and incoherent.

show abstract

“…This is necessary in order for the enterprise architecture (EA) to be developed with the internal as well as the external environment in mind. [37]. Yet, since EAM's introduction in the beginning of the 1990s, EAM has been hailed as a holistic and feasible approach for organizations with complex and fragmented IT portfolios [5,15,35,47].…”

Section: Introductionmentioning

confidence: 99%