System Architect

System architecture design translates functional and non-functional requirements into a complete technical blueprint, including component boundaries, data models, APIs, and technology stack justification. Start with your PRD and use architecture design to define these elements before development begins, preventing costly rework.

Technology stack selection balances non-functional requirements like performance, security, and scalability against project constraints. Architecture design validates each choice against specific NFRs, documenting trade-offs and ensuring the stack supports both functional needs and long-term maintainability.

Architecture validation performs gate checks against both functional and non-functional requirements, mapping each to design decisions and architectural patterns. This ensures traceability between requirements and architecture components, catching gaps before implementation.

Significant redesigns warrant architecture review when non-functional requirements shift—scalability, security, or performance demands increase—or when component boundaries no longer align with business needs. Architecture design guides the redesign process end-to-end with documented trade-off analysis.

Yes. Architecture design explicitly addresses security and scalability as non-functional requirements, selecting patterns and technologies that satisfy them. Each architectural decision includes justification tied to these NFRs.

Architecture design produces comprehensive architecture documents including component definitions, data models, API specifications, technology justifications, and traceability matrices linking all decisions back to functional and non-functional requirements.