The Togafr Enterprise Architecture Foundation Study Guide Preparation For The Togaf Enterprise Architecture Part 1 Examination Van Haren Publishing Full Chapter PDF Scribd

The Togaf(r) Enterprise Architecture
Foundation Study Guide: Preparation

for the Togaf Enterprise Architecture
Part 1 Examination Van Haren
Publishing
Visit to download the full and correct content document:
https://ebookmass.com/product/the-togafr-enterprise-architecture-foundation-study-gu
ide-preparation-for-the-togaf-enterprise-architecture-part-1-examination-van-haren-pu
blishing/
Personal PDF Edition. Not for redistribution.
Table of Contents
The TOGAF Enterprise Architecture Foundation Study Guide . . . . . . . . . . . . . . . . . . . . . vii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
The Open Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
How to Use this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Conventions Used in this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
About the TOGAF Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
About the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Referenced Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1. Key Learning Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2. The Open Group Certification for People Program . . . . . . . . . . . . . . . . . . . . . . . 1
1.3. The TOGAF Certification Portfolio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4. TOGAF Enterprise Architecture Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4.1. Format of the Examination Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4.2. What ID do I Need to Present to Take the Examination? . . . . . . . . . . . . . . 4
1.4.3. Can I Refer to Materials While I Take the Examination? . . . . . . . . . . . . . . 4
1.4.4. If I Fail, How Soon Can I Retake the Examination? . . . . . . . . . . . . . . . . . . . 4
1.5. Preparing for the Examination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6. Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.7. Test Yourself Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.8. Recommended Reading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1. Key Learning Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. What is an Enterprise? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3. The Purpose of Enterprise Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4. The Key Benefits of Enterprise Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5. What is the TOGAF Standard? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.5.1. Structure of the TOGAF Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6. A Framework for Enterprise Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.7. Architecture Domains in the TOGAF Standard . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.8. Architecture Abstraction in Enterprise Architecture . . . . . . . . . . . . . . . . . . . . 13
2.9. The Enterprise Continuum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.10. Architecture Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.11. TOGAF Content Framework and Enterprise Metamodel . . . . . . . . . . . . . . . . 17
2.12. Architecture Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.13. Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.14. Gap Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.15. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.16. Test Yourself Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.17. Recommended Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1. Key Learning Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4. Test Yourself Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.5. Recommended Reading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4. Introduction to the ADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2. The TOGAF ADM and its Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3. Draft and Approved Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4. Iteration and the ADM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.5. Governing Enterprise Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.6. Scoping an Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.7. Architecture Alternatives and Trade-Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.8. The Preliminary Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.9. Phase A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.10. Phases B, C, and D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.11. Phases E and F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.12. Phases G and H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.13. Requirements Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.14. Information Flow and the TOGAF ADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.15. Agile Software Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.16. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5. ADM Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2. Supporting Guidelines and Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3. Architecture Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.4. Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.5. Gap Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.6. Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.7. Business Transformation Readiness Assessment . . . . . . . . . . . . . . . . . . . . . . . . 62
5.8. The Characteristics of Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6. Applying the ADM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.2. How to Apply the TOGAF Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.3. Iteration within the ADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.4. The Architecture Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.5. Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.6. Purposes of Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.7. The Digital Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7. Architecture Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.2. Introduction to Governance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.3. Architecture Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.4. The Benefits of Architecture Governance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.5. The Role of an Architecture Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.5.1. Responsibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.6. Architecture Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.7. Architecture Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8. Architecture Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.2. Concepts and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.3. Building Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.4. Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.4.1. Architecture Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8.4.2. Architecture Definition Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.4.3. Architecture Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.4.4. Architecture Requirements Specification . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.4.5. Architecture Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.4.6. Architecture Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.4.7. Business Principles, Goals, and Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.4.8. Capability Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.4.9. Change Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.4.10. Communications Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.4.11. Compliance Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.4.12. Implementation and Migration Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.4.13. Implementation Governance Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.4.14. Request for Architecture Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.4.15. Requirements Impact Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.4.16. Statement of Architecture Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Appendix A: Answers to Test Yourself Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Appendix B: Test Yourself Examination Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
B.1. Examination Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Appendix C: Test Yourself Examination Paper Answers . . . . . . . . . . . . . . . . . . . . . . . 137
Appendix D: TOGAF Enterprise Architecture Level 1 Syllabus . . . . . . . . . . . . . . . . . 145
D.1. Learning Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
D.1.1. Unit 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
D.1.2. Unit 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
D.1.3. Unit 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
D.1.4. Unit 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
D.1.5. Unit 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
D.1.6. Unit 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
D.1.7. Unit 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
D.1.8. Unit 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
D.2. Body of Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Preface
[This page is intentionally blank]
vi The Open Group (2023)

The TOGAF Enterprise
Architecture Foundation
Study Guide
The Open Group
The TOGAF® Enterprise Architecture Foundation Study Guide vii

Copyright© 2023, The Open Group
All rights reserved.
No part of this publication may be reproduced, 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 owners.
Study Guide
TOGAF® Enterprise Architecture Foundation
Document Number: B230
Published by The Open Group, March 2023.
Comments relating to the material contained in this document may be submitted to:
The Open Group,

Apex Plaza,
Forbury Road,
Reading,
Berkshire, RG1 1AX,
United Kingdom
or by electronic mail to:
ogspecs@opengroup.org
Built with asciidoctor, version 2.0.18. Backend: pdf Build date: 2023-03-02 17:26:59
UTC
viii The Open Group (2023)

Preface The Open Group
Preface
The Open Group
The Open Group is a global consortium that enables the achievement of business
objectives through technology standards. With more than 900 member organizations,
we have a diverse membership that spans all sectors of the technology community –
customers, systems and solutions suppliers, tool vendors, integrators and consultants,
as well as academics and researchers.
The mission of The Open Group is to drive the creation of Boundaryless Information
Flow™ achieved by:
• Working with customers to capture, understand, and address current and

emerging requirements, establish policies, and share best practices
• Working with suppliers, consortia, and standards bodies to develop consensus

and facilitate interoperability, to evolve and integrate specifications and open
source technologies
• Offering a comprehensive set of services to enhance the operational efficiency of

consortia
• Developing and operating the industry’s premier certification service and

encouraging procurement of certified products
Further information on The Open Group is available at www.opengroup.org.
The Open Group publishes a wide range of technical documentation, most of which is
focused on development of Standards and Guides, but which also includes white
papers, technical studies, certification and testing documentation, and business titles.
Full details and a catalog are available at www.opengroup.org/library.
This Document
This document is the Study Guide for the TOGAF Enterprise Architecture Foundation
th
qualification. This document is aligned with the TOGAF Standard, 10 Edition.
It gives an overview of every learning objective included in the syllabus and in-depth
coverage on preparing and taking the TOGAF Enterprise Architecture Part 1
examination. It is specifically designed to help individuals prepare for the
examination.
The TOGAF® Enterprise Architecture Foundation Study Guide ix

This Document Preface
The audience for this Study Guide is:
• Individuals who need a basic understanding of a proven Enterprise Architecture

