The Architecture Capability Framework is the set of resources, guidelines and templates for standing up and running an architecture practice. You establish the Architecture Capability in the Preliminary Phase — and you can architect it using the ADM itself.
To apply TOGAF, an enterprise needs a working architecture practice — people, roles, processes, tools, governance. That practice is the "Architecture Capability".
- ▸🏗️ Architecture Capability = the enterprise's ability to DO architecture (org structure + roles + processes + tools + governance)
- ▸🎬 It is ESTABLISHED in the Preliminary Phase — before any architecture work starts
- ▸🔁 It can be architected using the ADM itself — treat the architecture practice as the "enterprise" and run Business/Data/Application/Technology architecture for it
- ▸🗄️ It is stored as the "Architecture Capability" class of the Architecture Repository
- ▸📈 It is sustained and matured through governance (Phase G/H feed back into it)
Explore what the framework contains, the Architecture Skills Framework, and the ACMM maturity model.
The Architecture Capability Framework is the set of resources, guidelines and templates for standing up and running an architecture practice. It is established in the Preliminary Phase.
Guidance on standing up an architecture practice — often run as its own ADM cycle (you architect the architecture capability itself: its business, data, application and technology).
The cross-organization body that provides operational oversight and governance of the architecture. (Covered in depth in the Governance topic.)
The review process and the six compliance levels used to check projects against the architecture.
Joint signed agreements of deliverables, quality and fitness-for-purpose between the architecture function and delivery partners.
The framework and processes for managing and controlling architecture enterprise-wide (the six characteristics: DART + I F).
Tools to assess and improve how mature the architecture practice is — e.g. the ACMM.
A structured view of the roles, skills and proficiency levels needed to do architecture work.
The Architecture Capability Framework bundles the reference material for running an architecture practice:
- ▸🎬 Establishing an Architecture Capability — guidance on standing up the practice
- ▸👥 Architecture Board — the operational oversight body
- ▸📏 Architecture Compliance — the review process and six compliance levels
- ▸📜 Architecture Contracts — joint agreements with delivery partners
- ▸⚖️ Architecture Governance — the framework and six characteristics (covered in the Governance topic)
- ▸📊 Architecture Maturity Models — assess and improve the practice (ACMM)
- ▸🎓 Architecture Skills Framework — roles, skills, and proficiency levels
A structured way to define who does architecture work and how deep their knowledge needs to be. It crosses three dimensions:
- ▸🎭 Roles — Enterprise, Business, Data, Application, Technology, Solution Architect (plus sponsors, managers, board members)
- ▸🗂️ Skill categories (7) — Generic; Business Skills & Methods; Enterprise Architecture; Program/Project Management; IT General Knowledge; Technical IT; Legal Environment
- ▸📶 Proficiency levels (4) — Background → Awareness → Knowledge → Expert
- ▸🧰 Used for role definitions, job descriptions, skills gap analysis, and training plans
Maturity models measure how good the architecture practice is, so you can plan improvements.
- ▸📊 The ACMM (Architecture Capability Maturity Model) rates the practice on 6 levels: 0 None, 1 Initial, 2 Under Development, 3 Defined, 4 Managed, 5 Measured
- ▸9️⃣ It assesses 9 architecture characteristics (architecture process, business linkage, senior-management involvement, operating-unit participation, architecture communication, IT security, architecture governance, IT investment strategy, and architecture development)
- ▸🎯 Output: a current-maturity profile vs a target profile — a gap to close
- ▸⚠️ Maturity models assess the PRACTICE, not a specific architecture deliverable