Keep calm and S.O.L.I.D
On winter 2012 I had the chance to attend a talk by Robert.C.Martin(aka Uncle Bob) in Dublin. I think it was awesome. Uncle Bob is the author of Clean Code(I’ve got it signed by him in person :p) and also is a very influential person in the software industry.
I’ve been thinking to write something about some of the contributions he did to the industry and post it here on my blog since that talk.
One of the last things he said to us, was to read as much as we could…
Before starting to write this post I thought about those words for a while…
I think that it was a great advice.
Nobody negates that real experience is probably best, but reading books is also very important.
They carry the experiences of persons who were there before and also the rules and the principles those persons discovered and documented on their way.
Don’t get me wrong, following rules and principles strictly does not always guarantee success(“the world keeps changing”) but understanding them can be of great help when facing great challenges.
So finally I decided to write this post about one of the biggest contributions of Uncle Bob to the world of object oriented programming, and that is the S.O.L.I.D principles.
Single Responsibility Principle
If we have a class that has multiple responsibilities/features/reasons to change; Modifications done to it carry the risk of affecting other parts of the class(other responsibilities/features/reasons to change).
In other words: Classes that do more than one thing are difficult to maintain.
SRP says: “A class should have only one reason to change”.
Lets have a look at an example:
As you can see, it is a clear example of a class with multiple reasons to change:
- Future business requirements might involve us changing the calculate method(e.g different metrics)
- Future business requirements might involve us changing the way the results are saved.
- Future business requirements might involve us changing the way the training plan is created based in the BMI.
We don’t want all the above mentioned requirement changes to affect the class. If we don’t seek for granularity at an early stage of development, we will very easily end up with difficult to maintain software.
What we need to do is think just on the one unique goal that the class will have.
Also we can think in what the class definitely will not do, so we can distinguish the other reasons to change that should not be there. Follow this way of thinking when fixing a violation of the SRP and it will help you detect the classes that you need to extract:
Open Close principle
The motivation behind the Open Close principle is to extend/change behaviour without modifying the existing code. This principle says:
“modules should be open for extension but close for modification”.
You probably think, that this sounds very contradictory, but in many OO programming languages like Java, there are mechanisms that will allow you to do this.
One of those mechanisms is polymorphism. By defining abstract functions/methods
Let’s have a look first at a violation of the open closed principle:
In the above code, if a new requirement arrives asking us to make some other type of meal different than veg and non veg, the class will need to be modified. The given above example is not maintainable.
Let’s see how to use polymorphism to remove that conditional logic and improve the solution:
As you can see the solution is more flexible, now it is easier to maintain and also we got rid of an evil flag that at long term will cause only problems when manipulating it. The class Meal that contains sensitive methods is open for extension but closed for modification.
The OCP principle is very powerful but we also must have in mind that by adding levels of abstraction( as alternative you can also think about Composition versus inheritance), we also increase the complexity and it is very important to understand that this principle should be applied only in those places where there is more likely to be often requirement changes.
Liskov substitution principle
This principle is concern about sub-classes classes replacing the behaviour of their base class.
If this occurs, the new classes can produce undesired effects when they are used/called in other parts of the program.
Liskov’s Substitution Principle states that if a client is calling a base class, then the reference to the base class should be able to be replaced with a derived class without affecting the functionality of base class.
Lets have a look at an example of violation of this principle:
Also a wild duck can quack and swim. But what about Duck toys?
As you see, some duck toys require batteries and also they don’t really quack, they just play a sound. Even if there are no compilation errors and it looks tempting to include duck toy in this inheritance chain, this is clear violation of Liskov’s substitution principle. The reason is that if a client instantiates the base class, the derived class DuckToy, is not capable of replacing it because the functionality is being affected.
One solution in this case could be to have a separate class by its own, to represent the duck toy.
Interface Segregation Principle
This is a very simple to understand principle, it says that clients should not be forced to implement interfaces they don’t use Just that simple. Have a look at a violation of this principle:
That was horrible uh? So there are many ways you can avoid this.
One example could be to combine specific interfaces as per needed:
That makes sense, we could say that a dog is a Runner and a Swimmer but definitely not a flyer. Using interfaces that have less methods help us avoid violating the Interface segregation principle.
Dependency Inversion Principle
This principle says “Don’t depend on anything concrete, depend only on things that are abstract.” So make sure that all of your dependencies point at things that are abstract. This will bring safety to your code and also make it flexible. Probably you are thinking that this principle, can be a bit radical; but obiously, in real following it always strictly is just very difficult(maybe even impossible). A tip that you can use to verify that you are following this principle when you call a function, is to program to the interface and not the realization.
One great example of this principle in practice is the Template design pattern. Lets have a look first at a common violation of the principle:
The above example is a badly coded class that makes 2 types of pizzas… There are many bad things in this piece of code, but I will just focus on the violation of the principle we are discussing. Since every call done to the pizza object is to a concrete method, what we get is something very rigid and inflexible.
Every pizza has some ingredients that are mandatory, such as the base, tomato, cheese and oregano,but the rest are optional, so: why do we care about making calls to concrete methods, to set those extra ingredients, if is not even our concern?
In the following snippet of code, a template method is introduced to abstract the optional part and let sub-classes implement them.
The S.O.L.I.D principles, were identified by Robert C.Martin, but the Acronym was created by Michael Feathers in the year 2000, today they are well known in the world of object oriented software and many there is plenty literature on books and internet about them.
Just for the end of this post I would like to share with you a great podcast interview that I found on the web, were Uncle Bob, explains S.O.L.I.D in detail.
Originally published at http://javing.blogspot.com/2013/09/keep-calm-and-solid.html
