bd-solution-architect

To design system architecture, you can generate architecture overviews, component designs, and database architectures. This process structures your platform by translating quality criteria into system-specific components, regardless of whether you use microservices or a modular monolith.

An Architecture Decision Record (ADR) captures the why behind architectural choices. You need ADRs to document decisions when evaluating styles like Clean Architecture or Hexagonal, ensuring your team understands the rationale behind structural choices.

Defining quality attribute scenarios involves specifying and assessing testability, modifiability, and scalability metrics. This skill translates these attributes into system-specific fitness functions to evaluate your architecture against desired quality benchmarks.

Yes, you can evaluate microservices versus a modular monolith by designing architecture overviews for both. This skill helps you compare options by documenting the decision in an ADR and defining quality attribute scenarios for each approach.

Yes, this approach supports Clean Architecture and Hexagonal design patterns. It evaluates and produces architecture regardless of style, adapting criteria to system-specific components for your chosen pattern.

The best way to document architectural fitness functions is to specify them as concrete scenarios that validate quality attributes. This skill defines these functions to continuously verify modifiability, testability, and scalability during system evolution.