The term information hiding used in this thread is very confusing (to me, at least). I believe David Parnas introduced it in 1971 to mean that a program's desi

The term information hiding used in this thread is very confusing (to me, at least). I believe David Parnas introduced it in 1971 to mean that a program's design was sliced along shared units of concerns (things that vary together) rather than "steps in a flowchart". https://prl.ccs.neu.edu/img/p-tr-1971.pdf https://prl.ccs.neu.edu/img/p-tr-1971.pdf I believe what you are trying to convey is called "data abstraction", as for example used by Reynolds, 1975; mentioned here: https://www.cs.utexas.edu/~wcook/papers/OOPvsADT/CookOOPvsADT90.pdf https://www.cs.utexas.edu/~wcook/papers/OOPvsADT/CookOOPvsAD... explained here: https://link.springer.com/chapter/10.1007%2F978-1-4612-6315-9_22 https://link.springer.com/chapter/10.1007%2F978-1-4612-6315-...