SOLID design principles

Question 1

what are the solid principles

Answer 1

single responsibility
open closed
liskov's substitution
interface segregation
dependency inversion

they are design principles for OOP

Question 2

single responsibility

Answer 2

concept of a class doing one specific thing and not trying to do more than it should (high cohesion)

states that every module, class or function should have responsibility over a single part of the functionaility and that responsibility should be entirely encapsulated by that class

Question 3

monster/god class

Answer 3

high cohesion - i.e. class is doing too much

Question 4

open closed

Answer 4

software entities should be open for extension by closed for modification. can allow behavior to be extended without modifying existing code

add new code without having to change to existing code

Question 5

Liskov substitution

Answer 5

ensuring that inheritance is used correctly

Question 6

interface segregation

Answer 6

clients should not be forced to depend on methods that they do not use. devs should favor thing interfaces

Question 7

dependency inversion

Answer 7

The Dependency Inversion principle states that our classes should depend upon interfaces or abstract classes instead of concrete classes and functions.