TOGAF® Version 9 - A Pocket Guide
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions
Content
2 - Trademarks [Seite 15]
3 - About the Authors [Seite 16]
4 - Acknowledgements [Seite 19]
5 - Chapter 1 Introduction to TOGAF® [Seite 20]
5.1 - 1.1 Introduction to TOGAF 9 [Seite 20]
5.2 - 1.2 Structure of the TOGAF Document [Seite 21]
5.3 - 1.3 What is Architecture in the Context of TOGAF? [Seite 22]
5.4 - 1.4 What kinds of Architecture does TOGAF deal with? [Seite 22]
5.5 - 1.5 What does TOGAF Contain? [Seite 23]
5.5.1 - 1.5.1 The Architecture Development Method (ADM) [Seite 24]
5.5.2 - 1.5.2 ADM Guidelines and Techniques [Seite 24]
5.5.3 - 1.5.3 Architecture Content Framework [Seite 25]
5.5.4 - 1.5.4 The Enterprise Continuum [Seite 25]
5.5.5 - 1.5.5 TOGAF Reference Models [Seite 25]
5.5.6 - 1.5.6 The Architecture Capability Framework [Seite 26]
6 - Chapter 2 The Architecture Development Method [Seite 28]
6.1 - 2.1 What is the ADM? [Seite 28]
6.2 - 2.2 What are the Phases of the ADM? [Seite 29]
6.3 - 2.3 The ADM in Detail [Seite 31]
6.3.1 - 2.3.1 Preliminary Phase [Seite 32]
6.3.2 - 2.3.2 Phase A: Architecture Vision [Seite 33]
6.3.3 - 2.3.3 Phase B: Business Architecture [Seite 34]
6.3.4 - 2.3.4 Phase C: Information Systems Architectures [Seite 35]
6.3.5 - 2.3.5 Phase D: Technology Architecture [Seite 38]
6.3.6 - 2.3.6 Phase E: Opportunities and Solutions [Seite 39]
6.3.7 - 2.3.7 Phase F: Migration Planning [Seite 41]
6.3.8 - 2.3.8 Phase G: Implementation Governance [Seite 42]
6.3.9 - 2.3.9 Phase H: Architecture Change Management [Seite 43]
6.3.10 - 2.3.10 Requirements Management [Seite 45]
6.4 - 2.4 Scoping the Architecture Activity [Seite 46]
7 - Chapter 3 Key Techniques and Deliverables of the ADM Cycle [Seite 48]
7.1 - 3.1 Tailored Architecture Framework [Seite 50]
7.2 - 3.2 Organizational Model for Enterprise Architecture [Seite 51]
7.3 - 3.3 Architecture Principles [Seite 52]
7.3.1 - 3.3.1 Developing Architecture Principles [Seite 52]
7.3.2 - 3.3.2 Defining Architecture Principles [Seite 53]
7.3.3 - 3.3.3 Qualities of Principles [Seite 55]
7.3.4 - 3.3.4 Applying Architecture Principles [Seite 55]
7.4 - 3.4 Business Principles, Business Goals, and Business Drivers [Seite 57]
7.5 - 3.5 Architecture Repository [Seite 57]
7.6 - 3.6 Architecture Tools [Seite 58]
7.7 - 3.7 Request for Architecture Work [Seite 58]
7.8 - 3.8 Statement of Architecture Work [Seite 59]
7.9 - 3.9 Architecture Vision [Seite 59]
7.10 - 3.10 Stakeholder Management [Seite 60]
7.10.1 - 3.10.1 Steps in the Stakeholder Management Process [Seite 61]
7.11 - 3.11 Communications Plan [Seite 63]
7.12 - 3.12 Business Transformation Readiness Assessment [Seite 64]
7.13 - 3.13 Capability Assessment [Seite 65]
7.14 - 3.14 Risk Management [Seite 66]
7.15 - 3.15 Architecture Definition Document [Seite 67]
7.15.1 - 3.15.1 Business Architecture [Seite 68]
7.15.2 - 3.15.2 Information Systems Architectures [Seite 69]
7.15.3 - 3.15.3 Technology Architecture [Seite 70]
7.16 - 3.16 Architecture Requirements Specification [Seite 70]
7.16.1 - 3.16.1 Business Architecture Requirements [Seite 71]
7.16.2 - 3.16.2 Information Systems Architectures Requirements [Seite 72]
7.16.3 - 3.16.3 Technology Architecture Requirements [Seite 72]
7.16.4 - 3.16.4 Interoperability Requirements [Seite 72]
7.17 - 3.17 Architecture Roadmap [Seite 72]
7.18 - 3.18 Business Scenarios [Seite 73]
7.19 - 3.19 Gap Analysis [Seite 74]
7.20 - 3.20 Architecture Viewpoints [Seite 76]
7.21 - 3.21 Architecture Views [Seite 79]
7.21.1 - 3.21.1 Developing Views in the ADM [Seite 79]
7.22 - 3.22 Architecture Building Blocks [Seite 79]
7.23 - 3.23 Solution Building Blocks [Seite 80]
7.24 - 3.24 Capability-Based Planning [Seite 81]
7.25 - 3.25 Migration Planning Techniques [Seite 82]
7.25.1 - 3.25.1 Implementation Factor Assessment and Deduction Matrix [Seite 82]
7.25.2 - 3.25.2 Consolidated Gaps, Solutions, and Dependencies Matrix [Seite 83]
7.25.3 - 3.25.3 Architecture Definition Increments Table [Seite 83]
7.25.4 - 3.25.4 Enterprise Architecture State Evolution Table [Seite 84]
7.25.5 - 3.25.5 Business Value Assessment Technique [Seite 85]
7.26 - 3.26 Implementation and Migration Plan [Seite 86]
7.27 - 3.27 Transition Architecture [Seite 87]
7.28 - 3.28 Implementation Governance Model [Seite 88]
7.29 - 3.29 Architecture Contracts [Seite 89]
7.30 - 3.30 Change Request [Seite 91]
7.31 - 3.31 Compliance Assessment [Seite 92]
7.32 - 3.32 Requirements Impact Assessment [Seite 92]
8 - Chapter 4 Guidelines for Adapting the ADM [Seite 94]
8.1 - 4.1 Introduction [Seite 94]
8.2 - 4.2 Applying Iteration to the ADM [Seite 96]
8.3 - 4.3 Applying the ADM at Different Enterprise Levels [Seite 101]
8.4 - 4.4 Security Architecture and the ADM [Seite 103]
8.5 - 4.5 Using TOGAF to Define and Govern SOAs [Seite 105]
8.5.1 - 4.5.1 Further Reading [Seite 107]
9 - Chapter 5 Architecture Content Framework [Seite 110]
9.1 - 5.1 Architecture Content Framework Overview [Seite 110]
9.2 - 5.2 Content Metamodel [Seite 111]
9.2.1 - 5.2.1 Core and Extensions [Seite 113]
9.2.2 - 5.2.2 Catalogs, Matrices, and Diagrams [Seite 113]
9.3 - 5.3 Architectural Artifacts [Seite 115]
9.4 - 5.4 Architecture Deliverables [Seite 119]
9.5 - 5.5 Building Blocks [Seite 119]
10 - Chapter 6 The Enterprise Continuum [Seite 122]
10.1 - 6.1 Overview of the Enterprise Continuum [Seite 122]
10.1.1 - 6.1.1 The Enterprise Continuum and Architecture Re-Use [Seite 123]
10.1.2 - 6.1.2 Using the Enterprise Continuum within the ADM [Seite 124]
10.2 - 6.2 Architecture Partitioning [Seite 124]
10.3 - 6.3 Architecture Repository [Seite 126]
11 - Chapter 7 TOGAF Reference Models [Seite 128]
11.1 - 7.1 TOGAF Foundation Architecture [Seite 128]
11.1.1 - 7.1.1 Technical Reference Model (TRM) [Seite 128]
11.2 - 7.2 Integrated Information Infrastructure Reference Model (III-RM) [Seite 128]
12 - Chapter 8 Architecture Capability Framework [Seite 130]
12.1 - 8.1 Establishing an Architecture Capability [Seite 132]
12.2 - 8.2 Architecture Governance [Seite 132]
12.3 - 8.3 Architecture Board [Seite 133]
12.4 - 8.4 Architecture Compliance [Seite 134]
12.5 - 8.5 Architecture Skills Framework [Seite 134]
13 - Appendix A Migration Summary [Seite 138]
13.1 - A.1 Introduction [Seite 138]
Chapter 2
The Architecture Development Method
This chapter describes the Architecture Development Method (ADM), its relationship to the rest of TOGAF, and high-level considerations for its use. It also includes a summary of each phase within the ADM.
Topics addressed in this chapter include:
An introduction to the ADM
The phases of the ADM
The objectives, steps, inputs, and outputs to the ADM phases
Requirements Management during the ADM cycle
Scoping the architecture activity
2.1 What is the ADM?
The ADM, a result of contributions from many architects, forms the core of TOGAF. It is a method for deriving organization-specific enterprise architectures and is specifically designed to address business requirements. The ADM describes:
A reliable, proven way of developing and using an enterprise architecture
A method of developing architectures on different levels4 (business, application, data, technology) that enable the architect to ensure that a complex set of requirements are adequately addressed
Guidelines on tools for architecture development
2.2 What are the Phases of the ADM?
The ADM consists of a number of phases that cycle through a range of architecture domains that enable the architect to ensure that a complex set of requirements is adequately addressed. The basic structure of the ADM is shown in Figure 2.
Figure 2: The Architecture Development Method Cycle
The ADM is applied iteratively throughout the entire process, between phases, and within them. Throughout the ADM cycle, there should be frequent validation of results against the original requirements, both those for the whole ADM cycle, and those for the particular phase of the process. Such validation should reconsider scope, detail, schedules, and milestones. Each phase should consider assets produced from previous iterations of the process and external assets from the marketplace, such as other frameworks or models.
The ADM supports the concept of iteration at three levels:
Cycling around the ADM: The ADM is presented in a circular manner indicating that the completion of one phase of architecture work directly feeds into subsequent phases of architecture work.
Iterating between phases: TOGAF describes the concept of iterating across phases (e.g., returning to Business Architecture on completion of Technology Architecture).
Cycling around a single phase: TOGAF supports repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content.
Further information on iteration is given in TOGAF 9, Part III: ADM Guidelines and Techniques (see Chapter 4).
Table 3: Architecture Development Method Activities by Phase
ADM Phase
Activity
Prepare the organization for successful TOGAF architecture projects. Undertake the preparation and initiation activities required to meet the business directive for a new enterprise architecture, including the definition of an organization-specific architecture framework and tools, and the definition of principles.
Every stage of a TOGAF project is based on and validates business requirements.
Requirements are identified, stored, and fed into and out of the relevant ADM phases, which dispose of, address, and prioritize requirements.
Set the scope, constraints, and expectations for a TOGAF project. Create the Architecture Vision. Define stakeholders. Validate the business context and create the Statement of Architecture Work. Obtain approvals.
Develop architectures at three levels:
Business
Information Systems
Technology
In each case, develop the Baseline and Target Architectureand analyze gaps.
Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases. Identify major implementation projects, and group them into Transition Architectures.
Analyze cost benefits and risk. Develop detailed Implementation and Migration Plan.
Provide architectural oversight for the implementation. Prepare and issue Architecture Contracts (Implementation Governance Board). Ensure that the implementation project conforms to the architecture.
Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise and maximizes the value of the architecture to the business.
2.3 The ADM in Detail
The following tables summarize the objectives, steps, and the inputs and outputs5 of each phase of the ADM cycle.
2.3.1 Preliminary Phase
The Preliminary phase prepares an organization to undertake successful enterprise architecture projects.
An overview of the phase is given below:
Objectives
Steps
To review the organizational context forconducting enterprise architecture
To identify the stakeholders, their requirements, and priorities
To confirm the commitment of the stakeholders
To identify and scope the elements of the enterprise organizations affected and define the constraints and assumptions; this is particularly important for large organizations where there may be a federated architecture environment
To define an organization's "architecture footprint"; that is, the people responsible for performing the architecture work, where they are located, and their responsibilities
To define the framework and detailed methodologies that are going to be used to develop the enterprise architecture in the organization; this is typically an adaptation of the ADM
To set up a governance and support framework to provide business process and architecture governance through the ADM cycle; these will confirm the fitness-for-purpose and ongoing effectiveness of the Target Architecture; normally this includes an initial pilot project
To select and implement supporting tools and other infrastructure to support the architecture activity
To define the constraining architecture principles
Scope the enterprise organizations impacted
Confirm governance and support frameworks
Define and establish enterprise architecture team and organization
Identify and establish architecture principles
Select and tailor architecture framework(s)
Implement architecture tools
Inputs
Outputs
TOGAF
Other architecture framework(s)
Business principles, business goals, and business drivers
Architecture governance strategy
IT strategy
Existing organizational model for enterprise architecture
Existing architecture framework, if any
Existing architecture principles, if any
Existing Architecture Repository, if any
Organizational model forenterprise architecture
Tailored Architecture Framework, including architecture principles
Initial Architecture Repository
Restatement of, or reference to, business principles, businessgoals, and business drivers
Request for Architecture Work
Governance Framework
2.3.2 Phase A: Architecture Vision
Phase A is about project establishment and initiates an iteration of the architecture development cycle, setting the scope, constraints, and expectations for the iteration. It is required in order to validate the business context and to create the approved Statement of Architecture Work.
Objectives
Steps
Obtain management commitment for thisparticular cycle of the ADM
Define and organize an architecture development cycle
Validate business principles, goals, drivers, and key performance indicators (KPIs)
Define, scope, and prioritize architecture tasks Identify stakeholders, their concerns, and objectives
Define business requirements and constraints
Articulate an Architecture Vision and valueproposition to respond to the requirements and constraints
Create a comprehensive plan in line with theproject management frameworks adopted bythe enterprise
Obtain formal approval to proceed
Understand the impact on, and of, otherparallel architecture development cycles
Establish the architecture project
Identify stakeholders, concerns, and business requirements
Confirm and elaborate business goals, business drivers, and constraints
Evaluate business capabilities
Assess readiness for business transformation
Define scope
Confirm and...
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.
File format: PDF
Copy-Protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our eBook Help page.