What's OO?

Nowadays almost every programmer knows about the Object-Oriented Analysis/Design. But I think only a few among us know what OO really is actually.

Why? Most treat OO as a kind of trash-packaging work, which means they cannot establish the appropriate modeling to present a precise description to the use case, while they just pack what they want to be together into a model concept -- some shouldn't be put together, or even abstracted.

A good OO design should stand for the essence of the target issue, should hit the very point of the problem to solve. It's not easy. You should be prepared with a pair of smart eyes to observe through the surface appearance without being blocked by the meaningless trivals.

This is why "the highest level of C++ is the OO technique", as one of the most senior engineer in my group said.