# Architecture review checklist (arc42)

> Instructions and checks for reviewing a software architecture document that follows the arc42 template. Read this file first. Fetch linked pages only when you need more detail.

## How to review

1. Read the user's architecture document completely.
2. Fetch the checklist page of each arc42 section (links below). Each page lists the checks for one section.
3. If the document does not follow arc42, first map its content to the arc42 sections and say so.
4. For each arc42 section, apply every check. Result per check: OK, ISSUE, MISSING (information is absent), or N/A (give a reason).
5. Fetch a linked concept page only when a result is ISSUE or unclear, or the user asks why.
6. Report per section: check, result, evidence (quote or location in the user's document), suggested fix, and the concept link for each ISSUE.
7. End with the three most important improvements, in priority order.
8. Do not invent requirements that are not in the checklist or in the linked pages.

## Pages

- [1. Introduction and Goals](https://arc.fuet.ch/review/arc42-01.md): Requirements overview, top quality goals, stakeholders
- [2. Architecture Constraints](https://arc.fuet.ch/review/arc42-02.md): Technical, organizational and regulatory constraints
- [3. Context and Scope](https://arc.fuet.ch/review/arc42-03.md): Business and technical context, external interfaces
- [4. Solution Strategy](https://arc.fuet.ch/review/arc42-04.md): Fundamental decisions and solution approaches
- [5. Building Block View](https://arc.fuet.ch/review/arc42-05.md): Static decomposition into building blocks
- [6. Runtime View](https://arc.fuet.ch/review/arc42-06.md): Behavior of building blocks in important scenarios
- [7. Deployment View](https://arc.fuet.ch/review/arc42-07.md): Technical infrastructure and mapping of building blocks to it
- [8. Cross-cutting Concepts](https://arc.fuet.ch/review/arc42-08.md): Concepts that apply to many building blocks
- [9. Architecture Decisions](https://arc.fuet.ch/review/arc42-09.md): Important, expensive, risky decisions with rationale
- [10. Quality Requirements](https://arc.fuet.ch/review/arc42-10.md): Quality tree and quality scenarios
- [11. Risks and Technical Debts](https://arc.fuet.ch/review/arc42-11.md): Known risks and technical debt
- [12. Glossary](https://arc.fuet.ch/review/arc42-12.md): Important domain and technical terms
- [Guides](https://arc.fuet.ch/guides/llms.txt): step-by-step help to create missing parts