OOPs simply explained

What is OOPs ? It is Object Oriented Programming. It comprises of

  1. Polymorphism
  2. Encapsulation
  3. Inheritance
  4. Abstraction

Already lost me ? Now here it is read about OOPs as if you deal with it every day. Let’s take at OOPs from a Corporate world point of view. There is an organization which comprises of several employees which form a hierarchy.

Now every employee has their way of working, some work hard, some like to delegate and some are smart. Though everyone does work in office, they do it in their own way. This is Polymorphism (implementing a function differently while keeping the semantics of function same).

Employees are after all humans, we all have secrets. We have our own perspective which we may or may not share with everyone i.e. we have state and behavior only accessible to us. We share some of our secrets with our closest friends, some of our perspective to a group of people depending upon our status. In the end we do keep everything close and private, nothing is visible clearly to the outer world. This is Encapsulation (state are private variables and most of the behavior is in protected methods, objects share state and behavior only through methods which again have access modifiers for better control).

Inheritance is simple. We all are employees, we all get salary on the end of month, we all have performance ratings, performance bonus payouts. We all are subjected to rules and regulations of organization. We all have to live by certain norms designed for employees. This all behavior is inherited by us because we are employees.

Abstraction sounds tricky especially if we compare it to encapsulation. First let me clear what abstraction is. So we all work in teams, a team is associated with a project. Each project originates from a client. Now not everyone on the team is in direct communication with client. Client just hands over the requirements to a point of contact, a Manager or Sales guy and then expects a product at the end of the deadline. We as team work on the requirements, follow some processes but all of this is abstracted away from client. He just gets one contact to pass on the parameters and how those parameters are used and end product is achieved does not matter; hence Abstraction. If you look at encapsulation, it is more focused on each object while abstraction is seen from the point of orchestration of functionality which is usually achieved by interaction between multiple objects.

Advertisements

One thought on “OOPs simply explained

  1. Great analogy!!
    Encapsulation, however, I like to think of as the capsuling of the related states and behavior together into a single unit. And **because of that capsuling (encapsulation)**, all of that you explained(data hiding and all) becomes possible.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s