Enterprise Architecture

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

1. Frameworks

1.1. Zachman

1.1.1. components may be viewed in different ways depending on purpose and context

1.1.2. is for Planners Owners Designers Builders Subcontractors

1.2. TOGAF

1.2.1. Models Enterprise at 4 levels Business Application Data Technology

1.2.2. Supports

2. EA Roadmap

2.1. describes

2.1.1. current architecture business application data technical

2.1.2. target architecture business application data technical

2.1.3. transition plan project prioritization risks and issues migration strategy estimated costs success factors 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 scalability re-usability etc. may be overkill for the business problems at hand

3.5. user rejection

3.5.1. focus on common solutions creates dependencies between business units additional user acceptance risks

3.6. new dependancies

3.6.1. multiple business units different business cycles change requests must be prioritized may request different change windows change requests may conflict

3.7. project delays

3.7.1. EA governance means 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 business technology

4.2. it's not Change Management

4.2.1. Gaps in EA differences between current target not = wish list not = change requests

4.2.2. so Future state far enough in future not to look like

4.3. Politically Oriented Architecture

4.3.1. office politics shape EA technology proliferation broken processes fragmented data

4.3.2. solution EA reveals POA behaviour to decision makers

4.4. Resume Oriented Architecture

4.4.1. benefit EA only

4.4.2. recognize technology trendy high demand skill technology new to the EA technology not complimentary to existing technology overkill no realistic business case

4.5. Ivory Tower EA

4.5.1. elegant

4.5.2. out of touch

4.5.3. Solution architects ignore the architecture no implementation path

4.6. The Sinking EA

4.6.1. sucked down into solution architecture infrastructure details even development

4.6.2. motivation solution work important projects refusing seen as lazy personal recognition easier than EA problems Old habits die hard

4.6.3. Visit link for more link

4.6.4. result EA wrong message sent neglected 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 important EAs are not police EAs must break down barriers governance obstructs

6.2.2. IT governance team to handle EA & other governance

6.3. involved in

6.3.1. prototypes irrelevant time-suck

6.3.2. RFIs

6.3.3. RFPs

6.3.4. investigate EA tools only

6.3.5. managing projects except in scope of EA avoid comment on project execution relationship breakdown

6.3.6. version matters not version cops

6.3.7. conducting additional kind of audit 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 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 business architecture application components EAI components services processes events application architecture requirements rules processes vision critical success factors data architecture data models master data management data integration data architecture business intelligence data quality technology architecture infrastructure telecom 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 business goals business strategy stakeholder concerns 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 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 is reflected in EA documentation

10. Inputs

10.1. link

10.1.1. business goals strategies environment subject matter experts

10.1.2. architecture reference frameworks current

10.1.3. policies governance legal frameworks limits budget time organizational constraints contracts & agreements

11. Skills required

11.1. link

11.1.1. understands business big picture thinking Systems Thinking EA frameworks IT financial management data architecture technical architecture IT operations

11.1.2. skills interpersonal presentation coaching explaining IT to executives influencing time management

11.1.3. leadership

12. Value

12.1. link

12.1.1. strategic information asset to shape the Enterprise

12.1.2. supports efficient planning has discipline to plan years out IT investments understanding current directing future

12.1.3. align IT with business

12.1.4. breakdown silos a blueprint for everyone to follow forces thinking globally when acting locally

12.1.5. help senior management understand IT

12.1.6. control costs early detection of projects likely to fail drill managers to reuse existing company IT assets

12.1.7. technology watch

12.1.8. evangelists for standards best practices

12.1.9. recognize enterprise innovation propagate it

12.1.10. control your IT assets pass audit inspections

12.1.11. technical gurus of last resort keep consultants and vendors honest

13. Job responsibilities

13.1. link

13.1.1. Primary role: lead the EA process Business must be active in defining the architecture

13.1.2. alignment IT strategy <-> business goals

13.1.3. IT strategic responsibility long term

13.1.4. manage IT risk

13.1.5. with solution architects align projects with EA

13.1.6. promote shared services & infrastructure

13.1.7. manage IT lifecycle direct investment new infrastructure tools applications software standard conditional strategic emerging/research sunset retired blacklisted

13.1.8. develop standards policies best practices

13.1.9. evangelize IT strategy roadmap

14. EA software

15. Resources

15.1. shapes for communication