Enterprise Architecture

Where it is applicable
1. public/private sector organisation
2. Entire business/corporation
3. Part of a larger enterprise
4. multiply outsourced business operation
What is it?
1. coherent whole of
  1. Principles
  2. Methods
  3. Models
  4. used in the design and realisation of
    1. organisational structure
    2. information systems
    3. infrastructure
Why consider it
1. Information systems must keep pace with those changes
Key Concepts
1. Linking Business Goals with Information System
2. "as is" to the "to be"
3. Used to capture significant representations of the architecture
4. Used to enhance communication
EA Frameworks
1. Zachman Framework
2. Federal Enterprise Architecture Planning
3. Enterprise Architecture Planning
4. TOGAF
  1. Architecture Development Method (ADM)
ADM Phases
1. 1. Preliminary
  1. outling ''as-is" and "to-be
2. 2. Business Architecture
  1. Business Strategy
  2. Governance
  3. Organisation
  4. Business Processes
3. 3. Data and Application Domains
  1. Architecture of IT applications deployed
4. 4. Technology Architecture
  1. Describes software and hardware capabilities
5. 5. Opportunities and Solutions
6. 5. Migration Planning
7. 6. Implementation Governance
8. 7. Architecture Change Management
Potential Pitfalls of EA modelling
1. Lack of senior managment commitment
2. Lack of governance
3. "Overscoping" the projects
4. Failure to establish good communication mechanisms

Resource summary

	Created by d.rams about 11 years ago