SOLID principles

Solid principles were promoted by which of these?

• Robert Hook

• Robert Rich

• Robert Martin

• Robert Downy

The SOLID acronym in Solid principles was introduced by

• Micheal Feathers

• Micheal White

• Micheal Father

• Micheal Brown

Concerning the solid principle which of these is odd?

• Dependency Inversion Principle

• Liskov Substitution Principle

• Interface Segregation Principle

• Single Reconstruction Principle

A specific form of decoupling where conventional dependency relationships established from high-level, policy-setting modules to low-level, dependency modules are reversed for the purpose of rendering high-level modules independent of the low-level module implementation details.

• High-level modules should not depend on low-level modules; both should depend on abstractions

• Abstractions should not depend on details; details should depend on abstractions

• What is the Open/Closed Principle?

• What are the five principles?

• What is the Liskov Substitution Principle?

• What is the Single Responsibility Principle?

• What is the Dependency Inversion Principle?

...is the notion that "objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program"

Liskov's notion of a behavioral subtype defines a notion of substitutability for mutable objects; that is, if S is a subtype of T, then objects of type T in a program may be replaced with objects of type S without altering any of the desirable properties of that program (e.g., correctness)

• What is the Open/Closed Principle?

• What are the five principles?

• What is the Liskov Substitution Principle?

• What is the Single Responsibility Principle?

• What is the Dependency Inversion Principle?

"software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification"[Bertrand Meyer-1988]. That is, such an entity can allow its behavior to be modified without altering its source code.

• What is the Open/Closed Principle?

• What are the five principles?

• What is the Liskov Substitution Principle?

• What is the Single Responsibility Principle?

• What is the Dependency Inversion Principle?

• Classes that implement interfaces should not be forced to implement methods they do not use. Another way of putting it is: use small interfaces, not fat ones

• Focuses on the cohesiveness of interfaces with respect to the implementors that use them

• Keep each implementation independent of interfaces that they do not use. If you need to change one interface, you shouldn't need to change the other

• What is the Open/Closed Principle?

• What is the Interface Segregation Principle?

• What is the Liskov Substitution Principle?

• What is the Single Responsibility Principle?

• What is the Dependency Inversion Principle?

Every object should have a single responsibility, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility.

• What is the Open/Closed Principle?

• What is the Interface Segregation Principle?

• What is the Liskov Substitution Principle?

• What is the Single Responsibility Principle?

• What is the Dependency Inversion Principle?

• Contravariance of method arguments in the subtype

• Covariance of return types in the subtype

• No new exceptions should be thrown by methods of the subtype, except where those exceptions are themselves subtypes of exceptions thrown by the methods of the supertype.

Is it a definition of the standard signature requirements of the Liskov Substitution Principle?

• True

• False

In it's simplest form, covariance, contravariance and invariance describe type "assignment compatibility":

• Covariant: class A is a covariant of class B when class A is a subtype of class B - class of type A can be assigned to an variable of class type B. Use out keyword in c# to indicate covariance. Often used in return type assignment compatibility.

• Contravariant: class A is a contravariant of class B when class A is a supertype of class B - class of type B can be assigned to a variable of class type A. Use in keyword in c# to indicate contravariance. Often used in method parameter assignment compatibility.

• Invariant: class A is neither a subtype nor a supertype of Class B - no assignment can be made between the two types.

→ Describe the Single Responsibility Principle.

• True

• False