Principles of Package Design
Principles of Package Design
Preparing your code for reuse
About the Book
In Principles of Package Design Matthias Noback tells you everything about designing software components, also known as packages. In the first part you'll revisit the SOLID principles of class design. They will help you prepare your classes for use in packages. The second part covers the important, yet lesser known package design principles. When you've finished this book, you'll be ready to design packages that have high cohesion, low coupling and are at the same time user- and maintainer-friendly.
This book has been revised and then republished by Apress. From now on you can order it from them: https://www.apress.com/us/book/9781484241189
- The situation
- Overview of the contents
- Notes about the code samples
- Thank you
- SOLID principles
- Why follow the principles?
- Prepare for change
The Single responsibility principle
- A class with too many responsibilities
- Responsibilities are reasons to change
- Refactoring: using collaborator classes
- Advantages of having a single responsibility
- A small peek ahead: common closure
The Open/closed principle
- A class that is closed for extension
- Refactoring: abstract factory
- Refactoring: making the abstract factory open for extension
- Refactoring: polymorphism
- Packages need classes that are open for extension
The Liskov substitution principle
- Violation: a derived class does not have an implementation for all methods
- Violation: different substitutes return things of different types
- Violation: a derived class is less permissive with regard to method arguments
- Violation: secretly programming a more specific type
The Interface segregation principle
Violation: leaky abstractions
Refactoring: create separate interfaces and use multiple inheritance
- What did we do?
- Refactoring: create separate interfaces and use multiple inheritance
Violation: multiple use cases
- Refactoring: separate interfaces and multiple inheritance
Violation: no interface, just a class
- Implicit changes in the implicit interface
- Refactoring: add header and role interfaces
- Violation: leaky abstractions
The Dependency inversion principle
Example of dependency inversion: the FizzBuzz generator
FizzBuzzclass open for extension
Removing the specificness from the
- Making the
Violation: a high-level class depends upon a low-level class
- Refactoring: abstractions and concretions both depend on abstractions
Violation: a class depends upon a class from another package
- Solution: add an abstraction and remove the dependency using composition
- Peeking ahead: abstract dependencies
- Example of dependency inversion: the FizzBuzz generator
Principles of cohesion
- Becoming a programmer
- The hardest part
- Class design principles benefit cohesion
- Package design principles, part I: Cohesion
The Release/reuse equivalence principle
- Keep your package under version control
- Add a package definition file
Use semantic versioning
Design for backward compatibility
Rules of thumb
- Don’t throw anything away
- When you rename something, add a proxy
- Only add parameters at the end and with a default value
- Methods should not have side effects
- Dependency versions should be permissive
- Use objects instead of primitive values
- Use private object properties and methods for information hiding
- Use object factories
- And so on
- Rules of thumb
- Design for backward compatibility
Add meta files
- Installation and configuration
- Extension points
- Limitations (optional)
- Change log
- Quality from the user’s point of view
What the package maintainer needs to do
- Add tests
The Common reuse principle
Signs that the principle is being violated
- Obvious stratification
- Obfuscated stratification
Classes that can only be used when … is installed
- Suggested refactoring
- A package should be “linkable”
- Cleaner releases
- Suggested refactoring
- Feature strata
- Guiding questions
- When to apply the principle
- When to violate the principle
- Why not to violate the principle
- Signs that the principle is being violated
The Common closure principle
A change in one of the dependencies
A change in an application layer
A change in the business
- The tension triangle of cohesion principles
- A change in one of the dependencies
Principles of coupling
The Acyclic dependencies principle
Coupling: discovering dependencies
Different ways of package coupling
- Not to be considered: global state
- Visualizing dependencies
- Different ways of package coupling
The Acyclic dependencies principle
- Nasty cycles
Cycles in a package dependency graph
- Dependency resolution
- Release management
- Is it all that bad?
Solutions for breaking the cycles
- Some pseudo-cycles and their dissolution
Some real cycles and their dissolution
- Dependency inversion
Inversion of control
- Chain of responsibility
- Mediator and chain of responsibility combined: an event system
- Coupling: discovering dependencies
The Stable dependencies principle
- Not every package can be highly stable
- Unstable packages should only depend on more stable packages
- Measuring stability
- Decreasing instability, increasing stability
Violation: your stable package depends on a third-party unstable package
- Solution: use dependency inversion
- A package can be both responsible and irresponsible
The Stable abstractions principle
- Stability and abstractness
How to determine if a package is abstract
- Abstract things belong in stable packages
- Abstractness increases with stability
- The main sequence
Types of packages
- Concrete, instable packages
- Abstract, stable packages
- Strange packages
Creating packages is hard
- Embracing software diversity
- Component reuse is possible, but requires more work
Creating packages is doable
- Reducing the impact of the first rule of three
- Reducing the impact of the second rule of three
- Creating packages is easy?
- Creating packages is hard
- Principles of cohesion
Appendix I: The full
- Appendix I: The full
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
C++ Best PracticesJason Turner
Level up your C++, get the tools working for you, eliminate common problems, and move on to more exciting things!
Continuous Delivery PipelinesDave Farley
This practical handbook provides a step-by-step guide for you to get the best continuous delivery pipeline for your software.
OpenIntro StatisticsDavid Diez, Christopher Barr, Mine Cetinkaya-Rundel, and OpenIntro
A complete foundation for Statistics, also serving as a foundation for Data Science.
Leanpub revenue supports OpenIntro (US-based nonprofit) so we can provide free desk copies to teachers interested in using OpenIntro Statistics in the classroom and expand the project to support free textbooks in other subjects.
More resources: openintro.org.
C++20 is the next big C++ standard after C++11. As C++11 did it, C++20 changes the way we program modern C++. This change is, in particular, due to the big four of C++20: ranges, coroutines, concepts, and modules.
The book is almost daily updated. These incremental updates ease my interaction with the proofreaders.
Atomic KotlinBruce Eckel and Svetlana Isakova
For both beginning and experienced programmers! From the author of the multi-award-winning Thinking in C++ and Thinking in Java together with a member of the Kotlin language team comes a book that breaks the concepts into small, easy-to-digest "atoms," along with exercises supported by hints and solutions directly inside IntelliJ IDEA!
Introductory Statistics with Randomization and SimulationMine Cetinkaya-Rundel, Christopher Barr, OpenIntro, and David Diez
A complete foundation for Statistics, also serving as a foundation for Data Science, that introduces inference using randomization and simulation while covering traditional methods.
Leanpub revenue supports OpenIntro, so we can provide free desk copies to teachers interested in using our books in the classroom.
More resources: openintro.org.
Ansible for DevOpsJeff Geerling
Ansible is a simple, but powerful, server and configuration management tool. Learn to use Ansible effectively, whether you manage one server—or thousands.
Java OOP Done RightAlan Mellor
Object Oriented Programming is still a great way to create clean, maintainable code. But only if you use it right.
This book gives you 25 years of OO best practice, ready to use.
You'll learn to design objects behaviour-first, use TDD to help, then confidently apply Design Patterns, SOLID principles and Refactoring to make clean, crafted code.
Introducing EventStormingAlberto Brandolini
The deepest tutorial and explanation about EventStorming, straight from the inventor.
Discrete Mathematics for Computer ScienceAlexander Shen, Alexander S. Kulikov, Vladimir Podolskii, and Aleksandr Golovnev
This book supplements the DM for CS Specialization at Coursera and contains many interactive puzzles, autograded quizzes, and code snippets. They are intended to help you to discover important ideas in discrete mathematics on your own. By purchasing the book, you will get all updates of the book free of charge when they are released.
Software Architecture for Developers: Volumes 1 & 2 - Technical leadership and communication
2 Books"Software Architecture for Developers" is a practical and pragmatic guide to modern, lightweight software architecture, specifically aimed at developers. You'll learn:The essence of software architecture.Why the software architecture role should include coding, coaching and collaboration.The things that you really need to think about before...
CCIE Service Provider Ultimate Study Bundle
2 BooksPiotr Jablonski, Lukasz Bromirski, and Nick Russo have joined forces to deliver the only CCIE Service Provider training resource you'll ever need. This bundle contains a detailed and challenging collection of workbook labs, plus an extensively detailed technical reference guide. All of us have earned the CCIE Service Provider certification...
Cisco CCNA 200-301 Complet
4 BooksCe lot comprend les quatre volumes du guide préparation à l'examen de certification Cisco CCNA 200-301.
Modern C++ by Nicolai Josuttis
CCDE Practical Studies (All labs)
3 BooksCCDE lab
"The C++ Standard Library" and "Concurrency with Modern C++"
2 BooksGet my books "The C++ Standard Library" and "Concurrency with Modern C++" in a bundle. The first book gives you the details you should know about the C++ standard library; the second one dives deeper into concurrency with modern C++. In sum, you get more than 600 pages full of modern C++ and about 250 source files presenting the standard library...
2 BooksDocker and Kubernetes are taking the world by storm! These books will get you up-to-speed fast! Docker Deep Dive is over 400 pages long, and covers all objectives on the Docker Certified Associate exam.The Kubernetes Book includes everything you need to get up and running with Kubernetes!
Modern Management Made Easy
3 BooksRead all three Modern Management Made Easy books. Learn to manage yourself, lead and serve others, and lead the organization.
The Future of Digital Health
6 BooksWe put together the most popular books from The Medical Futurist to provide a clear picture about the major trends shaping the future of medicine and healthcare. Digital health technologies, artificial intelligence, the future of 20 medical specialties, big pharma, data privacy and how technology giants such as Amazon or Google want to conquer...
Django for Beginners/APIs/Professionals