|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Martin Fowler, "Module Assembly," IEEE Software, vol. 21, no. 2, pp. 65-67, March/April, 2004. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2004.1270764, author = {Martin Fowler}, title = {Module Assembly}, journal ={IEEE Software}, volume = {21}, number = {2}, issn = {0740-7459}, year = {2004}, pages = {65-67}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2004.1270764}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Module Assembly IS - 2 SN - 0740-7459 SP65 EP67 EPD - 65-67 A1 - Martin Fowler, PY - 2004 KW - linkage KW - modularity KW - hiding KW - implementation VL - 21 JA - IEEE Software ER - | |||
When people talk about modularity, they usually focus on separating the interface and implementation. The whole of point of a module is that it should hide a secret in its implementation that isn?t apparent from the interface. A user can then take advantage of what the module does without knowing all the gory details of its implementation.
Index Terms:
linkage, modularity, hiding, implementation
Citation:
Martin Fowler, "Module Assembly," IEEE Software, vol. 21, no. 2, pp. 65-67, March-April 2004, doi:10.1109/MS.2004.1270764
Usage of this product signifies your acceptance of the Terms of Use.

