SOLID (object-oriented design)

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In computer programming, SOLID (Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion) is a mnemonic acronym introduced by Michael Feathers for the "first five principles" named by Robert C. Martin[1][2] in the early 2000s[3] that stands for five basic principles of object-oriented programming and design. The principles, when applied together, intend to make it more likely that a programmer will create a system that is easy to maintain and extend over time.[3] The principles of SOLID are guidelines that can be applied while working on software to remove code smells by causing the programmer to refactor the software's source code until it is both legible and extensible. It is part of an overall strategy of agile and adaptive programming.[3]

Overview[edit]

Initial Stands for
(acronym)
Concept
S SRP [4]
Single responsibility principle
a class should have only a single responsibility (i.e. only one potential change in the software's specification should be able to affect the specification of the class)
O OCP [5]
Open/closed principle
“software entities … should be open for extension, but closed for modification.”
L LSP [6]
Liskov substitution principle
“objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.” See also design by contract.
I ISP [7]
Interface segregation principle
“many client-specific interfaces are better than one general-purpose interface.”[8]
D DIP [9]
Dependency inversion principle
one should “Depend upon Abstractions. Do not depend upon concretions.”[8]
Dependency injection is one method of following this principle.

See also[edit]

Basic concepts and related topics[edit]

Design and development principles[edit]

References[edit]

  1. ^ “Principles Of OOD”, Robert C. Martin (“Uncle BOB”), butunclebob.com, Last verified 2009-01-14, unreachable 2014-05-08. (Note the “first five principles”, though the acronym is not used in this article.) Dates back to at least 2003.
  2. ^ “Getting a SOLID start.”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2013-08-19.
  3. ^ a b c “SOLID Object-Oriented Design”, Sandi Metz (Duke University), Talk given at the 2009 Gotham Ruby Conference in May, 2009. Last verified 2009-01-15.
  4. ^ "Single Responsibility Principle". 
  5. ^ "Open/Closed Principle". 
  6. ^ "Liskov Substitution Principle". 
  7. ^ "Interface Segregation Principle". 
  8. ^ a b “Design Principles and Design Patterns”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.
  9. ^ "Dependency Inversion Principle".