1. Frameworks
1.1. Zachman
1.1.1. components may be viewed in different ways
1.1.1.1. depending on purpose and context
1.1.2. is for
1.1.2.1. Planners
1.1.2.2. Owners
1.1.2.3. Designers
1.1.2.4. Builders
1.1.2.5. Subcontractors
1.2. TOGAF
1.2.1. Models Enterprise at 4 levels
1.2.1.1. Business
1.2.1.2. Application
1.2.1.3. Data
1.2.1.4. Technology
1.2.2. Supports
2. EA Roadmap
2.1. describes
2.1.1. current architecture
2.1.1.1. business
2.1.1.2. application
2.1.1.3. data
2.1.1.4. technical
2.1.2. target architecture
2.1.2.1. business
2.1.2.2. application
2.1.2.3. data
2.1.2.4. technical
2.1.3. transition plan
2.1.3.1. project prioritization
2.1.3.2. risks and issues
2.1.3.3. migration strategy
2.1.3.4. estimated costs
2.1.3.5. success factors
2.1.3.6. project measurements
3. Risks
3.1. security vulnerabilities / exposures
3.2. distracting critical staff
3.3. low adoption rates
3.4. increasing solution costs
3.4.1. enterprise-class solutions
3.4.1.1. scalability
3.4.1.2. re-usability
3.4.1.3. etc.
3.4.1.4. may be overkill for the business problems at hand
3.5. user rejection
3.5.1. focus on common solutions
3.5.1.1. creates dependencies between business units
3.5.1.2. additional user acceptance risks
3.6. new dependancies
3.6.1. multiple business units
3.6.1.1. different business cycles
3.6.1.2. change requests must be prioritized
3.6.1.3. may request different change windows
3.6.1.4. change requests may conflict
3.7. project delays
3.7.1. EA governance means
3.7.1.1. more check points
3.8. EA-introduced business performance metrics
3.8.1. sometimes unexpected / counter-productive results
3.8.2. often made a key selling point
4. Anti-patterns
4.1. Big Box EA
4.1.1. when EA is way too high level
4.1.2. not relevant to
4.1.2.1. business
4.1.2.2. technology
4.2. it's not Change Management
4.2.1. Gaps in EA
4.2.1.1. differences between
4.2.1.1.1. current
4.2.1.1.2. target
4.2.1.2. not = wish list
4.2.1.3. not = change requests
4.2.2. so
4.2.2.1. Future state
4.2.2.1.1. far enough in future
4.2.2.1.2. not to look like
4.3. Politically Oriented Architecture
4.3.1. office politics shape EA
4.3.1.1. technology proliferation
4.3.1.2. broken processes
4.3.1.3. fragmented data
4.3.2. solution
4.3.2.1. EA reveals POA behaviour to decision makers
4.4. Resume Oriented Architecture
4.4.1. benefit
4.4.1.1. EA only
4.4.2. recognize
4.4.2.1. technology trendy
4.4.2.1.1. high demand skill
4.4.2.2. technology new to the EA
4.4.2.3. technology not complimentary to existing
4.4.2.4. technology overkill
4.4.2.5. no realistic business case
4.5. Ivory Tower EA
4.5.1. elegant
4.5.2. out of touch
4.5.3. Solution architects
4.5.3.1. ignore the architecture
4.5.3.1.1. no implementation path
4.6. The Sinking EA
4.6.1. sucked down into
4.6.1.1. solution architecture
4.6.1.2. infrastructure details
4.6.1.3. even development
4.6.2. motivation
4.6.2.1. solution work
4.6.2.1.1. important projects
4.6.2.1.2. refusing seen as lazy
4.6.2.1.3. personal recognition
4.6.2.1.4. easier than EA problems
4.6.2.1.5. Old habits die hard
4.6.3. Visit link for more
4.6.3.1. link
4.6.4. result
4.6.4.1. EA
4.6.4.1.1. wrong message sent
4.6.4.1.2. neglected
4.6.4.1.3. EA thinking
4.7. Vendor Lock-in
4.7.1. EA should minimize
5. Simplicable.com
5.1. the excellent basis
5.2. for this map
5.3. link
6. Pitfalls
6.1. lack of focus
6.1.1. most common
6.2. EA Governance
6.2.1. s/b separate from EA
6.2.1.1. important
6.2.1.2. EAs are not police
6.2.1.3. EAs must break down barriers
6.2.1.3.1. governance obstructs
6.2.2. IT governance team
6.2.2.1. to handle EA
6.2.2.2. & other governance
6.3. involved in
6.3.1. prototypes
6.3.1.1. irrelevant time-suck
6.3.2. RFIs
6.3.3. RFPs
6.3.4. investigate EA tools only
6.3.5. managing projects
6.3.5.1. except in scope of EA
6.3.5.2. avoid comment on project execution
6.3.5.2.1. relationship breakdown
6.3.6. version matters
6.3.6.1. not version cops
6.3.7. conducting
6.3.7.1. additional kind of audit
6.3.7.1.1. will lose support
7. What?
7.1. collection of information describing
7.1.1. the business
7.1.2. the information
7.1.3. the technology
7.1.3.1. needed to operate the business
7.2. repository of information
7.2.1. needed to implement new technology
7.3. scope
7.4. domains
7.4.1. link
7.4.1.1. business architecture
7.4.1.1.1. application components
7.4.1.1.2. EAI components
7.4.1.1.3. services
7.4.1.1.4. processes
7.4.1.1.5. events
7.4.1.2. application architecture
7.4.1.2.1. requirements
7.4.1.2.2. rules
7.4.1.2.3. processes
7.4.1.2.4. vision
7.4.1.2.5. critical success factors
7.4.1.3. data architecture
7.4.1.3.1. data models
7.4.1.3.2. master data management
7.4.1.3.3. data integration
7.4.1.3.4. data architecture
7.4.1.3.5. business intelligence
7.4.1.3.6. data quality
7.4.1.4. technology architecture
7.4.1.4.1. infrastructure
7.4.1.4.2. telecom
7.4.1.4.3. security
7.5. EA lifecycle
7.5.1. link
8. Architecture Vision
8.1. The EA's elevator pitch
8.2. created
8.2.1. during project initiation
8.3. purpose
8.3.1. agree desired outcome for architecture
8.3.2. sell benefits of the architecture to decision-makers.
8.3.3. show how the architecture will support
8.3.3.1. business goals
8.3.3.2. business strategy
8.3.3.3. stakeholder concerns
8.3.3.4. stakeholder objectives
8.4. typical contents
8.4.1. Problem description
8.4.2. Objectives
8.4.3. Process descriptions
8.4.4. Roles and actors
8.4.5. Constraints
8.4.6. IT principles
8.4.7. Architecture overview
8.4.8. Mapping of proposed architecture to processes & requirements
9. EA Governance
9.1. link
9.1.1. EA impact?
9.1.2. update EA
9.1.3. technical assessment
9.1.4. PMO review
9.1.4.1. project management office (PMO)
9.1.5. implement
9.1.6. post implementation review
9.1.7. update EA
9.1.8. launch
9.1.9. ensure project-EA conformity
9.1.9.1. is reflected in EA documentation
10. Inputs
10.1. link
10.1.1. business
10.1.1.1. goals
10.1.1.2. strategies
10.1.1.3. environment
10.1.1.4. subject matter experts
10.1.2. architecture
10.1.2.1. reference
10.1.2.2. frameworks
10.1.2.3. current
10.1.3. policies
10.1.3.1. governance
10.1.3.2. legal frameworks
10.1.3.3. limits
10.1.3.3.1. budget
10.1.3.3.2. time
10.1.3.4. organizational constraints
10.1.3.5. contracts & agreements
11. Skills required
11.1. link
11.1.1. understands
11.1.1.1. business
11.1.1.2. big picture thinking
11.1.1.3. Systems Thinking
11.1.1.4. EA frameworks
11.1.1.5. IT financial management
11.1.1.6. data architecture
11.1.1.7. technical architecture
11.1.1.8. IT operations
11.1.2. skills
11.1.2.1. interpersonal
11.1.2.2. presentation
11.1.2.3. coaching
11.1.2.4. explaining IT to executives
11.1.2.5. influencing
11.1.2.6. time management
11.1.3. leadership
12. Value
12.1. link
12.1.1. strategic information asset
12.1.1.1. to shape the Enterprise
12.1.2. supports
12.1.2.1. efficient planning
12.1.2.1.1. has discipline to plan years out
12.1.2.2. IT investments
12.1.2.2.1. understanding current
12.1.2.2.2. directing future
12.1.3. align IT with business
12.1.4. breakdown silos
12.1.4.1. a blueprint
12.1.4.1.1. for everyone to follow
12.1.4.2. forces thinking globally
12.1.4.2.1. when acting locally
12.1.5. help senior management understand IT
12.1.6. control costs
12.1.6.1. early detection of projects likely to fail
12.1.6.2. drill managers to reuse existing company IT assets
12.1.7. technology watch
12.1.8. evangelists for
12.1.8.1. standards
12.1.8.2. best practices
12.1.9. recognize enterprise innovation
12.1.9.1. propagate it
12.1.10. control your IT assets
12.1.10.1. pass audit inspections
12.1.11. technical gurus of last resort
12.1.11.1. keep consultants and vendors honest
13. Job responsibilities
13.1. link
13.1.1. Primary role: lead the EA process
13.1.1.1. Business must be active in defining the architecture
13.1.2. alignment
13.1.2.1. IT strategy <-> business goals
13.1.3. IT strategic responsibility
13.1.3.1. long term
13.1.4. manage IT risk
13.1.5. with solution architects
13.1.5.1. align projects with EA
13.1.6. promote shared services & infrastructure
13.1.7. manage IT lifecycle
13.1.7.1. direct investment
13.1.7.1.1. new infrastructure
13.1.7.1.2. tools
13.1.7.1.3. applications
13.1.7.2. software
13.1.7.2.1. standard
13.1.7.2.2. conditional
13.1.7.2.3. strategic
13.1.7.2.4. emerging/research
13.1.7.2.5. sunset
13.1.7.2.6. retired
13.1.7.2.7. blacklisted
13.1.8. develop
13.1.8.1. standards
13.1.8.2. policies
13.1.8.3. best practices
13.1.9. evangelize
13.1.9.1. IT strategy
13.1.9.2. roadmap