The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.06 - November/December (2003 vol.20)
pp: 96-98
ABSTRACT
<p>One of the most important things about good design is modularity?dividing a system into separate pieces so that you can modify one module without the changes rippling all over the system. As David Parnas observed, modules should be arranged around system secrets, each module hiding its secret from the others. Then if the secret thing changes, you avoid a ripple effect.One of the most common secrets to hide these days is data structures. This column discusses guidelines for basic data hiding. The examples all use objects, but the arguments apply just as well to non-OO modules.</p>
CITATION
Martin Fowler, "Data Access Routines", IEEE Software, vol.20, no. 6, pp. 96-98, November/December 2003, doi:10.1109/MS.2003.1241375
19 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool