cwp:system-architect

To translate product requirements into a technical architecture blueprint, provide a high-level product brief to generate an architecture document containing component diagrams, technology stack decisions, API contracts, and data models.

Designing system components and data models from a product brief involves transforming requirements into component boundaries and data flows. This yields an executive summary, component diagrams, and data structure outlines suitable for engineering teams.

Yes, you can evaluate and select a technology stack for client, server, and data layers. The architecture design process maps product requirements to suitable infrastructure and technology decisions across these system boundaries.

To define API contracts and payload schemas during system design, translate product requirements into endpoint specifications and data structures. This process generates comprehensive API specifications within the architecture documentation.

Yes, this architecture design approach works for both frontend and backend planning. It applies to designing system components across backend, frontend, and data layers to produce comprehensive technical blueprints.

From system architecture design, you should expect documentation outputs including an executive summary, system component diagrams, data model outlines, and API specifications that guide engineering implementation.