How much realistic should be a model in domain driven design?

Mohammad Rahmani Published at Dev

Mohammad Rahmani

In Eric Evans book on domain driven design it is written:

Domain modeling is not a matter of making as “realistic” a model as possible. Even in a domain of tangible real-world things, our model is an artificial creation. Nor is it just the construction of a software mechanism that gives the necessary results.

Now I have two questions:

Should a model be designed somehow that it could evolve to a more realistic shape whenever NEEDED without touching the core model in previous iteration?
If the answer to the previous question is positive, where can I learn how to create realistic core models?
Again if the answer to the question one is possible, would a day come that our model reflects any problem in the world?

Dariss

Domain Model should not reflect real world. It should only show one point of view depending on the context.

Let's say we got a glass.

One may think, well it's a glass and we can fill it with water. It is used to drink.
Other may think, well it's a product and we can sell it.
Another one may say, glass an inventory item. I don't care how does it looks like, but how many glasses I got here.

Depending on the context, we model glass differently. Still it is the same glass, but means something else.

All information related to the subject you can find on Udi Dahan's blog.
And more in the subject of modeling reallity, can be found here Don’t try to model the real world, it doesn’t exist.

Collected from the Internet

Please contact [email protected] to delete if infringement.