Principle Block
Document architecture principles that guide design decisions. Capture the rationale, implications, and exceptions for each guiding principle.
Architecture principles are fundamental guidelines that inform design decisions across a system or organisation. Unlike constraints that limit choices, principles provide direction for choosing among alternatives. Well-documented principles help teams make consistent decisions without constant escalation.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Statement | Yes | The principle being established, expressed as a clear guideline |
| Description | No | Detailed explanation of what the principle means |
| Scope | No | Level of applicability: organisation-wide, platform, system, or component |
| Applies To | No | What this principle applies to (services, APIs, data, etc.) |
| Rationale | No | Why this principle was adopted |
| Implications | No | What following this principle means in practice |
| Exceptions | No | When this principle does not apply |
| Examples | No | Concrete examples of applying the principle |
| Status | No | Current state: proposed, adopted, or deprecated |
| Review Date | No | When to re-evaluate the principle |
| Notes | No | Additional context or observations |
Scope Values
Status Values
Example: Security Principle
An organisation-wide security principle that affects all service design.
Example: Data Principle
A platform-level principle governing data ownership.
Example: Technology Principle
A principle guiding technology selection for new projects.
Example: Integration Principle
A system-level principle for API design.