methodology
• Professionals who work for or join an organization applying the TOGAF Standard
• Individuals who need to start to learn the TOGAF method

®
• Individuals who want to achieve the TOGAF Enterprise Architecture Practitioner
qualification in a stepwise manner, or other certifications and certification
credentials from The Open Group where this certification is a prerequisite
A prior knowledge of Enterprise Architecture is advantageous but not required.

While reading this Study Guide, the reader should also refer to the TOGAF Standard.
The structure of the document is as follows:
• Chapter 1, Introduction introduces TOGAF certification and the TOGAF Enterprise

Architecture Foundation qualification, including the TOGAF Enterprise
Architecture Part 1 examination
• Chapter 2, Concepts introduces the concepts of Enterprise Architecture and the

TOGAF Standard; this includes the TOGAF Architecture Development Method, the
contents of the TOGAF framework, and the TOGAF Library
• Chapter 3, Terminology defines the key terminology required for the TOGAF
Enterprise Architecture Foundation qualification
• Chapter 4, Introduction to the ADM will help you understand the TOGAF ADM,
including the objectives of the ADM phases, and how to adapt and scope the ADM
for use
• Chapter 5, ADM Techniques introduces the techniques available to support

application of the ADM
• Chapter 6, Applying the ADM introduces the guidance available to support

application of the ADM, including iteration, partitioning, Agile delivery, and
application in a digital enterprise
• Chapter 7, Architecture Governance describes how Architecture Governance

contributes to architecture development
• Chapter 8, Architecture Content describes the key concepts related to the

Architecture Content produced while executing the ADM, building blocks, and
the key deliverables of the ADM phases
x The Open Group (2023)

Preface How to Use this Document
• Appendix A, Answers to Test Yourself Questions provides the answers to the Test
Yourself sections provided at the end of each chapter
• Appendix B, Test Yourself Examination Paper provides an examination to allow

you to assess your knowledge of the TOGAF Enterprise Architecture Foundation
Syllabus and your readiness to take the TOGAF Enterprise Architecture Part 1
Examination
• Appendix C, Test Yourself Examination Paper Answers provides the answers to the
Test Yourself examination
• Appendix D, TOGAF Enterprise Architecture Level 1 Syllabus provides the TOGAF

Enterprise Architecture Foundation Syllabus
How to Use this Document

The chapters in this document are arranged to cover the TOGAF Enterprise
Architecture Foundation syllabus and should be read in order. Where a topic
requires further information from a later part in the syllabus, a cross-reference is
provided.
Within each chapter are “Key Learning Points” and “Summary” sections that help you
to easily identify what you need to know for each topic.
Conventions Used in this Document

The following conventions are used throughout this document in order to help
identify important information and avoid confusion over the intended meaning:
• (Syllabus reference Unit X, Learning Outcome X.Y: Statement)
Used at the start of a text block to identify the TOGAF Enterprise Architecture
Foundation syllabus learning outcome.
• Ellipsis (…)
Indicates a continuation; such as an incomplete list of example items, or a

continuation from preceding text.
• Bold
Used to highlight specific terms.
• Italics
Used for emphasis. May also refer to other external documents.

The TOGAF® Enterprise Architecture Foundation Study Guide xi

Conventions Used in this Document Preface
In addition to typographical conventions, the following conventions are used to

highlight segments of text:
Note
A Note box is used to highlight useful or interesting

information.
Tip
A Tip box is used to provide key information that can save

you time or that may not be entirely obvious.
xii The Open Group (2023)

About the TOGAF Standard
About the TOGAF Standard

The TOGAF Standard, a standard of The Open Group, is a proven Enterprise
Architecture methodology and framework used by the world’s leading organizations
to improve business efficiency. It is the most prominent and reliable Enterprise
Architecture standard, ensuring consistent standards, methods, and communication
among Enterprise Architecture professionals. Those fluent in the TOGAF Standard
enjoy greater industry credibility, job effectiveness, and career opportunities. The
TOGAF Standard helps practitioners avoid being locked into proprietary methods,
utilize resources more efficiently and effectively, and realize a greater return on
investment.
The TOGAF® Enterprise Architecture Foundation Study Guide xiii

About the Author
About the Author

th
This document builds on materials from the TOGAF Standard, 10 Edition published by
The Open Group. The author listed here has prepared this document. See the
Acknowledgements section for more information.
Andrew Josey, The Open Group
Andrew Josey is VP Standards and Certification, overseeing all certification and

testing programs of The Open Group. He also manages the standards process for The
Open Group. Since joining the company in 1996, Andrew has been closely involved
with the standards development, certification, and testing activities of The Open
Group. He has led many projects including specification and certification
® ® ® ®
development for the ArchiMate , TOGAF , POSIX , and UNIX programs. Most
recently he has led the development of the Open Agile Architecture™ Practitioner
th
certification and the certification portfolio for the TOGAF Standard, 10 Edition. He
has led the automation of The Open Group standards development using a GitLab-
based automated build toolchain. He is the lead author of this document, and author
of more than ten guides published by The Open Group.
He is a member of the IEEE, USENIX, and the Association of Enterprise Architects

(AEA). He holds an MSc in Computer Science from University College London.
xiv The Open Group (2023)

Trademarks
Trademarks
ArchiMate, DirecNet, Making Standards Work, Open O logo, Open O and Check
Certification logo, Platform 3.0, The Open Group, TOGAF, UNIX, UNIXWARE, and the
Open Brand X logo are registered trademarks and Boundaryless Information Flow,
Build with Integrity Buy with Confidence, Commercial Aviation Reference
Architecture, Dependability Through Assuredness, Digital Practitioner Body of
Knowledge, DPBoK, EMMM, FACE, the FACE logo, FHIM Profile Builder, the FHIM
logo, FPB, Future Airborne Capability Environment, IT4IT, the IT4IT logo, O-AA, O-
DEF, O-HERA, O-PAS, Open Agile Architecture, Open FAIR, Open Footprint, Open
Process Automation, Open Subsurface Data Universe, Open Trusted Technology
Provider, OSDU, Sensor Integration Simplified, SOSA, and the SOSA logo are
trademarks of The Open Group.
Gartner is a registered trademark of Gartner, Inc.
ITIL is a registered trademark of AXELOS Limited.
POSIX is a trademark of the IEEE.
UML is a registered trademark and Unified Modeling Language is a trademark of

Object Management Group, Inc.
All other brands, company, and product names are used for identification purposes
only and may be trademarks that are the sole property of their respective owners.
The TOGAF® Enterprise Architecture Foundation Study Guide xv

