Why has OOAD succeded as an analysis and design methodology?

Today, when it comes to analysis and design of software systems, the first thing that comes to mind is OOAD.

Why is OOAD so popular?

There were many Systems Analysis and Design methodologies that came in. We had structured Systems Analysis and Design (SSAD) wherein DFDs and ER diagrams were basically a part of it. It survived for around 4-5 years.

After that OOAD came into picture. And since then whenever you think about Analysis and Design of systems, OOAD is the first thing that comes to mind. There are many Frameworks, Patterns and languages that are following the OOAD concepts.

What is so special OOAD that it has nearly become a standard today when it comes to systems analysis and design?

The earlier Analysis and Design methodologies that were there were also able to represent systems and automate systems. But there is something different and special about OOAD that it is so popular.

Let's go back to the definition of Software systems. A software system is an automated system which is supposed to automate the complexities of the real world system using the hardware in its most optimal form.

One of the reasons why OOAD as a methodology has succeeded is because OOAD allows you to model the real world in its most natural form.

The most important part is that it is able to do it in its most natural form. Earlier also there were analysis and design methodologies that came in and they were able to represent the systems, but the problem was they were not able to do it as naturally as OOAD.

In some later articles we will see that the only difference between a real world system and a system which is object oriented is that in one system you deal with physical location and in the other one you deal with memory locations. This is the only difference. Otherwise most of the concepts are just the same.

Hemant Jha
Founder - VPlanSolutions
Researcher, Trainer