---

Скачать книгу

---

can be applied alongside the TOGAF ADM for project planning, monitoring, and control.TOGAF Series Guide:Business CapabilitiesThis document describes what a business capability is, and how business capabilities can be used to enhance business analysis and planning.TOGAF Series Guide:Business ModelsThis document provides a basis for Enterprise Architects to understand and utilize business models, which describe the rationale of how an organization creates, delivers, and captures value.TOGAF Series Guide:Business ScenariosThis document describes the business scenarios method, which is a technique to validate, elaborate, and/or change the premise behind an architecture effort by understanding and documenting the key elements of a business scenario in successive iterations.TOGAF Series Guide:Information MappingThis document addresses how to provide the architect with a means to articulate, characterize, and visually represent the information that is critical to the business.TOGAF Series Guide:The TOGAF Integrated Information Infrastructure Reference Model (III-RM):An Architected Approach to Boundaryless Information Flow™This document addresses the TOGAF Integrated Information Infrastructure Reference Model (III-RM) in terms of its concepts, an overview, and its detailed taxonomy.TOGAF Series Guide:The TOGAF Leader’s Guide to Establishing and Evolving an EA CapabilityThis document puts forward advice on establishing an Enterprise Architecture Capability that aligns to a set of requirements and expectations specific to each enterprise.TOGAF Series Guide:The TOGAF Technical Reference Model (TRM)This document describes the TOGAF Technical Reference Model (TRM), including the core taxonomy, graphical representation, and the detailed platform taxonomy.TOGAF Series Guide:Using the TOGAF Framework to Define and Govern Service-Oriented ArchitecturesThis document provides guidance on how the architect can use the TOGAF standard to develop, manage, and govern Service-Oriented Architectures (SOA).TOGAF Series Guide:Value StreamsThis document addresses how to identify, define, model, and map a value stream to other key components of an enterprise’s Business Architecture.

      2.5 An Introduction to the TOGAF ADM

      The TOGAF Architecture Development Method (ADM) forms the core of the TOGAF standard and is a method for deriving organization-specific Enterprise Architecture. It is the result of contributions from many architecture practitioners.

      The ADM provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures. All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities.

      The ADM is described as a number of phases within a process of change illustrated by an ADM cycle graphic (see Figure 2).

Figure 2: The TOGAF ADM

      The Preliminary Phase describes the preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF framework, and the definition of Architecture Principles.

      Phase A: Architecture Vision describes the initial phase of an Architecture Development Cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.

      Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision.

      Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.

      Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project.

      Phase E: Opportunities and Solutions describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture defined in the previous phases.

      Phase F: Migration Planning describes the development of a detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.

      Phase G: Implementation Governance describes architectural oversight of the implementation.

      Phase H: Architecture Change Management describes procedures for managing change to the new architecture.

      Requirements Management describes the process of managing architecture requirements throughout the ADM.

      2.6 Using the TOGAF Framework with Other Frameworks

      Two of the key elements of any Enterprise Architecture framework are a definition of the deliverables that the architecting activity should produce, together with a description of the method for production.

      Many Enterprise Architecture frameworks focus on the first of these – the specific set of deliverables – and are relatively silent about the methods to be used to generate them.

      Because the TOGAF standard is a generic framework and intended to be used in a wide variety of environments, it provides a flexible and extensible content framework that underpins a set of generic architecture deliverables. As a result, the TOGAF framework may be used either in its own right, with the generic deliverables that it describes; or these deliverables may be replaced or extended by a more specific set, defined in any other framework that the architect considers relevant.

      In all cases, it is expected that the architect will adapt and build on the TOGAF framework in order to define a tailored method that is integrated into the processes and organization structures of the enterprise. This architecture tailoring may include adopting elements from other architecture frameworks, or integrating TOGAF methods with other standard frameworks, such as ITIL®, CMMI®, COBIT®, PRINCE2®, PMBOK®, and MSP®. It may also include adopting elements from reference materials in the TOGAF Library, such as the IT4IT™ Reference Architecture.

      As a generic framework and method for Enterprise Architecture, the TOGAF standard also complements other frameworks that are aimed at specific vertical business domains, specific horizontal technology areas (such as security or manageability), or specific application areas (such as e-commerce).

      2.7 Summary

      This chapter has introduced the basic concepts of Enterprise Architecture and the TOGAF standard.

      The TOGAF standard is an architecture framework. It enables you to design, evaluate, and build the right architecture for your organization. An architecture framework can be considered a “toolkit” that can be used for developing a broad range of different architectures. The value of a framework is that it provides a practical starting point for an architecture project. The TOGAF framework is designed to be adapted and used with other frameworks, when appropriate.

      The TOGAF Library is a reference library containing guidelines, templates, patterns, and other forms of reference material to accelerate the creation of new architectures for the enterprise.

      2.8 Test Yourself Questions

      There are no questions for this chapter as this topic is not examinable.

      2.9 Recommended Reading

      The

---

Скачать книгу