TOGAF标准9.2版口袋书(一)目录&前言
【声明】
本文档从淘宝购得,以作为togaf9.2认证考试自学之用,如有侵权请联系我处理。
来源:https://item.taobao.com/item.htm?spm=a230r.1.14.22.47b2145fq4djLU&id=646029334526&ns=1&abbucket=19#detail
Copyright © 2009-2018, The Open Group
版权所有@2009-2018, The Open Group
All rights reserved. 保留所有权利
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.
未经版权拥有者事先许可,本出版物的任何部分都不能以任何形式或任何手段:电子、 机械、 影印 、 隶制或其他方式等进行复制、 存储于检索系统、 或传送。
The views expressed in this documentare not necessarily those of any particular member of The Open Group.
本文档所表述的观点和The Open Group的任何特定会员的观点没有必然的关系。
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文档继续作为认证、 考试测试和其他用途的权威版本. 官方的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月发布。
Comments relatingto the material contained in this document may be submitted to:
与本文档中包含的材料有关的意见可以提交给:
The Open Group开放小组
Apex Plaza ForburyRoad Reading
Berkshire, RG1 1AXUnited Kingdom
or by electronicmail to:[email protected]
Copyright©2009-2018TheOpenGroup.AllRights Reserved. Guid一e (2018)
Contents目录
Preface前言 1
Trademarks商标 6
About the Authors关于作者 7
Acknowledgements致谢 9
1 Chapter 1 Introduction介绍 10
1.1 Introduction
to the TOGAF Standard 标准介绍... 10
1.2 Structure
of the TOGAF Documentation 文档结构... 11
1.3 What
is Architecture in the Context of the TOGAF Standard? 什么是TOGAF标准中的架构?... 13
1.4 What
kinds of Architecture does the TOGAF Standard deal with? TOGAF标准处理哪种架构?... 13
1.5 What
does the TOGAF Standard Contain? TOGAF标准包含什么?... 14
1.5.1 The
Architecture Development Method (ADM) 架构开发方法(ADM) 16
1.5.2 ADM
Guidelines and Techniques(ADM指引与技术) 16
1.5.3 Architecture
Content Framework架构内容框架... 17
1.5.4 The
Enterprise Continuum企业连续统一体... 17
1.5.5 The
Architecture Capability Framework架构能力框架... 17
2 Chapter 2 The Architecture Development Method架构开发方法 18
2.1 What
is the ADM?什么是ADM.. 18
2.2 What
are the Phases of the ADM? ADM的各个阶段是什么... 19
2.3 The
ADM in Detail(ADM详细介绍) 23
2.3.1 Preliminary
Phase预备阶段... 23
2.3.2 Phase
A: Architecture Vision架构愿景... 26
2.3.3 Phase
B: Business Architecture业务架构... 29
2.3.4 Phase
C: Information Systems Architectures信息系统架构... 31
2.3.5 Phase
E: Opportunities and Solutions机会与解决方案... 40
2.3.6 Phase
F: Migration Planning迁移规划... 44
2.3.7 Phase
G: Implementation Governance实施治理... 47
2.3.8 Phase
H: Architecture Change Management架构变更管理... 50
2.3.9 Requirements
Management需求管理... 53
2.4 Scoping
the Architecture Activity架构活动的范围... 55
3 Chapter 3 Key Techniques and Deliverables of the ADM Cycle ADM周期的关键技术和交付物 57
3.1 Tailored
Architecture Framework定制的架构框架... 60
3.2 Organizational
Model for Enterprise Architecture企业架构的组织模型... 61
3.3 Architecture
Principles架构原则... 62
3.3.1 Developing
Architecture Principles开发架构的原则... 62
3.3.2 Defining
Architecture Principles定义架构的原则... 63
3.3.3 Qualities
of Principles质量原则... 65
3.3.4 Applying
Architecture Principles应用架构原则... 66
3.4 Business
Principles, Business Goals, and Business Drivers业务原则,业务目标,和业务驱动... 67
3.5 Architecture
Repository架构库... 67
3.6 Architecture
Tools & Techniques架构工具和技术... 68
3.7 Request
for Architecture Work(架构工作请求)... 68
3.8 Statement
of Architecture Work架构工作声名/说明书... 69
3.9 Architecture
Vision架构愿景... 70
3.10 Stakeholder
Management利益关系人管理... 71
3.10.1 Steps in the Stakeholder Management Process利益相关方管理流程中的步骤... 72
3.11 Communications
Plan沟通计划... 75
3.12 Business
Transformation Readiness Assessment业务转型准备评估... 76
3.13 Capability
Assessment能力评估... 76
3.14 Risk
Management风险管理... 79
3.15 Architecture
Definition Document架构定义文档... 79
3.15.1 Business Architecture业务架构... 81
3.15.2 Information Systems Architectures信息系统架构... 82
3.15.3 Technology Architecture技术架构... 83
3.16 Architecture
Requirements Specification架构需求规格... 84
3.16.1 Business Architecture Requirements业务架构请求... 85
3.16.2 Information Systems Architectures Requirements信息架构请求... 85
3.16.3 Technology Architecture Requirements技术架构请求... 86
3.16.4 Interoperability Requirements互操作性请求... 86
3.17 Architecture
Roadmap架构路线图... 86
3.18 Business
Scenarios业务场景... 88
3.19 Gap
Analysis差距分析... 89
3.20 Architecture
Viewpoints架构视点... 92
3.21 Architecture
Views架构视图... 94
3.21.1 Developing Views in the ADM在ADM中开发视图... 94
3.22 Architecture
Building Blocks架构构件块... 95
3.23 Solution
Building Blocks解决方案构建块... 96
3.24 Capability-Based
Planning基于能力的计划... 96
3.25 Migration
Planning Techniques迁移计划技术... 98
3.25.1 Implementation Factor Assessment and Deduction Matrix实现因子评价与演绎矩阵... 98
3.25.2 Consolidated Gaps, Solutions, and Dependencies Matrix合并的差距,解决方案和依赖性矩阵... 99
3.25.3 Architecture Definition Increments Table架构定义增量表... 100
3.25.4 Transition Architecture State Evolution Table过渡架构状态演变表... 101
3.25.5 Business Value Assessment Technique商业价值评估技术... 102
3.26 Implementation
and Migration Plan实施和迁移计划... 103
3.27 Transition
Architecture过渡架构... 105
3.28 Implementation
Governance Model实施治理模型... 105
3.29 Architecture
Contracts架构契约... 106
3.30 Change
Request变更请求... 109
3.31 Compliance
Assessment 合规性评估... 110
3.32 Requirements
Impact Assessment 需求影响评估... 111
4 Chapter 4 Guidelines for Adapting the ADM调整ADM的指引 112
4.1 Introduction介绍... 112
4.2 Applying
Iteration to the ADM针对ADM应用迭代... 114
4.3 Applying
the ADM across the Architecture Landscape在架构景观中应用ADM.. 123
4.4 Using
the ADM with Different Architectural Styles采用不同的架构风格使用ADM.. 125
5 Chapter 5 Architecture Content Framework架构内容框架 126
5.1 Architecture
Content Framework Overview 架构内容框架概述... 126
5.2 Content
Metamodel 内容元模型... 128
5.2.1 Core
and Extensions核心与扩展... 130
5.3 Architectural
Artifacts架构制品... 130
5.3.1 Basic
Concepts基本概念... 130
5.3.2 Catalogs,
Matrices, and Diagrams目录,矩阵和图... 134
5.4 Architecture
Deliverables架构交付物... 136
5.5 Building
Blocks构建块... 136
6 Chapter 6 The Enterprise Continuum企业的连续系列 139
6.1 Overview
of the Enterprise Continuum企业连续系列概览... 139
6.1.1 The
Enterprise Continuum and Architecture Re-Use企业连续性体和架构重用... 141
6.1.2 Using
the Enterprise Continuum within the ADM 在ADM中使用企业连续系列... 142
6.2 Architecture
Partitioning 架构分区... 142
6.3 Architecture
Repository 架构知识库... 144
7 Chapter 7 Architecture Capability Framework架构能力框架 148
7.1 Establishing
an Architecture Capability 创建架构能力... 150
7.2 Architecture
Governance架构治理... 150
7.3 Architecture
Board架构委员会... 151
7.4 Architecture
Compliance架构合规性... 152
7.5 Architecture
Skills Framework架构技能框架... 154
7.5.1 The
Enterprise Repository企业知识库... 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基础架构... 164
Technical
Reference Model (TRM) 技术参考模型... 164
9.2 Integrated
Information Infrastructure Reference Model (III-RM)集成信息架构参考模型... 165
10 Glossary词汇表 167
【官方资料】 172
Preface前言
1) This Document关于本书
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企业版为基础,旨在帮助架构师致力于其组织的高效运营,并帮助高级管理人员了解开放群组架构框架(The Open Group Architecture Framework,TOGAF)的基本概念。本书的章节组织如下:
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,企业架构和TOGAF内容的高级视图,并介绍了TOGAF的一些关键概念。
Chapter 2provides an introduction to the Architecture Development Method (ADM), themethod that the TOGAF standard provides to develop Enterprise Architectures
第2章介绍了架构开发方法(Architecture Development Method,ADM),ADM是TOGAF提供的用来开发企业架构的方法。
Chapter 3provides an overview of key techniques and deliverables of the ADM cycle
第3章总体介绍了与ADM过程相关的各种关键技术和交付物。
Chapter 4provides an overview of the guidelines for adapting the ADM
第4章总体介绍了对ADM过程进行调整的一些指引。
Chapter 5provides an introduction to the Architecture Content Framework, a structuredmetamodel for architectural artifacts
第5章介绍了架构内容框架,即架构制品的一个结构化的元模型。
Chapter 6provides an introduction to the Enterprise Continuum, a high-level concept thatcan be used with the ADM to develop an Enterprise Architecture
第6章介绍了企业连续系列,即可以和ADM一起使用的,用 来开发企业架构的一个高级别概念。
Chapter 7provides an introduction to the Architecture Capability Framework, a set ofresources provided for establishment and operation of an architecture functionwithin an enterprise
第7章介绍了架构能力框架,即为建立和运营企业中的架构 职能所需的一系列资源。
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
企业架构师、业务架构师、IT架构师、数据架构师、系统架构师、解决方案架构师和希望初步了解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.
本书不需要读者具备企业架构的预备知识。阅读本书之后,希望寻求进一步信息的读者可以参考TOGAF 9的完整版1,该文档在www.opengroup.org/architecture/togaf9-doc/arch在线阅读,也支持全书下载。
About the TOGAF Standard, Version 9.2关于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标准的更新,该标准提供了改进的指导,纠正了错误,改进了文档结构,并删除了过时的内容。此版本中的关键增强包括对业务架构和内容元模型的更新。所有这些更改都使TOGAF框架更易于使用和维护。它保留了TOGAF 9.1标准的主要特征和结构,包括:
Modular Structure: The TOGAF standard has a modular structure. The modular structure supports:
模块化结构:TOGAF标准具有模块化结构。模块化结构支持:
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
该标准还附带了一套指导材料,称为TOGAF库,以支持TOGAF方法的实际应用。
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.
内容框架:TOGAF标准包括一个内容框架,用于在遵循架构开发方法(ADM)时创建的输出中提高一致性。TOGAF内容框架提供了一个详细的架构工作产品模型。
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标准的特点是一系列扩展的概念和指引,以支持建立一个集成的架构层次结构,该层次结构由较大的组织内部的团队在一个总体架构治理模型中运作。具体而言,包括以下概念:
Partitioning– a number of techniquesand considerations on how to partition the various architectures within anenterprise
分区——关于如何划分企业中的各种架构的一些技术和注意事项
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
架构存储库——架构存储库的逻辑信息模型,可用作执行ADM所创建的所有输出的集成存储
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
能力框架——组织、技能、角色和职责的结构化定义,以运行有效的企业架构能力;TOGAF标准还提供了一个过程的指导,可以遵循该过程来确定和建立适当的架构能力
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:
架构风格:TOGAF标准的设计是灵活的,它可以与各种架构风格一起使用。在TOGAF标准的第三部分:ADM指引和技术,并在TOGAF库中提供了例子。这些材料共同组成一组支持材料,详细说明如何将ADM应用于特定情况,例如:
The varying uses of iterationthat are possible within the ADM and when eachtechnique should be applied
在ADM中可能出现的迭代的不同使用,以及何时应用每种技术
The various types ofarchitecture development required within an enterprise and how these relate to one another
企业中所需的不同类型的架构开发,以及它们之间的相互关系
The use of the TOGAF ADM withService-Oriented Architectures (SOAs), Riskand Security, etc.
TOGAF
ADM与面向服务的架构(SOAs),风险管理和安全管理等一齐使用。
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细节:TOGAF标准9.2版包含了更多的详细信息,这些详细信息要优于早期版本的TOGAF标准,以支持执行ADM。加强的具体领域是:
The Architecture VisionandBusiness Architecturephases feature extended guidance on development of the Business Architecture; this includesfocus on Business Capabilities,Value Streams, and Organization Maps
架构愿景和业务架构阶段具有业务架构开发的扩展指导,包括业务功能、价值流和组织映射的重点
The Technology Architecture phaserecognizes that emerging technologies are increasinglyleading to technology-driven change
技术架构阶段认识到,新兴技术正日益导致技术驱动的变革
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.
指示延续;例如示例项的不完整列表,或前面文本的延续。
Bold粗体
Used to highlight specific terms.
用于突出特定术语。
Italics斜体字
Used for emphasis. May also refer toother external documents.
用于强调。也可指其他外部文件。
About The Open Group有关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是一个全球性的联盟,通过技术标准实现业务目标。我们在超过580个组织的不同成员,包括客户、系统和解决方案供应商、工具供应商、集成商、学者和跨多个行业的顾问。
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
捕捉、理解和处理当前和新出现的需求,制定政策,分享最佳实践
促进互操作性,形成共识,发展和整合规范和开源技术
经营行业一流的认证服务
Further information on The Open Group isavailable at www.opengroup.org.
关于开放小组的更多信息见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.
开放集团在开发和运营认证项目方面拥有超过25年的经验,并且在开发和促进行业采用用于验证是否符合开放标准或规范的测试套件方面拥有丰富的经验。
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.
开放小组出版广泛的技术文件,其中大部分集中在开发开放小组标准和指南,但也包括白皮书,技术研究,认证和测试文件,以及商业标题。
A catalog is available at www.opengroup.org/library.
目录可在www.opengroup.org/library查阅。
Trademarks商标
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.
所有其他品牌、公司和产品名称仅用于标识目的,可能是其各自所有者独有的商标。
About the Authors关于作者
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认证考试自学之用,如有侵权请联系我处理。
wx:Bobbywangzh
文档来源:https://item.taobao.com/item.htm?spm=a230r.1.14.22.47b2145fq4djLU&id=646029334526&ns=1&abbucket=19#detail