Our clients don't know what they need.
This happens due to the fact that no 1 can foresee the future.
Requirements will evolve and change rapidly over the lifecycle of the project. That's why we request to constantly refine systems.
We can keep building and discarding prototypes, but it's highly costly.
Often we can't afford to rewrite everything from scratch only due to the fact that any fresh domain insights were discovered.
This yet leads to a mismatched model.
Is there another way?
We can focus on domain only and refine our model through examples, until we find the right conceptual contours (http://ddd.fed.wiki.org/view/welcome-visitors/view/conceptual-contours).
Each specified iteration of the model is simply a kind of experimentation challenging the upfront decisions.
During this presentation I'm going to show how you can usage example mapping combined with business-oriented TDD to be able to run fast experiments straight on the domain model, without a request to rewrite the strategy again.
Website: https://jdd.org.pl
Facebook: https://www.facebook.com/JDDconf
Twitter: https://twitter.com/JDD_Krakow
