Apply SWEBOK v4 Software Design: turn requirements/architecture into module- and component-level design. Use whenever the user is doing high-level or detailed design, applying design principles (coupling/cohesion, information hiding, SOLID-style ideas), choosing a design method (OO, structured, DDD, event-driven, component-based), recording structural/behavioral design, or asks about "design", "projeto de software", "design pattern", "acoplamento", "coesão", "diagrama de classes" — not only when SWEBOK is named.
