This page contains my personal notes taken while reading the book Domain Driven Design by By Eric Evans.
Chapters Synthesis
Part I: Putting the Domain Model to Work
In this chapter it is pointed that models are the representation of a reality, not the reality itself. As world maps are made in a way that seems to have bigger and smaller countries that in reality (depending on what is important to put in evidence), so do models: as the author says they are an interpretation of a reality which abstracts relevant information to solve a problem and ignore needless details.
Furthermore, domain is explained as “Every software program relates to some activity or interest of its user. That subject are to which the user applies the program is the ‘domain’ of the software.”
So for a developer to effectively build a software that actually solves user problem, it is required to build proper knowledge about the software domain, which can comprehend a huge amount of information and for that reason only vital information should be considered.
For that, the author explains the “crunching knowledge”, which we can put in simple terms: sit down with business expert, explore and really understand what is important for them, and for the issue you are required to solve, sometimes even help they understand what is they actually need.
This should be done as soon as possible, so that we can develop a prototype binding model and implementation and collect user feedback.
~This is a work in progress :).