4. Taming the Beast Named Complexity
Modularity is not a new concept. In his 1972 paper “On the Criteria to Be Used in Decomposing Systems into Modules,” David Parnas cited the work of Gouthier and Pont as the first lucid statement of modular programming (1972):
A well-defined segmentation of the project effort ensures system modularity. Each task forms a separate, distinct program module. At implementation time each module and its inputs and outputs are well-defined, there is no confusion in the intended interface with other system modules. At checkout time the integrity of the module is tested independently; there are few scheduling problems in synchronizing the completion of several tasks before checkout can begin. Finally, the system is maintained ...
Get Java Application Architecture: Modularity Patterns with Examples Using OSGi now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
