Enterprise Architecture

Get Started. It's Free
or sign up with your email address
Rocket clouds
Enterprise Architecture by Mind Map: Enterprise Architecture

1. What?

1.1. collection of information describing

1.1.1. the business

1.1.2. the information

1.1.3. the technology

1.1.3.1. needed to operate the business

1.2. repository of information

1.2.1. needed to implement new technology

1.3. scope

1.4. domains

1.4.1. link

1.4.1.1. business architecture

1.4.1.1.1. application components

1.4.1.1.2. EAI components

1.4.1.1.3. services

1.4.1.1.4. processes

1.4.1.1.5. events

1.4.1.2. application architecture

1.4.1.2.1. requirements

1.4.1.2.2. rules

1.4.1.2.3. processes

1.4.1.2.4. vision

1.4.1.2.5. critical success factors

1.4.1.3. data architecture

1.4.1.3.1. data models

1.4.1.3.2. master data management

1.4.1.3.3. data integration

1.4.1.3.4. data architecture

1.4.1.3.5. business intelligence

1.4.1.3.6. data quality

1.4.1.4. technology architecture

1.4.1.4.1. infrastructure

1.4.1.4.2. telecom

1.4.1.4.3. security

1.5. EA lifecycle

1.5.1. link

2. Frameworks

2.1. Zachman

2.1.1. components may be viewed in different ways

2.1.1.1. depending on purpose and context

2.1.2. is for

2.1.2.1. Planners

2.1.2.2. Owners

2.1.2.3. Designers

2.1.2.4. Builders

2.1.2.5. Subcontractors

2.2. TOGAF

2.2.1. Models Enterprise at 4 levels

2.2.1.1. Business

2.2.1.2. Application

2.2.1.3. Data

2.2.1.4. Technology

2.2.2. Supports

3. EA Roadmap

3.1. describes

3.1.1. current architecture

3.1.1.1. business

3.1.1.2. application

3.1.1.3. data

3.1.1.4. technical

3.1.2. target architecture

3.1.2.1. business

3.1.2.2. application

3.1.2.3. data

3.1.2.4. technical

3.1.3. transition plan

3.1.3.1. project prioritization

3.1.3.2. risks and issues

3.1.3.3. migration strategy

3.1.3.4. estimated costs

3.1.3.5. success factors

3.1.3.6. project measurements

4. Architecture Vision

4.1. The EA's elevator pitch

4.2. created

4.2.1. during project initiation

4.3. purpose

4.3.1. agree desired outcome for architecture

4.3.2. sell benefits of the architecture to decision-makers.

4.3.3. show how the architecture will support

4.3.3.1. business goals

4.3.3.2. business strategy

4.3.3.3. stakeholder concerns

4.3.3.4. stakeholder objectives

4.4. typical contents

4.4.1. Problem description

4.4.2. Objectives

4.4.3. Process descriptions

4.4.4. Roles and actors

4.4.5. Constraints

4.4.6. IT principles

4.4.7. Architecture overview

4.4.8. Mapping of proposed architecture to processes & requirements

5. Risks

5.1. security vulnerabilities / exposures

5.2. distracting critical staff

5.3. low adoption rates

5.4. increasing solution costs

5.4.1. enterprise-class solutions

5.4.1.1. scalability

5.4.1.2. re-usability

5.4.1.3. etc.

5.4.1.4. may be overkill for the business problems at hand

5.5. user rejection

5.5.1. focus on common solutions

5.5.1.1. creates dependencies between business units

5.5.1.2. additional user acceptance risks

5.6. new dependancies

5.6.1. multiple business units

5.6.1.1. different business cycles

5.6.1.2. change requests must be prioritized

5.6.1.3. may request different change windows

5.6.1.4. change requests may conflict

5.7. project delays

5.7.1. EA governance means

5.7.1.1. more check points

5.8. EA-introduced business performance metrics

5.8.1. sometimes unexpected / counter-productive results

5.8.2. often made a key selling point

6. EA Governance

6.1. link

6.1.1. EA impact?

6.1.2. update EA

6.1.3. technical assessment

6.1.4. PMO review

6.1.4.1. project management office (PMO)

6.1.5. implement

6.1.6. post implementation review

6.1.7. update EA

6.1.8. launch

6.1.9. ensure project-EA conformity

6.1.9.1. is reflected in EA documentation

7. Anti-patterns

7.1. Big Box EA

7.1.1. when EA is way too high level

7.1.2. not relevant to

7.1.2.1. business

7.1.2.2. technology

7.2. it's not Change Management

7.2.1. Gaps in EA

7.2.1.1. differences between

7.2.1.1.1. current

7.2.1.1.2. target

7.2.1.2. not = wish list

7.2.1.3. not = change requests

7.2.2. so

7.2.2.1. Future state

7.2.2.1.1. far enough in future

7.2.2.1.2. not to look like

7.3. Politically Oriented Architecture

7.3.1. office politics shape EA

7.3.1.1. technology proliferation

7.3.1.2. broken processes

7.3.1.3. fragmented data

7.3.2. solution

7.3.2.1. EA reveals POA behaviour to decision makers

7.4. Resume Oriented Architecture

7.4.1. benefit

7.4.1.1. EA only

7.4.2. recognize

7.4.2.1. technology trendy

7.4.2.1.1. high demand skill

7.4.2.2. technology new to the EA

7.4.2.3. technology not complimentary to existing

7.4.2.4. technology overkill

7.4.2.5. no realistic business case

7.5. Ivory Tower EA

7.5.1. elegant

7.5.2. out of touch

7.5.3. Solution architects

7.5.3.1. ignore the architecture

7.5.3.1.1. no implementation path

7.6. The Sinking EA

7.6.1. sucked down into

7.6.1.1. solution architecture

7.6.1.2. infrastructure details

7.6.1.3. even development

7.6.2. motivation

7.6.2.1. solution work

7.6.2.1.1. important projects

7.6.2.1.2. refusing seen as lazy

7.6.2.1.3. personal recognition

7.6.2.1.4. easier than EA problems

7.6.2.1.5. Old habits die hard

7.6.3. Visit link for more

7.6.3.1. link

7.6.4. result

7.6.4.1. EA

7.6.4.1.1. wrong message sent

7.6.4.1.2. neglected

7.6.4.1.3. EA thinking

7.7. Vendor Lock-in

7.7.1. EA should minimize

8. Simplicable.com

8.1. the excellent basis

8.2. for this map

8.3. link

9. Pitfalls

9.1. lack of focus

9.1.1. most common

9.2. EA Governance

9.2.1. s/b separate from EA

9.2.1.1. important

9.2.1.2. EAs are not police

9.2.1.3. EAs must break down barriers

9.2.1.3.1. governance obstructs

9.2.2. IT governance team

9.2.2.1. to handle EA

9.2.2.2. & other governance

9.3. involved in

9.3.1. prototypes

9.3.1.1. irrelevant time-suck

9.3.2. RFIs

9.3.3. RFPs

9.3.4. investigate EA tools only

9.3.5. managing projects

9.3.5.1. except in scope of EA

9.3.5.2. avoid comment on project execution

9.3.5.2.1. relationship breakdown

9.3.6. version matters

9.3.6.1. not version cops

9.3.7. conducting

9.3.7.1. additional kind of audit

9.3.7.1.1. will lose support

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

14. EA software

15. Resources

15.1. shapes for communication