oma-architecture

To document software architecture decisions with explicit tradeoffs, you generate an Architecture Decision Record (ADR) that captures assumptions, risks, validation steps, and a source-grounded recommendation comparing materially different boundary options.

Choosing between a monolith and service extraction requires a design-twice comparison of module boundaries and ownership tradeoffs. You evaluate quality attributes and apply cost/benefit framing to determine if decomposition is justified.

Prioritize refactoring investments by applying CBAM-style cost and benefit analysis to your architecture. This frames each potential refactor as an investment, weighing the architectural risks against the expected quality attribute improvements.

You need ATAM-style risk analysis for module boundaries when evaluating tradeoff-heavy architectural choices. It clarifies whether a system design issue is truly an architectural problem and identifies quality attribute risks through scenario analysis.

No, this focuses on comparing materially different boundary and ownership approaches rather than superficial variations. It uses diagnostic routing to select the lightest sufficient method for evaluating your software architecture options.

Yes, architecture diagnosis clarifies whether your concern is genuinely an architecture problem before analysis. It routes the issue to the lightest sufficient method, preventing unnecessary evaluation of non-architectural system design concerns.