Abstract
In the previous chapter, we discussed the Common Reuse principle. It was the second principle of package cohesion and it told us that we should put classes in a package that will be used together with the other classes in the package. If a user wants to use a class or a group of classes separately, this calls for a package split.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Robert C. Martin, Engineering Notebook, C++ Report, Nov-Dec, 1996 (PDF available on http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod ).
- 2.
https://www.phptherightway.com/#databases
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
Eric Evans, Domain-Driven Design, Addison-Wesley Professional (2003)
- 11.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Matthias Noback
About this chapter
Cite this chapter
Noback, M. (2018). The Common Closure Principle. In: Principles of Package Design. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4119-6_8
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4119-6_8
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4118-9
Online ISBN: 978-1-4842-4119-6
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books