architect

To plan scalable software architecture, you define high-level component responsibilities, data models, API contracts, and integration patterns to guide feature planning and evaluate major design trade-offs.

Writing an Architecture Decision Record involves documenting decision rationale, trade-off analysis, and risk assessments for major design choices during system decomposition to reduce future rework.

Architectural reviews are needed during refactoring to evaluate system scalability, maintainability, and technology choices, ensuring proposed changes align with long-term design goals and minimize risk.

Evaluating technology trade-offs for system design requires understanding scalability planning and decision-making mechanisms to produce effective design proposals, component responsibilities, and risk assessments.

The best way to document API contracts and integration patterns is by generating high-level architecture designs that explicitly define component responsibilities and data models during feature planning.

High-level architecture design proposals focus on high-level component responsibilities and trade-offs, meaning they do not provide low-level implementation details or replace detailed code-level technical specifications.