The Preliminary Phase, Phases A to H and Requirements Management, each with its purpose and essential output.
From Ultra Transcenders OGEA-101 by Tony Rough (publishing soon)
The ADM has a Preliminary Phase, eight lettered phases from A to H, and Requirements Management at the centre. The table gives each phase’s purpose in one line and the essential output that the Practitioners’ Approach Series Guide (G186) associates with it.
| Phase | Purpose in brief | Essential output (G186) |
|---|---|---|
| Preliminary | Prepare and initiate the Architecture Capability, customise the TOGAF framework and define Architecture Principles | - |
| A: Architecture Vision | Set the scope, identify stakeholders, create the Architecture Vision and obtain approval to proceed | Enough documentation to obtain permission to proceed with developing a Target Architecture |
| B: Business Architecture | Develop the Business Architecture that supports the agreed Vision | A set of stakeholder-approved domain architectures, with gaps and the work to close them understood |
| C: Information Systems Architectures | Develop the Data and Application Architectures that support the Vision | As for B |
| D: Technology Architecture | Develop the Technology Architecture that supports the Vision | As for B |
| E: Opportunities & Solutions | Carry out initial implementation planning and identify delivery vehicles | A set of work packages addressing the gaps, with their value, effort and dependencies |
| F: Migration Planning | Plan the move from Baseline to Target by finalising a detailed Implementation and Migration Plan | An approved set of projects, each with objectives, constraints, resources and start and finish dates |
| G: Implementation Governance | Provide architectural oversight of the implementation | Completion of the projects that implement the changes |
| H: Architecture Change Management | Establish procedures for managing change to the new architecture | Direction to proceed with developing a new Target that addresses shortfalls against stakeholder preferences |
| Requirements Management | Manage architecture requirements throughout the ADM | - |
Chapter 5 covers the Preliminary Phase and Phase A, Chapter 6 covers Phases B, C and D, Chapter 7 covers Phases E and F, and Chapter 8 covers Phases G, H and Requirements Management. Figure 4.1 shows the phases and their links to Requirements Management.
This note is one section of Ultra Transcenders OGEA-101: Enterprise Architecture Foundation, an independent study guide that explains every learning unit the exam covers, topic by topic, with comparison tables, diagrams and the common traps, plus a glossary linked to the TOGAF Standard.
Publishing soon on Amazon in Kindle and paperback editions.
About the book · OGEA-101 terms in the glossary · All OGEA-101 study notes
What the Business, Data, Application and Technology domains each describe, and which subjects cut across all four.
The contextual, conceptual, logical and physical levels, the question each answers, and the difference between logical and physical.
Why the Enterprise Continuum is a classification scheme rather than a place, and what it does for communication and re-use.
How to set Baseline Architecture Building Blocks against Target ones to see what is included, what is new and what is eliminated.
Architecture Capability, Architecture Development, Transition Planning and Architecture Governance iterations, and the phases each one spans.
What an Architecture Board is accountable for, who should sponsor it and how large it should be.
How stakeholders' concerns are framed by viewpoints and addressed by views, and why a view and a viewpoint are not the same thing.