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 email@example.com to let us know what you think.
- Now that the architecture has a vision, and it's been architected and planned, it's time to get it up and running in phase G, the implementation phase. Implementation governance is exercised while the target architecture is being implemented by the organization. The task of the architect is then to check the implementation plan is being followed, and, if necessary, deal with any change requests that arise. What happens in this phase depends on the granularity of architecture. If it is strategic or segmented in nature, then the development of this will be handed over to other architects in the organization. But if the granularity is capability related, then in this phase both the detail design and implementation will be completed like a system being built. The complexities of the organizations that use the TOGAF Framework means it's likely that the best approach to implementation is in stages or transitions. This makes it possible for the business to realize the value and benefits of the architecture early on. Some general approaches include, tailoring an implementation program that enables the delivery of the transition architecture, establishing a phase timetable to reflect business priorities, following the organization's approach to corporate, IT, and architecture governance, making use of any project and or program approach, and defining an operations framework to ensure a long life for the proposed system. An important link exists between the organization of the architecture and implementation, one which will benefit from the development of architecture contracts. The contract will include the name, description, and objectives of the project, the scope, deliverables, and constraints of the project, the measures of effectiveness, or the architecture, the acceptance criteria to define what good looks like and when the architecture is complete, and the risks and issues to identify what might go wrong, and what the acceptable level of risk is. It's important to ensure that compliance with the architecture occurs, and that the implementation is compliant with projects and other ongoing projects. And that's it for the implementation phase. Next, we'll look at the last phase of the ADM, phase H, change management.
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.