|
Enterprise Architecture matters |
|
Adrian Grigoriu
|
|
Tuesday, 23 October 2007 |
Do you have a clear definition of what Enterprise Architecture (EA) is? I thought so. This is why I would like to return to what this is!
Is Enterprise Architecture
- an Enterprise state
- a document, a set of diagrams
- a process
- a program
- a strategic planning exercise and Enterprise portfolio management
- an Enterprise IT integration program
- a Business Process Management (BPM) development
- an organization alignment to strategy and business objectives
- an organization design?
Now, there is no penury of definitions: here are a few from reputed organizations:
CIO Definitions from SearchCIO.com, posted October, 2006:
"An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives. Purported advantages of having an enterprise architecture include improved decision making, improved adaptability to changing demands or market conditions, elimination of inefficient and redundant processes, optimization of the use of organizational assets, and minimization of employee turnover."
From General Accountability Office (GAO) of the US federal government, August 2006:
"An enterprise architecture is a blueprint for organizational change defined in models [using words, graphics, and other depictions] that describe (in both business and technology terms) how it operates today and how it intends to operate in the future; it also includes a plan for transitioning to this future state".
FEA definition:
"The FEA (Federal Enterprise Architecture) consists of a set of interrelated "reference models" designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps and opportunities for collaboration within and across agencies. Collectively, the reference models comprise a framework for describing important elements of the FEA in a common and consistent way. Through the use of this common framework and vocabulary, IT portfolios can be better managed and leveraged across the federal government."
From TOGAF 8.1 FAQ:
"An EA defines the components or building blocks that make up the overall Enterprise "their interrelationships and guidelines governing their design and evolution" All good definitions but sometimes seen from slightly different angles.
Let us try to consolidate them in a single enduring definition in the post to come.
Only registered users can write comments.
Please login or register. |
