So time again for some education. This time I took the Domain Driven Design Immersion course that is held by Patrik Fredriksson (@weakreference) from Citerus.
I try to make a summery of the course here in my blog on a day to day basis.
Last day, today we are going to talk about supple design and look at a reference implementation. We are also going to discuss about documentation and wrapping up with some general discussion.
- Making implicit rules explicit
- Extending the ubiquitous language to enable supple design
What implicit words can be made explicit?
Explicit rules through richer ubiquitous language
- Tighter service contract
- Invariants in objects and aggregates
- Define stakes for entities and aggregates
What documentation does DDD require/produces.
Context maps can be used to display the current state of the system.
SAD (Software architecture document) can be used to describe the design, techniques and the architecture. A good document to show new persons in the project, but it is still the code that is the truth.
- Show reference scenarios
- Flow diagram
Sample DDD application documentation
Sample DDD application code
Disclaimer: This is my notes and my interpretation of the information. I can really recommend going the course.