Software Engineering

Question 1

What are the 5 principles of SOLID

Answer 1

Single responsibility
Open-closed
Liskov substitution
Interface segregation
Dependency inversion

Question 2

Single responsibility principle

Answer 2

SOLID principle described by:

an object should have only a single responsibility.

Question 3

Open/closed principle

Answer 3

SOLID principle described by:

“software entities … should be open for extension, but closed for modification”.

Question 4

Liskov substitution principle

Answer 4

SOLID principle described by:
“objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program”. See also ‘design by contract’.

Question 5

Interface segregation principle

Answer 5

SOLID principle described by:

“many client specific interfaces are better than one general purpose interface.”

Question 6

Dependency inversion principle

Answer 6

SOLID principle described by:
one should “Depend upon Abstractions. Do not depend upon concretions.” Dependency injection is one method of following this principle.

Question 7

What does GRASP stand for?

Answer 7

General Responsibility Assignment Software Patterns (or Principles)

Question 8

The different patterns and principles used in GRASP

Answer 8

1. Controller
2. Creator
3. Indirection
4. Information Expert
5. High Cohesion
6. Low Coupling
7. Polymorphism
8. Protected Variations
9. Pure Fabrication