User:Yamau6809/sandbox

This is the user sandbox of Yamau6809. A user sandbox is a subpage of the user's user page. It serves as a testing spot and page development space for the user and is not an encyclopedia article. Create or edit your own sandbox here.

Other sandboxes: Main sandbox | Template sandbox

Finished writing a draft article? Are you ready to request review of it by an experienced editor for possible inclusion in Wikipedia? Submit your draft for review!

{Solid 主義} コンピュータ・プログラミングにおいて、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.

References

^ “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.
^ “Getting a SOLID start.”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.
^ ^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.
^ “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.
^ ^a ^b “Design Principles and Design Patterns”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.

Category:Software design Category:Object-oriented programming

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

[ub-old-web-solid-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.

[ub-solid-2] “Getting a SOLID start.”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.

[metz-presentation-2009-3] “SOLID Object-Oriented Design”, Sandi Metz (Duke University), Talk given at the 2009 Gotham Ruby Conference in May, 2009. Last verified 2009-01-15.

[schmitz-presentation-2009-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.

[martin-design-principles-5] “Design Principles and Design Patterns”, Robert C. Martin (“Uncle Bob”), objectmentor.com. Last verified 2009-01-14.

[1]

[2]

[3]

[4]

[5]

User:Yamau6809/sandbox

Overview

See also

Basic concepts and related topics

Design and development principles

References