Thanks George.

It’s true, I don’t disagree with what you say here. Here’s all I am trying to say:

I always learned the “modeling first” approach to OO design. And even today, no matter which language I use, I do pretty much always model my domain concepts with types in that language. However, what I don’t normally hear from the “modeling first” approach is, what do I do about all that other code I have to write but that has no manifestation in the domain?

It sounds like your answer is that most of the infrastructure code for your average programmer already exists in the form of libraries and frameworks. This is probably true.

All I can say is that my experience from using this approach often lead to designs where non-domain functionality, like display for instance, would get lumped in with the domain classes, since domain decomposition didn’t really tell me where this stuff needed to go.

Thanks bro.
Nels