What are the advantages/disadvantages you've found over event storming? Is this just a good way to knowledge crunch with stakeholders to get to a good analysis model, or do you find it leads to specific learnings you don't get with any other method?
Interesting! With a domain model like this, a program could exhaustively test all paths for invalid states. The model would need to some annotations of invariants or could ask a human to review.<p>I highly recommend Eric Evans' book "Domain-Driven Design: Tackling Complexity in the Heart of Software" (2003) mentioned on this page. It is a bit of slog, but worth it.<p>Or for a quick introduction to domain-driven design, check out the (free download) of "Domain Driven Design Quickly" e-book from InfoQ:<p><a href="https://www.infoq.com/minibooks/domain-driven-design-quickly" rel="nofollow">https://www.infoq.com/minibooks/domain-driven-design-quickly</a>
We changed the URL from <a href="https://github.com/WPS/domain-story-modeler" rel="nofollow">https://github.com/WPS/domain-story-modeler</a> to the project page, which gives more background info.
Very useful, I find that discovering domain knowledge can be a painful process when trying to build a relationship with a new client. Hopefully this will help