Object-oriented design anti-patterns

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
(Started page about OO anti patterns)
 
Line 3: Line 3:
 
The following are common object-oriented design anti patterns:
 
The following are common object-oriented design anti patterns:
  
*[[Anemic Domain Model]]  
+
*[[Anemic Domain Model]] - This anti pattern occurs when data and behavior is separated in the domain model.
*[[BaseBean]]
+
*[[BaseBean]] - This anti pattern occurs when inheritance of implementation is used; that is a class inherits from another class not because it makes sense semantically but because it wants to use methods defined in the superclass.
*[[Call super]]
+
*[[Call super]] - This anti pattern occurs when a superclass requires derived classes to call an overridden method.
*[[Circle-ellipse problem]]
+
*[[Circle-ellipse problem]] - This anti pattern occurs when inheritance is not used correctly and the [[Liskov substitution principle is violated]].
 
*[[Circular dependency]]
 
*[[Circular dependency]]
 
*[[Constant interface]]
 
*[[Constant interface]]

Revision as of 05:08, 18 July 2009

Object-oriented design anti patterns describe bad design solutions to common problems. As such, they are essentially the opposite of conventional design patterns.

The following are common object-oriented design anti patterns:

Many of these anti patterns are closely related to common design maxims.

See also

Personal tools