Solution architecture and design
Define components, integrations, data, security and deployment, and record the key decisions.
- Use when
- Any IT solution; depth grows with integrations, data and non-functional risk.
- Avoid when
- Non-IT projects.
- Source
- ISO/IEC/IEEE 42010; Simon Brown (C4)
- Level
- A · standard
For agents · MCP
explain_node({ "id": "p.solution_architecture" })