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 preliminary phase is complete, it's time to begin developing the architecture vision. So, what is an architecture vision and how is it created? Phase A, architecture vision is the place where the main architectural work begins. Whenever changes are needed to the current architecture of an enterprise, then the starting point is to visualize an architecture. This is called the target architecture. There are two objectives of the architecture vision phase. The first is to develop a high-level aspirational vision of the capabilities and business value that needs to be delivered as a result of the enterprise architecture. The architecture vision will be documented as a deliverable. The second is to get sign off from the sponsor, which will include getting an approval of the vision that you've developed. The Statement of Architecture Work deliverable defines a program of work to develop and deploy the architecture outlined in your architecture vision. However, it's likely that the first vision statement you produce will go through a number of iterations, and get changed as more information about the enterprise becomes available and things like new technologies are introduced. When creating an architecture vision, there are some key concepts, approaches, and considerations that you should take. The architecture vision should provide a first-cut, high-level description of the target architecture. It's also necessary to understand the baseline architecture as well. This is the current state of the organization and what we use to establish a consensus with the organization you're designing the architecture for. It's important to understand the organizational context. You'll gain some understanding of the organizational context during the preliminary phase and this should inform the vision. The architecture vision should cover main domains. Business, data, applications, and technology. Consideration may also need to be given to aspects such as security, digital issues, network managements, and other aspects that the organization might face. Organizational context is key. You should also consider some fundamental business concepts that might impact the organization. Things like business capabilities, value streams, and organizational applications. Lastly, something integral to the architecture vision is an understanding of emerging technologies. You'll want to try and grasp the potential impact on industries and enterprises, without which many business opportunities may be missed. That's it for this video. Next, we'll look at the architecting phases. Phases B, C, and D.
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.