entity perspectives


context:
so, i am attempting build ridiculously challenging domain model. articulate users, there churned ways component used (for example: proceed outlook employee; another proceed outlook employer). actuality, churned applications reusing core domain.



question:
wrong emanate domain churned perspectives? instance, build domain business run meant formulating kinds charge classes lift additional information entity on... however, controlling sole perspective, settlement many clearer since many charge classes rolled progenitor entity.



ideas? rebuttals? am i totally off-base?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

using mvc, should hoop communication between views? between models?