Acknowledgments
Acknowledgments
The Open Group gratefully acknowledges The Open Group Architecture Forum for
developing the standard on which this document is based.
The Open Group gratefully acknowledges the contributions of the authors of the
TOGAF Series Guides on which this Study Guide is based:
• Terence Blevins
• Sonia Gonzalez
• Heidi Hasz
• Dave Hornford
• Nathan Hornford
• Taylor Hornford
• Andy Ruth
• Sriram Sabesan
• Sadie Scotch
• Ken Street
• Samantha Toder
The Open Group gratefully acknowledges the following reviewers who participated in
the review of this document:
• Shammi Bhandaru
• Steve Else
• Chris Frost
• Max Hemingway
• Paul Homan
• Jens Kjærby
• Rolf Knoll
• Rita Neelam
• Simon Parker
• Sundar Ramanathan
• Vidyasagar Uddagiri
xvi The Open Group (2023)

Referenced Documents
The following documents are referenced in this Guide.
(Please note that the links below are good at the time of writing but cannot be
guaranteed for the future.)
® th
[C220] The TOGAF Standard, 10 Edition, a standard of The Open Group (C220),
published by The Open Group, April 2022; refer to:
www.opengroup.org/library/c220
® ®
[G152] TOGAF Series Guide: Integrating Risk and Security within a TOGAF
Enterprise Architecture (G152), published by The Open Group, April 2022;
refer to: www.opengroup.org/library/g152
® ®
[G217] TOGAF Series Guide: Using the TOGAF Standard in the Digital Enterprise
(G217), published by The Open Group, April 2022; refer to:
www.opengroup.org/library/g217
®
[G20F] TOGAF Series Guide: Enabling Enterprise Agility (G20F), published by The
Open Group, April 2022; refer to: www.opengroup.org/library/g20f
® ®
[G184] TOGAF Series Guide: TOGAF Leader’s Guide to Establishing and Evolving an
EA Capability (G184), published by The Open Group, April 2022; refer to:
www.opengroup.org/library/g184
®
[G186] TOGAF Series Guide: A Practitioners' Approach to Developing Enterprise
®
Architecture Following the TOGAF ADM (G186), published by The Open
Group, April 2022; refer to: www.opengroup.org/library/g186
[W076] Why does Enterprise Architecture Matter?, The Open Group White Paper
(W076), published by The Open Group, November 2008; refer to:
www.opengroup.org/library/w076
® th
[W212] An Introduction to the TOGAF Standard, 10 Edition, The Open Group White
Paper (W212), published by The Open Group, April 2022; refer to:
www.opengroup.org/library/w212
[X1603] The Open Group Certification for People: Certification Policy for Examination-
Based Programs (X1603), published by The Open Group, April 2016; refer to:
www.opengroup.org/library/x1603
[X2202] The Open Group Certification for People: Certification Policy for Examination-
Based Programs (Multi-Level) Version 4.0 (X2202), published by The Open
Group, April 2022; refer to: www.opengroup.org/library/x2202
[ISO 42010] ISO/IEC/IEEE 42010:2011, Systems and Software Engineering – Architecture

Description, published by ISO/IEC, December 2011; refer to:
www.iso.org/standard/50508.html
[ISO 31000] ISO 31000:2108, Risk Management – Guidelines, published by ISO, February
2018; refer to: www.iso.org/standard/65694.html
The TOGAF® Enterprise Architecture Foundation Study Guide xvii

[ISO 38500] ISO/IEC 38500:2015, Information Technology – Governance of IT for the

Organization, published by ISO/IEC, February 2015; refer to:
www.iso.org/standard/62816.html
[Naidoo 2002] Corporate Governance, Ranami Naidoo, published by Double Storey, 2002
The following web links are referenced in this Study Guide:
[WEB1] TOGAF Enterprise Architecture Foundation Data Sheet:

certification.opengroup.org/datasheets/togaf_ea_foundation.pdf
[WEB2] The Open Group TOGAF Certification Portfolio website:

www.opengroup.org/certifications/togaf-certification-portfolio
[WEB3] The digital edition of the TOGAF Standard:

www.opengroup.org/togaf/10thedition
[WEB4] The TOGAF Library: www.opengroup.org/library/togaf-library
xviii The Open Group (2023)

Chapter 1. Introduction 1.1. Key Learning Points
Chapter 1. Introduction
This chapter provides an introduction to this document.
1.1. Key Learning Points

This document is a Study Guide for students studying for the TOGAF Enterprise
Architecture Foundation qualification. This edition is aligned to the TOGAF Standard,
th
10 Edition [C220]. It will familiarize you with all the topics that you need to know in
order to pass the TOGAF Enterprise Architecture Part 1 examination.
It gives an overview of every learning objective included in the syllabus and in-depth
coverage on preparing and taking the examination. It is specifically designed to help
individuals prepare for the examination.
(Syllabus Reference: Unit 8, Learning Outcome 8.1: You should be able to explain the
TOGAF Certification Program and distinguish between the levels for certification)
This first chapter will provide you with important information on the TOGAF
Certification Program, the TOGAF Enterprise Architecture Foundation qualification
and the structure of the TOGAF Enterprise Architecture Part 1 examination.
1.2. The Open Group Certification for People Program

Certification is available to individuals who wish to demonstrate they have attained
the required knowledge and understanding of a particular topic. It leads to the award
of a certificate and Open Badge.
This Study Guide covers the TOGAF Enterprise Architecture Foundation qualification.
It can be studied in its own right independent of other learning paths.
Why Become Certified?
Becoming certified demonstrates clearly to employers and

peers your commitment to being an Enterprise Architect.
In particular, it demonstrates that you possess a body of
core knowledge about the TOGAF Standard as an open,
industry standard framework. The Open Group publishes
the definitive directory of certified individuals, and issues
certificates and Open Badges.
The TOGAF® Enterprise Architecture Foundation Study Guide 1

1.3. The TOGAF Certification Portfolio Chapter 1. Introduction
1.3. The TOGAF Certification Portfolio

The TOGAF certification portfolio includes certifications and certification credentials
th
built upon the TOGAF Standard, Version 9.2, and the TOGAF Standard, 10 Edition. It
includes a set of complementary learning paths centered around the TOGAF Standard
and the TOGAF Library. The paths include different amounts of learning, ranging
from short certification credentials (three hours of study or more) to multi-day
certifications.
The TOGAF certification learning paths included in the portfolio are:
• TOGAF 9 Foundation
• TOGAF 9 Certified
• TOGAF Enterprise Architecture Foundation
• TOGAF Enterprise Architecture Practitioner
• TOGAF Business Architecture Foundation
The TOGAF certification credential learning paths included in the portfolio are:
• Integrating Risk and Security in a TOGAF Enterprise Architecture
• TOGAF Framework: Digital Specialist
• TOGAF Framework: Agile Specialist
• TOGAF Enterprise Architecture Leader
• TOGAF Business Architecture Level 1
1.4. TOGAF Enterprise Architecture Foundation

The purpose of certification for TOGAF Enterprise Architecture Foundation is to
provide validation that the individual has gained an acceptable level of knowledge
and understanding of:
• The concepts of Enterprise Architecture and the TOGAF Standard
• The key terminology of the TOGAF Standard
• The Architecture Development Method (ADM) cycle and the objectives of each
phase, and how to adapt and scope the ADM for use
• The techniques available to support the ADM
• Applying the ADM, including iteration, partitioning, and application in a digital

