Models, Models everywhere ...

When you're working in a domain there can be many models on which you base your domain model. The domain model must reflect a proper balance of the various models a user sees (although it may all appear as one to them).

In our project we have three or four models, each competing with one another.

The Gui model reflects how users want to do data entry and control the workflow.

The Physical model reflects the "things" are users are performing accounting on (in this case, our things are wells and meters and oil and gas...)

The Accounting model reflects how they report on those activities. e.g. converting what really went on into ownership and taxes and revenues. Then telling the government all about it.

Our Domain model must reflect an appropriate space that allows all three of the things to be easy - as well as allowing for ease of development.