Architecture Principle: [Short Name]
| Field | Value |
|---|---|
| ID | AP-[number] |
| Domain | Enterprise / Business / Data / Application / Technology |
| Owner | [Role] |
| Status | Proposed / Approved / Retired |
| Effective date | YYYY-MM-DD |
| Review date | YYYY-MM-DD |
Statement
[One unambiguous rule.]
Rationale
[Why the enterprise adopts this principle and which outcomes or risks it addresses.]
Implications
Business and organization
- [Required behavior, cost, ownership, or operating impact]
Data and applications
- [Required behavior, constraint, or investment]
Technology and operations
- [Required behavior, standard, or lifecycle impact]
Governance
- [How conformance is demonstrated and who can approve an exception]
Examples
Conformant
[Concrete example.]
Non-conformant
[Concrete example.]
Related material
- Goals/outcomes:
- Policies/standards:
- Related principles:
- Known exceptions: