Please, I am reading about modular design in software, but I get a litle confused when the term "design decision" is used, especifically I am reading the book "A Philosophy of Software Design" by Ousterhout, John. This paragraph is confusing to me:
One of the most important techniques for achieving deep modules is information hiding. This technique was first described in a classic paper by David Parnas. The basic idea is that each module should encapsulate a few pieces of knowledge, which represent design decisions. The knowledge is embedded in the module's implementation but does not appear in its interface, so it is not visible to other modules.
Someone, please, knows what does it mean to hide design decisions in the context of software modularization? it is equivalent to implementation decisions? or something like that?
Thanks in advance.
