Software design consists of activities that modify current software systems into preferred ones. These activities usually produce a plan containing design decisions. section 3.1.3
Design is unavoidable, whether decisions are explicit or implicit. Collaborative modeling makes assumptions visible, brings different perspectives together, and reduces ambiguity that otherwise creates workarounds and accidental complexity. section 3.1 section 3.0
Use software design as a collaborative practice:
- Start from a shared model of the business problem before choosing a solution. section 3.0
- Invite stakeholders to challenge assumptions and contribute their knowledge. section 3.1
- Facilitate decisions rather than imposing designs; teach teams to run modeling sessions independently. section 1.2.5
- Define ambiguous terms, record important decisions, and revisit models as feedback changes understanding. section 3.1.1 section 11.3
BigScreen’s move toward a preferred system
BigScreen first models its current situation with the group’s perspectives and knowledge. It then uses design activities to plan changes toward a preferred system, including boundary decisions that may reshape its architecture. section 3.1.3
Not every design decision is architectural. Architecture is the subset of design decisions that changes the system’s foundational shape; localized changes without broader ripple effects need not receive architectural treatment. Design quality also depends on social and cognitive conditions, including disagreement, power, bias, and resistance. section 3.1.3 section 1.2.5
