In the real world everything (including you and me) exist in the form of objects. These objects are identified by the system analyst upon request of a customer (who actually uses services of objects) and handed-over to the designer. The designer in turn creates classes which group all those objects exhibiting similar characteristics and behaviors into a single unit. These units are then passed to programmers, who implement objects’s framework given by the designer. Thus, objects move from the customer to the programmer.

Programmers create objects using its framework. These objects work in a collaborative and cooperative manner to produce the required output. These software objects now start moving from programmers to test engineers, and finally to the customer, who is the actual user of these objects, to solve real-world problems. To realize this effective migration of objects from one person to another, these must be an effective means of communication among all those involved in the development of a software project. They need to communicate their ideas in terms of objects. That is, system analyst delivers requirement specification in terms of objects, software designer delivers design specification in terms of classes (object groups). And even programmers need to express their ideas or write code in terms of objects. Hence, the demand for an object oriented requirements specification (OORS), object oriented analysis (OOA). Object oriented design (OOD), and object-oriented programming (OOP) has grown tremendously.

C++ is an object-oriented language that a C programmer can appreciate, especially who is an early-age assembly language programmer. C++, was first oriented towards execution performance and then towards flexibility. Most of the features which C++ adds to C involve no runtime overhead; few that do can be avoided by the efficiency conscious programmers.