The wheel has turned full circle.
In 1988, I wrote a textbook entitled Software Engineering. Virtually the only
mention of the object-oriented paradigm in that book was one section that described
object-oriented design.
By 1994, the object-oriented paradigm was starting to gain acceptance in the
software industry, so I wrote a textbook called Classical and Object-Oriented
Software Engineering. Six years later, however, the object-oriented paradigm
had become more important than the classical paradigm. To refl ect this change,
I switched the order of the two topics in the title of the textbook I wrote in 2000,
and called it Object-Oriented and Classical Software Engineering.
Nowadays, use of the classical paradigm is largely restricted to maintaining
legacy software. Students learn C++ or Java as their fi rst programming language,
and object-oriented languages are used in subsequent computer science and
computer engineering courses. Students expect that, when they graduate, they will
work for a company that uses the object-oriented paradigm. The object-oriented
paradigm has all but squeezed out the classical paradigm. And that is why I have
written a textbook entitled Object-Oriented Software Engineering.