CSC/ECE 517 Fall 2009/wiki3 3 cp
Common Closure Principle
In simple words the Common Closure Principle refers to classes that change topether, belong together, this is a very simple definition taken from the book Java Design: Objects, UML and Process written by Kirk Knoernschild.
A more explained definition of Common Closure Principle, given by Robert Martin, is
THE CLASSES IN A PACKAGE SHOULD BE CLOSED TOGETHER AGAINTS THE SAME
KINDS OF CHANGES. A CHANGE THAT AFFECTS A PACKAGE AFFECTS ALL THE
CLASSES WITHIN THAT PACKAGE.
See Granularity PDF Article written by Robert Martin for more details
In other words, what affects one, affects all broader and detailed explanations are given in this wikiwork.
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."