CSC/ECE 517 Fall 2009/wiki3 3 cp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
==Introduction and Objective== | ==Introduction and Objective== | ||
According to [http://www.objectmentor.com/omTeam/martin_r.html | According to [http://www.objectmentor.com/omTeam/martin_r.html Robert Martin] the definition of Common Closure Principle is that | ||
"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 ?== | ==How to Implement Common Closure Principle ?== | ||
Revision as of 03:35, 18 November 2009
Common Closure Principle
Introduction and Objective
According to Robert Martin the definition of Common Closure Principle is that
"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."