Vous êtes sur la page 1sur 1

Enterprise Architecture Management


1 4
Architecture Vision Architecture Change Management Business Architecture

Implementation Governance

Requirements Management

Information Systems Architectures

Preliminary phase, architecture vision and requirements management

successful EnterIn this step you the stakeholders of your initiative.

Business architecture, information systems architecture and technology architecture

Opportunities and solutions, migration planning and implementation governance

Architecture change management

Migration Planning Opportunities and Solutions

Technology Architecture

The phase is imperative to prise Architecture Management. have to determine the scope, and the architecture principles

The development of your architecture takes place in three architecture domains: business architecture, information systems architecture and technology architecture. Firstly, you need to describe the current state architecture, also known as the baseline architecture, and the future state architecture, also known as the target 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 baseline and target architectures. Make sure you understand the impacts on the entire architecture landscape.

If necessary you can adapt the EA framework and tool to fit to the requirements of your organisation. Subsequently, you should establish requirements management which is a key concept for all the following phases. Outline the future state architecture. Make sure to establish the necessary capabilities for successfully implementing the future architecture. Last but not least, define KPIs to be able to measure the achievement of objectives.

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 implementation. Subsequently, work out solutions and alternatives 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 implementation complies with the architecture principles and guidelines.

Introduce architecture change management in order to be able to monitor your enterprise architecture continuously. 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.

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 ADOit. The EA Tool ADOit is TOGAF certified.*

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

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

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

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

das Architekturframework nach Ihren individuellencapability Bedrfnissen. Consider designing a business map. It will help you define the architecture vision and break down the scope into key aspects of your EA initiative.
Es gibt keine Silver-Bullet. Definieren Sie

ADOit Enterprise Architecture Community

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

Define transition architectures by setting life cycles for architecture elements.

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


ADOit make architectures work

Imprint: publisher and manufacturer: BOC Information Technologies Consulting AG, place of publishing and manufactoring: Vienna; Copyright BOC Information Technologies Consulting AG, Vienna. The BOC Management Office as well as ADOscore, ADONIS, ADOlog, ADOit and ADONIS:Community are registered trademarks of the BOC Information Technologies Consulting AG. All of the content is protected. All other named brands are property of the respective companies. All changes can only be made with a written letter of agreement from the BOC Information Technologies Consulting AG. Reproductions in any form are only allowed with the Copyright remark. Publications and translations need a written letter of agreement from the BOC Information Technologies Consulting AG. *The Open Group TOGAF 9 Tool Certification Mark is a trademark of The Open Group.