Before going in to discuss what is OOAD, we have to understand how we 'think' usually.

While there could be many thinking that exists before OO, it is very common to think in procedural oriented way as that was the latest development before OO has come to party.

So what is that thinking and what is the procedural way, a short recap:

As the software development happens only when there is a requirement, let us take some requirement.

Let us take the example of coffee maker.

What is Object Oriented Analysis and Design?

Martin Fowler in his book "UML distilled" says you will one day realize that you have got the Object Oriented thinking in you. And I have realized the same!

Its a Paradigm which you will get in you without knowing that you have got it!

Someone who has done programming in a procedural oriented programming in college, student project or in early part of their career will tend to think in the same until the turning point moment comes. You cannot know when the turning point moments comes in your life and that exactly true, you cannot tell when you will get the OO thinking in you.

But once you start thinking in OO, you need to grow it so that you keep yourself in it as there is every chance that we may slip from it and go back to procedural oriented. 

When we discuss so much about Object Oriented, we have to mention here that programming in procedural oriented is NO sin. Procedural programming has it own servings, it's own audience and satisfies the requirement of its purpose.

So what makes OO interesting?