LEARN. PRACTICE. GROW.Concept and mechanism
In Phase D, Technology Architecture, infrastructure design should support identified requirements and interactions. A recovery need is not satisfied merely by buying two machines; dependencies and conditions for service operation matter. Phase E, Opportunities and Solutions, relates gaps to delivery options and transition states. Phase F, Migration Planning, develops implementation and migration planning using sequence, dependencies, value, and resources. These distinctions explain why a component list is not a plan and why a schedule date does not prove a dependency will be ready.
Guided application
Imagine two migration waves: the first moves the application, while the replacement file producer arrives only in the second. If daily reconciliation depends on the old producer, the intermediate state must preserve it or bring the replacement forward with approval. Phase G, Implementation Governance, oversees implementation’s architectural alignment, including deviations and evidence. It does not automatically make the architect responsible for every operational or budget decision. In Phase H, Architecture Change Management, new needs may lead to limited treatment or new architecture work according to impact. Requirements continue to be managed throughout the cycle. Finishing a project does not freeze service architecture forever.
A server’s absence from the final target does not authorize shutting it down before replacing its remaining function.
Common pitfalls
Target without transition; oversight as doing everything; new requirement as mandatory restart of the whole program.
Related topics: Techniques for clarifying decisions · Iteration, scope, and partitioning
Plan usable states and follow change into operation.
Reference: How ArchiMate and TOGAF complement each other · OGEA-101, TOGAF Enterprise Architecture Foundation; body of knowledge drawn from TOGAF Standard, 10th Edition