The Open Group's syllabus (X2202) for OGEA-102 as of April 2022, mapped to the chapters of Ultra Transcenders OGEA-102: Enterprise Architecture Practitioner.
| Objective | Chapters |
|---|---|
| Unit 1: The Context for Enterprise Architecture | |
| 1.1 Guiding effective change as the purpose of EA | 1. The Practitioner's Job: Guiding Effective Change |
| 1.2 What an EA looks like | 1. The Practitioner's Job: Guiding Effective Change |
| 1.3 Architecture Capability | 1. The Practitioner's Job: Guiding Effective Change |
| 1.4 Architecture Governance and the architect's role | 2. Governance, Compliance and the Architect's Role |
| 1.5 Compliance, conformance levels and reviews | 2. Governance, Compliance and the Architect's Role |
| 1.6 Alignment to objectives, with Agile as an example | 3. Agile, Architecture States and the Digital Enterprise |
| 1.7 Managing several architecture states | 3. Agile, Architecture States and the Digital Enterprise |
| 1.8 Enterprise Security Architecture | 4. Security and Risk Across the Enterprise |
| 1.9 Security as a cross-cutting concern | 4. Security and Risk Across the Enterprise |
| 1.10 Managing the uncertainty of change | 3. Agile, Architecture States and the Digital Enterprise; 4. Security and Risk Across the Enterprise |
| 1.11 EA in the four contexts of a digital enterprise | 3. Agile, Architecture States and the Digital Enterprise |
| Unit 2: Stakeholder Management | |
| 2.1 Identifying stakeholders, concerns, views and communication | 5. Stakeholder Management and Architecture Views |
| 2.2 Using architecture views | 5. Stakeholder Management and Architecture Views |
| 2.3 Managing engagement and requirements | 5. Stakeholder Management and Architecture Views |
| 2.4 Using trade-off | 6. Trade-offs and the Steps Common to Every Phase |
| Unit 3: Phase A, the Starting Point | |
| 3.1 Information needed and how iteration adds to it | 7. Phase A in Practice |
| 3.2 Applying the phase: scope, stakeholders, goals, drivers and constraints | 7. Phase A in Practice |
| 3.3 Just-enough security architecture | 4. Security and Risk Across the Enterprise; 7. Phase A in Practice |
| 3.4 Outputs: Statement of Architecture Work, Architecture Vision, Communications Plan | 7. Phase A in Practice |
| Unit 4: Architecture Development | |
| 4.1 Steps common to all phases | 6. Trade-offs and the Steps Common to Every Phase |
| 4.2 Risk and security during development | 4. Security and Risk Across the Enterprise |
| 4.3 Business principles, goals and drivers | 8. Phase B and the Business Architecture Toolkit |
| 4.4 Applying Phase B | 8. Phase B and the Business Architecture Toolkit |
| 4.5-4.6 Phase C information and application | 9. Phases C and D in Practice |
| 4.7-4.8 Phase D information and application | 9. Phases C and D in Practice |
| 4.9 Outputs of Phases B, C and D | 8. Phase B and the Business Architecture Toolkit; 9. Phases C and D in Practice |
| Unit 5: Implementing the Architecture | |
| 5.1 Risk and security in Phases E, F and G | 4. Security and Risk Across the Enterprise; 10. Phase E: Building the Implementation and Migration Strategy; 11. Phase F: Migration Planning, Value and Viability; 12. Phase G: Implementation Governance and Architecture Contracts |
| 5.2 Phase E steps | 10. Phase E: Building the Implementation and Migration Strategy |
| 5.3 Three approaches to implementation | 10. Phase E: Building the Implementation and Migration Strategy |
| 5.4 Work packages | 10. Phase E: Building the Implementation and Migration Strategy |
| 5.5 Transition Architectures | 3. Agile, Architecture States and the Digital Enterprise; 10. Phase E: Building the Implementation and Migration Strategy |
| 5.6 Impact and coordination of migration projects | 11. Phase F: Migration Planning, Value and Viability |
| 5.7 Business value of work packages | 11. Phase F: Migration Planning, Value and Viability |
| 5.8 Prioritising projects | 11. Phase F: Migration Planning, Value and Viability |
| 5.9 Confirming the roadmap | 11. Phase F: Migration Planning, Value and Viability |
| 5.10 Outputs for implementation | 10. Phase E: Building the Implementation and Migration Strategy; 11. Phase F: Migration Planning, Value and Viability |
| 5.11 Phase G inputs | 12. Phase G: Implementation Governance and Architecture Contracts |
| 5.12 Executing implementation governance | 12. Phase G: Implementation Governance and Architecture Contracts |
| 5.13 Outputs supporting governance | 12. Phase G: Implementation Governance and Architecture Contracts |
| 5.14 Architecture Contracts | 12. Phase G: Implementation Governance and Architecture Contracts |
| 5.15 Balancing opportunity and viability | 11. Phase F: Migration Planning, Value and Viability |
| Unit 6: Architecture Change Management | |
| 6.1 Change Requests and other triggers | 13. Phase H and Requirements Management |
| 6.2 Activities for effective change management | 13. Phase H and Requirements Management |
| 6.3 Outputs | 13. Phase H and Requirements Management |
| Unit 7: Requirements Management | |
| 7.1 Inputs | 13. Phase H and Requirements Management |
| 7.2 How its steps match the ADM phase steps | 13. Phase H and Requirements Management |
| 7.3 Purpose of its outputs | 13. Phase H and Requirements Management |
| Unit 8: Supporting the ADM Work | |
| 8.1 The TOGAF Library | 14. The Repository, Levels, Building Blocks and the Metamodel |
| 8.2 Business scenarios | 8. Phase B and the Business Architecture Toolkit |
| 8.3 Compliance assessments | 2. Governance, Compliance and the Architect's Role |
| 8.4 Migration planning techniques | 10. Phase E: Building the Implementation and Migration Strategy; 11. Phase F: Migration Planning, Value and Viability |
| 8.5 Repository structure | 14. The Repository, Levels, Building Blocks and the Metamodel |
| 8.6 A well-run repository | 1. The Practitioner's Job: Guiding Effective Change; 14. The Repository, Levels, Building Blocks and the Metamodel |
| 8.7-8.9 Architecture levels and detail | 14. The Repository, Levels, Building Blocks and the Metamodel |
| 8.10 Architecture Building Blocks | 14. The Repository, Levels, Building Blocks and the Metamodel |
| 8.11 Phase B techniques | 8. Phase B and the Business Architecture Toolkit |
| 8.12 Gap analysis | 6. Trade-offs and the Steps Common to Every Phase |
| 8.13 Iteration | 3. Agile, Architecture States and the Digital Enterprise; 7. Phase A in Practice |
| 8.14 Implementation Factor Catalog and related techniques | 10. Phase E: Building the Implementation and Migration Strategy |
| 8.15-8.18 Metamodel, content framework and taxonomy | 14. The Repository, Levels, Building Blocks and the Metamodel |
| 8.19 Risk assessment | 4. Security and Risk Across the Enterprise |
The full list of tasks under each objective is in the official OGEA-102 exam page. The book is organised by topic, so one chapter often serves several objectives.