In the previous article, we gained an intuitive understanding of classes and their role in solving real problems through software. Although this concept is essential in object-oriented programming, classes are only specifications and are not executed when a program is run. In short, a class is only the blueprint, not the house: It is the house that provides the shelter, not the blueprint. In this article, we will explore objects, the actionable realization of classes in software, as well as provide a bit of a back-story to the original introduction of classes the object-oriented paradigm into the world of software engineering. These two topics will allow us to finally move into the world of classes and objects in Java.

Before we reach that point, though, we must answer a simple question: What is an object?

Source: DZone