The course website doesn't give much details so feel free to view my website that details the course syllabus so you know exactly what you will be learning including UML, GRASP, Design Patterns, OO Metrics and more.
It takes the cognitive overhead off of the programming language completely and focus on design principles in a really modern learning style.
The tough part is the patterns that are used: https://en.wikipedia.org/wiki/Design_Patterns
Go buy that book and learn to read and understand enough c++ and small talk to read it cover to cover OR find examples in your favorite language.
This book is a trap, because it will take you a while to get out of the mindset of being "pattern happy" (maybe). There is plenty of material to follow up with afterwards to learn the downsides of each pattern, and when not to use them.
if, while, for, foreach, do, goto, and switch.
Implementing something as simple as a FizzBuzz solution under those constraints will be enough to understand OOP.
the main topics that one should learn are:
* some tidbit of history on why oop
* fundamental object oriented concepts: inheritance, encapsulation, and interfaces
* network of objects and their restricted interactions
* modeling a domain using objects
* documenting objects and their interactions
* how are objects represented in memory
* SOLID principles
* solutions (design patterns) to common problems
* concurrent design and thread safety in oop designs
* tools in oop design (CRC cards, UML, etc.)
* actually making projects and laying out the code in an implementation language.
Here are some books I seem to like so far.
Holger Gast - How to Use Objects: Code and Concepts (https://www.amazon.com/gp/product/0321995546)
This book seems to be what I was looking for. It has an integrated practical approach using the Eclipse source code as examples for various object oriented concepts. I have cross-checked various sources and it seems like this book covers all relevant concepts including SOLID principles.
Bertrand Meyer - Object-Oriented Software Construction
This seems to be a great reference. However, I haven't looked too thoroughly into it. I found a nice quote though.
"Today, no one will call security if one of the cocktail guests
declares object-oriented tastes. This is the buzzword effect, which
has been dubbed mOOzak: the omnipresence, in the computer press, of
O-O this and O-O that, causing a general dilution of the concepts.
The words flow so continuously from the loudspeakers — object,
class, polymorphism... — as to seem familiar, but are the concepts
widely understood? Often not." (29.1)
According to the Wikipedia article about him, he also created the idea of Design by Contract , involving preconditions, postconditions and invariants, and DbC is built-in to Eiffel. DbC is now supported in many languages or in their libraries.
Scott Ambler's The Object Primer was also good, also read some years ago.
IBM developerWorks article by him about the topic:
Just checked, it is still available, though the page at the link below says there is a newer version (linked on same page):
Update: Just remembered, when I was checking out Eiffel some years ago, I had read up on success stories about it. One very interesting one was about how HP used it to create a printer driver for a printer, after attempts using another more mainstream language had worked, but the driver had a lot of bugs. IIRC, the article  said that with Eiffel, the new version of the driver was created a lot faster, and also had a lot less bugs.
 Found the article from a Google search: