TOGAF標準9.2版口袋書(一)目錄&前言
【聲明】
本文檔從淘寶購得,以作為togaf9.2認證考試自學(xué)之用,如有侵權(quán)請聯(lián)系我處理。
Copyright ? 2009-2018, The Open Group
版權(quán)所有@2009-2018贸伐, The Open Group
All rights reserved. 保留所有權(quán)利
No part of this publication may bereproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying,recording, or otherwise, without the prior permission of the copyright owner.
未經(jīng)版權(quán)擁有者事先許可,本出版物的任何部分都不能以任何形式或任何手段:電子膀值、 機械初厚、 影印 剔蹋、 隸制或其他方式等進行復(fù)制万俗、 存儲于檢索系統(tǒng)宽涌、 或傳送糊肠。
The views expressed in this documentare not necessarily those of any particular member of The Open Group.
本文檔所表述的觀點和The Open Group的任何特定會員的觀點沒有必然的關(guān)系惭笑。
In the event of any discrepancybetween text in this document and the official TOGAF documentation, the TOGAF documentation remains theauthoritative version for certification, testing by examination, and other purposes. The official TOGAFdocumentation can be obtained online at www.opengroup.org/togaf.
在本文中的文字和官方的TOGAF 9文檔存在差異的情況時鼎兽, TOGAF 9文檔繼續(xù)作為認證熊咽、 考試測試和其他用途的權(quán)威版本. 官方的TOGAF 9文檔可以通過以下鏈按在線獲扰椴浴:WWW.opengroup.org/togaf
The TOGAF? Standard, Version 9.2 APocket Guide
Document Number: G185
TOGAF?Standard潦匈,9.2版,袖珍指南
文件編號:G185
Published by The Open Group, April 2018.
The Open Group于2018年4月發(fā)布赚导。
Comments relatingto the material contained in this document may be submitted to:
與本文檔中包含的材料有關(guān)的意見可以提交給:
The Open Group開放小組
Apex Plaza ForburyRoad Reading
Berkshire, RG1 1AXUnited Kingdom
or by electronicmail to:ogspecs@opengroup.org
Copyright?2009-2018TheOpenGroup.AllRights Reserved. Guid一e (2018)
Contents目錄
About the Authors關(guān)于作者??? 7
1???? Chapter 1 Introduction介紹??? 10
to the TOGAF Standard 標準介紹... 10
of the TOGAF Documentation 文檔結(jié)構(gòu)... 11
is Architecture in the Context of the TOGAF Standard? 什么是TOGAF標準中的架構(gòu)茬缩?... 13
kinds of Architecture does the TOGAF Standard deal with? TOGAF標準處理哪種架構(gòu)?... 13
does the TOGAF Standard Contain? TOGAF標準包含什么吼旧?... 14
Architecture Development Method (ADM) 架構(gòu)開發(fā)方法(ADM) 16
Guidelines and Techniques(ADM指引與技術(shù)) 16
Content Framework架構(gòu)內(nèi)容框架... 17
Enterprise Continuum企業(yè)連續(xù)統(tǒng)一體... 17
Architecture Capability Framework架構(gòu)能力框架... 17
2???? Chapter 2 The Architecture Development Method架構(gòu)開發(fā)方法??? 18
is the ADM?什么是ADM.. 18
are the Phases of the ADM? ADM的各個階段是什么... 19
ADM in Detail(ADM詳細介紹) 23
Phase預(yù)備階段... 23
A: Architecture Vision架構(gòu)愿景... 26
B: Business Architecture業(yè)務(wù)架構(gòu)... 29
C: Information Systems Architectures信息系統(tǒng)架構(gòu)... 31
E: Opportunities and Solutions機會與解決方案... 40
F: Migration Planning遷移規(guī)劃... 44
G: Implementation Governance實施治理... 47
H: Architecture Change Management架構(gòu)變更管理... 50
Management需求管理... 53
the Architecture Activity架構(gòu)活動的范圍... 55
3???? Chapter 3 Key Techniques and Deliverables of the ADM Cycle ADM周期的關(guān)鍵技術(shù)和交付物??? 57
Architecture Framework定制的架構(gòu)框架... 60
Model for Enterprise Architecture企業(yè)架構(gòu)的組織模型... 61
Principles架構(gòu)原則... 62
Architecture Principles開發(fā)架構(gòu)的原則... 62
Architecture Principles定義架構(gòu)的原則... 63
of Principles質(zhì)量原則... 65
Architecture Principles應(yīng)用架構(gòu)原則... 66
Principles, Business Goals, and Business Drivers業(yè)務(wù)原則凰锡,業(yè)務(wù)目標,和業(yè)務(wù)驅(qū)動... 67
Repository架構(gòu)庫... 67
Tools & Techniques架構(gòu)工具和技術(shù)... 68
for Architecture Work(架構(gòu)工作請求)... 68
of Architecture Work架構(gòu)工作聲名/說明書... 69
Vision架構(gòu)愿景... 70
Management利益關(guān)系人管理... 71
3.10.1??????????????? Steps in the Stakeholder Management Process利益相關(guān)方管理流程中的步驟... 72
Plan溝通計劃... 75
Transformation Readiness Assessment業(yè)務(wù)轉(zhuǎn)型準備評估... 76
Assessment能力評估... 76
Management風(fēng)險管理... 79
Definition Document架構(gòu)定義文檔... 79
3.15.1??????????????? Business Architecture業(yè)務(wù)架構(gòu)... 81
3.15.2??????????????? Information Systems Architectures信息系統(tǒng)架構(gòu)... 82
3.15.3??????????????? Technology Architecture技術(shù)架構(gòu)... 83
Requirements Specification架構(gòu)需求規(guī)格... 84
3.16.1??????????????? Business Architecture Requirements業(yè)務(wù)架構(gòu)請求... 85
3.16.2??????????????? Information Systems Architectures Requirements信息架構(gòu)請求... 85
3.16.3??????????????? Technology Architecture Requirements技術(shù)架構(gòu)請求... 86
3.16.4??????????????? Interoperability Requirements互操作性請求... 86
Roadmap架構(gòu)路線圖... 86
Scenarios業(yè)務(wù)場景... 88
Analysis差距分析... 89
Viewpoints架構(gòu)視點... 92
Views架構(gòu)視圖... 94
3.21.1??????????????? Developing Views in the ADM在ADM中開發(fā)視圖... 94
Building Blocks架構(gòu)構(gòu)件塊... 95
Building Blocks解決方案構(gòu)建塊... 96
Planning基于能力的計劃... 96
Planning Techniques遷移計劃技術(shù)... 98
3.25.1 Implementation Factor Assessment and Deduction Matrix實現(xiàn)因子評價與演繹矩陣... 98
3.25.2 Consolidated Gaps, Solutions, and Dependencies Matrix合并的差距圈暗,解決方案和依賴性矩陣... 99
3.25.3 Architecture Definition Increments Table架構(gòu)定義增量表... 100
3.25.4 Transition Architecture State Evolution Table過渡架構(gòu)狀態(tài)演變表... 101
3.25.5 Business Value Assessment Technique商業(yè)價值評估技術(shù)... 102
and Migration Plan實施和遷移計劃... 103
Architecture過渡架構(gòu)... 105
Governance Model實施治理模型... 105
Contracts架構(gòu)契約... 106
Request變更請求... 109
Assessment 合規(guī)性評估... 110
Impact Assessment 需求影響評估... 111
4???? Chapter 4 Guidelines for Adapting the ADM調(diào)整ADM的指引??? 112
4.1?????? Introduction介紹... 112
Iteration to the ADM針對ADM應(yīng)用迭代... 114
the ADM across the Architecture Landscape在架構(gòu)景觀中應(yīng)用ADM.. 123
the ADM with Different Architectural Styles采用不同的架構(gòu)風(fēng)格使用ADM.. 125
5???? Chapter 5 Architecture Content Framework架構(gòu)內(nèi)容框架??? 126
Content Framework Overview 架構(gòu)內(nèi)容框架概述... 126
Metamodel 內(nèi)容元模型... 128
and Extensions核心與擴展... 130
Artifacts架構(gòu)制品... 130
Concepts基本概念... 130
Matrices, and Diagrams目錄掂为,矩陣和圖... 134
Deliverables架構(gòu)交付物... 136
Blocks構(gòu)建塊... 136
6???? Chapter 6 The Enterprise Continuum企業(yè)的連續(xù)系列??? 139
of the Enterprise Continuum企業(yè)連續(xù)系列概覽... 139
Enterprise Continuum and Architecture Re-Use企業(yè)連續(xù)性體和架構(gòu)重用... 141
the Enterprise Continuum within the ADM 在ADM中使用企業(yè)連續(xù)系列... 142
Partitioning 架構(gòu)分區(qū)... 142
Repository 架構(gòu)知識庫... 144
7???? Chapter 7 Architecture Capability Framework架構(gòu)能力框架??? 148
an Architecture Capability 創(chuàng)建架構(gòu)能力... 150
Governance架構(gòu)治理... 150
Board架構(gòu)委員會... 151
Compliance架構(gòu)合規(guī)性... 152
Skills Framework架構(gòu)技能框架... 154
Enterprise Repository企業(yè)知識庫... 155
8???? Appendix A Migration Summary附錄A遷移摘要??? 156
A.1?????? 從TOGAF標準的9.1升級到9.2版本有哪些更改... 156
9???? Appendix B TOGAF Reference Models參考模型??? 164
9.1?????? TOGAF Foundation Architecture? TOGAF基礎(chǔ)架構(gòu)... 164
Reference Model (TRM) 技術(shù)參考模型... 164
Information Infrastructure Reference Model (III-RM)集成信息架構(gòu)參考模型... 165
Preface前言
1)?This Document關(guān)于本書
This is the Pocket Guide to the TOGAF? Standard, Version 9.2. It isintended to help architects focus onthe efficient and effective operations of their organization and senior managers understand the basics of theTOGAF standard. It is organized as follows:
本書以TOGAF 9企業(yè)版為基礎(chǔ),旨在幫助架構(gòu)師致力于其組織的高效運營员串,并幫助高級管理人員了解開放群組架構(gòu)框架(The Open Group Architecture Framework勇哗,TOGAF)的基本概念。本書的章節(jié)組織如下:
Chapter 1 provides a high-levelview of the TOGAF standard, Enterprise Architecture, and the contents and keyconcepts of the standard; it also introduces the TOGAF Library, a portfolio ofguidance material supporting the standard
第1章介紹了TOGAF寸齐,企業(yè)架構(gòu)和TOGAF內(nèi)容的高級視圖欲诺,并介紹了TOGAF的一些關(guān)鍵概念抄谐。
Chapter 2provides an introduction to the Architecture Development Method (ADM), themethod that the TOGAF standard provides to develop Enterprise Architectures
第2章介紹了架構(gòu)開發(fā)方法(Architecture Development Method,ADM)瞧栗,ADM是TOGAF提供的用來開發(fā)企業(yè)架構(gòu)的方法斯稳。
Chapter 3provides an overview of key techniques and deliverables of the ADM cycle
第3章總體介紹了與ADM過程相關(guān)的各種關(guān)鍵技術(shù)和交付物。
Chapter 4provides an overview of the guidelines for adapting the ADM
第4章總體介紹了對ADM過程進行調(diào)整的一些指引迹恐。
Chapter 5provides an introduction to the Architecture Content Framework, a structuredmetamodel for architectural artifacts
第5章介紹了架構(gòu)內(nèi)容框架挣惰,即架構(gòu)制品的一個結(jié)構(gòu)化的元模型。
Chapter 6provides an introduction to the Enterprise Continuum, a high-level concept thatcan be used with the ADM to develop an Enterprise Architecture
第6章介紹了企業(yè)連續(xù)系列殴边,即可以和ADM一起使用的憎茂,用 來開發(fā)企業(yè)架構(gòu)的一個高級別概念。
Chapter 7provides an introduction to the Architecture Capability Framework, a set ofresources provided for establishment and operation of an architecture functionwithin an enterprise
第7章介紹了架構(gòu)能力框架锤岸,即為建立和運營企業(yè)中的架構(gòu) 職能所需的一系列資源竖幔。
Appendix Aprovides an overview of the changes between Version 9.1 and Version 9.2 of theTOGAF standard
附錄A總體對比了TOGAF 9.2和TOGAF9.1之間的差異。
The audience for this document is:
文檔的受眾:
Enterprise Architects, BusinessArchitects, IT architects, data architects, systems architects, solutionsarchitects, and senior managers seeking a first introduction to the TOGAFstandard
企業(yè)架構(gòu)師是偷、業(yè)務(wù)架構(gòu)師拳氢、IT架構(gòu)師、數(shù)據(jù)架構(gòu)師蛋铆、系統(tǒng)架構(gòu)師馋评、解決方案架構(gòu)師和希望初步了解TOGAF的高級管理者。
A prior knowledgeof Enterprise Architecture is not required.After reading this document, the reader seeking further informationshould refer tothe TOGAF documentation1?available?online atwww.opengroup.org/architecture/togaf9-doc/arch and also available as a hardcopy book.
本書不需要讀者具備企業(yè)架構(gòu)的預(yù)備知識刺啦。閱讀本書之后留特,希望尋求進一步信息的讀者可以參考TOGAF 9的完整版1,該文檔在www.opengroup.org/architecture/togaf9-doc/arch在線閱讀玛瘸,也支持全書下載蜕青。
About the TOGAF Standard, Version 9.2關(guān)于TOGAF9.2標準
The TOGAF Standard, Version 9.2 is an update to the TOGAF 9.1standard providing improved guidance,correcting errors, improving the document structure, and removing obsolete content. Key enhancements made in this versioninclude updates to the BusinessArchitecture and theContent Metamodel. All of thesechanges make the TOGAF framework easier to useand maintain. It retains the major features and structure of the TOGAF9.1 standard including:
TOGAF標準9.2版是對TOGAF 9.1標準的更新,該標準提供了改進的指導(dǎo)糊渊,糾正了錯誤右核,改進了文檔結(jié)構(gòu),并刪除了過時的內(nèi)容渺绒。此版本中的關(guān)鍵增強包括對業(yè)務(wù)架構(gòu)和內(nèi)容元模型的更新蒙兰。所有這些更改都使TOGAF框架更易于使用和維護。它保留了TOGAF 9.1標準的主要特征和結(jié)構(gòu)芒篷,包括:
Modular Structure: The TOGAF standard has a modular structure. The modular structure supports:
模塊化結(jié)構(gòu):TOGAF標準具有模塊化結(jié)構(gòu)搜变。模塊化結(jié)構(gòu)支持:
Greater usability – definedpurpose for each part; can be used in isolation as a standalone set ofguidelines
更大的可用性——為每個部分定義了目的;可以單獨作為一組獨立的指引使用
Incremental adoption of theTOGAF standard
逐步采用TOGAF標準
Accompanying the standard is aportfolio of guidance material, known as the TOGAF Library, to support thepractical application of the TOGAF approach
該標準還附帶了一套指導(dǎo)材料针炉,稱為TOGAF庫挠他,以支持TOGAF方法的實際應(yīng)用。
1 The TOGAF? Standard, Version9.2 (C182); refer to?www.opengroup.org/library/c182.
Content Framework: The TOGAF standard includes a content framework to drive greater consistency in the outputs thatare created when following the Architecture?Development Method (ADM). The TOGAFcontent framework provides a detailed?model of architectural work products.
內(nèi)容框架:TOGAF標準包括一個內(nèi)容框架篡帕,用于在遵循架構(gòu)開發(fā)方法(ADM)時創(chuàng)建的輸出中提高一致性殖侵。TOGAF內(nèi)容框架提供了一個詳細的架構(gòu)工作產(chǎn)品模型贸呢。
Extended Guidance: The TOGAF standard features an extended set of concepts and guidelines to support the establishment ofan integrated hierarchy of architectures being developed?byteams within larger organizations that operate within an overarchingarchitectural governance model. Inparticular, the following concepts are included:
擴展指南:TOGAF標準的特點是一系列擴展的概念和指引,以支持建立一個集成的架構(gòu)層次結(jié)構(gòu)拢军,該層次結(jié)構(gòu)由較大的組織內(nèi)部的團隊在一個總體架構(gòu)治理模型中運作楞陷。具體而言,包括以下概念:
Partitioning– a number of techniquesand considerations on how to partition the various architectures within anenterprise
分區(qū)——關(guān)于如何劃分企業(yè)中的各種架構(gòu)的一些技術(shù)和注意事項
Architecture Repository – a logical
information model for an Architecture Repository which can be used as an integrated
store for all outputs created by executing the ADM
架構(gòu)存儲庫——架構(gòu)存儲庫的邏輯信息模型茉唉,可用作執(zhí)行ADM所創(chuàng)建的所有輸出的集成存儲
Capability Framework – a structured
definition of the organization, skills, roles, and responsibilities required to
operate an effective Enterprise Architecture Capability; the TOGAF standard
also provides guidance on a process that can be followed to identify and
establish an appropriate Architecture Capability
能力框架——組織固蛾、技能、角色和職責(zé)的結(jié)構(gòu)化定義度陆,以運行有效的企業(yè)架構(gòu)能力艾凯;TOGAF標準還提供了一個過程的指導(dǎo),可以遵循該過程來確定和建立適當(dāng)?shù)募軜?gòu)能力
Architectural Styles: The TOGAF standardis designed to be flexibleand it can be used withvarious architectural styles.Examples are providedboth in the TOGAF standard, in Part III: ADM Guidelines and Techniques, and inthe TOGAF Library. Together these comprise a set of supporting materials that show in detail how the ADM can beapplied to specific situations; forexample:
架構(gòu)風(fēng)格:TOGAF標準的設(shè)計是靈活的懂傀,它可以與各種架構(gòu)風(fēng)格一起使用趾诗。在TOGAF標準的第三部分:ADM指引和技術(shù),并在TOGAF庫中提供了例子蹬蚁。這些材料共同組成一組支持材料恃泪,詳細說明如何將ADM應(yīng)用于特定情況,例如:
The varying uses of iterationthat are possible within the ADM and when eachtechnique should be applied
在ADM中可能出現(xiàn)的迭代的不同使用犀斋,以及何時應(yīng)用每種技術(shù)
The various types ofarchitecture development required within an enterprise and how these relate to one another
企業(yè)中所需的不同類型的架構(gòu)開發(fā)贝乎,以及它們之間的相互關(guān)系
The use of the TOGAF ADM withService-Oriented Architectures (SOAs), Riskand Security, etc.
TOGAF
ADM與面向服務(wù)的架構(gòu)(SOAs),風(fēng)險管理和安全管理等一齊使用闪水。
Additional ADM Detail: The TOGAF Standard, Version 9.2 includes additional detailed information over earlier versionsof the TOGAF standard for supporting the execution of theADM. Particular areas of enhancement are:
附加ADM細節(jié):TOGAF標準9.2版包含了更多的詳細信息糕非,這些詳細信息要優(yōu)于早期版本的TOGAF標準蒙具,以支持執(zhí)行ADM球榆。加強的具體領(lǐng)域是:
The Architecture VisionandBusiness Architecturephases feature extended guidance on development of the Business Architecture; this includesfocus on Business Capabilities,Value Streams, and Organization Maps
架構(gòu)愿景和業(yè)務(wù)架構(gòu)階段具有業(yè)務(wù)架構(gòu)開發(fā)的擴展指導(dǎo),包括業(yè)務(wù)功能禁筏、價值流和組織映射的重點
The Technology Architecture phaserecognizes that emerging technologies are increasinglyleading to technology-driven change
技術(shù)架構(gòu)階段認識到持钉,新興技術(shù)正日益導(dǎo)致技術(shù)驅(qū)動的變革
Conventions Used in this Document本文檔使用約定
The following conventions are used throughout this document in orderto help identify importantinformation and avoid confusion over the intended meaning:
本文件通篇使用了下列公約,以幫助確定重要信息篱昔,避免混淆含義:
Ellipsis (…) 省略號
Indicates a continuation; such as anincomplete list of example items, or a continuationfrom preceding text.
指示延續(xù)每强;例如示例項的不完整列表,或前面文本的延續(xù)州刽。
Bold粗體
Used to highlight specific terms.
用于突出特定術(shù)語空执。
Italics斜體字
Used for emphasis. May also refer toother external documents.
用于強調(diào)。也可指其他外部文件穗椅。
About The Open Group有關(guān)The Open Group
?
The Open Group is a global consortium that enables the achievement of business objectives through technology standards.Our diverse membership of more than 580 organizations includes customers, systems and solutions suppliers, toolsvendors, integrators, academics, andconsultants across multiple industries.
The Open Group是一個全球性的聯(lián)盟辨绊,通過技術(shù)標準實現(xiàn)業(yè)務(wù)目標。我們在超過580個組織的不同成員匹表,包括客戶门坷、系統(tǒng)和解決方案供應(yīng)商宣鄙、工具供應(yīng)商、集成商默蚌、學(xué)者和跨多個行業(yè)的顧問冻晤。
The Open Group aims to: 開放小組的目的是:
Capture, understand, andaddress current and emerging requirements, establish policies, and share best practices
Facilitate interoperability,develop consensus, and evolve and integrate specifications and open source technologies
Operate the industry’s premier certification service
捕捉、理解和處理當(dāng)前和新出現(xiàn)的需求绸吸,制定政策鼻弧,分享最佳實踐
促進互操作性,形成共識惯裕,發(fā)展和整合規(guī)范和開源技術(shù)
經(jīng)營行業(yè)一流的認證服務(wù)
Further information on The Open Group isavailable at www.opengroup.org.
關(guān)于開放小組的更多信息見www.Open Group.org温数。
The Open Group has over 25 years’ experience in developing andoperating certification programs and has extensiveexperience developing and facilitating industryadoption of test suites used to validate conformanceto an open standard or specification.
開放集團在開發(fā)和運營認證項目方面擁有超過25年的經(jīng)驗,并且在開發(fā)和促進行業(yè)采用用于驗證是否符合開放標準或規(guī)范的測試套件方面擁有豐富的經(jīng)驗蜻势。
The Open Group publishes a wide range of technicaldocumentation, most of which is focusedon development of Open Group Standards and Guides, but which also includes white papers,technical studies, certification and testing documentation, and business titles.
開放小組出版廣泛的技術(shù)文件撑刺,其中大部分集中在開發(fā)開放小組標準和指南,但也包括白皮書握玛,技術(shù)研究够傍,認證和測試文件,以及商業(yè)標題挠铲。
A catalog is available at www.opengroup.org/library.
目錄可在www.opengroup.org/library查閱冕屯。
ArchiMate?, DirecNet?, Making StandardsWork?, OpenPegasus?, Platform 3.0?, The OpenGroup?,
TOGAF?,
UNIX?, UNIXWARE?, X/Open?, and the Open Brand
X? logo are registered trademarks and Boundaryless Information Flow?, Buildwith Integrity Buy withConfidence?, Dependability Through Assuredness?, EMMM?, FACE?, the FACE? logo, IT4IT?, the IT4IT? logo, O-DEF?, O-PAS?,Open FAIR?, Open Platform 3.0?,Open Process Automation?, Open Trusted Technology Provider?, SOSA?, theOpen O? logo, and The Open GroupCertification logo (Open O and check?) are trademarks of The Open Group.
The Open Group認證logo是The Open
Group的商標。
All other brand, company, and product namesare used for identification purposes only andmay be trademarks that are the sole property of their respective owners.
所有其他品牌拂苹、公司和產(chǎn)品名稱僅用于標識目的安聘,可能是其各自所有者獨有的商標。
Andrew Josey, The Open Group
Andrew Josey is VP Standards andCertification, overseeing all certification and testing programs of The Open Group. He also manages the standards process for The Open Group. AtThe Open Group, he has led many standards development projects including specification and certification development for the ArchiMate?, IT4IT?, TOGAF?, Open FAIR?, POSIX?, and UNIX? programs. He is a member of the IEEE, USENIX, FLOSSUK,and the Association ofEnterprise Architects (AEA). He holds an MSc in ComputerScience from UniversityCollege London.
Professor Rachel Harrison,Oxford Brookes University
Rachel Harrison is a Professorof Computer Sciencein the Department of Computingand Communication Technologies at Oxford Brookes University. Previouslyshe was Professor of ComputerScience, Head of the Department of Computer Science, and Director of Research for the School of Systems Engineering atthe University of Reading. Her research interests include systems evolution, software metrics, requirementsengineering, software architecture, usabilityand software testing. She has published over 100 refereedpapers and consultedwidely with industry, workingwith organizations such as IBM, the DERA, Philips ResearchLabs, Praxis CriticalSystems, and The Open Group. She is Editor-in-Chief of the Software Quality Journal, published by Springer. She is the author of the studyguides for the TOGAF 9 certificationprogram.
Paul Homan, IBM?
Paul Homan is the Chief Technology Officer for Industrial sector clients within IBM’s Global Business Services. He is aCertified Master IT Architect, specializing in Enterprise Architecture with over 20 years’experience in IT. Highly passionate and practically experienced in architecture, strategy, design authority, and governance areas,Paul is particularly interested in Enterprise Architecture leadership,Requirements Management, and Business Architecture. He joined IBM from end-user environments, having worked as ChiefArchitect in both the UK Post Office and Royal Mail. He has not only established Enterprise Architecture practices, but hasalso lived with the results!Since joining IBM, Paul has dedicated his time to both advising clients on ArchitectureCapability as well as actively leading architecture efforts on large client programs. Paul has also been a leader in building IBM’s capability aroundEnterprise Architecture and the TOGAFframework.
Matthew F. Rouse, DXC Technology
?
Matthew Rouse is an Enterprise Architect and DeputyAccount Chief Technologist at DXC Technology.Matthew has over 20 years’ IS/IT experience in applications development, system architecture, IS/IT strategy, and Enterprise Architecture. He brings expertise in strategic IS/IT planning and architecture to ensurethat enterprises align their IS/IT investments with their business objectives. Matthewis a Chartered IT Professional member of the British Computer Society, a Master Certified ITArchitect, and a member of the IEEE ComputerSociety.
Tom van Sante, KPN Consulting Nederland
?
Tom van Sante is a Principal Consultant for KPN ConsultingNederland. He started his career inIT over 30 years ago after studying architecture at the Technical University inDelft. Working in a variety of functions,from operations to management, he has alwaysoperated on the bordersbetween business and IT. He was involved in the introduction and development of ITIL/ASL/BiSL in the Netherlands. He hasworked in numerous appointments for Governmentand Industry advising on the use of IT in modern society.
Mike Turner, EY
Mike Turner led Capgemini’s development effort on TOGAF Version 9and also worked in the core team thatdeveloped the SAP Enterprise Architecture Framework (a joint initiative between Capgemini and SAP). He is currentlyworking as Director, Strategy and Architecture?Advisory at EY.
Paul van der Merwe, WesBank?
Paul van der Merwe is Head of Group Enterprise Architecture, ITGovernance, and IT Strategy atWesBank. A conceptual thinker, he has driven a number of advances in the fieldsin which he has specialized, amongthem software development, business intelligence, ICT management, and Enterprise Architecture. Thefundamental approach to Enterprise Architecture advocated by him is repository-based EnterpriseArchitecture that should be established within organizations as an ongoing practice that enables businessand technology capabilities.
Acknowledgements致謝
The Open Group gratefullyacknowledges the following:
Past and present members of TheOpen Group Architecture Forum for developingthe TOGAF standard
Capgemini and SAP forcontributed materials
The following reviewers of thisand previous editions of this document:
Martyn Bowis
Corinne Brouch
Steve Else
Bill Estrem
Henry Franken
Dave Hornford
Judith Jones
Henk Jonkers
J. Bryan Lail
Mike Lambert
Kiichiro Onishi
Roger Reading
Saverio Rinaldi
John Rogers
Robert Weisman
Nicholas Yakoubovsky
【聲明】
本文檔從淘寶購得瓢棒,以作為togaf9.2認證考試自學(xué)之用浴韭,如有侵權(quán)請聯(lián)系我處理。
wx:Bobbywangzh