JavaZone 2009 - Anemic domain models: diagnosis, causes, effects and possible treatments
Object-orientation has been the mainstream programming language paradigm for the last 20 years. One of the central techniques in object-oriented programming is encapsulation using objects that both contain data and behavior. Nevertheless, in real applications we tend to end up with anemic domain models as opposed to "proper" domain models, where we have objects that only have data and no behavior, or vice versa. In many cases this results in a procedural style of programming, rather than an object-oriented style, not leveraging the language's features. Encapsulation suffers, possibly resulting in tight coupling in the application. In this talk I will try to give some reason why this happens, which problems this causes, and possible ways to avoid it.
Vidar Kongsli
Vidar Kongsli works as a developer and architect at Bekk Consulting AS. He has a long experience developing enterprise solutions based on Microsoft .NET, Java, and Lotus Domino. Additionally, he is currently focusing on agile development, (automated) testing, and quality assurance.