Atitit. Research and Development Management---TOGAF architecture (ADM development method) Summary

Atitit. Research and Development Management---TOGAF architecture (ADM development method) Summary

1. TOGAF is an enterprise architecture framework that has emerged over the last 20 years 1

2. TOGAF Content Structure 1

3. TOGAF implementation Process 2

4. Reference 4

1. TOGAF is the Enterprise Architecture Framework that has emerged over the last 20 years

, whose goal is to become the standard for EA development. TOGAF is created by members of the Open Group Consortium, TOGAF is not the first to reflect the overall EA focus. Initially, TOGAF included only the technical architecture (versions 1 to 7), however, the Business Architecture area (version 9,enterprise Edition) was recently added to the framework, which quickly pushed TOGAF to the top spot in today's EA framework selection.

The contents of the TOGAF and their relationship are expressed by the following schematic diagram:

Author:: Old Wow's paw Attilax Ayron, email:1466519819@qq.com

Reprint please indicate source: Http://blog.csdn.net/attilax

2. TOGAF content structure

The contents of TOGAF are divided into three main parts:

· TOGAF Competency Framework (TOGAF Capability Framework): In order to effectively operate the enterprise architecture and maximize its effectiveness in an enterprise, a set of appropriate organizational structures, processes, skills, roles and responsibilities need to be defined and combined. and TOGAF's competency framework is providing guidance on how to organize these elements.

· TOGAF architecture Development methodology and content framework (TOGAF ADM (Architecture development method) & Content Framework): This section is the core of TOGAF, it contains two aspects of the content. The architecture development method is TOGAF to the enterprise architecture construction method, it takes a cyclic iteration model as the foundation to divide the construction process of enterprise architecture into a number of steps, and elaborates the input and output of each step as well as the methods adopted. As part of the new content framework, it A detailed description of the various work products included in the enterprise architecture and the relationship between them is given.

· TOGAF Enterprise Continuum and tools (TOGAF enterprises Continuum and tools): Enterprise Continuum is a view of the Enterprise Architecture repository that provides a way to classify and organize the various architectures and solution artifacts in the enterprise. Enterprise Architecture process is a dynamic process, so the way to organize and classify work products is not only a static method, but also a dynamic method that can change its classification with the evolution of enterprise architecture. In the perspective of this approach, with the evolution of the enterprise architecture, its content from the general trend to special, and its level of detail from a brief to detailed, and with the precipitation of practice, the original special structure or solution products may become a broader range of generic products. In addition, this section provides several reference models to help build the enterprise architecture and other ancillary tools.

3. TOGAF implementation process

The architecture development approach provides complete guidance for implementing and implementing an organization's enterprise architecture. The process consists of multiple, continuous stages in a closed loop.

Figure 1:TOGAF Architecture Development Methodology (Architecture development Method,adm)

The initial goal is to identify the realization process stakeholders and make it

Phase A of the process is used to clarify the EA vision. The architecture Vision (Architecture Vision) artifact leverages the business drivers to define the purpose of the enterprise architecture effort and to create a rough description of the baseline and target environment. If the business goals are unclear, part of the work in this phase is to help the business people identify their key goals and the appropriate processes that must be supported by the enterprise architecture. Also is the schema work description generated in this phase (Statement of architectural works), outlines the scope and constraints of the EA, and represents the plan for the work of the architecture.

Phase B is used to detail the work on the business domain architecture. The baseline and target architectures outlined in the Architectural Vision (Architecture vision) are described here in detail, making them useful inputs for technical analysis. Business process modeling, business goal modeling, and use case modeling are some of the techniques used to generate business architectures, which in turn include gap analysis of the desired state.

Phase C involves the delivery of applications and data (information) architectures. This phase leverages the baseline and phase A (Architecture Vision) to start with the target architecture, as well as the results of the business gap analysis (part of the business architecture), within the scope, and according to the schema work description (Statement of architectural works) To deliver applications and data architectures for current and prospective environments.

Phase D completes the detailed architectural work of the TOGAF ADM loop with the delivery of the technical architecture. As in the previous phase, the gap analysis and the draft framework were used as baselines, due to early agreement on architectural guidelines. Modeling tags, such as UML, are actively used in this phase to generate various viewpoints.

The purpose of phase E is to clarify the opportunities presented by the target architecture and to outline possible solutions. The work in this phase revolves around the feasibility and practicability of implementing the scheme. Artifacts generated here include implementation and migration policies (implementation and migration strategy), high-level implementation plan (High-level implementation plan), and project list , as well as an updated application architecture as the blueprint used to implement the project.

Phase F prioritizes the proposed implementation and performs detailed planning and gap analysis of the migration process. The work involves assessing dependencies between projects and minimizing their overall impact on the operations of the enterprise. In this phase, the project list is updated, the implementation plan is detailed (Implementation plan), and the blueprint is passed to the implementation team.

As the list of projects stabilizes, the focus moves to clearly more specific goals and recommendations for each implementation project. In phase G, the relationship between the governance Architecture (TOGAF) and the development Organization is established (for example, possibly by a combination of RUP and project Management Knowledge (Project Management Body of Knowledge,pmbok), or other project management methods, and implement the selected project under the formal architecture governance. The delivery of the phase is the architecture contract (Architecture contracts) accepted by the development organization. The final output of phase G is a schema-compliant solution.

The focus in phase H shifts to the change management of the architecture baselines achieved by the delivery of the implemented solution. This stage may be born as a successor to the enterprise architecture work to set the target of the schema work request (ask for Architecture works).

4. reference

Enterprise Architecture Research Summary (--TOGAF) Overview and Architecture development Method (ADM)-Push cool. htm

TOGAF Architecture Development Methodology ADM Introduction _it168 technology development. htm