software-architecture-review

Software architecture review evaluates system design trade-offs, boundaries, and risks. You need it for new system evaluations, major refactors, and architecture health checks across codebases to guide reliable system evolution.

Perform an architecture review using a three-phase process: Discovery to collect findings, Analysis to identify coupling hotspots and failure modes, and Recommendations to generate an updated review document with prioritized issues.

Yes, the architecture review process applies to major refactors. It evaluates dependency boundaries, data flow, and design trade-offs to produce a central design-review artifact with a concise summary for stakeholders.

The best way to document architecture risks is generating a REVIEW_FILE during the evaluation. This artifact captures prioritized findings, boundary violations, and a final summary to communicate design issues to stakeholders.

No, architecture review requires no specific frameworks or dependencies. It provides a disciplined framework applicable across codebases to surface design trade-offs and potential failure modes without external tooling.