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.
- The approved architecture vision developed in phase A, provides the blueprint for more detailed architecting. In phases B, C and D, an understanding of the business, Information System and technology architecture is developed. So, what happens in these phases. Phases B, C, and D all have essentially the same objective, which is to develop a target architecture that addresses the statement of Architecture Work and stakeholders concerns. The architect will also identify a set of roadmap components, such as Gaps, which are features in the target architecture that are not present in the baseline architecture. Timescales on how long it may take to fill the gaps. Risks, assumptions, issues and dependencies and recommendations for implementation. In the Phase E, opportunities and solutions, a formal implementation and migration plan will be initiated based on the identified roadmap components. Now, let's get into each phase. First phase B, Business Architecture. This describes how the enterprise needs to operate to achieve business goals and respond to the strategic drivers identified in the statement of architecture work. We already know that the objective is to develop the target business architecture, but how should an architect approach it? Let's break this down into more detail. First, business architecture is a prerequisite for other domains. Its scope is determined by the architecture vision. It should demonstrate business value, make use of existing business strategies, or create new ones. The business scenario is a useful technique for gathering useful information. Second, you'll need a baseline architecture. This is what the current architecture looks like. If one isn't available, then this needs to be created. Third, you'll need the business capability map developed in the architecture vision phase. This provides a self-contained view of the business that is independent of the current organizational structure, business processes, information systems and applications and the rest of the product or service portfolio. Forth, you'll need to apply value streams. Value streams are end to end value adding activities, also known as value stages that underpin the products or services provided to customers, stakeholders or end users. They provide valuable stakeholder context into why the organization needs business capabilities, while business capabilities provide what the organization needs, for a particular value stage to be successful. Fifth, an organization map will show the key organizational units, partners and stakeholder groups. It could also identify the capabilities possessed, and the value streams, that each part of the organization participates in. Sixth, using business modeling. Modeling is fundamental to business architecture. In addition to capabilities and value streams, other models include use cases, activity of business process models, and even class models to model data. Finally, you'll need to make use of assets in the architecture repository. This could include industry reference models, enterprise specific business architecture views, enterprise specific building blocks and standards. Next, let's look at phase C, information systems and how it enables the business architecture. This is a composite phase made up of data and application architecture. The phase can be performed in either data first, or application first, depending on circumstances. Some architects like to address the information and data side of a system first, though others focus on an application first approach. The approach to this phase revolves around effective management and migrating of data, coupled with ensuring people with appropriate data skills are available. Make sure you look in the architecture repository for tools and resources. These can include industry data models, examples exist in many key industry sectors, such as oil and gas, government and retail. And application models. These are developed by organizations such as the Object Management Group, the Open Group and the TM forum. Phase D is about enabling the architecture vision, target business, data and application building blocks to be delivered through technology components and technology services, in a way that addresses the statement of architecture work and stakeholder concerns. And, like phases B and C, you'll need to identify roadmap components based on the gaps between baseline and target architectures. This is done by considering emerging technologies and involves understanding the evolution of technology as a major driver for change. This includes embracing digital innovations and taking into account evolving solutions development. The ADM flexibility allows technology change to become a strategic resource. There are a few architecture repository items that can be useful here. Existing I.T. services as documented in the I.T. repository or I.T. service catalog. The technical reference model, TRM. Generic technology models relevant to the organization's industry vertical sector. And, technology models relevant to common systems architectures. That's it for the architecting phases. Next we'll look at the planning phases, phases E and F.
About the Author
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.