CSC/ECE 517 Fall 2009/wiki1b 13 zz: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Bob Martin's Stable Dependencies Principle says, "The dependencies between packages should be in the direction of the stability of the packages. A package should only depend upon packages that are more stable than it is." | Bob Martin's Stable Dependencies Principle says, "The dependencies between packages should be in the direction of the stability of the packages. A package should only depend upon packages that are more stable than it is." | ||
=Bob Martin= | |||
[http://today.java.net/pub/au/90 Robert C. Miller] defines the domain of [http://www.objectmentor.com/resources/articles/Principles_and_Patterns.pdf design patterns] to be the architecture of systems modules (packages, classes and components) and their interconnections. His design patterns address the four major reasons for failure of the systems: rigidity, fragility, immobility and viscosity [http://www.objectmentor.com/resources/articles/oodmetrc.pdf]. | |||
Following are the list of few design principles quoted by him to avoid the pitfalls associated with unsuccessful software engineering, | |||
[http://labs.cs.utt.ro/labs/ip2/html/lectures/5/lecture5.ppt Reuse/Release Equivalence Principle] | |||
[http://iface.wordpress.com/2006/04/08/common-closure-principle/ Common Closure Principle] | |||
[http://www.objectmentor.com/omSolutions/oops_what.html Common Reuse Principle] | |||
[http://ifacethoughts.net/2006/04/10/acyclic-dependencies-principle/ Acyclic Dependencies Principle] | |||
[http://www.objectmentor.com/resources/articles/stability.pdf Staple Dependencies Principle] | |||
[http://ifacethoughts.net/2006/04/20/stable-abstractions-principle/ Stable Abstraction Principle] | |||
Revision as of 17:09, 15 November 2009
Bob Martin's Stable Dependencies Principle says, "The dependencies between packages should be in the direction of the stability of the packages. A package should only depend upon packages that are more stable than it is."
Bob Martin
Robert C. Miller defines the domain of design patterns to be the architecture of systems modules (packages, classes and components) and their interconnections. His design patterns address the four major reasons for failure of the systems: rigidity, fragility, immobility and viscosity [1].
Following are the list of few design principles quoted by him to avoid the pitfalls associated with unsuccessful software engineering, Reuse/Release Equivalence Principle Common Closure Principle Common Reuse Principle Acyclic Dependencies Principle Staple Dependencies Principle Stable Abstraction Principle