7/28/2019 EA Poster en-1

1/1

Es gibt keine Silver-Bullet. Denieren Sie

das Architekturframework nach Ihren indivi-

duellen Bedrfnissen.

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 youdefine 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. Differentstakeholders have different information needs. The figure

above shows a master planning matrix.

Assess alternative s to solutions and project proposals

based on business fit, technology fit, risks and costs in acomprehensible way.

Define transition architectures by setting life cycles forarchitecture elements.

Make sure that architecture compliance reports are available

for management at the push of a button.

Shared responsibility: Only review the quality of architectureelements under your responsibility.

InformationSystems

Architectures

Business

Architecture

ArchitectureVision

Preliminary

Architecture

Change

Management

Implementation

Governance

MigrationPlanning

Opportunitiesand

Solutions

Technology

Architecture

RequirementsManagement

www.boc-group.com/ADOit

ADOitEnterprise Architecture Community

www.adoit-community.com

Imprint:publisherandmanufacturer:BOCInformationTechnologiesConsultingAG

,placeofpublishingandmanufactoring:Vienna;

CopyrightBOCInformationTechnologiesConsultingAG

,Vienna.

TheBOC

ManagementOfceaswellasADOscore,

ADONIS,

ADOlog,

ADOitandADONIS:CommunityareregisteredtrademarksoftheBOC

InformationTechnologiesConsultingAG.

Allofthecontentisprotected.

Allother

namedbrandsarepropertyoftherespectivecompanies.

Allchangescanonlybemadewithawrittenletterofagree-

mentfromt

heBOC

InformationTechnologiesConsultingAG.

Reproductionsinanyforma

reonlyallowedwiththeCopyrightremark.

Publicationsandtranslationsneedawrittenletterofagreementfromt

heBOCInformationTechnologiesConsultingAG.

*TheOpenGroupTOGAF

9ToolCerticationMarkisatrademarkofTheOpenGroup.

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, dene 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.

BOCs 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

ADO it.

Design Implement Govern

Enterprise Architecture Management

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 management3

1

4

3

ADOit make architectures work

2

The EA Tool ADO it is TOGAF certified.*