Es gibt keine „Silver-Bullet“. Definieren Sie das Architekturframework nach Ihren indivi-duellen Bedürfnissen.

Define architecture principles based on corporate strategy and business goals. They will guide you through the design of your enterprise architecture.

Consider designing a business capability map. It will help you define the architecture vision and break down the scope into key aspects of your EA initiative.

Use a dependency view to describe your architecture on all levels.

Make sure to choose the right viewpoints. Different stakeholders have different information needs. The figure above shows a master planning matrix.

Assess alternatives to solutions and project proposals based on business fit, technology fit, risks and costs in a comprehensible way.

Define transition architectures by setting life cycles for architecture elements.

Make sure that architecture compliance reports are available for management at the push of a button.

Shared responsibility: Only review the quality of architecture elements under your responsibility.

InformationSystems

Architectures

BusinessArchitecture

Architecture Vision

Preliminary

ArchitectureChange

Management

Implementation Governance

Migration Planning

Opportunities and

Solutions

TechnologyArchitecture

RequirementsManagement

www.boc-group.com/adoit

ADOIT –Enterprise Architecture Community

www.adoit-community.com

Impr

int: p

ublis

her a

nd m

anufa

cture

r: BOC

Pro

ducts

& S

ervic

es AG

, plac

e of p

ublis

hing a

nd m

anufa

ctorin

g: Vi

enna

; © C

opyri

ght B

OC P

rodu

cts &

Ser

vices

AG, V

ienna

. The

BOC

Man

agem

ent O

ffice a

s well

as AD

OSCO

RE, A

DONI

S, AD

OLOG

, ADO

IT, AD

ONIS

:Com

munit

y an

d ADO

IT:Co

mmun

ity ar

e reg

ister

ed tr

adem

arks

of th

e BOC

Pro

ducts

& S

ervic

es A

G. A

ll of th

e con

tent is

prote

cted.

All o

ther n

amed

bran

ds ar

e pro

perty

of th

e res

pecti

ve co

mpan

ies. A

ll cha

nges

can o

nly be

mad

e with

a wr

itten l

etter

of ag

reem

ent fr

om th

e BOC

Pro

ducts

&

Servi

ces A

G. R

epro

ducti

ons i

n any

form

are o

nly al

lowed

with

the C

opyri

ght r

emar

k. Pu

blica

tions

and t

rans

lation

s nee

d a w

ritten

lette

r of a

gree

ment

from

the B

OC P

rodu

cts &

Ser

vices

AG.

1 Prepare 2 4The phase is imperative to successful Enter-prise Architecture Management. In this step you have to determine the scope, the stakeholders and the architecture principles of your initiative. If necessary you can adapt the EA framework and tool to fit to the requirements of your organisation. Subse-quently, you should establish requirements manage-ment which is a key concept for all the following phases.

Outline the future state architecture. Make sure to estab-lish the necessary capabilities for successfully implement-ing the future architecture. Last but not least, define KPIs to be able to measure the achievement of objectives.

The discipline of Enterprise Architecture Management (EAM) pursues the goal of increasing business efficiency by optimising enterprise IT to better support business processes as well as defining appropriate housekeeping measures. It supports the translation of information from business to IT and IT to business.

BOC’s approach to EAM is strongly based on TOGAF® (The Open Group Architecture Framework). It brings together the BOC Best Practices and the TOGAF® specifications, both from a method and tool point of view, by applying the Architecture Development Method (ADM) and using ADOIT.

Design Implement Govern

Enterprise Architecture Management with ADOIT

Preliminary phase, architecture vision and requirements management

The development of your architecture takes place in three architecture domains: business architecture, informa-tion systems architecture and technology architecture. Firstly, you need to describe the current state architec-ture, also known as the baseline architecture, and the future state architecture, also known as the tar-get architecture, for each of the mentioned domains.

Secondly, identify the dependencies of the three levels and match the levels in the target architecture. Use gap analyses to identify the differences between the base-line and target architectures. Make sure you understand the impacts on the entire architecture landscape.

Business architecture, information systems architecture and technology architecture

Opportunities and solutions: In this phase you should make a first draft of the implementation plan and identify implementation projects that are likely to be affected by the planned implementa-tion. Subsequently, work out solutions and al-ternatives and define transition architectures.

Migration planning: Perform in-depth cost-benefit analysis and develop an implementation plan.

Implementation governance: Drive the projects that implement the solutions and make sure that the imple-mentation complies with the architecture principles and guidelines.

Opportunities and solutions, migra-tion planning and implementation governance

Introduce architecture change management in order to be able to monitor your enterprise architecture con-tinuously. You will need to establish change and risk management processes.

Make sure that changes to the architecture are being checked against the business needs captured during requirements management. This will help you ensure that the architecture initiative increases business efficiency and shows business value.

In order to implement new requirements, trigger the ADM phases again and iterate as many times as necessary.

Architecture change management31

4

3

ADOIT – make architectures work

2

The EA Tool ADOIT is TOGAF® certified.*

Do you want to start

your Enterprise

Architecture Management

activities right away?

Get your FREE Version of the

ADOIT:Community Edition

www.adoit-community.com