software-architecture-review

To conduct a software architecture review, execute Discovery, Analysis, and Recommendations phases to evaluate components and generate a review file. The process requires access to codebase structure, design docs, and test suites to surface smells and produce actionable mitigations.

An architecture review process for complex systems applies Discovery, Analysis, and Recommendations phases to enforce repeatable, evidence-based decisions. It systematically handles smells, patterns, and trade-offs to reduce risk and guide design improvements.

Yes, an architecture review can find scalability risks in your system design by analyzing components for modularity and performance issues. The optional Adversarial mode actively surfaces gaps, generating a risk register with actionable mitigations.

For a codebase architecture analysis, you need to provide access to your codebase structure, design docs, and test suites. These inputs enable the evaluation of modularity, performance, and reliability across system components.

To evaluate architectural trade-offs and code-quality patterns, apply the Analysis phase which systematically handles smells and patterns with reference-guided suggestions. This process yields documentation-first artifacts like risk registers and actionable mitigations.

Use Adversarial or Enrichment modes for an architecture review when you need to extend coverage and surface gaps in existing reviews. Adversarial mode challenges findings, while Enrichment mode deepens analysis of complex system components.