06Stage 6 of 8 · Communication
How do decisions become understandable?
Here you capture decisions and architectural images in such a way that your team can continue to work with them.
You need
- Review findings and risks
- Compared options
Who
Product owner leads
with Payment module owner, Platform team
How to proceed
- 1
Document essential decisions and their reasons.
- 2
Choose suitable architectural views for those involved.
- 3
Discuss open points and consequences together.
In the shop
Record decisions for the shop
- ADR
- A modular application rather than independent services, with reasons and consequences.
- C4 view
- Context, the shop application and database as containers, then components.
- arc42
- Order goal linked to payment flow, rollout, ADR and restore risk.
- Open point
- The restore risk remains recorded and visible.
This creates
- ADRs
- Architectural description
- Common understanding
Tools for this:C4 modelSequence diagramDeployment viewarc42 architecture documentationAll under “Show & record” →
Done when
- Key decisions are recorded with their reasons in ADRs.
- Views match their respective stakeholders.
- Open points and consequences have been discussed together.
Appropriate Building Blocks
Documentation · ArtifactArchitecture Decision RecordAn Architecture Decision Record documents the context, rationale and consequences of a significant architecture decision.Documentation · ModelC4 modelThe C4 model explains system structure across suitable levels from context to code.Documentation · Templatearc42arc42 organizes requirements, views, decisions and risks in an architecture description.Fundamentals · ConceptArchitecture viewsArchitecture views explain a system from the perspective that answers a specific question.