architect

Software architecture design defines the structure of software components before implementation. You need a structured decision process for one-way-door structural changes and large-scale complex architectures to ensure stakeholder agreement on the direction before coding begins.

To design a new module architecture, sketch and visualize module boundaries and classmethod signatures. Document the structural decisions in a design file like 'dev-notes/design/design.md' to record the agreed-upon direction for stakeholders.

Yes, you can visualize module boundaries, classmethod signatures, and fields before writing implementation code. Visualizing components helps stakeholders agree on the architecture direction and prevents non-trivial design errors during development.

The best way to facilitate decision-making for complex software architecture is using a structured framework that visualizes components and documents structural choices. This ensures stakeholders agree on one-way-door changes before implementation starts.

Yes, software architecture design applies specifically to large-scale and complex architectures. It provides a structured framework for visualizing components and making non-trivial structural decisions, requiring stakeholder input and documentation tools.

You should avoid using a structured software design process for trivial tasks that do not involve one-way-door structural changes. It is specifically built for large-scale complex architectures and non-trivial design tasks requiring stakeholder agreement.