Design Priciples

Question 1

S (in SOLID)

Answer 1

-Single Responsibility-

Class has ownership over only one thing, and everything needed to manage that is in the class

Question 2

O (in SOLID)

Answer 2

-Open/Closed Principle-

Open for extension, closed for modification. If you want to make a class that overrides a parent in some way that’s ok, but you shouldn’t be able to fundamentally change that parent on the fly.

Question 3

L (in SOLID)

Answer 3

-Liskov Substitution-

If S is a subtype of T, then an object of S should be able to fill in everywhere T fills. If you’re extending a class it has to do everything the parent could do.

Question 4

Recursion

Answer 4

Instructions that reference the “same” procedure as part of it’s own procedure.

Question 5

I (in SOLID)

Answer 5

-Interface segmentation-

Don’t depend on interfaces they don’t use. You’re better off using many small interface than one big one,where not everything is used.

Question 6

D (in SOLID)

Answer 6

-Dependency Inversion-

High level abstractions should not depend on low level implementations.

Question 7

Encapsulation

Answer 7

The data/internals of a class are hidden to others

Question 8

Abstraction

Answer 8

Develop for function not for implementation. Decompose into smaller components.

Question 9

Inheritance

Answer 9

Child classes take on properties/data from their parents

Question 10

Polymorphism

Answer 10

Two related classes can implement the same function, but have different results/implementations