Inversion of Responsibility

Encyclopedia : I : IN : INV : Inversion of Responsibility

To meet Wikipedia's and make it more accessible to a general audience, this article may require [Cleanupcleanup].
The introduction to this article provides insufficient context for those unfamiliar with the subject matter.
Please help Wikipedia by improving the introduction according to the guidelines laid out at [Guide to layout]. You can discuss the issue on the .

Please [Glossary#Wwikify] (format) this article or section as suggested in the [Guide to layoutGuide to layout] and the [Manual of StyleManual of Style].
Remove this template after wikifying. This article has been tagged since April 2006.

In OO design we typically design from top(abstract) to down(concrete) and the dependency flow from top to bottom. In other words abstract classes depend on concrete classes.By refactoring we can change the dependency flow from concrete to abstract.This is termed as inversion of dependency or Responsibility.

Simple Java example

public class InversionOfResponsibility
public void println(java.io.PrintStream printStream)

public static void main( String[] args )

NOTE: This article is probably referring to the concept of Inversion of Control, as it is more commonly known [link].

From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.