In programming, there are a lot of thought processes, object oriented happens to be the most popular of them, but there are other equally challenging processes like functional, which aim to reduce verbosity in OO processes. Then why this book is required at a time when object oriented thinking has matured enough already.
How does this book then stand out, especially due to presence of books already in this subject like 'Object Oriented Design in java'?
There are certainly many different thought processes when it comes to programming. The first edition of the book was in the development process just as the initial version of Java was being released. I was doing Java training at the time and realized that many people were under the impression that structured and object-oriented programming were mutually exclusive. I don't agree with that. I contend that structured programming techniques are actually encapsulated with object-oriented design. Thus, they work together.
The real question is whether or not you start teaching programming with object concepts first or structured constructs like variables, loops, conditions, etc.
The intent of the Object-Oriented Though Process is to look at programming from a higher level and use the structured constructs to help teach the object concepts such as encapsulation, polymorphism, composition and inheritance.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com