enterprise
2 The Open Group (2023)

Chapter 1. Introduction 1.4. TOGAF Enterprise Architecture Foundation
• How Architecture Governance contributes to architecture development
• Architecture content – the outputs produced while executing the ADM
The learning objectives at this level focus on knowledge and comprehension.
Examination
Certification for TOGAF Enterprise Architecture Foundation is achieved by passing

the TOGAF Enterprise Architecture Part 1 examination. This is a multiple-choice
examination with 40 questions.
Certain topic areas are weighted as more important than others and thus have more
questions in the examination. The topic areas covered by the examination together
with the number of questions per area in the examination are as follows:
1. Concepts (8 questions)
2. Introduction to the ADM (14 questions)
3. Introduction to ADM Techniques (6 questions)
4. Introduction to Applying the ADM (4 questions)
5. Introduction to Architecture Governance (3 questions)
6. Architecture Content (5 questions)
1.4.1. Format of the Examination Questions

The examination questions are multiple-choice. These are very similar in format to
the Test Yourself questions included in each chapter. Note that the exact format for
display is test center-specific and will be made clear on the display monitor when
taking the examination.
Exam Tip
Please read each question carefully before reading the

answer options. Be aware that some questions may seem
to have more than one right answer, but you are to look
for the one that makes the most sense and is the most
correct.

1.5. Preparing for the Examination Chapter 1. Introduction
1.4.2. What ID do I Need to Present to Take the

Examination?
You should consult with the examination provider regarding the forms of picture ID
you are required to present to verify your identity.
1.4.3. Can I Refer to Materials While I Take the

Examination?
No, it is a closed-book examination.
1.4.4. If I Fail, How Soon Can I Retake the Examination?

You should check the current policy on The Open Group website. At the time of
writing, the policy states that individuals who have failed the examination are not
allowed to retake the examination within one (1) month of the sitting.
1.5. Preparing for the Examination

You can prepare for the examination by working through this Study Guide section-by-
section. After completing each section, you should answer the Test Yourself questions,
and read the referenced sections from the TOGAF documentation. Once you have
completed all the sections in this Study Guide, you can then attempt the Test Yourself
examination paper in Appendix B. It is designed to give a thorough test of your
knowledge. If you have completed all the prescribed preparation and can attain a
pass mark for the Test Yourself examination paper as described in Appendix C, then it
is likely you are ready to sit the examination.
1.6. Summary
The Open Group Certification for People: TOGAF Certification Program is a
knowledge-based certification program. It consists of multiple learning paths,
including the TOGAF Enterprise Architecture Foundation qualification.
This Study Guide is preparation for taking the TOGAF Enterprise Architecture Part 1
examination.
Preparing for the examination includes the following steps:
• You should work through this Study Guide step-by-step
• At the end of each chapter, you should complete the Test Yourself questions and
read the documentation listed under Recommended Reading

Chapter 1. Introduction 1.7. Test Yourself Questions
• Once you have completed all the chapters in this Study Guide, you should attempt
the Test Yourself examination paper provided in Appendix B
• If you can attain the target score in Appendix C, then you have completed your
preparation
1.7. Test Yourself Questions

Q1: Which of the following describes the TOGAF Enterprise Architecture Part 1
examination?
A. It is an open-book examination.
B. It has 40 multiple-choice questions.
C. The exam policy requires you to wait 60 days before a retake.
D. It contains at least four (4) questions related to product management.
Q2: Which of the following is the prerequisite for taking this certification?
A. AEA membership
®
B. ITIL Foundation
C. TOGAF 9 Foundation
D. None required
Q3: Which of the following is a learning unit topic included in the TOGAF Enterprise
Architecture Foundation syllabus?
A. Architecture Governance
B. Digital Infrastructure
C. Interoperability Requirements
D. Value Streams
Q4: Which of the following describes the retake policy for the TOGAF Enterprise
Architecture Part 1 examination?
A. You must wait seven (7) days before a retake.
B. You can retake the exam immediately.
C. You must wait one (1) month before a retake.
D. You must wait three (3) weeks before a retake.

1.8. Recommended Reading Chapter 1. Introduction
1.8. Recommended Reading

The following are recommended sources of further information for this chapter:
• TOGAF Enterprise Architecture Foundation Data Sheet [WEB1]
• The Open Group Certification for People: Certification Policy for Examination-
Based Programs [X1603]
• The Open Group Certification for People: TOGAF Conformance Requirements

(Multi-Level), Version 4.0 [X2202]
• The Open Group TOGAF Certification Portfolio website [WEB2]
• The Digital Edition of the TOGAF Standard [WEB3]

Chapter 2. Concepts 2.1. Key Learning Points
Chapter 2. Concepts
This chapter introduces the concepts of Enterprise Architecture and the TOGAF
Standard.
Key Points Explained
This chapter will help you to answer the following questions:
• What is an enterprise?
• What is Enterprise Architecture?
• What is the purpose of Enterprise Architecture?
• What are the business benefits of Enterprise Architecture?
• Why is the TOGAF Standard suitable as a framework for Enterprise Architecture?
• What kinds of architecture does the TOGAF Standard deal with?
• What is architecture abstraction?
• What is the Enterprise Continuum?
• What is the Architecture Repository?
• What are the TOGAF Content Framework and Enterprise Metamodel?
• What is an Architecture Capability?
• What is risk management?
• What is gap analysis?
2.2. What is an Enterprise?

(Syllabus Reference: Unit 1, Learning Outcome 1.1: You should be able to describe what
an enterprise is.)
The TOGAF Standard considers an “enterprise” to be any collection of organizations

that have common goals. The term “Enterprise” in the context of “Enterprise
Architecture” can be applied to either an entire enterprise, encompassing all its
business activities and capabilities, information, and technology that make up the
entire infrastructure and governance of the enterprise, or to one or more specific
areas of interest within the enterprise.

2.2. What is an Enterprise? Chapter 2. Concepts
An enterprise may include partners, suppliers, and customers as well as internal

business units. In all cases, the architecture crosses multiple systems, and multiple
functional groups within the enterprise.
Examples of an enterprise include:
• A whole corporation or a division of a corporation
• A government agency or a single government department
• A chain of geographically distant organizations linked together by common

ownership
• Groups of countries, governments, or governmental organizations (such as

militaries) working together to create common or shareable deliverables or
infrastructures
• Partnerships and alliances of businesses working together, such as a consortium

or supply chain
Many organizations comprise multiple enterprises and may develop and maintain
independent Enterprise Architectures to address each one. These enterprises often
have much in common with each other including processes, functions, information
systems, and there is great potential for wider gain in the use of a common
architecture framework. For example, a common framework can provide a basis for
the development of common building blocks and solutions, and a shareable
Architecture Repository for the integration and re-use of business models, designs,
information, and data.
What is Enterprise Architecture?
There are many definitions of Enterprise Architecture.

