CSC/ECE 517 Fall 2009/wiki3 3 cp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Common Closure Principle == | == Common Closure Principle == | ||
==Introduction and Objective== | |||
According to [http://www.objectmentor.com/omTeam/martin_r.html Bob Martin's ] Common Closure Principle states, | According to [http://www.objectmentor.com/omTeam/martin_r.html Bob Martin's ] Common Closure Principle states, | ||
"Classes within a released component should share common closure. That is, if one needs to be changed, they all are likely to need to be changed. What affects one, affects all." | "Classes within a released component should share common closure. That is, if one needs to be changed, they all are likely to need to be changed. What affects one, affects all." | ||
==How to Implement Common Closure Principle ?== | |||
====Java Example==== | |||
====Ruby Example==== | |||
==What are the advantages and disadvantages?== | |||
==Reading Recommendations== | |||
==Reference Books== | |||
== External Links == | == External Links == | ||
[http://www.objectmentor.com/omTeam/martin_r.html Bob Martin's ] | [http://www.objectmentor.com/omTeam/martin_r.html Bob Martin's ] | ||
==Appendix== | |||
Revision as of 03:29, 18 November 2009
Common Closure Principle
Introduction and Objective
According to Bob Martin's Common Closure Principle states,
"Classes within a released component should share common closure. That is, if one needs to be changed, they all are likely to need to be changed. What affects one, affects all."