Common reuse principle
From CSSEMediaWiki
(Difference between revisions)
(New page: From {{Ref|1}}: <blockquote> [It] is very important to decide which classes should be bound together by a package. Improper selection of classes can create unwanted dependencies and turn u...) |
|||
Line 6: | Line 6: | ||
==References== | ==References== | ||
#{{Note|1}} http://iface.wordpress.com/2006/04/05/common-reuse-principle/ | #{{Note|1}} http://iface.wordpress.com/2006/04/05/common-reuse-principle/ | ||
+ | |||
+ | ==See Also== | ||
+ | *[[Common closure principle]] |
Revision as of 07:06, 5 October 2008
From [1]:
[It] is very important to decide which classes should be bound together by a package. Improper selection of classes can create unwanted dependencies and turn usage of that package into a nightmare. [The] Common Reuse Principle (CRP) lays down a good foundation to determine which classes should be packaged together: The classes in a package are reused together. If you reuse one of the classes in a package, you reuse them all. It says that only cohesive classes should be packaged together. As with everything, the packaging of classes and the cohesiveness should be defined from the user’s perspective. If a user uses a package, all the classes in that package should be reusable in the same context.