According to TOGAF, an Enterprise Architecture capability is made up of :
- The method for developing new architectures
- The content framework
- The enterprise continuum
- The architecture repository
- The reference models
- The capability framework
These several parts of TOGAF are briefly described next. The following sections present the « crub notes » for each one of these six key parts of TOGAF.
(A) ADM (Architecture Development Method)
The ADM describes what needs to be done in order to create an architecture. The ADM describes the 10 activities that are required for developing and managing an Enterprise Architecture. It is expected that the generic ADM be customized for a particular organization.
TOGAF considers ADM as its core. It is the only part of the TOGAF body of knowledge that is considered mandatory, if an organization wants to be TOGAF compliant. The other components might be replaced by equivalent ones ; for example, the Architecture Content Framework may be replaced by the Zachmann Framework.
The figure reproduced below presents an overview of TOGAF ADM.
TOGAF ADM |
(B) Architecture Content Framework
The content framework describes what the architecture should look like once it is done. The architects executing the ADM will produce a number of outputs. The Architecture Content Framework provides the structure for organizing these outputs.
ACM uses three categories for classifying the architects’ work products:
- Deliverables
- Artifacts (granular architecture works – lists, matrices and diagrams)
- Building blocks (a potentially reusable architecture component)
The Architecture Content Metamodel identifies all the types of building blocks that may exist within an architecture.
The figure reproduced below depicts the Architecture Content Metamodel.
(C) Enterprise Continuum
No architecture is developed from the scratch. The architects build on previously existing knowledge.
During their engagements, the architects use diverse architecture and solution models – foundation models, industry models, etc. – that are extended and customized to the organizations’ needs. They represent invaluable knowledge, that has to be leveraged if the architecture team will produce assets that create value to the organization.
The Enterprise Continuum organizes the models used by the architecture team, in a way that is meaningful to the organization.
The figure reproduced below depicts the general organization of the Enterprise Continuum.
(D) Architecture Repository
The architecture work creates a huge volume of architectural output. Effective management and leverage of these contents require a formal taxonomy, processes and tools. TOGAF « provides a structural framework for an Architecture Repository that allows an enter pr ise to distinguish between different types of architectural assets that exist at different levels of abstraction in the organization ».
The Architecture Repository holds six classes of information.
- The Architecture Metamodel
- The Architecture Capability
- The Architecture Landscape
- The Standards Information Base
- The Reference Library
- The Governance Log
The figure reproduced below depicts the structure of the TOGAF Architecture Repository and some relationships with other enterprise contents.
ARCHITECTURE REPOSITORY |
(E) Reference Models
An Enterprise Architecture requires at least one « Reference Model », that defines the complete landscape of IT asset categories.
The reference model has double function
- It sets the taxonomy of IT assets, so that all participants in the organization talks the same language when discussing about the assets
- It provides a diagramatic representation of the IT asset landscape, facilitating the communication between architects and the rest of participants in the IT processes
The figure reproduced below depicts the TOGAF Technical Reference Model.
TOGAF TRM |
(F) Capability Framework
The enterprise architecture function requires a set of appropiate organization structures, processes, roles, responsibilities and skills. TOGAF Architecture Capability Framework provides a set of reference materials for this matter. Despite they do not make up a comprehensive template, these reference materials are of great value for the architecture team.
The figure reproduced below depicts the overall structure of the TOGAF Architecture Capability Framework.
TOGAF ARCHITECTURE CAPABILITY FRAMEWORK |
The following sections present the « crub notes » for each one of these six key parts of TOGAF.
[END OF POST]
Viendo estas cosas me ha dado un repelús al recordar mis tiempos de gerente en DMR dándole intensamente al PowerPoint :-)
ReplyDeleteAhora soy feliz con mis algoritmos de control, mis transformadas Z, mis FFTs, mis trastos (de verdad, que pesan y se pueden tocar) meneándose de un lado para otro...
¡Eso es! Menos "bla-bla-bla" y más ingeniería.
DeleteAfortunadamente, TOGAF también va de esto - proveer un body of knowledge con suficiente amplitud, "chicha" y rigor, como para ser admitido en un currículo de ingeniería. Otros frameworks se quedan a mitad de camino; en mi opinión, TOGAF sí que "da la talla".
(Por cierto, "transformadas Z": desde la carrera no escuchaba de ellas!! Bueno saber que se usan de verdad.)
Un saludo, Mario