2 ms·
Yes, I only think you can even talk about a domain model if there actually is some kind of world (real or imaginary) or some collection of entities to model.
by henning 19y ago
Yes, I only think you can even talk about a domain model if there actually is some kind of world (real or imaginary) or some collection of entities to model.
- gruseom 19y agoThis is a good point. When you're building a model of X, your design is guided by asking questions about X and getting consistent answers to them. This works if X exists separately from the model and is stable and coherent. But when these assumptions don't hold, the same techniques can easily produce a design that is arbitrary and complicated.
- gruseom 19y agoBy the way, do you know the book Domain-Driven Design? I think it is the most sophisticated book on OO and domain modeling. But I also think that it's straining beyond OO toward a design style that is not really about object models, but rather about how to create a good language for talking about one's problem. (The application then reduces to a series of statements in that language.) Lisp programmers would be comfortable with this distinction. In the book it's obscured by the fact that the examples are in Java.