Abstract
As I explained in the introduction to the package design principles, all programmers develop a sense of “belonging together”. But next to this intuition with regard to cohesion, programmers also have a nose for coupling. Looking at a piece of code, they will be able to figure out what it is coupled to. As their careers progress, they will develop an ever stronger “coupling radar” by figuring out the actual dependencies of any piece of code.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
Robert C. Martin, Engineering Notebook, C++ Report, Nov-Dec, 1996 (PDF available on http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod ).
- 2.
Erich Gamma e.a., Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley, 1994.
- 3.
Erich Gamma e.a., Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley, 1994.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Matthias Noback
About this chapter
Cite this chapter
Noback, M. (2018). The Acyclic Dependencies Principle. In: Principles of Package Design. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4119-6_9
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4119-6_9
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