Most focus on structure and organization. Two definitions
are as follows:
“The process of translating business vision and strategy

into effective enterprise change by creating,
communicating, and improving the key principles and
models that describe the enterprise’s future state and
®
enable its evolution.” (Source: Gartner )
“A set of abstractions and models that simplify and

communicate complex structures, processes, rules, and
constraints to improve understanding, implementation,
forecasting, and resourcing.” (Source: DoDAF)

Chapter 2. Concepts 2.3. The Purpose of Enterprise Architecture
2.3. The Purpose of Enterprise Architecture

(Syllabus Reference: Unit 1, Learning Outcome 1.2: You should be able to explain the
purpose of Enterprise Architecture.)
An Enterprise Architecture is developed to guide effective change. It provides a

framework for change, linked to both strategic direction and business value and a
sufficient view of the organization to manage complexity, support continuous change,
and manage the risk of unanticipated consequences.
All enterprises are seeking to improve. Regardless of whether they are a public,
private, or social enterprise, there is a need for deliberate, effective change to
improve. Examples of improvement can be shareholder value or agility for a private
enterprise, a mandate-based value proposition or efficiency for a public enterprise,
or simply an improvement of mission for a social enterprise.
Guidance on effective change will take place during the activity to realize the
approved Enterprise Architecture. During implementation, Enterprise Architecture is
used by the stakeholders to govern change. The first part of governance is to direct
change activity – align the change with the optimal path to realizing the expected
value. The second part of governance is to control the change activity – ensuring the
change stays on the optimal path.
Enterprise Architecture enables achievement of the right balance between business

transformation and continuous operational efficiency. A good Enterprise Architecture
facilitates effective governance, management, risk management, and exploitation
opportunities.
In addition, much of the global privacy legislation demands that processes around
personal data are fully documented in a way that can be easily understood by
untrained readers – such as the data subjects, judges, and lawyers. The penalties for
failing to have this can be very significant, so that the creation of appropriate controls
and documentation is essential.
2.4. The Key Benefits of Enterprise Architecture

(Syllabus Reference: Unit 1, Learning Outcome 1.3: You should be able to list the key
benefits of having an Enterprise Architecture.)
The key business benefits for having an Enterprise Architecture are as follows:
• More effective strategic decision-making by C-Level executives and business

leaders
• More effective and efficient business operations


2.5. What is the TOGAF Standard? Chapter 2. Concepts
• More effective and efficient Digital Transformation and operations
• Better return on existing investment, reduced risk for future investment
• Faster, simpler, and cheaper procurement
Why does Enterprise Architecture Matter?
Ultimately, the benefits of Enterprise Architecture derive

from the better planning, earlier visibility, and more
informed designs that result when it is introduced. [W076]
2.5. What is the TOGAF Standard?

The TOGAF Standard is a framework for Enterprise Architecture. Put simply, it is a
standard approach for developing, approving, using, and maintaining Enterprise
Architectures. It applies to all Enterprise Architecture practices. It is based on an
iterative process model supported by best practices and a re-usable set of existing
architectural assets.
The TOGAF Standard is developed and maintained by The Open Group Architecture
Forum. The original development of the TOGAF Standard, Version 1, in 1995, was
based on the US Department of Defense Technical Architecture Framework for
Information Management (TAFIM). Starting from this sound foundation, The Open
Group Architecture Forum has developed successive versions of the TOGAF Standard
at regular intervals and published each one on The Open Group public website.
Successive versions have represented the current state of stable, scalable, best
practice.
2.5.1. Structure of the TOGAF Documentation

The TOGAF documentation set is structured to address the transition from common
universal scaffolding to the unique configuration within an organization. It includes
the formal TOGAF Standard [C220] and a broader body of knowledge in the TOGAF
Library, as shown in Figure 1. The standard consists of two complementary sets of
documents, the TOGAF Fundamental Content and the TOGAF Series Guides.

Chapter 2. Concepts 2.6. A Framework for Enterprise Architecture
Figure 1. The TOGAF Documentation Set
The TOGAF Fundamental Content includes the universal concepts of Enterprise

Architecture. The TOGAF Series Guides take these concepts and make them actionable
– they provide proven, stable, and enduring best practice. Together, the TOGAF
Fundamental Content and the TOGAF Series Guides are the TOGAF Standard. The
intent of dividing the TOGAF Standard into these separate documents, is to allow for
different areas of specialization to be considered in detail and potentially addressed
in isolation. It also allows for individual documents to be amended without impacting
the whole document set. Although all the constituent documents work together as a
whole, it is also feasible to select individual documents for adoption while excluding
others. The standard includes extended guidance material to address specific
concerns and use-cases through the TOGAF Series Guides.
2.6. A Framework for Enterprise Architecture

(Syllabus Reference: Unit 1, Learning Outcome 1.4: You should be able to explain why
the TOGAF Standard is suitable as a framework for Enterprise Architecture.)
Developing and sustaining an Enterprise Architecture is a technically complex

process which involves many stakeholders and decision processes in the
organization. Adopting the TOGAF Standard as a framework provides a standardized

2.7. Architecture Domains in the TOGAF Standard Chapter 2. Concepts
approach and de-risks the activity. Using the TOGAF Standard results in Enterprise
Architecture that is consistent, reflects the needs of stakeholders, employs best
practice, and gives due consideration both to current requirements and the perceived
future needs of the business.
The TOGAF Standard is also suitable as a framework for Enterprise Architecture since
it provides:
• A definition and description of a standard cycle of change, used to plan, develop,

implement, govern, change, and sustain an architecture for an enterprise; see the
TOGAF ADM
• A definition and description of the building blocks in an enterprise used to

deliver business services and information systems (see the TOGAF Content
Framework)
• A set of guidelines, techniques, and advice to create and maintain an effective

Enterprise Architecture and deliver change through new Solution Architectures
at all levels of scale, pace, and detail
2.7. Architecture Domains in the TOGAF Standard

(Syllabus Reference: Unit 1, Learning Outcome 1.5: You should be able to list the four
architecture domains that are commonly accepted as subsets of an overall Enterprise
Architecture and which the TOGAF Standard supports.)
The TOGAF Standard covers the development of four architecture domains. These
four domains are closely related and commonly accepted as subsets of an overall
Enterprise Architecture. They are shown in Table 1.
Table 1. Architecture Domains Supported by the TOGAF Standard

Architecture Domain Description
Business Architecture The business strategy, capabilities, governance, organization, and

key business processes.
Data Architecture The structure of an organization’s logical and physical data assets
and data management resources.
Application Architecture A blueprint for the individual applications to be deployed, their

interactions, and their relationships to the core business
processes of the organization.

