1 The Evolution of Object-Oriented Programming (OOP)

Object-oriented programming (OOP) has undergone a fascinating journey since its early
beginnings in the 1960s. Here's a glimpse into its evolution:

1.1 Early Beginnings (1960s):

 Simula: The first object-oriented language, developed in 1967 by Ole-Johan Dahl and
Kristen Nygaard. It introduced concepts like classes, objects, inheritance, and
polymorphism, laying the foundation for OOP.
 Challenges: Simula was primarily used for simulation purposes and wasn't widely
adopted, partly due to its limited implementation and slow performance.

1.2 Growth and Refinement (1970s-1980s):

 Smalltalk: Developed at Xerox PARC in the 1970s, Smalltalk was the first fully
object-oriented language, popularizing many key OOP concepts. It emphasized
simplicity, elegance, and a graphical user interface (GUI).
 C++: Developed by Bjarne Stroustrup in the early 1980s, C++ combined the power of
C with object-oriented features, making OOP accessible to a wider audience. It quickly
became popular for developing complex systems.
 Other languages: OOP concepts inspired various languages like Eiffel, Objective-C
(used in early Apple OS), and CLOS (Common Lisp Object System).

1.3 Widespread Adoption and Standardization (1990s-2000s):

 Java: Released in 1995, Java offered a platform-independent OOP language, further
boosting OOP adoption. Its focus on security and portability made it ideal for web and
enterprise applications.
 Standardization: The Object Management Group (OMG) standardized interfaces and
specifications for object-oriented technologies, promoting interoperability and
development tools.
 Web development: OOP played a crucial role in web development with frameworks
like Java Server Pages (JSP) and Ruby on Rails, enabling dynamic and interactive web
applications.
Modern Era (2010s-present):
 Evolution of existing languages: Languages like C++ (version 11 & 14) and Java
(versions 7 & 8) added features like lambda expressions and functional programming
capabilities, adapting to modern development needs.
 New paradigms: Functional programming gained traction, influencing object-oriented
design through concepts like immutability and functional interfaces.
 Micro-services architecture: OOP principles are leveraged in micro-services
architecture for modular and scalable systems, often using languages like Kotlin and
Scala.

Page 1 of 7
1.4 Future of OOP:
 OOP remains a fundamental paradigm for many developers, but other paradigms like
functional programming are gaining ground.
 The future might see a hybrid approach, combining object-oriented and functional
paradigms based on specific project requirements.
 OOP principles like encapsulation, abstraction, and polymorphism will likely remain
relevant, but their implementation may evolve with new technologies and trends.

1.5 Key Takeaways:

 OOP has come a long way, evolving from niche applications to powering complex
systems across various domains.
 While newer paradigms emerge, OOP's core principles remain valuable and are
adaptable to changing technologies.
 The future of OOP lies in its ability to integrate with other paradigms and adapt to meet
new challenges in software development.

1.6 Why do we need object-oriented programming?

 To make the development and maintenance of projects more effortless.
 To provide the feature of data hiding that is good for security concerns.
 We can solve real-world problems if we are using object-oriented programming.
 It ensures code reusability.
 It lets us write generic code: which will work with a range of data, so we don’t have to
write basic stuff over and over again.

Page 2 of 7
2 Introduction of Object Oriented Programming
As the name suggests, Object-Oriented Programming or OOPs refers to languages that use
objects in programming. Object-oriented programming aims to implement real-world entities
like inheritance, hiding, polymorphism, etc in programming. The main aim of OOP is to bind
together the data and the functions that operate on them so that no other part of the code can
access this data except that function.
OOPs Concepts:
 Class
 Objects
 Data Abstraction
 Encapsulation
 Inheritance
 Polymorphism
 Dynamic Binding
 Message Passing

2.1 Class:
 “A class is a user-defined data type”.
 It consists of data members and member functions, which can be accessed and used
by creating an instance of that class.
 It represents the set of properties or methods that are common to all objects of one
type.
 “A class is like a blueprint for an object.”

For Example: Consider the Class of Cars. There may be many cars with different names and
brands but all of them will share some common properties like all of them will have 4 wheels,
Speed Limit, Mileage range, etc. So here, Car is the class, and wheels, speed limits, mileage
are their properties.

2.2 Object:
 It is a basic unit of Object-Oriented Programming and represents the real-life
