TOGAF 9.2 Foundation
This module takes a deep dive in to the different phases of the Architecture Development Method, focusing on the objectives and approaches to each of the 9 phases. This module is supported by videos and a PDF, and is followed by a quiz to help support your understanding.
This module will cover:
- The Architecture Development Method
- Preliminary Phase
- Phase A: Architecture Vision
- Phase B: Business Architecture
- Phase C: Information Systems Architectures
- Phase D: Technology Architecture and Foundation Architecture
- Phase E: Opportunities and Solutions and Planning Techniques
- Phase F: Migration Planning and Techniques
- Phase G: Implementation Governance
- Phase H: Architecture Change Management
- ADM Requirements Management
This course is intended for anyone looking to understand Enterprise Architecture. It is helpful however to have several years' experience in IT in a variety of roles, or to have an understanding of Enterprise or IT Architecture.
Prerequisites of the Certifications
There are no formal pre-requisites for this course.
We welcome all feedback and suggestions - please contact us at firstname.lastname@example.org to let us know what you think.
- Now that the architecting phases have been completed, it's time to begin planning the transition to the new architecture. In phase E, "opportunities and solutions", and Phase F, "migration planning". The focus moves to planning how the target architecture is implemented. So, how are these phases carried out? Let's start with phase E. The real work in phase E begins once several iterations of the previous phases have been concluded and a set of architecture building blocks have been prepared. These should be accompanied by roadmap components, such as a list of gaps between the target and baseline architectures. Let's look at the objectives of phase E. They are, to generate the initial, complete version of the architecture roadmap based on the gap analysis and candidate architecture roadmap components from phases B, C, and D, to determine whether an incremental approach is required and, if so, to identify any transition architectures that will deliver continuous value to the business, and to define the overall solution building blocks to finally meet the target architecture, based on the architecture building blocks. With the first objective, the architecture roadmap is an aggregate of several different aspects, gaps, work packages, implementation recommendations, possible transitions, and significant changes. So the term "initial complete" is suggesting that the comprehensive roadmap document will be started in this phase. Phase E is very much a time for review. This includes reviewing the requirements, how ready the organization is, what constraints need to be considered. In addition to these requirements, you'll also need to create an architecture listing individual work packages. A work package is the actions identified to achieve objectives. In effect, the work package identifies logical groups of changes. A transition architecture, describing the enterprise as a architecturally significant state between the baseline and target architectures. An implementation and migration plan that provides a schedule of the projects that will realize the target architecture. Finally, the architecture roadmap should also refer to all of the stakeholders that have contributed requirements. Next, let's look at the objectives of phase F, "migration planning". the focus of phase F is the creation of an implementation and migration plan. In cooperation with the project and portfolio managers, the roadmap and the implementation and migration plan are then integrated with the enterprise's other change activity. These change activities include, assessing the dependencies, costs, and benefits of the various migration projects within the context of the enterprise's other activities. In this phase, you'll need to finalize the architecture roadmap and the supporting implementation and migration plan. This requires detailed planning. You need to take into consideration everything you know about the organizational context here. You'll want to ensure that the implementation and migration plan is coordinated with the enterprise's approach to managing and implementing change. You may be able to refer to the enterprise's overall change portfolio, if they have one. You could even look at working with change agents in the organization too. You'll need to ensure that the business value and cost of the work packages and transition architectures is understood by key stakeholders. Here you'll need to understand and effectively communicate the costs and benefits of the architecture, as well as any risks. And that's it for this video. In the next video, we'll look at phase G, "implementation Governance".
In a varied career that began in 1974, John Coleshaw has trodden a relatively unusual path whereby his roles have split evenly between Business and IT. In the early 80s he was the Credit Manager for a multi-national electronics company, and at the same time built a computerised financial and credit analysis tool using the original version of the IBM PC. In the mid-80s, whilst performing the role of senior underwriter in the Credit Insurance industry, he managed the IT system, as well as developed an innovative risk analysis tool. At the start of the 90s, as a manager in a financial information company, he developed an early form of expert system whose purpose was to predict corporate failure.
His current career as an IT trainer began in 1998, specialising at the time in Object Oriented programming languages. In 2002 he started developing and delivering IT Architecture training and has now had the opportunity to meet and discuss architecture matters with over a thousand architects. The courses he trains now span both The Open Group (TOGAF and ArchiMate), and BCS.
He has a book to his name, one written in the late 80s on Credit Risk Analysis.