Skip to main content

Decisions for Software Design and Architectures

Decisions is the practice of documenting architecture so reasoning survives team changes. It uses architecture decision records for individual choices, lightweight diagrams for structure and living documents kept in version control, so future maintainers understand what was decided, which options were rejected and why.

Stage: Practice · Part of the Software Design and Architecture roadmap · Last reviewed 19 November 2026

What to learn in Decisions

Decisions interview questions

Why record rejected alternatives in a decision record?

They show what was considered and why it lost, which stops the team re-debating the same options and helps later readers judge whether the reasoning still holds when conditions change.

How do you keep architecture documentation from going stale?

Keep it small, store it beside the code, generate diagrams from source where possible, review it in pull requests, and document decisions and reasons rather than details that change often.

Where Decisions fits in the Software Design and Architecture roadmap

Decisions belongs to the Practice stage (advanced level). Decide and evolve.

Back to the full Software Design and Architecture roadmap