OOMD

[OOMD]
Object-Oriented Modeling and Design
Rumbaugh & al

General opinion
In the name of pragmatism, misses some the main ideas which make
object orientation:
- the unicity of the conceptual framework all along the development
  cycle (Note:
 conceptual tool.)
- the openness of the problems, resulting into clear-cut ph
- it proposes a "methodology" (Note:
 methodology.) based on
  semantics poorer than these supported by C++.
- it tries and integrate methodologies based on relational databases
  and finite state machines, without noticing that they are
  incompatible with object-orientation.

2.1.1, p 16

Abstraction is the selective examination of certain aspects of a
problem. The goal of abstraction is to isolate those aspects that are
important for some purpose and suppress those aspects that are
unimportant. Abstraction must always be for some purpose, because the
purpose determines what is important and what is unimportant.

[...]

In building models, [...], you must not search for absolute truth but
for adequacy to some purpose. There is no single "correct" model of a
situation, only adequate and inadequate ones.


15.7.4, p 320 Strong Typing Versus Weak Typing

Strong typing [...] serves two purposes.  [It] provides active support [...]
in detecting [errors].  [It] also increases opportunities for optimization.
[...] No power is lost by the use of strong typing [...]

Modern programming language theory has been evolving in the direction of
strong type checking.  Much of the advances in programming language theory
have derived from restricting the programmer's ability to perform dangerous
operations.  [...] Strong typing improves the reliability of delivered
software.