Enterprise architecture management

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Enterprise Architecture Management Maturity Framework : Maturity Stages, Critical Success Attributes, and Core Elements.[1]

Enterprise Architecture Management (or EAM) in the field of Enterprise architecture describes and structures complex IT systems in terms of their business, application, information, and technical layers, and to reform programs through the planning process as strategic business demands, and as standards and guidelines for the development of local solutions and service offers.[citation needed]

Overview[edit]

The fundamental prerequisites for effective EAM are a current, consistent baseline of information about the as-is landscape and an integrated planning process from demand to budget to reach the to-be landscape. The enterprise architecture function also involves reviewing and consolidating detailed architecture decisions and migration plans to identify efficiencies, advance standardization, and align business and IT priorities.[citation needed]

As IT architectural layers, business support processes, and organizational structures become more sophisticated and prone to constant change, EAM will only result in haphazard business and IT alignment if the primary focus is on delivering sets of technically based models. This approach is only helpful insofar as it depicts the enterprise architecture as a snapshot in time, but it offers no reiterative process support to develop architecture solutions and test against different scenarios, benchmarks, and standards as dictated by the ever converging business and IT strategy.[citation needed]

Moreover, a model-centric approach is prohibitively time-intensive to keep updated and leaves too much room for error as changes to the architecture occur unchecked and isolated in the heads of small groups of architecture specialists. Instead, the EAM effort has to bring the highly distributed knowledge of all experts to the table and allow every participant to provide such knowledge and input in the terms that best fit the experience and expectations of the contributing stakeholders.[citation needed]

Application[edit]

Successful Enterprise Architecture programs are approached from a management perspective as opposed to a modeling perspective. A new generation of EA Planning tools are emerging that support not only the modeling of the architecture, but also the creation of roll-out and implementation plans for continuous IT improvement over time.[clarification needed][citation needed]

An important aspect of this approach is support of collaboration amongst a wide group of stakeholders from both business and IT including C-level, IT strategists, planning teams, technology implementers, and business analysts, who contribute to the EA management and planning process. In this way EAM supports sustainable business strategy realization.[citation needed]

See also[edit]

References[edit]

  1. ^ United States General Accounting Office (2003-04). A Framework for Assessing and Improving Enterprise Architecture Management (Version 1.1). April 2003. Retrieved from http://www.gao.gov/new.items/d03584g.pdf.

External links[edit]