I am reading "Patterns, Principles, and Practices of Domain-Driven Design" by Scott Millett and Nick Tune and so far it has been a great read (first 2 chapters read) but one term they seem to use a lot and appears to have a fairly abstract meaning is the term "model". They talk about developing a model using domain knowledge captured by things like Event Storming and Impact Mapping, but what exactly is a "model"? My best guess is its really the aggregation of your business model (rules and processes that business stakeholder see as requirements of the business) and your analysis model (logic and processes of the software itself) along with probably even more conceptual things, but I am unsure.
Could someone give me an example of what "defining your model" would mean in the world of DDD? Also, when the author says "model" I assuming he means "domain model"... but again I could be wrong.
Any clarification on what this is to any degree would be very helpful. Thanks