CSC/ECE 517 Fall 2009/wiki3 1 kp

Anti-patterns

Software design anti-patterns

Object-oriented design anti-patterns

• Anaemic Domain Model

Separating the business logic from the Domain Model is termed as Anaemic Domain Model.One of the prime reason for it being popular is, it provides separation of logic and data. To site few places this is used are Java's Entity beans and .Net's three layered service application. A short example for Anaemic Model is given below,

 class BankAccnt {
   private double balance;
   public double getBalance() {
   return balance;
 }
 public void setBalance(double balance) {
   this.balance = balance;
 }  
 class AccntService {
   public void debit(Account account, double amount) {
   account.setBalance(account.getBalance() - amount);
  }
 } 

Although, the above code looks right by providing segration of data and service, its in violation of OOP principle of data and behaviour encapsulation.It could lead to problems when there are muliple type of accounts and some of them have overdraft protection, then debit method has to check for accoount type.This can be corrected by moving the behaviour (debit method) into BankAccnt Class.