Читать книгу IT Architecture from A to Z: Theoretical basis. First Edition - Vadim Aldzhanov - Страница 14

The processes of creation and development, change management, control of the implementation of architectural solutions in TOGAF are integrated into a single Architecture Development Method (ADM). This method can and should be adapted to the company’s objectives at all levels of architecture development. At the same time, there is no need to develop all possible documents and go too deep into details. ADM offers a ready-made set of techniques, tools, templates, and check sheets for each stage. The Architecture Development Method (ADM) contains ten phases. Each phase is divided into sub-processes (stages), individual works, and so on.

TOGAF Architecture Development Method (ADM)

For example, phase D includes the following main sub-processes:

•Description of the current technological architecture.

° An overview of the business architecture, data architecture and applications for defining the initial data and the required level of detail.

° Description of the current system with the required level of detail, selected to identify the required changes when creating the target architecture, i.e. the registry software and hardware platforms used.

° Identification and description of elementary architectural blocks to be used in the new architecture. In fact, it is a question of available architectural templates.

° Development of a draft technical report summarizing the main results of the study of the current state and the possibility of using typical units.

° Submission of the draft report for review, analysis of comments and introduction of amendments, if required.

• Creation of the target technological architecture.

° Description of the current system using TOGAF terms.

° Defining architecture perspectives (representations).

° Creation of a target architecture model.

° Definition of IT services.

° Confirmation of business requirements.

° Definition of architecture and blocks used (templates).

° Carrying out a gap analysis.

Table: Phases and Objectives of the ADM

The main objectives of the preliminary phase are:

• To create an architectural practice;

• To prepare the company for the launch of architectural projects;

• To enlist the leadership support;

• To create architectural principles;

• To adapt the methodology for the company’s goals and objectives.

The main objectives of phase A (Architecture Vision) are:

• To launch an architectural project, define goals and objectives, framework, scope and constraints of the project, develop a vision of the architecture, define the relevant stakeholders;

• To develop a “project charter” and get a formal confirmation of the project start.

The main objectives of phase B (Business Architecture) are:

• To develop an architecture with a description of the current and target architecture;

• To conduct gap analysis.

The main objectives of phase C (Information Systems Architectures) are:

• To develop an architecture with a description of the current and target architecture;

• To conduct gap analysis.

The main objectives of phase D (Technology Architecture) are:

• To develop an architecture with a description of the current and target architecture;

• To conduct gap analysis.

The main objectives of phase Е (Opportunities and Solutions) are:

• To plan the implementation of project objectives;

• To identify major implementation projects and group them into transition architectures.

The main objectives of phase F (Migration Planning) are:

• To conduct cost and risk analysis;

• To develop a detailed implementation and migration plan.

The main objectives of phase G (Implementation Governance) are:

• To govern the overall project implementation;

• To prepare architectural contracts.

• To ensure conformance with the defined architecture by implementation projects.

The objectives of phase H (Architecture Change Management) are:

• To prepare for the next turn of the Architecture Development Cycle.

• To ensure the compliance of the change management with the actual needs of the business and maximum value to the business.

The main objectives of the Architecture Requirements Management are:

• To collect and agree on business requirements at each phase of the architectural project;

• To identify, store, the requirements, to define the priorities and use then in the relevant phases of the architectural design.

The TOGAF specification also enables flexible work with stages. The specification states the following:

Before applying the architecture design methodologies, one needs to check whether the components are applicable and then link them to the specific circumstances of the individual enterprise. This allows creating a methodology for architecture developing for a particular enterprise.

The TOGAF model enables partial implementation of stages, skipping, merging, reordering, and amending them to meet specific requirements. Not surprisingly, two TOGAF certified consultants working with the same organization can develop two completely different processes.

The TOGAF model is even more flexible for the architecture created. In fact, TOGAF “knows nothing” about architecture. The quality of the final architecture can be good, bad or even undetermined. TOGAF describes how to create an enterprise architecture, but does not describe how to create a good one. The quality of the final product depends on the experience of the company’s staff and the TOGAF consultant. Those who introduce TOGAF hoping to get a miracle cure, will be severely disappointed (like using any single methodology).