Click here to Skip to main content
11,929,166 members (45,182 online)
Click here to Skip to main content
Add your own
alternative version

Tagged as


17 bookmarked

Pillars of OOPS: Part 1 - Encapsulation

, 13 Sep 2012 CPOL
Rate this:
Please Sign up or sign in to vote.
I have covered here some basic information to achieve encapsulation.


In object oriented programming systems, we have lots of concepts which we have to think of when designing systems. A few of them are very important and a few of them are considered pillars of object oriented programming systems. Here I start with the first pillar of object oriented programming systems and that is encapsulation.


Encapsulation is the first pillar or principle of object-oriented programming. In simple words, “Encapsulation is a process of binding data members (variables, properties) and member functions (methods) into a single unit”. And Class is the best example of encapsulation.

Important points

  • Through encapsulation a class can hide the internal details of how an object does something. Encapsulation solves the problem at the implementation level.
  • A class or structure can specify how accessible each of its members (variables, properties, and methods) is to code outside of the class or structure. Encapsulation simplifies the interaction between objects. An object can use another object without knowing all its data or how its data is maintained. For example, a Client object might have name, address, company, and department properties. If a Bank object wants to use a Client object, it can request the name and address for the bank without needing to know the company and department details of the Client object.
  • With the help of encapsulation, a class can change the internal implementation without hurting the overall functionality of the system.
  • Encapsulation protects abstraction.

Need or purpose of encapsulation

  • To hide and prevent code (data) from the outside world (here the world means other classes and assemblies).
  • To prevent code (data) from accidental corruption due to programming errors so that we can deliver expected output. Due to programming mistakes, code may not behave properly and it has an effect on data and then it will affect the functionality of the system. With encapsulation we can make variables, properties, and methods private so it is not accessible to all but accessible through proper channels only to protect it from accidental corruption from other classes.
  • To have a class better control over its fields (validating values etc…).

Ways to achieve encapsulation with code example

We can achieve encapsulation by the following ways. Take a look at the methods to achieve encapsulation with code example:

  1. By using the get and set methods (Accessors and Mutators)
  2. public class Account
        private string accoutName;
        // get methods
        public string GetAccount()
            return accoutName;
        // Set method
        public void SetAccount(string name)
            accoutName = name;
    static void Main()
        string name ="SAVING_ACCOUNT";
        Account account = new Account();
        name = string.Empty;
        name = account.GetAccount();            

    In the above example we use the get and set methods (GetAccount and SetAccount) to return account and set account name. We use the private variable accountName and as it is not accessible directly, to use this variable, we use the get and set methods.

  3. By using properties (read only properties, write only properties)
  4. Like the above example we can achieve encapsulation using properties also.

    We can use a property (which has a get and set part), or we can use a read only property (which has only a get part) or we can also use a write only property (which has only a set part). But in all cases we can achieve encapsulation.

    Have a look at the following example using properties.

    // Encapsulation using properties 
    public class Account
        private string accoutName="SAVING_ACCOUNT";
        // property which has get and set
        public string AccoutName
                return accoutName;
                accoutName = value;
        private string address="India";
        // readonly property
        public string Address
                return address;
        private string phone = "1234567890";
        // writeonly property
        public string Phone
    static void Main()
        // Encapsulation using properties 
        string name = string.Empty;
        Account account = new Account();
        // call get part
        name = account.AccoutName;
        // change the value
        name = "CURRENT_ACCOUNT";
        // call set part
        account.AccoutName = name;
        string address = string.Empty;           
        // call readonly property 
        address = account.Address;
        // now address has value “India”
        string phone = "1234567890";
        // call writeonly property
        account.Phone = phone;
        // now account.Phone has value “1234567890”

    Here when we create a new instance of the account class, all the private variables in the account class (account name, address, and phone) are assigned with values. In the main class we can skip the variables (name, address, and phone) and directly use System.Console to write the output. I use the variables so that during debugging we can check how the values of the variables in the main class change after every call to the properties.

  5. Using an Interface
  6. Sometimes we can use an interface to implement encapsulation. Although the interface itself is a main concept or pillar in the object oriented programming system, I will show a simple sample here. Later on in the series, I will share a detailed example of an Interface.

    IAccount myAccount = new AsianAccount();
    IAccount myAccount = new EuropeanAccount();
    IAccount myAccount = new USAAccount();

    Now, based on the current location (for which we can have variables), whenever we want to view the balance information of a specific account, we can use the IAccount interface and we can see how AsianAccount, EuropeanAccount, and USAAccount hide information from each other, getting the balance details through the IAccount interface.

What’s next?

Encapsulation is the first pillar of object-oriented programming systems. I have covered here some basic information to achieve encapsulation. In the next series I will cover the second pillar of OOPS and that is abstraction.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Dharmesh Solanki, India
Software Developer (Senior)
India India
Dharmesh Solanki,
Ahmedabad, India

You may also be interested in...

Comments and Discussions

Questionrest of the oop concepts Pin
Alisha_Iqbal20-Apr-15 15:50
professionalAlisha_Iqbal20-Apr-15 15:50 
SuggestionNice Article Pin
Ankit Nanglia19-Mar-15 19:51
memberAnkit Nanglia19-Mar-15 19:51 
GeneralMy vote of 1 Pin
RsaBrother's21-Oct-14 4:09
memberRsaBrother's21-Oct-14 4:09 
GeneralMy vote of 3 Pin
testingdemo12320-Mar-13 2:40
membertestingdemo12320-Mar-13 2:40 
GeneralMy vote of 1 Pin
Shelke Amit11-Dec-12 18:55
memberShelke Amit11-Dec-12 18:55 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.151126.1 | Last Updated 13 Sep 2012
Article Copyright 2012 by Dharmesh Solanki, India
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid