ArchiMate Relationships Part 2: The Composition Relationship in Aviation
Exploring the Composition relationship in ArchiMate through an airline’s departure process, detailing structural whole-part dependencies.
Tags
- enterprise-architecture 12
- aviation 12
- adr 10
- fitness-functions 10
- policy-as-code 10
- spec-driven-development 10
- agentic-engineering 10
- archimate 2
- solution-architecture 2
enterprise-architecture
ArchiMate Relationships Part 1: The Serving Relationship in Aviation
Starting a 10-part series on ArchiMate relationships, explained with practical, multi-layer aviation architecture examples.
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
aviation
ArchiMate Relationships Part 2: The Composition Relationship in Aviation
Exploring the Composition relationship in ArchiMate through an airline’s departure process, detailing structural whole-part dependencies.
ArchiMate Relationships Part 1: The Serving Relationship in Aviation
Starting a 10-part series on ArchiMate relationships, explained with practical, multi-layer aviation architecture examples.
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
adr
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
fitness-functions
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
policy-as-code
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
spec-driven-development
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
agentic-engineering
Enforceable Architecture Part 10: Putting It All Together — A Complete Pipeline
The final part of the series: how ADR-as-spec, fitness functions, policy-as-code, and review boards fit together into one working system.
Enforceable Architecture Part 9: Versioning Policies as Your Architecture Evolves
Architecture is not fixed forever. Part 9 shows how to change a rule safely, without breaking everything that depended on the old one.
Enforceable Architecture Part 8: Case Study — Catching a Layering Violation Before It Ships
A walkthrough of one violation, from the moment code is written to the moment a fitness function catches it.
Enforceable Architecture Part 7: CI/CD Gates for Architectural Compliance
Fitness functions and policies only matter if they actually run. Part 7 shows where to place them in the pipeline.
Enforceable Architecture Part 6: Building an Exception-Driven Review Board
Not every rule should be absolute. Part 6 shows how to build a fast, lightweight process for handling real exceptions.
Enforceable Architecture Part 5: Spec-Driven Development in the Agent Era
AI agents write code fast. Spec-Driven Development makes sure they write the right code, not just fast code.
Enforceable Architecture Part 4: Policy-as-Code — Rules That Apply Across the Whole Airline
One fitness function checks one rule. Policy-as-code lets you manage hundreds of rules across every team, consistently.
Enforceable Architecture Part 3: Fitness Functions — Automated Tests for Your Architecture
You already test your code. Part 3 explains fitness functions — the equivalent tests for your architecture.
Enforceable Architecture Part 2: ADR-as-Spec — Decisions a Machine Can Actually Check
Most Architecture Decision Records are just prose nobody re-reads. Part 2 shows how to turn them into specs a system can check.
Enforceable Architecture Part 1: Why Architecture Rules Die When Nobody Enforces Them
A rule that only lives in a wiki diagram is not really a rule. Part 1 of a 10-part series on enforceable architecture, with aviation examples.
archimate
ArchiMate Relationships Part 2: The Composition Relationship in Aviation
Exploring the Composition relationship in ArchiMate through an airline’s departure process, detailing structural whole-part dependencies.
ArchiMate Relationships Part 1: The Serving Relationship in Aviation
Starting a 10-part series on ArchiMate relationships, explained with practical, multi-layer aviation architecture examples.
solution-architecture
ArchiMate Relationships Part 2: The Composition Relationship in Aviation
Exploring the Composition relationship in ArchiMate through an airline’s departure process, detailing structural whole-part dependencies.
ArchiMate Relationships Part 1: The Serving Relationship in Aviation
Starting a 10-part series on ArchiMate relationships, explained with practical, multi-layer aviation architecture examples.