understanding object orientation concepts

When I was in uni, I had issues with object orientated languages. Mostly because of my prior procedural training in COBOL and C. Hence Java was a pain. The hardest part of OO was having to deliberately erase what you already know about procedural languages.

Thankfully, my occupation only required system administration skills. After downloading and installing the Eclipse IDE, I decided to give OO another shot. Thanks to time, I've totally forgotten how to code hence its almost like starting fresh.

Believe it or not, it all makes sense to me now, also being able to see the benefit not only from a programming persepective, but also from a business and process point of view. If anyone had issues with configuration management for application maintenance, extracting classes and objects can potentially define your configuration items (CI).

Of course the granularity can be determined on how far up or down the hierachy you want to go. So in esscence, the terminology and approaches aren't too far different.

I suppose another explaination of object orientation from a musican's point of view can be done with the association of Apple's garage band application. Sounds categories are like the classes and the actual sound objects are associated with each class, similar to directory structures, except that each object can inherit attributes from different classes.

e.g. a electronic beat is both has drum class attributes and electronic class attributes.

How easy is that?