While TOGAF provides the overarching enterprise structure, specific solution designs require tactical frameworks to ensure technical excellence, scalability, and agility.
This framework provides a consistent set of strategies and best practices for designing and evaluating cloud architectures. It moves away from heavy documentation and focuses on 6 Pillars:
Why it suits Solution Design: It provides concrete checklists and "Lenses" that help architects validate if their specific solution is production-ready.
Similar to the AWS version, this WAF framework is a set of guiding tenets used to improve the quality of a workload. It focuses on 5 Pillars: Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency.
Why it suits Solution Design: It is deeply integrated with the Azure Advisor and Assessment tools, allowing architects to get real-time, automated feedback on their solution design.
Created by Simon Brown, the C4 model is a lean graphical notation technique for modeling software architecture through hierarchical diagrams:
Why it suits Solution Design: It eliminates "wall of text" documentation by allowing architects to explain a solution to different stakeholders by simply "zooming" in or out.
Poka-Yoke is a methodology within Lean Manufacturing focused on preventing human errors in processes or making them immediately detectable before they result in defects. The concept assumes that mistakes are inevitable, but systems can be designed to either eliminate the possibility of error or quickly identify it. The ultimate objective is to achieve near-zero defects without relying on end-of-line inspection, by embedding quality directly into the process.
Poka-Yoke methods typically include contact methods (detecting deviations in shape, size, or color), fixed-value methods (ensuring a specific number of actions are completed), and motion-step methods (enforcing correct process sequence). These techniques are widely used in manufacturing industries such as automotive and electronics, as well as in logistics, supply chain operations, and software systems (e.g., input validation, workflow enforcement). They are also embedded in everyday products to enhance safety and usability.
In terms of solution architecture Poka-Yoke manifests as design patterns and guardrails, and scalable digital workflows with built-in error-proofing, manifested as discrete design principles (example).
The IASA model (found in the BTABoK — Business Technology Architecture Body of Knowledge) is a value-driven engagement framework rather than a rigid step-by-step process. While frameworks like TOGAF focus on "how to document the enterprise," IASA focuses on "how the architect delivers value."
IASA organizes architecture around five core competencies:
The Engagement Model: This is the "active" part of the methodology. It defines how architects interact with stakeholders throughout the product lifecycle. It emphasizes Continuous Architecture—integrating design decisions directly into Agile/DevOps loops rather than waiting for a formal "architecture phase."
Structured Canvases: To keep it "lightweight," IASA uses visual tools (like the Architecture Decision Record or Value Management canvases) to capture critical information quickly on a single page, replacing hundreds of pages of traditional documentation.
In an Agile context, architecture is built incrementally. It focuses on the Architectural Runway, the technical foundation that enables business features to be implemented quickly.
Why it suits Solution Design: It avoids "Big Design Up Front" (BDUF), ensuring the architecture remains flexible as business requirements change.