Jump to content

SOLID: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
attribute the SOLID acronym correctly to Michael Feathers.
Line 1: Line 1:
In [[computer programming]], '''SOLID''' ('''Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion''') is a [[mnemonic]] [[acronym]] introduced by [[Robert C. Martin]]<ref name="ub-old-web-solid">[http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod “Principles Of OOD”], [[Robert C. Martin]] (“Uncle Bob”), butunclebob.com, Last verified 2009-01-14. (Note the “first five principles”, though the acronym is not used in this article.) Dates back to at least 2003.</ref><ref name="ub-solid">[http://blog.objectmentor.com/articles/2009/02/12/getting-a-solid-start “Getting a SOLID start.”], [[Robert C. Martin]] (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.</ref> in the early 2000s<ref name="metz-presentation-2009">[http://www.confreaks.com/videos/240-goruco2009-solid-object-oriented-design “SOLID Object-Oriented Design”], Sandi Metz (Duke University), Talk given at the 2009 Gotham [[Ruby (programming language)|Ruby]] Conference in May, 2009. Last verified 2009-01-15.</ref> that stands for five basic principles of [[object-oriented programming]] and [[object-oriented design|design]]. The principles when applied together intend to make it more likely that a [[computer programmer|programmer]] will create a system that is easy to [[Software maintenance|maintain]] and extend over time.<ref name="metz-presentation-2009"/> The principles of SOLID are guidelines that can be applied while working on software to remove [[code smell]]s by causing the programmer to [[code refactoring|refactor]] the software's [[source code]] until it is both legible and extensible. It is typically used with [[test-driven development]], and is part of an overall strategy of [[agile software development|agile]] and [[Adaptive Software Development|adaptive programming]].<ref name="metz-presentation-2009"/><ref name="schmitz-presentation-2009">[http://nonprofits.accesscomm.ca/springseminar/nug/Introducing_SOLID.ppt “Introducing SOLID Object-Oriented Design Principles and Microsoft Unity”], Uwe Schmitz, Presentation given at the Regina .NET User Group in May, 2009. Last verified 2009-01-14.</ref>
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" identified by [[Robert C. Martin]]<ref name="ub-old-web-solid">[http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod “Principles Of OOD”], [[Robert C. Martin]] (“Uncle Bob”), butunclebob.com, Last verified 2009-01-14. (Note the “first five principles”, though the acronym is not used in this article.) Dates back to at least 2003.</ref><ref name="ub-solid">[http://blog.objectmentor.com/articles/2009/02/12/getting-a-solid-start “Getting a SOLID start.”], [[Robert C. Martin]] (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.</ref> in the early 2000s<ref name="metz-presentation-2009">[http://www.confreaks.com/videos/240-goruco2009-solid-object-oriented-design “SOLID Object-Oriented Design”], Sandi Metz (Duke University), Talk given at the 2009 Gotham [[Ruby (programming language)|Ruby]] Conference in May, 2009. Last verified 2009-01-15.</ref> that stands for five basic principles of [[object-oriented programming]] and [[object-oriented design|design]]. The principles when applied together intend to make it more likely that a [[computer programmer|programmer]] will create a system that is easy to [[Software maintenance|maintain]] and extend over time.<ref name="metz-presentation-2009"/> The principles of SOLID are guidelines that can be applied while working on software to remove [[code smell]]s by causing the programmer to [[code refactoring|refactor]] the software's [[source code]] until it is both legible and extensible. It is typically used with [[test-driven development]], and is part of an overall strategy of [[agile software development|agile]] and [[Adaptive Software Development|adaptive programming]].<ref name="metz-presentation-2009"/><ref name="schmitz-presentation-2009">[http://nonprofits.accesscomm.ca/springseminar/nug/Introducing_SOLID.ppt “Introducing SOLID Object-Oriented Design Principles and Microsoft Unity”], Uwe Schmitz, Presentation given at the Regina .NET User Group in May, 2009. Last verified 2009-01-14.</ref>


==Overview==
==Overview==

Revision as of 13:48, 13 September 2012

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" identified 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 typically used with test-driven development, and is part of an overall strategy of agile and adaptive programming.[3][4]

Overview

Initial Stands for
(acronym)		 Concept
S SRP
Single responsibility principle
an object should have only a single responsibility.
O OCP
Open/closed principle
“software entities … should be open for extension, but closed for modification”.
L LSP
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
Interface segregation principle
“many client specific interfaces are better than one general purpose interface.”[5]
D DIP
Dependency inversion principle
one should “Depend upon Abstractions. Do not depend upon concretions.”[5]
Dependency injection is one method of following this principle.

See also

Design and development principles

References

  1. ^ “Principles Of OOD”, Robert C. Martin (“Uncle Bob”), butunclebob.com, Last verified 2009-01-14. (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 2009-01-14.
  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. ^ “Introducing SOLID Object-Oriented Design Principles and Microsoft Unity”, Uwe Schmitz, Presentation given at the Regina .NET User Group in May, 2009. Last verified 2009-01-14.
  5. ^ a b “Design Principles and Design Patterns”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.
Stub icon

This computer-programming-related article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=SOLID&oldid=512179909"