Domain Models

From Zanecorpwiki

As domain models mature, they better approximate the objective reality (as far as such a thing can be said to exist). As such, the models tend to unify as they mature.

Immature domains will be populated by many locally useful but largely disjoint models. The local models are naturally incomplete, and often wrong in some objective way--in-so-far as they describe something as other than it actually is--but they often continue to be useful.

This phenomenon is widespread. In science, for instance, we use Newton's model of gravity despite the fact that it's incorrect. There are multiple overlapping and disjoint theories describing the natural forces which have to some extent and are expected by many to continue to approach something like a unified theory. In software engineering there are many security modules such as roles, ACLs, etc. which are largely unified by a AOTref group=notesAOT is the actor/operation/target class of models./ref

These domains are quite fluid and can be viewed through numerous lenses. We have a plethora of personal apps for scheduling, todo, budgets, etc. These could be viewed as each touching a different domain, but there is a larger domain of personal organization and a lot to be gained from integration. One can therefore expect that over time these applications will be unified under an umbrella domain.

Notes

references group=notes /