SOLID Principles: Difference between revisions
New page for SOLID, needs more detail |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''SOLID''' is an acronym for five design principles in [[Object-Oriented Programming]] to make the software more readable, extensible, and maintainable. The '''SOLID Principles''' are as follows: | '''SOLID''' is an acronym for five design principles in [[Object-oriented programming|Object-Oriented Programming]] to make the software more readable, extensible, and maintainable. The '''SOLID Principles''' are as follows: | ||
:'''<u>S</u>ingle Responsibility Principle''' - a class should only have a single responsibility. | :'''<u>S</u>ingle Responsibility Principle''' - a class should only have a single responsibility. | ||
| Line 11: | Line 11: | ||
[[Category:Object-Oriented Programming]] | [[Category:Object-Oriented Programming]] | ||
[[Category:Programming Principles]] | |||
Latest revision as of 16:54, 14 March 2021
SOLID is an acronym for five design principles in Object-Oriented Programming to make the software more readable, extensible, and maintainable. The SOLID Principles are as follows:
- Single Responsibility Principle - a class should only have a single responsibility.
- Open/Closed Principle - software should be open for extension but closed for modification.
- Liskov Substitution Principle - "objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program."
- Interface Segregation Principle - "many client-specific interfaces are better than one general-purpose interface."
- Dependency Inversion Principle - one should "depend upon abstractions, [not] concretions."
SOLID Principles in G
More to Come