Chapter 2. Concepts 2.8. Architecture Abstraction in Enterprise Architecture
Architecture Domain Description
Technology Architecture The digital architecture and the logical software and hardware
infrastructure capabilities that are required to support the
deployment of business, data, and application services. This
includes digital services, Internet of Things (IoT), social media
infrastructure, cloud services, IT infrastructure, middleware,
networks, communications, processing, and standards.
There are many other domains that could be defined by combining appropriate views
of the Business, Data, Application, and Technology domains; for example,
Information Architecture, Risk and Security Architectures, Digital Architecture.
2.8. Architecture Abstraction in Enterprise Architecture

(Syllabus Reference: Unit 1, Learning Outcome 1.6: You should be able to briefly describe
how architecture abstraction is used in Enterprise Architecture.)
Architecture abstraction is a technique for dividing a problem area into smaller

problem areas that are easier to model and therefore easier to solve. Abstraction
levels are layered in nature, moving from high-level models to more detailed models.
Architecture effort can be divided into distinct abstraction levels that answer the four
fundamental questions about an architecture:
• Why – why is the architecture needed?
• What – what functionality and other requirements need to be met by the

architecture?
• How – how do we structure the functionality?
• With what – with what assets shall we implement this structure?
Architecture effort can be divided into four distinct abstraction levels, as shown in
Table 2, that cross Business, Data, Application, and Technology.

2.9. The Enterprise Continuum Chapter 2. Concepts
Table 2. Architecture Abstraction Levels

Abstraction Level Description
Contextual Understanding the environment in which an enterprise operates

and the context in which architecture work is planned and
executed. It answers why an enterprise undertakes architecture
work, what is the scope of work, and the motivation in terms of
goals, drivers, and objectives.
Conceptual Decomposing the requirements to understand the problem, and

what is needed to address the problem, without unduly focusing
on how the architecture will be realized.
Logical Identifying the kinds of business, data, application, and

technology components needed to achieve the services identified
in the conceptual level. It is about identifying how an architecture
can be organized and structured, in an implementation-
independent fashion.
Physical The allocation and implementation of physical components to

meet the identified logical components. It is about determining
with what physical components the logical-level components can
be realized.
2.9. The Enterprise Continuum

(Syllabus Reference: Unit 1, Learning Outcome 1.7: You should be able to briefly describe
the Enterprise Continuum.)
The Enterprise Continuum, shown in Figure 2, provides a classification for

architecture and solution artifacts, both internal and external to the Architecture
Repository, as they evolve from generic Foundation Architectures to Organization-
Specific Architectures.
The simplest way of thinking of the Enterprise Continuum is as a view of the

repository of all the architecture assets. It can contain Architecture Descriptions,
models, building blocks, patterns, architecture viewpoints, and other artifacts – that
exist both within the enterprise and in the IT industry at large, which the enterprise
considers to have available for the development of architectures for the enterprise.
A distinction is made between architectures and their possible solutions, thus

creating an Architecture Continuum and a Solutions Continuum. As shown in Figure
2, the relationship between them is one of guidance and support.

Chapter 2. Concepts 2.10. Architecture Repository
Figure 2. The Enterprise Continuum
The Enterprise Continuum supports two general ideas: re-use where possible,
especially the avoidance of re-invention, and an aid to communication. The assets in
both the Architecture and Solutions Continuums are structured from generic to
specific in order to provide a consistent language to effectively communicate the
differences between architectures. Understanding where you are in the continuum
helps everyone to communicate effectively. Use of the Enterprise Continuum can
eliminate ambiguity when discussing concepts and items amongst different
departments within the same organization or even different organizations building
Enterprise Architectures. Understanding the architecture helps to better understand
the solution. Being able to explain the general concept behind a solution makes it
easier to understand possible conflicts.
2.10. Architecture Repository

(Syllabus Reference: Unit 1, Learning Outcome 1.8: You should be able to briefly explain
the Architecture Repository.)
Operating a mature Architecture Capability within a large enterprise creates a huge

volume of architectural output. Effective management and leverage of these
architectural work products require a formal taxonomy for different types of
architectural asset alongside dedicated processes and tools for architectural content
storage.

2.10. Architecture Repository Chapter 2. Concepts
The TOGAF Standard provides a structural framework for an Architecture Repository,

as shown in Figure 3, that allows an enterprise to distinguish between different types
of architectural assets that exist at different levels of abstraction in the organization.
This Architecture Repository is one part of the wider Enterprise Repository, which
provides the capability to link architectural assets to components of the Detailed
Design, Deployment, and Service Management Repositories.
Figure 3. Overview of TOGAF Architecture Repository
The major components within an Architecture Repository are as follows:
• The Architecture Metamodel describes the organizationally tailored application

of an architecture framework, including a metamodel for architecture content
• The Architecture Capability defines the parameters, structures, and processes

that support governance of the Architecture Repository
• The Architecture Landscape presents an architectural representation of assets in

use, or planned, by the enterprise at particular points in time
• The Standards Library captures the standards with which new architectures
must comply, which may include industry standards, selected products and
services from suppliers, or shared services already deployed

Chapter 2. Concepts 2.11. TOGAF Content Framework and Enterprise Metamodel
• The Reference Library provides guidelines, templates, patterns, and other forms
of reference material that can be leveraged in order to accelerate the creation of
new architectures for the enterprise
• The Governance Repository provides a record of governance activity across the

enterprise
• The Architecture Requirements Repository provides a view of all authorized

architecture requirements which have been agreed with the Architecture Board
• The Solutions Landscape presents an architectural representation of the Solution

Building Blocks (SBBs) supporting the Architecture Landscape which have been
planned or deployed by the enterprise
2.11. TOGAF Content Framework and Enterprise

Metamodel
(Syllabus Reference: Unit 1, Learning Outcome 1.9: You should be able to briefly explain
the TOGAF Content Framework and Enterprise Metamodel.)
The TOGAF Content Framework and Enterprise Metamodel define a formal structure
and also provide guidance for organizations that wish to implement their
architecture within an architecture tool.
The Content Framework defines a categorization framework to be used to structure

the Architecture Description, the work product used to express an architecture, and
the collection of models that describe the architecture.
The Enterprise Metamodel defines the types of entities to appear in the models that
describe the enterprise, together with the relationships between these entities. It
allows architectural concepts to be captured, stored, filtered, queried, and
represented in a way that supports consistency, completeness, and traceability.
The categorization mechanism of the Content Framework can be used to structure a

representation of the TOGAF Enterprise Metamodel, as shown in Figure 4.

2.11. TOGAF Content Framework and Enterprise Metamodel Chapter 2. Concepts
Figure 4. TOGAF Content Framework Overview

Chapter 2. Concepts 2.12. Architecture Capability
2.12. Architecture Capability

(Syllabus Reference: Unit 1, Learning Outcome 1.10: You should be able to briefly
explain Architecture Capability.)
In order to carry out architectural activity effectively within an enterprise, it is

