The TOGAF Architecture Development Method (ADM) provides complete guidance for implementing and executing an organization's enterprise architecture. The process consists of multiple, consecutive phases enclosed in a closed loop
The purpose of the Preliminary Phase is to identify implementation process stakeholders and get them on the same page about the enterprise architecture work. This phase delivers Architecture Guiding Principles that is based on the organization's business principles and describes process and criteria for monitoring the EA implementation's progress.
Phase A of the process is dedicated to articulating the EA vision. The Architecture Vision artifact draws upon the business drivers to clarify the purpose of the enterprise architecture effort and to create first-cut descriptions of the baseline and target environments. If the business objectives are unclear, then part of the work in this phase is to help the business to identify its key objectives and corresponding processes, which the enterprise architecture must support. The Statement of Architectural Work, which is also produced in this phase, delineates the EA's scope and constraints and presents a plan for the architectural work.
Phase B is dedicated to detailed work on the architecture of the business domain. Both baseline and target architectures that were outlined in the Architecture Vision are detailed to make them useful inputs into technical analysis. Business process modeling, business object modeling, and use case modeling are some of the techniques that are used to produce the Business Architecture, which in turn includes gap analysis of the desired state.
Phase C is concerned with delivery of Application and Data (Information) architectures. This phase draws upon on the baseline and the target architectures started in Phase A (Architecture Vision) and results of the business gap analysis (part of the Business Architecture) to deliver Application and Data architectures for both current and envisaged environments, within the scope and according to the plan outlined in the Statement of Architectural Work.
Phase D completes the detailed architecture work of the TOGAF ADM cycle with the delivery of Technology Architecture. As in the preceding phases, gap analysis and draft architectures are used as a baseline, as are the architecture guiding principles agreed upon in the preliminary phase. Modeling notations, such as UML, are actively used during this phase to produce various viewpoints.
The purpose of Phase E is to clarify the opportunities presented by the target architectures and to outline the potential solutions. The work in this phase revolves around feasibility and practicality of the implementation alternatives. Artifacts produced here include Implementation and Migration Strategy, High-level Implementation Plan, and Project List, as well as an updated Application Architecture that acts as a Blueprint to be used by the implementation projects.
Phase F moves to prioritize proposed implementation projects and perform detailed planning and gap analysis of the migration process. This work includes assessing dependencies between projects and minimizing their overall impact on enterprise operations. In this phase, the Project List is updated, the Implementation Plan is detailed, and the Blueprint is handed to the implementation teams.
As the list of projects stabilizes, the focus shifts to formulating more specific objectives and recommendations for each of the implementation projects. During Phase G, connection between the governing architecture (TOGAF) and the development organization (which may be regulated by the combination of RUP and the Project Management Body of Knowledge (PMBOK), for instance, or some other project management methodology) is established and selected projects are implemented under the formal architecture governance. A phased deliverable is Architecture Contracts, which are accepted by the development organization. The ultimate outputs of Phase G are the architecture-compliant solutions.
The focus in Phase H shifts towards change management of the architecture baseline that is achieved with the delivery of the implemented solutions. The phase might produce a Request for Architecture Work that sets targets for a subsequent cycle of enterprise architecture efforts.
via ibm.com
No comments:
Post a Comment