Due to the confusion which the term 'Enterprise Architecture' seems to reflect, attempting to articulate a precise definition could be challenging. Here my effort will be to gain some clarity at a simplistic level.
In essence, the scope of Enterprise Architecture can be gathered thru the acronym 'BAIT' as follows:
- Business Architecture (business processes, perspective, plans, drivers etc)
- Applications Architecture (applications development and management standards)
- Information Architecture (structure, assets, relationships)
- Technology Architecture (IT infrastructure standards including hardware, software etc)
The distinction therefore, between Enterprise Architecture (EA) and IT Architecture is that EA includes all 4 elements above. The focus of IT architecture however, is restricted to the applications, information and technology areas (excluding the business architecture).
EA hence documents the relationship between these 4 layers & with the external environment (e.g. customers, stakeholders, regulatory compliance requirements etc).
Enterprise Architecture provides a model in order to:
- Capture the current state architecture
- Capture the desired future state architecture
- Develop an actionable roadmap to make the transition to the desired state architecture (achieved thru a governance process)
Enterprise Architecture defines Principles which are high level statements defining how IT will be used to support and be aligned with the business.
In brief, Enterprise Architecture provides a top-down approach, starting with the organisation's Business Strategy, then studying the IT Strategy. Models such as TOGAF [1] or Zachman [2] are used to capture the architecture.
To gain tangible benefit, a roadmap of initiatives/projects is developed to progress the organisation from the current state to desired state. Once executed, the result will be an organisation more effectively managed, better aligned and more agile.
This could be a somewhat simplified description considering the wide-reach of Enterprise Architecture and its interfaces across the business (e.g. with IT Investment planning, Project Management etc), however it suffices as a simple description allowing the reader to gain clarity on understanding one of IT's most challenges areas.
Enterprise architecture helps to close the gap between IT and the business at all levels. It takes a 360 degree view by gaining an intimate understanding of the business and how technology supports existing and future requirements.
References:
[1] http://www.opengroup.org/togaf/
[2] http://www.zifa.com/framework.html
