Why Use a Framework?
Architecture frameworks provide a common language, a structured process, and reusable templates. They help ensure consistency across teams and projects. However, they are tools — not goals.
| Framework | Best For | Process | Ceremony |
|---|---|---|---|
| TOGAF | Large enterprises, regulated | ADM (step-by-step) | High |
| Zachman | Taxonomy & classification | None (classification only) | Medium |
| SAFe | Agile at scale | ART, PI Planning | High |
| Lean / Lightweight | Startups, small teams | ADR + C4 + Event Storming | Low |
TOGAF (The Open Group Architecture Framework)
Best for: Large enterprises, regulated industries, formal architecture teams.
TOGAF’s core is the ADM (Architecture Development Method) — a step-by-step process covering:
- Preliminary phase (framework setup)
- Architecture Vision
- Business, Data, Application, Technology architectures
- Opportunities and migration planning
- Governance
Pros: Comprehensive, widely recognised, vendor-neutral.
Cons: Heavy ceremony, can be slow, overwhelming for small teams.
Zachman Framework
Best for: Taxonomy and classification of architectural artefacts.
Zachman is a 6×6 matrix (six interrogatives × six perspectives) that categorises architectural descriptions. It doesn’t prescribe a process — just a way to organise thinking.
| Contextual | Conceptual | Logical | Physical | Detailed | |
|---|---|---|---|---|---|
| What | Inventory | Business entity | Data model | Schema | Records |
| How | Process list | Business flow | App logic | System design | Programs |
| Where | Locations | Business geography | Network | Topology | Addresses |
| Who | Org chart | Roles & responsibilities | Security | Access control | Identities |
| When | Events | Business cycle | Scheduling | Timing | Triggers |
| Why | Goals | Business strategy | Rules | Constraints | Decisions |
Pros: Excellent for ensuring coverage, useful as a checklist.
Cons: No process guidance, abstract, can feel academic.
SAFe (Scaled Agile Framework)
Best for: Organisations practising agile at scale.
SAFe includes architectural guidance within its Agile Release Train (ART) concept. Architects participate in PI Planning, define enablers, and guide Non-Functional Requirements.
Pros: Integrates architecture with agile delivery, practical ceremonies.
Cons: Prescriptive, can feel rigid, opinionated about team structure.
Lightweight Alternatives
For most teams — especially startups and mid-size companies — a full framework is overkill. Consider:
- ADR-first — capture decisions as lightweight Architecture Decision Records with no formal process
- C4 + Event Storming — use C4 for static structure and Event Storming for behavioural modelling
- Lean Architecture — just enough structure to align the team, evolved iteratively
Start with ADR + C4 diagrams. Add ceremony only when you feel the pain of not having it — not before. Most teams never outgrow lightweight approaches.
Choosing a Framework
Apply the CORE framework to framework selection itself:
| CORE Pillar | Question |
|---|---|
| Constraints | What governance, regulatory, or contractual requirements exist? |
| Outcomes | What problems are you actually trying to solve? |
| Risks | What happens without a framework? What if you adopt a heavy one? |
| Evolvability | Can you start light and add ceremony later if needed? |
In most cases, start with the lightest approach that provides enough structure and scale up only when the pain of not having more ceremony exceeds the pain of having it.