entities.
 An Object is an instance of a Class.

 When a class is defined, no memory is allocated but when it is instantiated (i.e. an

object is created) memory is allocated.
 An object has an identity, state, and behavior.
 Each object contains data and code to manipulate the data.
 Objects can interact without having to know details of each other’s data or code, it is
sufficient to know the type of message accepted and type of response returned by the
objects.

Page 3 of 7
 For example “Dog” is a real-life Object, which has some characteristics like color, Breed,
Bark, Sleep, and Eats.

2.3 Data Abstraction:

Data abstraction is one of the most essential and important features of object-oriented
programming.
“Data abstraction refers to providing only essential information about the data to the
outside world, hiding the background details or implementation.”
Consider a real-life example of a man driving a car. The man only knows that pressing the
accelerators will increase the speed of the car or applying brakes will stop the car, but he does
not know about how on pressing the accelerator the speed is increasing, he does not know
about the inner mechanism of the car or the implementation of the accelerator, brakes, etc in
the car. This is what abstraction is.

2.4 Encapsulation:
“Encapsulation is defined as the wrapping up of data under a single unit. It is the
mechanism that binds together code and the data it manipulates.”
In Encapsulation, the variables or data of a class are hidden from any other class and can be
accessed only through any member function of their class in which they are declared. As in
encapsulation, the data in a class is hidden from other classes, so it is also known as data-
hiding.

Page 4 of 7
 Consider a real-life example of encapsulation, in a company; there are different sections like
the accounts section, finance section, sales section, etc. The finance section handles all the
financial transactions and keeps records of all the data related to finance. Similarly, the sales
section handles all the sales-related activities and keeps records of all the sales. Now there may
arise a situation when for some reason an official from the finance section needs all the data
about sales in a particular month. In this case, he is not allowed to directly access the data of
the sales section. He will first have to contact some other officer in the sales section and then
request him to give the particular data. This is what encapsulation is. Here the data of the sales
section and the employees that can manipulate them are wrapped under a single name “sales
section”.

2.5 Inheritance:
Inheritance is an important pillar of OOP(Object-Oriented Programming).
“The capability of a class to derive properties and characteristics from another class is
called Inheritance.”
When we write a class, we inherit properties from other classes. So when we create a class, we
do not need to write all the properties and functions again and again, as these can be inherited
from another class that possesses it. Inheritance allows the user to reuse the code whenever
possible and reduce its redundancy.

Page 5 of 7
2.6 Polymorphism:
“The word polymorphism means having many forms. In simple words, we can define
polymorphism as the ability of a message to be displayed in more than one form.”
For example, A person at the same time can have different characteristics. Like a man at the
same time is a father, a husband, an employee. So the same person posses different behavior in
different situations. This is called polymorphism.

2.7 Dynamic Binding:

 In dynamic binding, the code to be executed in response to the function call is decided
at runtime.
 Dynamic binding means that the code associated with a given procedure call is not
known until the time of the call at run time.
Dynamic Method Binding One of the main advantages of inheritance is that some derived class
D has all the members of its base class B. Once D is not hiding any of the public members of B,
then an object of D can represent B in any context where a B could be used. This feature is
known as subtype polymorphism.

2.8 Message Passing:

It is a form of communication used in object-oriented programming as well as parallel
programming.
Objects communicate with one another by sending and receiving information to each other. A
message for an object is a request for execution of a procedure and therefore will invoke a
function in the receiving object that generates the desired results. Message passing involves
specifying the name of the object, the name of the function, and the information to be sent.

Page 6 of 7
3 Benefits of OOP:
 Modularization: Breaks down complex problems into smaller, manageable objects.
 Code reusability: Inheritance and polymorphism promote code reuse, reducing
development time and effort.
 Maintainability: Encapsulation makes code easier to understand and modify without
unintended side effects.
 Flexibility: Polymorphism allows for dynamic behavior and adaptability to changing
requirements.
 Real-world modeling: Objects naturally map to real-world entities, making code more
intuitive and easier to reason about.

4 Limitations:
 Complexity: Can lead to complex object hierarchies and intricate
interactions, potentially making code harder to understand and debug.
 Overuse: Over-reliance on inheritance and tightly coupled objects can make code
inflexible and difficult to change.

Page 7 of 7