Key takeaways
- A framework must describe baseline, target, building blocks, and the path between them.
- TOGAF covers both deliverables and method, the ADM.
- A standard approach lowers the risk of a complex, multi-actor effort.
- Three contributions: ADM, Content Framework, guidelines and techniques.
- TOGAF can be tailored and combined with ITIL, COBIT, PRINCE2, and other practices.
What an architecture framework should offer
An architecture framework is a base structure used to develop a wide variety of architectures. It should allow a starting state and a target state to be described as building blocks, show how those building blocks fit together, and plan the move from one to the other. It is normally tailored to the organization, which gives it shared tools and vocabulary.
Every EA framework combines two key elements: a definition of the deliverables to produce and the method for producing them. Most frameworks detail the deliverables and say little about method. TOGAF stands out by providing both, with the ADM as its method.
A standard approach that lowers risk
Developing and sustaining an EA is complex: many actors and decision processes are involved. Adopting a standardized approach reduces that risk. Produced through the collaborative work of a whole community, TOGAF leads to an architecture that is consistent, true to stakeholder needs, grounded in best practice, and mindful of both current and anticipated future needs.
Its value proposition is to help organizations work effectively using recognized practices that apply across sectors. Its guidance is meant to be adapted to varied needs, including the agile enterprise and Digital Transformation.
Three concrete contributions
The Study Guide sums up what makes TOGAF suitable in three contributions, each tied to a part of the standard.
- A standard change cycle, the ADM, to plan, develop, implement, govern, evolve, and sustain the architecture
- A definition of the building blocks that deliver business services and information systems, through the Content Framework
- Guidelines, techniques, and advice to sustain the EA and deliver Solution Architectures at any scale, pace, and level of detail
Tailor and combine
TOGAF is generic: its deliverables can be used as they are, replaced, or extended by those of another framework. The architect is expected to tailor it into a method built into the enterprise’s processes and structures, combining it where useful with ITIL, COBIT, CMMI, PRINCE2, PMBOK, or MSP, or with Library resources such as the IT4IT Reference Architecture.
It particularly benefits organizations running a transformation, those aiming for Boundaryless Information Flow, those wanting procurement specifications that favor open systems, and those that must improve their offering as part of Digital Transformation.
TERMS TO KNOW
The terms, in context.
- Architecture framework
- A base structure, with methods and tools, for developing varied architectures.
- ADM
- TOGAF’s iterative cycle for developing and evolving architecture.
- Content Framework
- A frame that categorizes architecture building blocks and work products.
- Boundaryless Information Flow
- Access to integrated information within and between enterprises.