necessary to put in place an appropriate business capability for architecture, through
organization structures, roles, responsibilities, skills, and processes. An Enterprise
Architecture Capability is the ability to develop, use, and sustain the architecture of a
particular enterprise, and use the architecture to govern change.
An overview of the TOGAF Architecture Capability is shown in Figure 5.
Figure 5. TOGAF Architecture Capability Overview
Barring Architecture Capabilities set up to purely support change delivery programs,

it is increasingly recognized that a successful Enterprise Architecture practice must
sit on a firm operational footing. In effect, an Enterprise Architecture practice must
be run like any other operational unit within a business; i.e., it should be treated like
a business. To this end, and over and above the core processes defined within the
ADM, an Enterprise Architecture practice should establish capabilities in the
following areas:
• Financial Management

2.13. Risk Management Chapter 2. Concepts
• Performance Management
• Service Management
• Risk and Opportunity Management
• Resource Management
• Communications and Stakeholder Management
• Supplier Management
• Configuration Management
• Environment Management
An Enterprise Architecture Capability Model is shown in Figure 6.
Figure 6. Enterprise Architecture Capability Model
2.13. Risk Management

explain risk management.)
The ISO 31000 definition of “risk” is the “effect of uncertainty on objectives”. [ISO
31000]
The effect of uncertainty is any deviation from what is expected – positive and
negative. The uncertainty is concerned with predicting future outcomes, given the
limited amount of information available when making a decision. This information
can never be perfect, although our expectation is that given better quality

Chapter 2. Concepts 2.14. Gap Analysis
information we can make better quality decisions. Every decision is based on

assessing the balance between potential opportunities and threats, the likelihood of
beneficial outcomes versus damaging outcomes, the magnitude of these potential
positive or negative events, and the likelihood associated with each identified
outcome. Identifying and assessing these factors is known as “risk assessment” or
“risk analysis”. “Risk management” is the art and science of applying these concepts
in the decision-making process.
Risk management is about striking a balance between positive and negative outcomes
resulting from the realization of either opportunities or threats. There will always be
risk with any architecture/business transformation effort. It is important to identify,
classify, and mitigate these risks before starting so that they can be tracked
throughout the transformation effort.
Mitigation is an ongoing effort and often the risk triggers may be outside the scope of
the transformation planners (e.g., merger, acquisition) so planners must monitor the
transformation context constantly. Risks can be identified and mitigated, but it is
within the governance framework that risks have to be first accepted and then
managed.
There are two levels of risk that should be considered, namely:
• Initial Level of Risk: risk prior to determining and implementing mitigating

actions
• Residual Level of Risk: risk after implementation of mitigating actions (if any)
2.14. Gap Analysis

explain gap analysis.)
Gap analysis is a technique used in the ADM to validate an architecture that is being
developed.
The premise is to highlight a shortfall between the Baseline Architecture and the
Target Architecture; that is, items that have been deliberately omitted, accidentally
left out, or not yet defined. An example is shown in Table 3. The steps are as follows:
• Draw up a matrix with all the Architecture Building Blocks (ABBs) of the Baseline
Architecture on the vertical axis, and all the ABBs of the Target Architecture on
the horizontal axis
• Add to the Baseline Architecture axis a final row labeled “New”, and to the Target
Architecture axis a final column labeled “Eliminated”

2.14. Gap Analysis Chapter 2. Concepts
• Where an ABB is available in both the Baseline and Target Architectures, record
this with “Included” at the intersecting cell
• Where an ABB from the Baseline Architecture is missing in the Target

Architecture, each must be reviewed
If it was correctly eliminated, mark it as such in the appropriate “Eliminated”

cell. If it was not, you have uncovered an accidental omission in your Target
Architecture that must be addressed by reinstating the ABB in the next iteration
of the architecture design – mark it as such in the appropriate “Eliminated” cell.
• Where an ABB from the Target Architecture cannot be found in the Baseline
Architecture, mark it at the intersection with the “New” row as a gap that needs
to be filled, either by developing or procuring the building block
Table 3. Gap Analysis Example

Target Architecture → Video Enhanced Mailing List Eliminated ↓
Conferencing Telephony Services
Baseline Architecture ↓ Services Services
Broadcast Services Intentionally

Eliminated
Video Conferencing Included

Services
Telephony Services Potential

Match
Shared Screen Services Unintentionally

excluded – a gap in
Target Architecture
New → Gap: Gap:

Enhanced Enhanced
services to be services to be
developed or developed or
procured procured
When the exercise is complete, anything under “Eliminated” or “New” is a gap, which
should either be explained as correctly eliminated, or marked as to be addressed by
reinstating or developing/procuring the function.

Chapter 2. Concepts 2.15. Summary
2.15. Summary
This chapter has introduced the following topics:
• The definitions of an Enterprise and Enterprise Architecture, including the

purpose and benefits of Enterprise Architecture
• An introduction to the TOGAF Standard, an architecture framework that enables

you to design, evaluate, and build the right architecture for your organization
• An introduction to the TOGAF documentation including the TOGAF Library,

which is a reference library provided to accelerate the creation of new
architectures for the enterprise
• The TOGAF Standard as an Enterprise Architecture Framework that can be used

for developing a broad range of different architectures, and which provides a
practical starting point for an architecture project
• Architecture abstraction, a technique for dividing a problem into smaller

problem areas that are easier to model and therefore easier to solve
• Architecture Principles that are general rules and guidelines that relate to
architecture work
• The Enterprise Continuum, which provides a classification for architecture and

solution artifacts
• The Architecture Repository, a structural framework that allows an enterprise to

distinguish between different types of architectural assets that exist at different
levels of abstraction in the organization
• The Content Framework and Enterprise Metamodel, which define a formal

structure and also provide guidance for organizations that wish to implement
their architecture within an architecture tool
• An Enterprise Architecture Capability, which is the business capability for

architecture, through organization structures, roles, responsibilities, skills, and
processes
• How the TOGAF Standard can be used with other frameworks
• Risk management, which is about striking a balance between positive and

negative outcomes resulting from the realization of either opportunities or
threats
• Gap analysis, a technique used to validate an architecture being developed

2.16. Test Yourself Questions Chapter 2. Concepts
2.16. Test Yourself Questions

Q1: Which of the following best describes why the TOGAF Standard is suitable as a
framework for Enterprise Architecture?
A. It de-risks a technically complex process.
B. It contains an extensive body of knowledge called the TOGAF Library.
C. The TOGAF documentation includes the universal concepts of Enterprise

Architecture.
D. It enables more effective decision-making by business leaders.
Q2: Complete the sentence: Three of the four architecture domains that are
commonly accepted as subsets of an overall Enterprise Architecture are …
A. Baseline, Transition, Target.
B. Data, Application, Technology.
C. Capability, Segment, Strategic.
D. Abstract, Logical, Physical.
Q3: Which architecture abstraction level answers why an enterprise undertakes

