Conceptual Model of Enterprise Architecture Management

2017 ◽  
Vol 26 (03) ◽  
pp. 1730001 ◽  
Author(s):  
Svyatoslav Kotusev

Enterprise architecture (EA) is a description of an enterprise from an integrated business and IT perspective. Enterprise architecture management (EAM) is a management practice embracing all the management processes related to EA aiming to improve business and IT alignment. EAM is typically described as a sequential four-step process: (i) document the current state, (ii) describe the desired future state, (iii) develop the transition plan and (iv) implement the plan. This traditional four-step approach to EAM essentially defines the modern understanding of EA. Based on a literature review, this paper demonstrates that this four-step approach to EAM, though practiced by some companies, is inadequate as a model explaining the EAM phenomenon in general. As a substitute, this paper synthesizes the generic conceptual model of EAM providing a more realistic conceptualization of EAM describing it as a decentralized network of independent but interacting processes, artifacts and actors.

2010 ◽  
pp. 996-1026
Author(s):  
Klaus D. Niemann

A comprehensive enterprise architecture management has strategic and operative aspects. Strategic tasks cover the identification of appropriate fields of activity for information technology (IT) investments in accordance with business strategy and portfolio management. Enterprise architecture management is cross-linked with other IT management processes and delivers the necessary information for a sustainable governance. The continuous analysis of the IT landscape, the deduction of measures for optimization and its controlling also belong to the tasks of architecture management. Standards for development and infrastructures are made, e.g. reference architectures and a “book of standards”, whose implementation is overseen by solution architects throughout the operative architecture management.


Author(s):  
Klaus D. Niemann

A comprehensive enterprise architecture management has strategic and operative aspects. Strategic tasks cover the identification of appropriate fields of activity for information technology (IT) investments in accordance with business strategy and portfolio management. Enterprise architecture management is cross-linked with other IT management processes and delivers the necessary information for a sustainable governance. The continuous analysis of the IT landscape, the deduction of measures for optimization and its controlling also belong to the tasks of architecture management. Standards for development and infrastructures are made, e.g. reference architectures and a “book of standards”, whose implementation is overseen by solution architects throughout the operative architecture management.


2019 ◽  
Vol 34 (2) ◽  
pp. 102-128 ◽  
Author(s):  
Svyatoslav Kotusev

Enterprise architecture is a description of an enterprise from an integrated business and IT perspective intended to bridge the communication gap between business and IT stakeholders and improve business and IT alignment. Enterprise architecture consists of multiple different artifacts providing certain views of an organization and the available enterprise architecture literature offers a number of comprehensive lists of artifacts that can be used as part of an enterprise architecture practice. However, these lists of enterprise architecture artifacts were never validated empirically and the practical usage of different artifacts still remains largely unexplored. Based on a comprehensive empirical analysis of enterprise architecture artifacts used in 27 diverse organizations, this study identifies the list of 24 common artifacts that proved useful in practice and describes in detail their usage and purpose. Although this study does not attempt to theorize on the findings, it makes a significant empirical contribution to the enterprise architecture discipline. In particular, this study (1) provides the first consistent list of enterprise architecture artifacts that actually proved useful in organizations, (2) offers the first available systematic description of their usage, (3) questions the common view of enterprise architecture as a set of business, information, applications and technology architectures and (4) questions the widely accepted conceptualization of enterprise architecture as a set of the current state, future state and transition roadmap. This study provides compelling empirical evidence in favor of reconceptualizing enterprise architecture and calls for further research in this direction.


2017 ◽  
Vol 40 ◽  
pp. 120-166 ◽  
Author(s):  
Fatemeh Rahimi ◽  
◽  
John Gøtze ◽  
Charles Møller ◽  
◽  
...  

Sign in / Sign up

Export Citation Format

Share Document