Encapsulation in Object Oriented Programming


Encapsulation in Object Oriented Programming

Encapsulation is one of the four fundamentals of the Object oriented programming.

What is Encapsulation?

Encapsulation is a language mechanism to restrict the access of the Objects components to other Objects or Classes. 
Encapsulation helps in enforcing the security of the data related to a particular object. In the programming models like Structural, procedural and Modular programming, there was not much provision to safeguard the data from the other procedures or functions. This can lead to the misuse of data or even the design by responsibility principle of OOAD can be some times breached.
Every Object in Object oriented programming has full control of what members(Fields and methods) to be accessible to its peers in a package, outside the package and should only be visible to its own members alone.
Encapsulation in Object Oriented Programming is implemented by mentioning the Access Modifiers like public, protected, private and default access.
The access to the data  and methods can be restricted to a package, classes level etc.,

Encapsulation with Example

Let me explain the concept of Encapsulation with an example.  Say, you are a student in a class and some of the things you and your friends know, say nick names, should not be revealed to the professors, your parents does not have knowledge of you not attending the classes or poor performance in a subject etc.,
In our own life, we would like to shield/share some information to a group of people. In the same fashion, object as instances of a class has full control of its members. 
When a class is created and its members are defined, the access modifiers are applied to its fields and methods.
When an object is created using that particular class, the access will be restricted based on the defined access of the members.
Encapsulation is nothing but hiding the features that are not relevant for other objects but are essential for their own features.
For Example, I have create a class Car which has two methods:
Encapsulation in Oops
  1. move().
  2. internalCombustion()
The move method depends on internalCombustion() method. But an Employee needs only move method and need not be aware of internalCombustion behavior. So, the internalCombustion behavior can be declared private so that it can be only visible to the members inside the class.

Summary:

Encapsulation is a primary fundamental principle in Object oriented programming. It is used to enforce the security to restrict the visibility of the members to other components. 

Comments

Post a Comment

Popular posts from this blog

Approval Process

Image
Salesforce: Approval Process - Who can approve ? To build an approval workflow in Salesforce is simple, since Salesforce provide  Approval Processes . You can find this under  Setup  -  Create  -  Workflow & Approvals  -  Approval Processes . In early blogs, we have discussed about  Serial and Parallel Approval  in Salesforce, in this blog, we would like to discuss in depth option of users can approve? Manager Approval In the approval process  Step 3. Specify Approver Field and Record Editability Properties , there is option to determine next automated approver. Notice that  Next Automated Approver Determined By  is not a mandatory field here. Option available here: Manager   - a standard field in user object and has no relation with Role Hierarchy All custom fields in user object with type = Hierarchy - in above sample: Boss and Sales Director. If you select  Manager  as in above screenshot, when you set up Approval Step, in  Step 3. Select Assigned Approv
Read more

Spring Batch 2.0 -Basic Concepts

There is always a healthy debate when talking Java and batches. When I heard  Spring Batch , I had to try it out.  On a previous project, many eons back, I did some batch processing in Java. What hurt me there (after a lots of optimizations) was a call to another persons module. His module happily loaded up an entity bean. You can guess where that ended. Next release I went through the code and replaced the entity bean calls with ONE update SQL statement. That fixed things. I was processing 200k records in 15-20 minutes, with an extremely small memory footprint. Even this I could reduce further if I tuned another module. But the performance was deemed enough and we moved on. What I personally felt from that experience was the need of a decent Java-based Batch processing framework. Of course having this does not mean use Java for batches. Sometimes for bulk processing doing it in the database may be the right approach. In this blog I want to go over Spring Batch processing. We wi
Read more

Sending Mass Emails From Salesforce

Image
Create a Email Template  Then you either go to the Lead Tab or the Contact Tab and scroll down the page until you see the Mass Email link in the Tools section. On the first step of the mass email wizard is to create your target list. To do this you have the option of leveraging an existing View that is available on the Leads tab, or you can create a new View from within the wizard. In this example we will create our target list from within the wizard by clicking the   Create New View   link. In my example I’m   creating a quick View   to grab any Lead that is in the State of California. Notice in Step 2 of the View you can use a Campaign to filter (handy if your Campaign has your target list as Campaign Members!). Remember you have governor limits based on your edition (see paragraph two of this blog posts). If you’re running Professional Edition for example, and your View pulls more than 250 records, you’ll need to add additional filters to your View to reduce the
Read more