Java solid principles

S.O.L.I.D. principle

The Single-responsibility principle: "There should never be more than one reason for a class to change."[5] In other words, every class should have only one responsibility.[6]

The Open–closed principle: "software entities ... should be open for extension, but closed for modification."[7]

The 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.[8]

The Interface segregation principle: "many client-specific interfaces are better than one general-purpose interface."[9][4]

The Dependency inversion principle: "depend upon abstractions, [not] concretions."[10][4]

Similar codes

0 vote131 views1 answer
Java pair class
Java
0 vote141 views1 answer
What Is Spring Boot and What Are Its Main Features?
Java Spring
0 vote162 views3 answers
SetCookie("showPopupBannerBeta", 1, 1
Java
0 vote113 views1 answer
Javax.servlet.filter
Java
1 vote113 views1 answer
Containskey java complexity
Java
2 votes110 views1 answer
Rider find and replace
Java
6 votes141 views1 answer
Spigot get player from UUID
Java
0 vote147 views1 answer
Number output swing java
Java
0 vote160 views1 answer
Intellij set target bytecode version
Java
0 vote135 views1 answer
Javacal
Java