Object-Oriented Programming

The process of creating objects out of class is called instantiation.

The process of assigning similar objects/entities to object classes/entity type is known as classification.

Specialisation lattice has the constraints that a subclass can be a subclass of more than one class/subclass relationship.

This is the correct answer.

This is the correct answer. 

Object-Oriented Programming (OOP) was specifically designed to manage software complexity by organizing code into reusable objects with encapsulated data and behavior. OOP doesn't aim to increase complexity (which would be counterproductive) nor is it primarily about implementing procedures (that's procedural programming). The core philosophy of OOP is complexity management through abstraction, inheritance, and encapsulation.

Objects hide their internal implementation details from users through information hiding and abstraction. Users interact only through well-defined public interfaces without needing to understand internal complexity. This encapsulation allows internal changes without breaking client code.

Objects are viewed as black boxes because users interact through interfaces without seeing internal implementation. The black box metaphor encapsulates the OOP principle of information hiding - inputs go in, outputs come out, but internal processing remains invisible.

Message passing is how objects communicate in OOP - one object invokes another object's method. This indirect communication maintains encapsulation since objects don't directly access each other's internals. Message passing enables polymorphism and dynamic binding.

Encapsulation uses access specifiers (public, private, protected) to control access to class members. These keywords define visibility boundaries - public for external access, private for internal only, and protected for class hierarchy. Access specifiers are the primary tool for implementing encapsulation.

Inheritance allows a derived class to replicate features and properties from a base class, promoting code reuse. Option A (Abstraction) hides implementation details, Option C (Polymorphism) allows same interface different behaviors, and Option D (Data hiding) encapsulates private members - none describe 'replicating features'.

Derived classes can access both public and protected members of the base class. Public members are accessible everywhere, while protected members are accessible within the class and its derived classes. Private members are inaccessible to the derived class, making options A, B, and C incorrect.

Polymorphism allows objects of different types to respond to the same method call in different ways. Option B (Inheritance) is the mechanism enabling polymorphism but not the behavior itself. Abstraction (Option C) hides complexity, and Data Hiding (Option D) encapsulates private members.

Inheritance promotes code reusability by allowing derived classes to reuse existing code from base classes. Option B is false because inheritance is widely used. Option C is false - inheritance can improve efficiency through code reuse. Option D describes modularization or decomposition, not inheritance specifically.

Method overriding provides a different implementation of a method in the derived class, maintaining the same method signature. Option A (Overloading) is same method name with different parameters within the same class. Abstraction (Option C) and Data Hiding (Option D) are different OOP concepts.