Some design decisions have an impact on the trajectory of the whole project.

Modeling is most needed in complex circumstances, yet the typical dynamics of large projects too often derail it or disconnect it from the real design. A related issue: modeling is best carried out by small, dynamic teams with a lot of autonomy, yet creating large systems requires coordination and project-spanning decisions. Managers and developers alike need to pay close attention to this intersection of design, project organization, and politics. This tutorial will introduce them to a suite of techniques for that purpose.

First, distilling a shared vision of the system's core and the roles of its parts can focus development effort on real business assets, and tell when 'good enough good enough' versus when to push for excellence.

Then, "context mapping" addresses a vital fact of life: different groups model differently. Ignoring these realities leads to dumbed-down models and costly, buggy integrations, and disruption of project plans where they depend on other teams.

Objectives: Awareness of the factors that endanger the ambitions of a complex software project and the tools DDD provides for dealing with them

Format: Combines lecture, reenactment of typical scenarios, and discussion.