Define basic principle of object oriented programming.

Object-oriented programming (OOP) is a way of organizing and designing code based on the idea of objects. Here's a simple explanation of its basic principles:

Objects: In OOP, everything is treated as an "object." An object is like a mini-program that contains both data (information) and functions (actions) that can operate on that data. For example, you can have an object called "Car" that stores information like its color, make, and model, and can also perform actions like "start," "stop," and "accelerate."

Classes: Objects are created from "classes." Think of classes as blueprints or templates for objects. Going back to the "Car" example, the class defines what a car is and what it can do. You can create many individual car objects from this one class.

Encapsulation: Encapsulation means bundling together the data (attributes) and functions (methods) that operate on that data within an object. It's like putting everything related to a concept, such as "Car," in one box. This helps in organizing and controlling access to the data, which can improve security and maintainability.

Inheritance: Inheritance allows you to create a new class based on an existing class. This new class inherits the properties and behaviors of the existing class. For example, you can have a general "Vehicle" class and create more specific classes like "Car" and "Motorcycle" that inherit from the "Vehicle" class. This saves you from repeating code and promotes code reuse.

Polymorphism: Polymorphism means that objects of different classes can be treated as objects of a common superclass. This allows you to write code that can work with objects from different classes as long as they share a common interface. For instance, you can have a method that takes a "Vehicle" object as an argument, and it can work with both "Car" and "Motorcycle" objects because they inherit from "Vehicle."

In essence, OOP helps you model and organize your code in a way that mirrors real-world objects and their relationships. It promotes code reusability, maintainability, and flexibility by breaking down complex systems into smaller, manageable pieces (objects) that can interact with each other in a structured manner.