OOP

Question 1

Abstraction

Answer 1

Abstraction is a model of a real-world object or phenomenon,
limited to a specific context, which represents all details relevant to this context with high accuracy and omits all the rest.

Question 2

Encapsulation

Answer 2

Encapsulation is the ability of an object to hide parts of its state and behaviors from other objects, exposing only a limited interface to the rest of the program.

Question 3

Inheritance

Answer 3

Inheritance is the ability to build new classes on top of existing ones. The main benefit of inheritance is code reuse.

Question 4

Polymorphism

Answer 4

Polymorphism is the ability of a program to detect the real class of an object and call its implementation even when its real type is unknown in the current context.

Question 5

Solid - S

Answer 5

Single Responsibility Principle
A class should have just one reason to change.

Question 6

Solid - O

Answer 6

Open/Closed Principle
Classes should be open for extension but closed for
modification.

Question 7

Solid - L

Answer 7

Liskov Substitution Principle
When extending a class, remember that you should be
able to pass objects of the subclass in place of objects of the parent class without breaking the client code.

Question 8

Solid - I

Answer 8

Interface Segregation Principle
Clients shouldn’t be forced to depend on methods they
do not use.

Question 9

Solid - D

Answer 9

Dependency Inversion Principle
High-level classes shouldn’t depend on low-level classes. Both should depend on abstractions. Abstractions shouldn’t depend on details. Details should depend on abstractions.