CSC/ECE 517 Fall 2009/wiki3 5 SD: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 4: Line 4:




The Dependency Inversion Principle(DIP) states that:
== Introduction ==
<ol>
<li>High-level modules should not depend on low-level modules. Both should depend on [http://en.wikipedia.org/wiki/Abstraction_(computer_science) abstractions].</li>
<li>Abstractions should not depend upon details. Details should depend upon abstractions.</li>
</ol>


<h3>Description</h3>
<h3>Description</h3>
In conventional application architecture, lower-level components are designed to be consumed by higher-level components which enable increasingly complex systems to be built. In this composition, higher-level components depend directly upon lower-level components to achieve some task. This dependency upon lower-level components makes applications rigid, fragile and immobile.
In conventional application architecture, lower-level components are designed to be consumed by higher-level components which enable increasingly complex systems to be built. In this composition, higher-level components depend directly upon lower-level components to achieve some task. This dependency upon lower-level components makes applications rigid, fragile and immobile.

Revision as of 04:07, 12 November 2009


Dependency inversion principle

Introduction

Description

In conventional application architecture, lower-level components are designed to be consumed by higher-level components which enable increasingly complex systems to be built. In this composition, higher-level components depend directly upon lower-level components to achieve some task. This dependency upon lower-level components makes applications rigid, fragile and immobile.

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2009/wiki3_5_SD&oldid=26683"