OO as a Form of Modular Programming

The above subject is discussed in Bertrand Meyer,
"Object-Oriented Software Construction," Second
Edition, 1997, Chapter 3, "Modularity".

I have omitted much of the text in order to support
and emphasize the points I have raised recently.
OO [Design] is modular programming, and
Modular programming is design methods.

"Modular programming was once taken to mean the
construction of programs as assemblies of small pieces,
usually subroutines. But such a technique cannot bring
real extendibility and reusability benefits unless we have
a better way of guaranteeing that the resulting pieces
-- the modules -- are self-contained and organized in
stable architectures. ...

"A software construction method is modular, then, if it
helps designers produce software systems made of
autonomous elements connected by a coherent, simple
structure. ... The focus will be on design methods, but
the ideas also apply to earlier stages of system construction
(analysis, specification) and must of course be maintained
at the implementation and maintenance stages.

"... This chapter introduces a set of complementary
properties: five criteria, five rules and five principles of
modularity which, taken collectively, cover the most
important requirements on a modular design method.

"... The discussion will lead in a later chapter to the O-O
form of module -- the class -- ..."

-----

Found on the internet, some time ago:

C++ is the only current language making
COBOL look good. -- Bertrand Meyer



.