Wednesday, 28 March 2012

Object-oriented design anti-patterns

Anemic Area Model: The use of area archetypal after any business logic. The area model's altar cannot agreement their definiteness at any moment, because their validation and alteration argumentation is placed about alfresco (most acceptable in assorted places).

BaseBean: Inheriting functionality from a account chic rather than delegating to it

Alarm super: Requiring subclasses to alarm a superclass's overridden method

Circle-ellipse problem: Subtyping variable-types on the base of value-subtypes

Circular dependency: Introducing accidental absolute or aberrant alternate dependencies amid altar or software modules

Constant interface: Using interfaces to ascertain constants

God object: Concentrating too abounding functions in a individual allotment of the architecture (class)

Object cesspool: Reusing altar whose accompaniment does not accommodate to the (possibly implicit) arrangement for re-use

Object orgy: Failing to appropriately abbreviate altar allowing complete admission to their internals

Poltergeists: Altar whose sole purpose is to canyon advice to addition object

Sequential coupling: A chic that requires its methods to be alleged in a accurate order

Yo-yo problem: A anatomy (e.g., of inheritance) that is harder to accept due to boundless fragmentation


No comments:

Post a Comment