architecture work, and what is the scope of work?
A. Conceptual
B. Contextual
C. Logical
D. Physical
Q4: Which of the following is a structural framework that allows an enterprise to

distinguish between different types of architectural assets?
A. Architecture Framework
B. Architecture Repository
C. Governance Repository
D. Strategic Architecture

Chapter 2. Concepts 2.16. Test Yourself Questions
Q5: Which of the following is a purpose of gap analysis?
A. Assessing readiness for change within an Enterprise Architecture team
B. Documenting a categorization framework to structure architecture views
C. Identifying shortfalls between Baseline and Target Architectures
D. Finding a balance between positive and negative outcomes
Q6: Complete the sentence: The Enterprise Continuum provides a classification for …
A. architecture and solution artifacts.
B. architecture views and viewpoints.
C. risk categorizations.
D. services and information systems.
Q7: Which does the TOGAF Standard define as a collection of organizations that have
common goals?
A. An architecture
B. An enterprise
C. A federation
D. A system
Q8: Complete the sentence: The Enterprise Metamodel defines …
A. a categorization model used to structure the Architecture Description.
B. a structural model for an Architecture Repository.
C. the assets in use by the enterprise as a structural model.
D. the types of entities used in models describing the enterprise.
Q9: Complete the sentence: Risk management is …
A. a categorization model used prior to determining mitigating actions.
B. about predicting future shortfalls in a Target Architecture.
C. striking a balance between positive and negative outcomes.
D. the effect of uncertainty on objectives.

2.17. Recommended Reading Chapter 2. Concepts
2.17. Recommended Reading

The following are recommended sources of further information for this chapter:
® th
• The Open Group White Paper, An Introduction to the TOGAF Standard, 10
Edition [W212]
® th
• TOGAF Standard, 10 Edition [C220], Introduction and Core Concepts
® th
• TOGAF Standard, 10 Edition [C220], ADM Techniques

Chapter 3. Terminology 3.1. Key Learning Points
Chapter 3. Terminology
This chapter will help you understand the relevant terminology for the TOGAF
Enterprise Architecture Foundation qualification. The source of all definitions in this
chapter is the TOGAF Standard – Introduction and Concepts, Definitions, unless
otherwise indicated.
The terms defined here are used in this Study Guide. They
are not separately examinable unless used in the learning
objective of another unit in the syllabus.
3.2. Terms and Definitions

Application Architecture
A description of the structure and interaction of the applications that provide key
business capabilities and manage the data assets.
Architecture
1. The fundamental concepts or properties of a system in its environment embodied

in its elements, relationships, and in the principles of its design and evolution.
(Source: ISO/IEC/IEEE 42010:2011)
2. The structure of components, their inter-relationships, and the principles and

guidelines governing their design and evolution over time.
Architecture Development Method (ADM)
The core of the TOGAF framework. A multi-phase, iterative approach to develop and
use an Enterprise Architecture to shape and govern business transformation.
See also Section 4.2.

Another random document with
no related content on Scribd:
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.
The Foundation’s business office is located at 809 North 1500 West,

Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact
Section 4. Information about Donations to

the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many small
donations ($1 to $5,000) are particularly important to maintaining tax
exempt status with the IRS.
The Foundation is committed to complying with the laws regulating

charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states where

we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot make

any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.
Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.
Section 5. General Information About Project

Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.
Project Gutenberg™ eBooks are often created from several printed

editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.
This website includes information about Project Gutenberg™,

including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.

The Togafr Enterprise Architecture Foundation Study Guide Preparation For The Togaf Enterprise Architecture Part 1 Examination Van Haren Publishing Full Chapter PDF Scribd

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Togafr Enterprise Architecture Foundation Study Guide Preparation For The Togaf Enterprise Architecture Part 1 Examination Van Haren Publishing Full Chapter PDF Scribd

Uploaded by

Copyright:

Available Formats

The Togaf(r) Enterprise Architecture

Foundation Study Guide: Preparation

Personal PDF Edition. Not for redistribution.

Personal PDF Edition. Not for redistribution.

Personal PDF Edition. Not for redistribution.

Personal PDF Edition. Not for redistribution.

[This page is intentionally blank]

Personal PDF Edition. Not for redistribution.

vi The Open Group (2023)

Personal PDF Edition. Not for redistribution.

The TOGAF® Enterprise Architecture Foundation Study Guide vii

No part of this publication may be reproduced, stored in a retrieval system, or

Published by The Open Group, March 2023.

The Open Group,

or by electronic mail to:

Personal PDF Edition. Not for redistribution.

viii The Open Group (2023)

• Working with customers to capture, understand, and address current and

• Working with suppliers, consortia, and standards bodies to develop consensus

• Offering a comprehensive set of services to enhance the operational efficiency of

• Developing and operating the industry’s premier certification service and

Further information on The Open Group is available at www.opengroup.org.

Personal PDF Edition. Not for redistribution.

The TOGAF® Enterprise Architecture Foundation Study Guide ix

The audience for this Study Guide is:

• Individuals who need a basic understanding of a proven Enterprise Architecture

• Individuals who need to start to learn the TOGAF method

A prior knowledge of Enterprise Architecture is advantageous but not required.

The structure of the document is as follows:

• Chapter 1, Introduction introduces TOGAF certification and the TOGAF Enterprise

• Chapter 2, Concepts introduces the concepts of Enterprise Architecture and the

• Chapter 5, ADM Techniques introduces the techniques available to support

• Chapter 6, Applying the ADM introduces the guidance available to support

• Chapter 7, Architecture Governance describes how Architecture Governance

• Chapter 8, Architecture Content describes the key concepts related to the

Personal PDF Edition. Not for redistribution.

x The Open Group (2023)

• Appendix B, Test Yourself Examination Paper provides an examination to allow

• Appendix D, TOGAF Enterprise Architecture Level 1 Syllabus provides the TOGAF

How to Use this Document

Conventions Used in this Document

• (Syllabus reference Unit X, Learning Outcome X.Y: Statement)

Indicates a continuation; such as an incomplete list of example items, or a

Used to highlight specific terms.

Used for emphasis. May also refer to other external documents.

The TOGAF® Enterprise Architecture Foundation Study Guide xi

In addition to typographical conventions, the following conventions are used to

A Note box is used to highlight useful or interesting

A Tip box is used to provide key information that can save

Personal PDF Edition. Not for redistribution.

xii The Open Group (2023)

About the TOGAF Standard

Personal PDF Edition. Not for redistribution.

The TOGAF® Enterprise Architecture Foundation Study Guide xiii

About the Author

Andrew Josey, The Open Group

Andrew Josey is VP Standards and Certification, overseeing all certification and

He is a member of the IEEE, USENIX, and the Association of Enterprise Architects

Personal PDF Edition. Not for redistribution.

xiv The Open Group (2023)

Gartner is a registered trademark of Gartner, Inc.

ITIL is a registered trademark of AXELOS Limited.

POSIX is a trademark of the IEEE.