3. –R. Gauthier and S. Pont, Designing Systems Programs, 1970.
“Each task forms a separate, distinct program
module. At implementation time each module
and its inputs and outputs are well-defined. At
checkout time the integrity of the module is
tested independently. Finally, the system is
maintained in modular fashion.”
4. –D. Parnas, On the Criteria to Be Used in Decomposing Systems into
Modules, 1972.
“The major advancement in the area of
modular programming has been the
development of coding techniques and
assemblers which
(l) allow one module to be written with
little knowledge of the code in another
module, and
!
(2) allow modules to be reassembled and
replaced without reassembly of the whole
system.”
5. –R.S. Fabry, How to design a system in which modules can be changed on
the fly, 1976.
If the module does manage permanent
data structures which must be modified
and the system is one which is expected to
continue operation throughout the
change, the problem is more difficult, but
it can be solved. This paper discusses a
solution.